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.

News

1/15/2010
11:11 AM
George Crump
George Crump
Commentary
50%
50%

Disposing Of Primary Storage

Every few years you are going to need to replace your enterprise storage system. A challenge that many storage managers face is what to do with the old system. Today you have laws that require you to make sure information is not readable when that storage leaves your walls and you have individuals that want to see what trouble they can dig up by resurrecting old systems.

Every few years you are going to need to replace your enterprise storage system. A challenge that many storage managers face is what to do with the old system. Today you have laws that require you to make sure information is not readable when that storage leaves your walls and you have individuals that want to see what trouble they can dig up by resurrecting old systems.In reality the chances of you being unlucky enough to have thrown your system out or put it on an auction site and then have someone pull usable data from those drives is unlikely. Most administrators will at least format the drives. The problem is formatting the drives may not be enough to meet the laws surrounding public release of private information. The laws may also be getting tougher.

Several states have enacted or are considering legislation that will require you to have data security standards in place, always. Not just disclose when a breech has occurred. Personally, I think this makes a bit more sense. Letting me know that you have lost your data and someone might have it really does not help all that much. Stopping it from happening in the first place, that makes sense.

Data that leaves your building has increasing pressure on it to be encrypted in some way. Tapes are always the first consideration, and I'll save you yet another "tape fell off the back of the truck" story. Primary storage however is often left out of the discussion. It doesn't get transported around like tapes do. Its protected, or should be, by your own internal security measures. What's the fear? At some point you are going to dispose of it for a newer model. No matter how you do that you are putting your data in someone else's hands. Again, formatting is probably not enough. Encryption is needed.

Beyond understanding the need, the resistance to encrypting storage in the past has centered around concerns about performance impact and difficulty of implementation. First there are plenty of choices of how and where to encrypt data. Companies like Brocade, EMC, NetApp and Thales are all offering encryption capabilities either by an add-on appliance, on the storage controller or built right into the storage infrastructure. Drive manufacturers like Seagate and IBM are delivering hard drives on the drive itself. HBA manufacturers like Emulex are delivering encryption at the HBA.

Most of the vendors claim little or no performance loss as a result of encryption. Additionally most of these systems are relatively seamless to install. In some cases it is basically automatic. While there is some complexity around key management vendors are moving toward standardization along this front as well.

Solutions like these make the disposal of storage safer. Once the array is unplugged from the storage infrastructure it is rendered unreadable for all practical means. At least thus far encryption meets the requirements set by the various state laws being enacted. You might as well face it, the requirement to secure customer data is here to stay and the laws that protect the consumer are only going to become more stringent, embracing storage encryption now can save a lot of headaches later.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15222
PUBLISHED: 2020-09-24
In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the `jti` value is not checked. When using client authentication method "private_key_jwt", OpenId specification say...
CVE-2020-15223
PUBLISHED: 2020-09-24
In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.34.0, the `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacke...
CVE-2020-12842
PUBLISHED: 2020-09-24
ismartgate PRO 1.5.9 is vulnerable to privilege escalation by appending PHP code to /cron/checkUserExpirationDate.php.
CVE-2020-12843
PUBLISHED: 2020-09-24
ismartgate PRO 1.5.9 is vulnerable to malicious file uploads via the form for uploading sounds to garage doors. The magic bytes for WAV must be used.
CVE-2020-13119
PUBLISHED: 2020-09-24
ismartgate PRO 1.5.9 is vulnerable to clickjacking.