Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

5/20/2009
05:11 PM
Sara Peters
Sara Peters
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Ruminating on CSI SX

Citizens of the Information Security Nation, to you I say Classify and inventory your data and assets! Tedium? Odium? Delirium? Yes, probably all three. But worth the trouble.

Citizens of the Information Security Nation, to you I say Classify and inventory your data and assets!

Tedium? Odium? Delirium? Yes, probably all three. But worth the trouble.Yesterday we wrapped up CSI SX, and learned about many far more exciting topics like the security challenges of Web 2.0, virtualization, cloud computing and more. Yet, at the root of nearly all the solutions to these thrilling challenges was the humble act of data classification and inventory--knowing what your data is, and where it is.

For example, we learned that the PCI Council continues to keep mum on the topic virtualization, and whether or not the technology intrinsicly violates a few requirements of the PCI DSS. The Council is leaving that issue to the discretion of the auditors; and it's the security manager's job to convince those auditors that your data center was virtualized in an intelligent, careful way that properly secures all payment card data... How can you prove that unless you've identified all that payment card data and know precisely where it all resides?

We learned that putting data in the cloud doesn't automatically transfer your e-discovery responsibilities to the cloud provider. So when the courts come a-lookin' for data--possibly including metadata and logs--it's your job to hand it over. How can you hand it over if you don't know where it is...and if it's not in your possession?

Aye, there's the rub.* The heart of the thing, again, is in inventory. The lesson here is that your inability to provide that data may be a reason to either keep out of the cloud entirely, or make an airtight service agreement with the cloud provider, so that you know precisely what liability, indemnity, litigation costs, etc. they intend to shoulder.

Then of course there's the possibility (even probability) that you're spending too much on security. What? Blasphemy! Bite your tongue, woman, les the CEO should hear you and slash my budget to the quick.

No, really. Why give everything in your business the security works? Not all those assets are all that important.

Yet, if you've thoroughly classified and inventoried all that data, you can isolate it and partition the royal jewels from the Cracker Jack decoder rings, then apply the security measures accordingly.

Many more thought-provoking topics were discussed during CSI SX--synergistic security, the questionable value of secure software development, the absence of logic, the effects of long times-to-fix, etc. I'll catch you up on them anon, once I'm finished with my trek through the Interop exhibition hall.

* I've recently been prone to quote from Hamlet's "To be or not to be" soliloquy in which he contemplates suicide. But don't let that worry you. I've just been running a bit Shakespearean lately. Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12949
PUBLISHED: 2019-06-25
In pfSense 2.4.4-p2 and 2.4.4-p3, if it is possible to trick an authenticated administrator into clicking on a button on a phishing page, an attacker can leverage XSS to upload arbitrary executable code, via diag_command.php and rrd_fetch_json.php (timePeriod parameter), to a server. Then, the remot...
CVE-2019-12957
PUBLISHED: 2019-06-25
In Xpdf 4.01.01, a buffer over-read could be triggered in FoFiType1C::convertToType1 in fofi/FoFiType1C.cc when the index number is larger than the charset array bounds. It can, for example, be triggered by sending a crafted PDF document to the pdftops tool. It allows an attacker to use a crafted pd...
CVE-2019-12958
PUBLISHED: 2019-06-25
In Xpdf 4.01.01, a heap-based buffer over-read could be triggered in FoFiType1C::convertToType0 in fofi/FoFiType1C.cc when it is trying to access the second privateDicts array element, because the privateDicts array has only one element allocated.
CVE-2019-12951
PUBLISHED: 2019-06-24
An issue was discovered in Mongoose before 6.15. The parse_mqtt() function in mg_mqtt.c has a critical heap-based buffer overflow.
CVE-2019-10689
PUBLISHED: 2019-06-24
VVX products using UCS software version 5.9.2 and earlier with Better Together over Ethernet Connector (BToE) application version 3.9.1 and earlier provides insufficient authentication between the BToE application and the BToE component, resulting in leakage of sensitive information.