Protego field desk
Threat Detection and Incident Response · 14% of exam

L15. AWS Incident Response Framework & Playbooks

Video generating

Check back soon for the video lesson on AWS Incident Response Framework & Playbooks

Course outlineLesson 15 of 18
AWS Security Specialty Exam Prep: course overview

The NIST-aligned IR lifecycle applied to AWS: pre-provisioned break-glass access, isolate-don't-terminate containment for compromised instances, and AWS Detective for root-cause analysis.

Exam scope: Use the current SCS-C03 guide linked below; this lesson covers the topic rather than the complete exam syllabus.

The NIST-Aligned Lifecycle

AWS incident response guidance describes preparation, detection and analysis, containment/eradication/recovery, and post-incident activity. These remain useful operational phases. NIST SP 800-61 Revision 3 now integrates incident response across the CSF 2.0 functions, rather than treating the older four-phase diagram as the current NIST model. The exam tests this framework less as trivia and more as a way of reasoning about which action is appropriate at which stage. A question describing an active compromise is asking about containment, not preparation, and the two call for very different answers.

Preparation: Build the Response Before You Need It

Preparation happens long before an incident, and it decides how fast and how safely a team can respond once one occurs. Three elements matter most on the exam:

  • Pre-provisioned break-glass IAM roles: dedicated roles reserved for incident response, created ahead of time so responders are not requesting new permissions mid-incident, when an attacker may already have visibility into IAM activity.
  • A resource tagging strategy: consistent tags let responders quickly identify what an affected resource does and who owns it, cutting the time spent figuring out blast radius during an actual event.
  • A dedicated forensics account: a tightly access-controlled account, separate from production, purpose-built to receive evidence.

Containment: Isolate, Don't Terminate

The most exam-relevant containment rule concerns a suspected compromised EC2 instance: do not terminate it immediately. Termination destroys volatile evidence, including memory contents, that could reveal how the attacker got in and what they did. Remove the instance from production traffic and apply a quarantine security group with no ingress or egress rules on every attached network interface. Existing tracked connections can survive security-group rule changes, so verify containment and use carefully scoped NACL or host controls when immediate interruption is needed. Security groups also do not filter every service path, such as Amazon-provided DNS. Preserve approved forensic access, capture memory where feasible, snapshot EBS volumes, and separately contain compromised IAM credentials. An EBS snapshot does not capture RAM.

ActionEffect on Evidence
Terminate immediatelyDestroys memory and ephemeral state, evidence lost
RebootClears memory contents, evidence lost
Quarantine security groupBlocks new allowed connections; verify tracked connections and preserve forensic access

AWS Detective for Root-Cause Analysis

Once an incident is contained, responders still need to understand scope and root cause, and manually correlating raw CloudTrail, VPC Flow Log, and GuardDuty data across dozens of API calls is slow. AWS Detective ingests GuardDuty findings, CloudTrail logs, and VPC Flow Logs and builds a visual graph of relationships between resources, IP addresses, and API calls. An analyst can pivot from a single finding to every resource and principal it touched, which speeds up determining the full scope of a compromise far beyond what manual log correlation allows.

Forensics Accounts Keep Evidence Clean

A dedicated forensics account, separate from production and tightly scoped in who can access it, is where evidence such as EBS snapshots, memory dumps, and exported logs gets copied for analysis. Isolating this work avoids contaminating production environments during an active investigation and avoids granting broad forensic access to anyone who does not strictly need it, which matters both for chain of custody and for limiting risk if the investigation itself is being watched by the attacker. Exam tip: Whenever a question describes a live compromised resource, the answer that terminates or reboots it first is almost always wrong. Isolate and preserve, then investigate.

References

Continue Learning

Exam Focus Points
  • ✓AWS operational response phases remain useful; current NIST SP 800-61r3 aligns incident response with CSF 2.0
  • ✓Preparation includes pre-provisioned break-glass IAM roles, a consistent resource tagging strategy, and a dedicated forensics account with tightly controlled access
  • ✓Isolate and preserve compromised EC2 instances; quarantine security groups alone may leave tracked connections open, so verify containment
  • ✓Before remediating a compromised instance, capture an EBS snapshot (and memory if possible) to preserve forensic evidence
  • ✓AWS Detective visualizes relationships across GuardDuty findings, CloudTrail, and VPC Flow Logs, speeding up root-cause and scope analysis compared to manually correlating raw logs
Knowledge Check

1. GuardDuty flags an EC2 instance as likely compromised and communicating with a command-and-control server. What should be the first containment action?

2. What is the primary purpose of a dedicated forensics account in an AWS incident response program?

3. An analyst is trying to understand how a compromised IAM credential was used across dozens of API calls and multiple resources. Which service is purpose-built to visualize these relationships?