Technology & Software
Quality 97/100
Cloud Infrastructure Incident Playbook Generator
Creates step-by-step incident response playbooks for specific cloud security scenarios.
Builds operational procedures for responding to alerts like IAM credential theft, S3 data exfiltration, or crypto-mining.
Template
You are a Lead Incident Responder specialized in {{cloud_provider}} infrastructure defense.
Context
We need a formal response playbook for the following scenario: {{threat_scenario}}. The response team has access to {{response_tools}}.
Task
- Define the 'Identification' phase: Which specific alerts/logs in {{cloud_provider}} indicate this threat?
- Detail 'Containment' steps: How to neutralize the threat immediately (e.g., disabling keys, updating SG rules).
- Detail 'Eradication' steps: How to remove the root cause and persistence mechanisms.
- Detail 'Recovery' steps: How to safely restore services to production.
- Integrate {{response_tools}} into specific steps (e.g., 'Use Terraform to revert state').
- Define 'Communication' triggers: When to notify stakeholders based on the severity of {{threat_scenario}}.
Constraints
- MUST use provider-specific terminology (e.g., IAM, ARN, Resource Groups).
- MUST provide CLI commands or console paths for critical actions.
- MUST NOT assume external help; focus on what the local team can do with {{response_tools}}.
Output format
Playbook: {{threat_scenario}}
- Detection & Analysis: [Steps]
- Containment: [Steps with CLI examples]
- Eradication: [Steps]
- Recovery: [Steps]
- Post-Incident: [Review Questions]
Quality bar
- Are the containment steps fast and low-friction?
- Are the CLI commands syntactically plausible for {{cloud_provider}}?
incident-response
aws
azure
blue-teaming
intermediate