Documented incidentIncident 2023-03-23GitHubEngineering postmortem

GitHub's RSA SSH host private key briefly exposed in a public repository (2023)

GitHub.com's RSA SSH private key was briefly exposed in a public GitHub repository.

What happened

  • GitHub replaced the key out of caution and stated it had no reason to believe the exposed key was abused; it was not the result of a compromise of GitHub systems.We updated our RSA SSH host key

The failure pattern

Watch the pattern: Privileged action without an enforceable approval gate

Safeguards that address it

CollectSEA's engineering analysis of what would have prevented or contained this failure.

  • Scan for private keys before they are publishedUse pre-commit and push-time secret scanning to block private keys from leaving controlled repositories.
  • Protect and rotate key materialKeep host keys in a vault with access logging and have a rehearsed rotation and notification plan.

Related standards

CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

Building something similar?

Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

Analyze your design