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

1/30/2013
02:28 PM
Wendy Nather
Wendy Nather
Commentary
50%
50%

Going Green With Your Ones And Zeros

For better security, use less data

I know what you’re thinking. "This is the same person who wrote 'Log All The Things,' right?" And of course everyone wants to do so because of Big Data. But there’s another angle to logging and monitoring, along with the rest of your enterprise data, and that’s what I’m calling the "principle of least use."

Your confidential data is radioactive. It contaminates any container it touches, whether it’s a file, database, or server. You can’t always keep track of it; you don’t necessarily know for sure where it flows, who’s accessing it, or what it’s used for. And regular data can become radioactive if it comes in contact with the confidential stuff. So to keep the contagion from spreading -- the liability plague, so to speak -- you’re better off keeping that confidential data in as few places and states as possible.

Your legal department will tell you that the less data you keep, the less is discoverable in a lawsuit. The less you store, the less can be deemed responsive to a public information act request. This is why some government agencies can have very short email retention policies, for example. And most of you already know that the fewer places you keep credit-card data, the fewer systems are in scope for PCI compliance. Overall, the less you have, the less you need to protect.

But it’s not just about storage or transmission; it’s about use. For the sake of privacy, applications should not collect or process any personally identifying information that they don’t have to. Sometimes architects want to add all sorts of things to the data model because "you never know if you might need it later." Or they’re going to import data that’s being used for a different purpose, and it’s too much trouble to reformat or strip out the parts they don’t need. That’s how you end up with Big Data, or perhaps Data Bloat (which is unintentional Big Data).

So security architects should be thinking not just about how to implement the principles of least privilege and separation of duties; they should also be thinking about overuse of data, and about cleaning up data after its use (or, at the very least, sanitizing it). Especially when it comes to data about people -- if you don’t need to know or discover something about an individual, then don’t. And don’t leave data laying around for someone to recombine later into radioactive material.

Where does this leave logs, you ask? Yes, the whole point of keeping logs is to have a history of what happened, be able to diagnose things after the fact, and so on. Compliance may require you to keep certain logs for certain periods of time. There’s not much you can do about any of that. But you can look at any other logging that’s going on -- particularly application logging, which might be writing all sorts of confidential information to make troubleshooting easier (including passwords!). Don’t send the logs all over the place; don’t share them where you don’t have to. Everything in a log should have a good reason for being there, and anything that uses the log data should be doing it for known purposes.

In other words, treat your log data as the valuable resource that it is, and make conservation part of your policies. Keep radioactive logs separate from nonradioactive ones. Know what liabilities you’re keeping along with your event data. Use only what you need. I’m not calling for a ban on plastic, but think green, sustainable syslog. And thank you for not littering.

Wendy Nather is Research Director of the Enterprise Security Practice at the independent analyst firm 451 Research. You can find her on Twitter as @451wendy.

Wendy Nather is Research Director of the Enterprise Security Practice at independent analyst firm 451 Research. With over 30 years of IT experience, she has worked both in financial services and in the public sector, both in the US and in Europe. Wendy's coverage areas ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4931
PUBLISHED: 2021-02-24
IBM MQ 9.1 LTS, 9.2 LTS, and 9.1 CD AMQP Channels could allow an authenticated user to cause a denial of service due to an issue processing messages. IBM X-Force ID: 191747.
CVE-2020-11987
PUBLISHED: 2021-02-24
Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
CVE-2020-11988
PUBLISHED: 2021-02-24
Apache XmlGraphics Commons 2.4 is vulnerable to server-side request forgery, caused by improper input validation by the XMPParser. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
CVE-2021-21974
PUBLISHED: 2021-02-24
OpenSLP as used in ESXi (7.0 before ESXi70U1c-17325551, 6.7 before ESXi670-202102401-SG, 6.5 before ESXi650-202102101-SG) has a heap-overflow vulnerability. A malicious actor residing within the same network segment as ESXi who has access to port 427 may be able to trigger the heap-overflow issue in...
CVE-2021-22667
PUBLISHED: 2021-02-24
BB-ESWGP506-2SFP-T versions 1.01.09 and prior is vulnerable due to the use of hard-coded credentials, which may allow an attacker to gain unauthorized access and permit the execution of arbitrary code on the BB-ESWGP506-2SFP-T (versions 1.01.01 and prior).