Executive Summary
In May 2026, the Cybersecurity and Infrastructure Security Agency (CISA) experienced a significant security lapse when a contractor inadvertently exposed sensitive credentials on a public GitHub repository named 'Private-CISA.' This repository, maintained by an employee of Nightwing—a contractor for CISA—contained approximately 844 MB of internal data, including administrative AWS GovCloud keys, plaintext passwords for internal systems, SSH keys, and SAML certificates. The repository was publicly accessible from November 2025 until its discovery in May 2026 by security researcher Guillaume Valadon of GitGuardian. Upon notification, CISA took steps to remove the repository and revoke the exposed credentials. (techcrunch.com)
This incident underscores the critical importance of stringent credential management and the need for continuous monitoring of public code repositories to prevent unauthorized data exposure. It also highlights the necessity for organizations, especially those responsible for national cybersecurity, to enforce robust security protocols and ensure that contractors adhere to the same standards to mitigate potential risks.
Why This Matters Now
The CISA GitHub credential leak serves as a stark reminder of the vulnerabilities associated with improper credential management and the risks posed by public code repositories. In an era where cyber threats are increasingly sophisticated, organizations must prioritize the implementation of comprehensive security measures, including regular audits, employee training, and the enforcement of strict access controls, to safeguard sensitive information and maintain public trust.
Attack Path Analysis
A contractor inadvertently published sensitive CISA credentials, including AWS GovCloud keys, in a public GitHub repository. This exposure could have allowed unauthorized access to CISA's cloud infrastructure. With these credentials, an attacker could escalate privileges within the environment. The attacker might then move laterally across CISA's internal systems. Establishing command and control channels would enable persistent access. Finally, the attacker could exfiltrate sensitive data, leading to significant operational impact.
Kill Chain Progression
Initial Compromise
Description
A contractor inadvertently published sensitive CISA credentials, including AWS GovCloud keys, in a public GitHub repository.
MITRE ATT&CK® Techniques
Unsecured Credentials: Credentials in Files
Search Open Websites/Domains: Code Repositories
Exfiltration Over Web Service: Exfiltration to Code Repository
Credentials from Password Stores
Credentials in Files
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Secure Storage of Account Data
Control ID: 7.1.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Identity and Access Management
Control ID: 2.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Government Administration
CISA's GitHub leak exposes critical vulnerabilities in federal credential management, incident response protocols, and contractor oversight requiring immediate zero-trust implementation.
Computer/Network Security
Data exposure incidents highlight gaps in secrets scanning, GitHub monitoring, and security researcher communication channels that cybersecurity firms must address.
Computer Software/Engineering
Public repository credential leaks demonstrate urgent need for automated secrets detection, secure development practices, and comprehensive code repository monitoring.
Information Technology/IT
AWS credential exposure and plaintext password storage reveal critical weaknesses in cloud key management and multi-cloud visibility requiring enhanced controls.
Sources
- Lessons Learned from CISA’s Recent GitHub Leakhttps://krebsonsecurity.com/2026/07/lessons-learned-from-cisas-recent-github-leak/Verified
- US cyber agency CISA exposed reams of passwords and cloud keys to the open webhttps://techcrunch.com/2026/05/19/us-cyber-agency-cisa-exposed-reams-of-passwords-and-cloud-keys-to-the-open-web/Verified
- America's top cyber-defense agency left a GitHub repo open with passwords, keys, tokens – and incredibly obvious filenameshttps://www.theregister.com/security/2026/05/19/americas-top-cyber-defense-agency-left-a-github-repo-open-with-passwords-keys-tokens-and-incredibly-obvious-filenames/5242915Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have constrained the attacker's ability to escalate privileges, move laterally, establish command and control channels, and exfiltrate data within CISA's cloud environment.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: While Aviatrix CNSF cannot prevent the exposure of credentials, it would likely limit the attacker's ability to exploit these credentials to gain unauthorized access to critical workloads.
Control: Zero Trust Segmentation
Mitigation: Aviatrix Zero Trust Segmentation would likely constrain the attacker's ability to escalate privileges by enforcing strict access controls and limiting the scope of accessible resources.
Control: East-West Traffic Security
Mitigation: Aviatrix East-West Traffic Security would likely limit the attacker's ability to move laterally by enforcing strict communication policies between workloads.
Control: Multicloud Visibility & Control
Mitigation: Aviatrix Multicloud Visibility & Control would likely constrain the attacker's ability to establish command and control channels by monitoring and controlling outbound communications.
Control: Egress Security & Policy Enforcement
Mitigation: Aviatrix Egress Security & Policy Enforcement would likely limit the attacker's ability to exfiltrate data by enforcing strict outbound data transfer policies.
With Aviatrix CNSF controls in place, the operational impact would likely be reduced due to constrained attacker movement and limited data exfiltration capabilities.
Impact at a Glance
Affected Business Functions
- Internal IT Systems
- Cloud Infrastructure Management
- Security Operations
Estimated downtime: N/A
Estimated loss: N/A
Administrative credentials for AWS GovCloud servers and internal CISA systems, including plaintext usernames and passwords.
Recommended Actions
Key Takeaways & Next Steps
- • Implement continuous monitoring of public code repositories to detect and remediate exposed secrets promptly.
- • Enforce strict access controls and least privilege principles to minimize the impact of credential exposure.
- • Utilize Zero Trust Segmentation to limit lateral movement within the network.
- • Deploy Egress Security & Policy Enforcement to monitor and control outbound traffic, preventing unauthorized data exfiltration.
- • Establish clear and distinct reporting channels for security incidents to ensure timely response and mitigation.



