Commentary

Need For Security Looming Larger In 2008

Hey, great news! Everyone's finally starting to take data security seriously. It only took what, countless thefts, misplaced laptops, unprotected networks, greedy employees, a lack of policies, and the threats of massive and costly legalities to get us all on board?

Hey, great news! Everyone's finally starting to take data security seriously. It only took what, countless thefts, misplaced laptops, unprotected networks, greedy employees, a lack of policies, and the threats of massive and costly legalities to get us all on board?


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Actually, I'm being sarcastic -- truth is not everyone's on board yet. But just about everyone's taking notice.

I know I'm going to be pointing out the big ol' elephant in the room here, but 2007 was not a good year for data protection and privacy. We started off in January with TJX's customer data debacle. Just recently, officials in Great Britain announced that the records of more than 3 million U.K. residents learning to drive vanished from a data warehouse here in the United States (the data actually went missing in May). Meanwhile, tucked between the other 10 months are countless more tales of misplaced or misappropriated data.

Thankfully, heads are starting to turn (probably because a bunch have started to roll), and the decision is coming down within many organizations: Security shouldn't be a tack-on or a side note. Even the typically fence-sitting senior execs, wary about any extra spending, are now starting to admit that the benefits of enacting security policies far exceed any headaches that might come with implementing and upholding them. Good thing, too -- the cost of data loss is skyrocketing: the average cost for a single missing customer record is around $200, and with records vanishing millions at a time, well you do the nauseating math.

It's just a little frustrating that its taken so many incidents to get people on board. Just like the farmer who closes the barn door after the cows are gone, folks are beginning to realize (in some cases a little too late) that there may be something to all this data security prevention stuff after all.

2008 is going to have to be the year where everyone pitches in to protect the company data. I'm not just talking about working late hours to implement software, either. I'm talking even doing something as simple as while you're walking down the hallway at the end of the day, jiggle the doorknobs of your co-worker's offices to make sure they're locked. Sounds stupid? Maybe -- but I prefer knowing my cows are safe in the barn for the night.

What will your company do to get a better handle on customer data in the coming year? Share your thoughts below.


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