Commentary

Google Report: Spam, Security, User Support Are Trouble Spots For IT

Google's Enterprise folks released the results of a massive IT study that polled 575 CEOs, CIOs, and CTOs in large, multinational enterprises as well as small organizations. The results? Spam continues to be annoying. IT pros are having difficulty reaching security, compliance objectives. IT pros are spending too much time helping end users.

Google's Enterprise folks released the results of a massive IT study that polled 575 CEOs, CIOs, and CTOs in large, multinational enterprises as well as small organizations. The results? Spam continues to be annoying. IT pros are having difficulty reaching security, compliance objectives. IT pros are spending too much time helping end users.The results probably don't surprise anyone who works in an IT department. The poll looked specifically at messaging and drew six main conclusions based on the input of nearly 600 C-level types.

Everyone pretty much agrees that spam is a major issue. Every type of electronic communication increased in volume in 2007 compared with 2006. Unfortunately, the growth rate of spam jumped, too. The report reads, in part, "Based on data from Postini, data centers spam volume per user was up 57% in 2007 over 2006. What does this mean in real terms? It means that the average unprotected user would have received 36,000 spam messages in 2007, compared with 23,000 spam messages in 2006." That's a pretty hefty increase. How is your IT shop dealing with the volume?


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Even though I think the responsibility for security should be shared by the employee and IT, execs feel differently. They believe it's IT's burden to secure the enterprise and protect it from threats. The report says, "53% of all executives and messaging professionals surveyed indicated that they feel their IT department is the primary department responsible for communications security and compliance. Only 18% of survey participants felt that security and compliance accountability rests equally with IT as well as end-users." IT admins do need to be in charge of researching and enacting enterprise security, no doubt. But how does the end user not figure into the equation? If I leave my laptop sitting in a Starbucks, isn't it my fault, and not IT's? Making employees at least partly responsible for security should be discussed in every enterprise.

Whoever is responsible, the job is getting tougher every day. "The top challenges organizations face in meeting compliance goals are planning for disaster recovery, ensuring compliant business processes, preventing unintentional data leakage, and protecting internal systems from breach by hackers."

And it is taking up way too much IT time. "Time spent ensuring adherence to compliance procedures (46%), arranging system upgrades to enhance security (44%), and overcoming network delays or outages due to security breaches (42%) were all high on respondents' lists of concerns."

One thing that Google is predicting: the number of attacks is going to balance out. The bad news is that the attacks will be increasingly more complex and dangerous to your organization. "Businesses will be challenged to identify new and different types of malicious content as well as protect sensitive information against evolving social engineering techniques that circumvent security measures by manipulating or tricking users into disclosing or performing actions that divulge confidential data."

How are things in your shop? Similar? Completely different? Do you agree that things are going to get increasingly complex?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links