Recover Security Incident
Overview
Return systems and people to a trusted operating state using explicit eradication and validation criteria. Recovery is complete only when restored behavior, security controls, access, monitoring, and residual risk are verified.
Read references/recovery-gates.md for staged return-to-service gates.
Workflow
- Establish eradication criteria.
- Identify root/access path, persistence, affected identities/secrets, vulnerable configuration/code, related artifacts, and known scope.
- Choose restore basis.
- Decide clean rebuild, known-good backup, patched image, repaired configuration, provider recovery, or controlled cleanup from evidence and integrity confidence.
- Eradicate.
- Remove verified mechanisms, patch or mitigate the entry path, rotate/revoke secrets and sessions from trusted systems, repair policies/configuration, and preserve evidence of changes.
- Restore in stages.
- Validate offline or isolated, restore dependencies/data, enable limited traffic/users, monitor, then broaden service.
- Verify security and function.
- Reproduce the original detection/path as a negative test, confirm expected functionality, review access/persistence/network/logging, and check backups and monitoring.
- Remove temporary controls deliberately.
- Inventory emergency rules, disabled services, isolation, temporary accounts, logging, tokens, and exceptions; retain only approved controls with owners/expiry.
- Close and improve.
- Record timeline, root cause, affected scope, actions, notifications, evidence retention, lessons, structural hardening, and residual risk owner.
Output
Return eradication evidence, restore basis, staged recovery results, negative retest, temporary-control disposition, monitoring window, lessons/actions, and residual-risk decision.
1---2name: recover-security-incident3description: Recover from an incident by eradicating compromise and restoring service. Use when hosts, identities, applications, cloud resources, network controls, or data need rebuild, patching, rotation, repair, validation, and return to service.4---56# Recover Security Incident78## Overview910Return systems and people to a trusted operating state using explicit eradication and validation criteria. Recovery is complete only when restored behavior, security controls, access, monitoring, and residual risk are verified.1112Read [references/recovery-gates.md](references/recovery-gates.md) for staged return-to-service gates.1314## Workflow15161. Establish eradication criteria.17 - Identify root/access path, persistence, affected identities/secrets, vulnerable configuration/code, related artifacts, and known scope.182. Choose restore basis.19 - Decide clean rebuild, known-good backup, patched image, repaired configuration, provider recovery, or controlled cleanup from evidence and integrity confidence.203. Eradicate.21 - Remove verified mechanisms, patch or mitigate the entry path, rotate/revoke secrets and sessions from trusted systems, repair policies/configuration, and preserve evidence of changes.224. Restore in stages.23 - Validate offline or isolated, restore dependencies/data, enable limited traffic/users, monitor, then broaden service.245. Verify security and function.25 - Reproduce the original detection/path as a negative test, confirm expected functionality, review access/persistence/network/logging, and check backups and monitoring.266. Remove temporary controls deliberately.27 - Inventory emergency rules, disabled services, isolation, temporary accounts, logging, tokens, and exceptions; retain only approved controls with owners/expiry.287. Close and improve.29 - Record timeline, root cause, affected scope, actions, notifications, evidence retention, lessons, structural hardening, and residual risk owner.3031## Output3233Return eradication evidence, restore basis, staged recovery results, negative retest, temporary-control disposition, monitoring window, lessons/actions, and residual-risk decision.
gaelic-ghost