SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 

Destroying Data

By Steve Jones,

For many of the data professionals out there, our job is to ensure that data is protected. We work to protect the information in our databases in a variety of ways that allow our organization to continue to work in adverse situations. We often schedule backup schemes to ensure we can recover data from losses. We perform maintenance to ensure efficient access to information, and we move data from one system to another so that a wide variety of applications and clients can use it. We spend most of our workday trying to ensure that data is where it needs to be.

It's worth considering that there may be times when we are asked to destroy data as well. If hardware is being upgraded, then it might be a part of our job description to ensure that no traces of data exist in old systems. Even if it's not our job, we might want to ensure that hardware is destroyed or permanently wiped. It's unlikely to be an issue, but there are numerous stories of someone buying used equipment with old data on it. This is such a low bar of something to check that there isn't an excuse to avoid removing old data.

If you aren't sure what to do, don't have time, or want independent proof, maybe you want to use a service. There are numerous ones, which makes sense with the growth in legislation requiring stronger data protections as well as the embarrassment from management that wants to outsource their risk to another entity. This might be especially handy for larger organizations that could have multiple types of devices, some of which aren't as accessible as a hard drive in a server chassis. There are services to ensure wiping of phones, tablets, and more.

It's a little funny to me to think of destroying data when most of my career has revolved around protecting data. What I mostly think about here is that too often many organizations have thought about data as an asset of the company to be used as needed, but not necessarily protected throughout its life cycle, and certainly not classified according to it's sensitivity.

I hope that with the growing value of data, and regular misuse of information, and the security issues that appear in the news that most companies would start to actively manage their data in the future, from capture to destruction.

 
Total article views: 29 | Views in the last 30 days: 1
 
Related Articles
FORUM

SQL Datafile... How to protect ????

SQL Datafile... How to protect ????

FORUM

Protecting SSRS reports

Protecting SSRS reports

ARTICLE

Protect and Monitor

How do you protect and monitor your databases? Auditing is one way, but Steve Jones thinks this subs...

BLOG

Protected: Has it come true?

There is no excerpt because this is a protected post.

ARTICLE

What Data Should You Protect?

Perhaps we need to protect more data, according to Steve Jones. With the ability to identify most pe...

Tags
database weekly    
editorial    
security    
 
Contribute