NASA data leak exposes and compromises employee records

You would think that one of the most technologically advanced organizations in the world could avoid a cybersecurity breach. This is turning out to not be the case as NASA employees discovered this week when they were notified of a large data breach. In an internal memo sent out by NASA headquarters and written by Bob Gibbs, assistant administrator for the Office of Human Capital Management, employees were informed that personally identifiable data was exposed when a server tied to HR records was breached. The memo stated that classified mission data was not thought to be exposed, but the damage done is still significant. The most important data from the internal memo about the NASA data leak is quoted below:

On Oct. 23, 2018, NASA cybersecurity personnel began investigating a possible compromise of NASA servers where personally identifiable information (PII) was stored. After initial analysis, NASA determined that information from one of the servers containing Social Security numbers and other PII data of current and former NASA employees may have been compromised... those NASA Civil Service employees who were on-boarded, separated from the agency, and/or transferred between Centers, from July 2006 to October 2018, may have been affected. Once identified, NASA will provide specific follow-up information to those employees, past and present, whose PII was affected, to include offering identity protection services and related resources, as appropriate. Our entire leadership team takes the protection of personal information very seriously. Information security remains a top priority for NASA.

The line about InfoSec being a top priority is laughable to anyone who knows NASA’s internal security practices. I have close ties to individuals at Jet Propulsion Laboratory, whose identities will remain anonymous to protect their jobs, and I can confidently state that NASA’s security protocols are a complete joke. Upper management especially makes poor decisions on a regular basis that compromise numerous facets of internal networks that carry sensitive data.

You don’t need to take my source’s word for it, however, as even the U.S. government has determined that NASA has a long way to go with regards to InfoSec. (And this NASA data leak was not the first time the agency’s security protocols have been shown to be insufficient.) In the latest Federal Information Security Modernization Act of 2014 (FISMA) - 2018 report, which determines government agencies’ compliance with a bill (FISMA) intended to improve cybersecurity practices, NASA performed poorly. The FISMA reports score on a letter grade system, and NASA received an “F” from the government making it among the worst in the entire U.S. government for InfoSec.

What this NASA data leak clearly shows is that the agency needs to get its act together.

Featured image: Wikimedia

Derek Kortepeter

Derek Kortepeter is a graduate of UCLA and tech journalist that is committed to creating an informed society with regards to Information Security. Kortepeter specializes in areas such as penetration testing, cryptography, cyber warfare, and governmental InfoSec policy.

Published by
Derek Kortepeter

Recent Posts

IFA 2019: All the top smartphone announcements and unveilings

IFA 2019, this year’s version of the annual consumer electronics trade show, did not disappoint. Is one of these smartphones…

12 mins ago

Outlook connectivity: Troubleshooting and solving common issues

IT professionals all dread getting this fevered message from employees and clients: “I’m having Outlook connectivity issues!” Here’s what you…

5 hours ago

Using tags with Azure runbook automation to control your costs

Here’s a script designed to start and stop virtual machines based on tags associated at the resource group level. It…

8 hours ago

Software-defined perimeter solutions: Why this is the future of security

Traditional VPNs are showing their age in the modern cloud-powered workplace. That’s why software-defined perimeter solutions are in your future.

3 days ago

Why you need to check your virtualization host’s NUMA configuration

Should you disallow NUMA spanning in your Hyper-V architecture? There are two sides to this story, and you’ll get both…

3 days ago

Getting started with Visual Studio Code and integrating with Azure DevOps

Coding may not be the No. 1 job duty for cloud admins, but it is often a part of the…

3 days ago