Risk
12/20/2007
11:17 AM
Tom LaSusa
Tom LaSusa
Commentary
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.