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.

Attacks/Breaches

6/24/2019
01:00 PM
50%
50%

Raspberry Pi Used in JPL Breach

NASA report shows exfiltration totaling more than 100 GB of information since 2009.

Auditors' reports tend to make for dry reading. But NASA's Inspector General has delivered a report on "Cybersecurity Management and Oversight at the Jet Propulsion Laboratory" that includes twists and turns — like a hacker using a vulnerable, unapproved Raspberry Pi as a doorway into JPL systems.

That Raspberry Pi was responsible for 500 megabytes of NASA Mars mission data leaving JPL servers. The intrusion resulted in an advanced persistent threat (APT) that was active in JPL's network for more than a year before being discovered.

This was the most recent breach listed in the report. Other breaches noted date back to 2009 and include exfiltration totaling more than 100 gigabytes of information. Several of the intrusions feature command-and-control servers with IP addresses located in China, though the responsibility for the latest attack was not assigned to any country or actor.

The Inspector General's report makes a number of suggestions, including greater network segmentation, more rigorous external device approval, and an improved trouble ticket process, for improving cybersecurity at the lab.

Read more here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/27/2019 | 9:16:06 PM
Identified and found numerous security vulnerabilities
We also found that security problem log tickets, created in the ITSDB when a potential or actual IT system security vulnerability is identified, were not resolved for extended periods of time—sometimes longer than 180 days.
However, we found the database inventory incomplete and inaccurate, placing at risk JPL's ability to effectively monitor, report, and respond to security incidents.
Further, we found that JPL's network gateway that controls partner access to a shared IT environment for specific missions and data had not been properly segmented to limit users only to those systems and applications for which they had approved access.
PL had not implemented a threat hunting program recommended by IT security experts to aggressively pursue abnormal activity on its systems for signs of compromise, and instead rely on an ad hoc process to search for intruders.
We found that multiple JPL incident management and response practices deviate from NASA and recommended industry practices.For example, unlike NASA's Security Operations Center (SOC), JPL's SOC does not maintain round-the-clock availability of IT security incident responders and JPL's incident response plan does not include all federally-recommended elements.
In addition, team coordination issues delayed completion of incident containment and eradication steps for the April 2018 incident.
No controls were in place to ensure JPL compliance with this requirement nor did NASA officials have access to JPL's incident management system.
As of March 2019, the Agency had not approved JPL's plans to implement new IT security policies and requirements NASA included in its October 2018 contract.

From looking at the report, the JPL Raspberry PI was just one item that was a major issue, I think where I am confused is how did a device from the public get on the network of NASA's Jet Propulsion system's network? There should have been some sort of notification that looked up MAC addresses that were purchased or perform a reg-ex lookup of mac addresses that are not on the production network's device purchase list.
MAC Address/OUIVendor
B8:27:EB Raspberry Pi Foundation
Cisco Network - show mac address-table | in b8:27:eb
show ip arp vlan <vlan no> | include b827.eb

This is from NASA's final security report - https://oig.nasa.gov/docs/IG-19-022.pdf. They stated this occurred over the last 10 years. I am not sure about the rest of the group but the contract, employees and the rest of the security department should all be fired from this point (start from the top, remove everyone and start again).

This is what I mean by incompentence at the highest level.

Todd S
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4231
PUBLISHED: 2020-05-28
IBM Security Identity Governance and Intelligence 5.2.6 could allow an authenticated user to perform unauthorized commands due to hazardous input validation. IBM X-Force ID: 175335.
CVE-2020-4232
PUBLISHED: 2020-05-28
IBM Security Identity Governance and Intelligence 5.2.6 could allow an attacker to enumerate usernames to find valid login credentials which could be used to attempt further attacks against the system. IBM X-Force ID: 175336.
CVE-2020-4233
PUBLISHED: 2020-05-28
IBM Security Identity Governance and Intelligence 5.2.6 could allow a remote attacker to obtain sensitive information, caused by the failure to set the secure flag for the session cookie in SSL mode. By intercepting its transmission within an HTTP session, an attacker could exploit this vulnerabilit...
CVE-2020-4244
PUBLISHED: 2020-05-28
IBM Security Identity Governance and Intelligence 5.2.6 could allow an unauthorized user to obtain sensitive information through user enumeration. IBM X-Force ID: 175422.
CVE-2020-4245
PUBLISHED: 2020-05-28
IBM Security Identity Governance and Intelligence 5.2.6 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 175423.