Ep. 103 Effective data management at end of lifecycle and after a breach

If you have ever raised teenagers, you know the phrase, “unintended consequences.”

In today’s world of federal technology, this concept can be applied to data storage.  What are the consequences if you do not thoroughly erase data?  It could be an open door for data leakage. 

For example, what happens when your agency moves data from one cloud to another?  Is it erased?  How do you know? 

Let’s talk about the 500-pound elephant in the room – a cybersecurity event.  Today’s malicious actors have been known to place trojan horses in other areas of a system.  The concept of data sanitization is a concern for many federal leaders.

Ok.  We know we have standards for data erasure.  Civilian agencies have heard of NIST 800-88 and the folks at the Pentagon know DoD 5220-22 M/M ECE.  That is all well and good if applied properly. 

Many breaches occur because of human error; the same humans are tasked with applying these procedures for data sanitization. 

Maurice Uenuma from Blancco gives a great overview of some of the problems with effectively administering data erasure.  He brings up some issues that you may not have considered:

In a world of feds at the edge, what happens to data stored on remote devices?

How to automate erasure to make it compliant and secure

End-of-life cycle issues apply to software development and hardware as well.

Scalable storage is great – what happens to the dynamic elements of data storage?

 

Follow John Gilroy on Twitter @RayGilray

Follow John Gilroy on LinkedIn  https://www.linkedin.com/in/john-gilroy/

Listen to past episodes of Federal Tech Podcast  www.federaltechpodcast.com