# Incident Response Documentation
When a cybersecurity incident hits a government agency, the response team faces competing demands: contain the threat, preserve evidence, notify stakeholders, and document everything — simultaneously. Documentation often suffers because it feels less urgent than stopping the attack. But poor documentation creates legal liability, hinders post-incident analysis, and can result in compliance violations.
Before an incident occurs, AI helps create detailed playbooks for common scenarios:
Create an incident response playbook for: [Ransomware attack on a municipal government network]
Structure:
DETECTION & INITIAL ASSESSMENT (first 30 minutes)
- How the incident is likely to be detected
- Initial triage questions to determine scope
- Immediate containment actions
- Who to notify and in what order
CONTAINMENT (30 minutes - 4 hours)
- Network isolation procedures
- Evidence preservation steps
- System-by-system priority for containment
- Decision tree: when to disconnect systems vs. monitorUpgrade to Pro to access the full content
What you'll learn: