aws-samples/aws-incident-response-playbooks resource
None observed · 2026-08-28
Health v2 · maintenance only
66/100
- Activity 96
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2274
- days_rel: n/a
- days_push: 26
- n_releases_24m: 0
Adoption not part of the score
1099 stars · 232 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A collection of sample incident response playbooks for AWS environments, aligned to NIST SP 800-61r3 and CSF 2.0. It provides templates and scenario-specific guides for handling identity, compute, and data security incidents in the cloud.
Use cases
- build incident response capability on aws
- respond to compromised iam credentials
- handle ransomware in aws environment
- create incident response playbooks for cloud
- triage security incident severity
- plan response to ec2 compromise
- prepare for ddos response on aws
- map incident response to nist framework
When to choose
- you run workloads on AWS and need IR documentation
- you want playbooks aligned to NIST SP 800-61r3
- you need templates to customize for your security team
When to avoid
- you need automated incident response tooling rather than documentation
- you are not using AWS
- you need official AWS support or documentation
Facets
learning-resource · maturity active
security documentation security cloud-computing cloud incident-response playbooks aws nist-800-61 cloud-security forensics security-operations devops
1 source
- readme: https://github.com/aws-samples/aws-incident-response-playbooks · fetched 2026-08-28 · 7d979e46c4da
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| aws-samples/aws-incident-response-playbooks | main | 66 |
For agents
markdown · JSON · MCP: product_card(name="aws-samples/aws-incident-response-playbooks")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem