TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) left sensitive credentials in a public GitHub repository for about six months. The leak included passwords and keys for internal systems, but CISA states no sensitive data was confirmed as compromised. The incident highlights ongoing cybersecurity risks within government agencies, such as the dangers of leaked SSH keys.
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) left its cloud storage credentials publicly accessible on GitHub for an undetermined period, according to Krebs on Security. The agency stated that no sensitive data was confirmed as compromised, but the exposure raised alarms about cybersecurity protocols within a federal agency responsible for protecting critical infrastructure.
According to Krebs on Security, CISA’s public GitHub repository, named ‘Private-CISA,’ contained files with plaintext passwords, security tokens, and administrative credentials for internal systems. The repository was created in November of the previous year, and the exposure lasted approximately six months before being addressed over the weekend, illustrating how human error in the development pipeline can lead to security breaches.
The exposed files included ‘importantAWStokens,’ which contained administrative credentials for three Amazon AWS GovCloud servers, and ‘AWS-Workspace-Firefox-Passwords.csv,’ listing plaintext usernames and passwords for dozens of internal CISA systems, including a system called ‘LZ-DSO,’ likely short for ‘Landing Zone DevSecOps.’
Why It Matters
This incident underscores vulnerabilities in federal cybersecurity practices, especially regarding the handling and storage of sensitive credentials, such as leaked SSH keys. The exposure of internal system passwords and tokens poses risks of unauthorized access, data breaches, and potential exploitation by malicious actors. It also raises questions about the effectiveness of internal safeguards and oversight within government agencies tasked with cybersecurity.
secure password manager for cybersecurity professionals
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
CISA, established in 2018, has faced ongoing challenges, including political turmoil and leadership instability, especially during the Trump administration and its aftermath. The agency’s role is to secure U.S. infrastructure from cyber threats, making its own cybersecurity practices critical. Previous incidents have highlighted vulnerabilities across government agencies, but this leak is notable for the severity of exposed credentials and the length of time they were publicly accessible.
“This is the worst leak that I’ve witnessed in my career.”
— Guillaume Valadon, GitGuardian
“Currently, there is no indication that any sensitive data was compromised as a result of this incident. We are working to implement additional safeguards to prevent future occurrences.”
— CISA spokesperson
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It remains unclear how the credentials were initially exposed—whether through an insider mistake, misconfiguration, or other vulnerabilities. The full extent of any potential compromise or malicious activity resulting from the leak is also unknown. Additionally, details about the specific timeline of when sensitive data was added to the repository are still emerging.
AWS credential security products
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
CISA has stated it is implementing additional safeguards to prevent similar incidents. Investigations are likely ongoing to determine the cause of the leak, and cybersecurity experts will monitor for any signs of exploitation, emphasizing the importance of security culture in organizations. Future updates may clarify whether any data was accessed or misused.
As an affiliate, we earn on qualifying purchases.
Key Questions
How did the leak happen?
It is not yet clear whether the credentials were exposed due to a misconfiguration, insider error, or another vulnerability. CISA has not provided detailed information about the exact cause.
Could this leak have led to a security breach?
CISA states there is no confirmed evidence that sensitive data was compromised, but the exposure of internal credentials could potentially enable unauthorized access if exploited by malicious actors.
What is CISA doing to fix the issue?
The agency has fixed the repository and is working to implement additional safeguards to prevent future leaks, according to their statement.
How long was the information exposed?
The repository was created in November of the previous year and was publicly accessible for approximately six months before being fixed over the weekend.
What are the implications for government cybersecurity?
This incident highlights ongoing vulnerabilities in federal cybersecurity practices and the importance of securing internal credentials against accidental exposure.
Source: reddit
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
