Back to Feed
BreachesJul 13, 2026

Lessons Learned from CISA’s Recent GitHub Leak

CISA contractor exposed AWS Govcloud keys and internal credentials on GitHub for six months.

A CISA contractor inadvertently exposed sensitive internal credentials, including AWS Govcloud keys and plaintext passwords, in a public GitHub repository for nearly six months. The leak was only discovered after a security firm and a reporter intervened. CISA's postmortem highlighted significant delays in rotating compromised credentials and issues with its incident notification channels, emphasizing the need for better key management and clearer reporting processes.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run GitHub?

Get an email when a new story names GitHub, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

A CISA contractor accidentally committed sensitive credentials — including AWS GovCloud keys and plaintext passwords — to a public GitHub repository, where they remained exposed for nearly six months. The breach was not discovered internally; it took intervention from an external security firm and a journalist to surface the issue, revealing a critical gap in both secret detection tooling and monitoring practices. Once discovered, CISA's response was hampered by slow credential rotation and unclear incident notification channels, compounding the risk window. This incident underscores that human error in handling secrets is inevitable, making automated detection, rapid response playbooks, and robust key management controls essential — even for the organizations responsible for defending others.

What helps against this

How we list vendors

Entities

GitHub (vendor)Amazon AWS (vendor)AWS Govcloud (product)AWS-Workspace (product)GitGuardian (vendor)