secret-breach-response

To handle a leaked secret in git history or CI/CD pipelines, you must detect, classify, and contain the exposed credential. This Skill orchestrates the incident response by guiding revocation, rotation, and access auditing to reduce the blast radius.

Revoking and rotating cloud credentials after a breach involves classifying the exposed key and executing a structured remediation workflow. This Skill guides the revocation, credential rotation, and access auditing while enforcing human approval for destructive actions.

Yes, you can automate incident response for leaked API keys while preventing unintended destructive actions. This Skill enforces auto-detection combined with mandatory human approval for destructive actions, ensuring safe credential rotation and revocation.

To document a post-mortem after a credential leak in a repository, you need to generate structured incident records. This Skill produces post-mortem documentation alongside the access audit, capturing the full containment and remediation workflow.

Yes, this secret breach response workflow supports AWS keys, service accounts, and API keys. It applies detection and classification across CI/CD pipelines, git history, and cloud credentials to initiate appropriate incident response protocols.