Home · Wiki · Incidents & Campaigns
type: incident · created: 2026-07-18 · updated: 2026-07-18 · tags: [data-leak, government-agency, supply-chain, incident] · confidence: high · affected_sectors: [government, technology] · au_impact: true

CISA GitHub Data Leak

CISA published a postmortem on a significant data leak in which a contractor published 844 MB of sensitive internal data — including AWS GovCloud keys and plaintext passwords for dozens of internal systems — in a public GitHub repository for nearly six months.

Timeline

Date Event
~Jan 2026 Contractor inadvertently publishes data to public repo
Multiple GitGuardian sends 9 automated alerts to CISA during exposure window
May 2026 KrebsOnSecurity notifies CISA directly
May 2026 CISA acknowledges — takes over 48 hours to rotate all exposed keys
July 13, 2026 CISA publishes postmortem via Krebs on Security (raw/digests/Cyber-Digest-2026-07-18.md)

What Was Exposed

  • 844 MB of sensitive internal data
  • AWS GovCloud keys (highly sensitive — GovCloud is CISA's own cloud infrastructure)
  • Plaintext passwords for dozens of internal systems
  • Access data to CISA's operational environments

Security Failures Identified

  1. GitGuardian sent 9 alerts before the leak was acted upon through journalism — the automated alerting system worked, but the escalation/remediation process failed
  2. No audit trail for credential rotation in third-party contractor environments
  3. 48+ hour key rotation time — far exceeding CISA's own standards for incident response

Significance for Australia

The incident serves as a case study for Australian government agencies (ACSC, ASD, home-affairs-cyber) managing cloud infrastructure through third-party contractors. Key lessons: - Automated security tooling is only as good as the escalation path - GovCloud/Protected-level credential management requires contractor auditing - Plaintext passwords in repositories violates ACSC's Essential Eight guidelines

Related Pages