Risk
12/20/2007
11:17 AM
Tom LaSusa
Tom LaSusa
Commentary
50%
50%

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?

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.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: nice one
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-1235
Published: 2015-04-19
The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in the HTML parser in Blink, as used in Google Chrome before 42.0.2311.90, allows remote attackers to bypass the Same Origin Policy via a crafted HTML document with an IFRAME element.

CVE-2015-1236
Published: 2015-04-19
The MediaElementAudioSourceNode::process function in modules/webaudio/MediaElementAudioSourceNode.cpp in the Web Audio API implementation in Blink, as used in Google Chrome before 42.0.2311.90, allows remote attackers to bypass the Same Origin Policy and obtain sensitive audio sample values via a cr...

CVE-2015-1237
Published: 2015-04-19
Use-after-free vulnerability in the RenderFrameImpl::OnMessageReceived function in content/renderer/render_frame_impl.cc in Google Chrome before 42.0.2311.90 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger renderer IPC messages ...

CVE-2015-1238
Published: 2015-04-19
Skia, as used in Google Chrome before 42.0.2311.90, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via unknown vectors.

CVE-2015-1240
Published: 2015-04-19
gpu/blink/webgraphicscontext3d_impl.cc in the WebGL implementation in Google Chrome before 42.0.2311.90 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted WebGL program that triggers a state inconsistency.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.