Study guide
3.2 Testing & Validating Incident Response Plans
AWS Certified Security – Specialty SCS-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Getting Started with the SCS-C03 Exam
0.1 SCS-C03 Exam Format, Domains & Study Strategy
2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services
1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification
3 Chapter 2: Enterprise Logging Architecture & Analysis
2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs
4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks
3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks
5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis
4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective
6 Chapter 5: Edge Protection, WAF & DDoS Mitigation
5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS
7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security
6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect
8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit
7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI
9 Chapter 8: Enterprise Authentication, Federation & Directory Services
8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures
10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation
9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags
11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing
10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation
12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance
11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores
13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI
12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture
14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection
13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults
15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance
14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog
16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing
15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews
3.2 Testing & Validating Incident Response Plans
Key Takeaways Explain This Topic AI
AWS Fault Injection Service (FIS) executes controlled chaos engineering experiments against production-like environments to validate security detection, alerting thresholds, and automated response runbooks.
FIS experiment templates define specific target resources, disruption actions (such as CPU stress, network latency, and process termination), and automated CloudWatch alarm stop conditions that immediately abort the experiment if safety thresholds are breached.
AWS Resilience Hub assesses application components against defined Recovery Time Objective (RTO) and Recovery Point Objective (RPO) targets, uncovering architectural drift and generating tailored FIS experiment templates.
Tabletop exercises validate decision-making hierarchies, legal disclosure requirements, and cross-functional communications, whereas technical GameDays validate operational detection telemetry and automated containment tools under live conditions.
Runbook drift occurs when infrastructure modifications, IAM policy updates, or API changes render operational playbooks obsolete; continuous automated testing is required to identify and remediate these procedural gaps.
Last updated: September 2026
Testing & Validating Incident Response Plans
Having documented incident response playbooks is insufficient for modern cloud security. During an actual security breach, organizations frequently discover that runbooks are out of date, automation scripts fail due to missing IAM permissions, contact lists contain former employees, or security alerting thresholds fail to fire under real-world conditions. Incident readiness must be validated empirically. Through controlled fault injection, automated resiliency assessments, and multi-team simulation exercises, security teams uncover operational blind spots and eliminate runbook drift before adversaries strike.
The Imperative for Incident Response Testing: Beyond Paper Runbooks
Traditional disaster recovery often relied on periodic, scheduled documentation reviews. In dynamic cloud environments, infrastructure changes continuously through infrastructure as code (IaC) pipelines, microservice updates, and automated scaling. This rapid pace introduces runbook drift —a condition where documented standard operating procedures (SOPs) no longer reflect the technical reality of the running infrastructure.
To counter runbook drift, organizations adopt Security Chaos Engineering : +-------------------------------------------------------------+
- | 1. Formulate Hypothesis: |
- | "Terminating the security agent will trigger an alert |
- | and initiate auto-remediation within 2 minutes." |
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | 2. Inject Controlled Disruption (AWS FIS): |
- | Kill the security monitoring daemon on 20% of instances.|
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | 3. Monitor Telemetry & Safety Guardrails: |
- | Verify CloudWatch metrics; stop if 5xx error rate > 5%. |
- +-------------------------------------------------------------+
- |
- v
- +-------------------------------------------------------------+
- | 4. Validate Outcome & Remediate Gaps: |
- | Did the alert fire? Did the runbook execute successfully?|
- +-------------------------------------------------------------+
By systematically testing hypotheses about how defensive systems respond to failure or attack, teams build empirical confidence in their detection and response capabilities.
AWS Fault Injection Service (FIS) Mechanics & Security Testing
AWS Fault Injection Service (FIS) is a fully managed chaos engineering service designed to run controlled fault injection experiments on AWS workloads. While frequently used to test high availability and fault tolerance, FIS is an essential tool for validating incident response and security monitoring pipelines .
Core Components of AWS FIS
An FIS experiment is defined by a declarative Experiment Template consisting of four primary building blocks:
Targets: The specific AWS resources upon which the experiment executes. Targets can be Amazon EC2 instances, Amazon ECS tasks, Amazon EKS pods, Amazon RDS databases, or IAM roles. Targets are resolved dynamically using resource tags, resource filters, or specific ARNs. Responders define target scopes using selectionMode: "PERCENT(n)" (e.g., impact 20% of matching instances) or selectionMode: "COUNT(n)" (e.g., impact exactly 1 instance) to strictly control blast radius.
Actions: The precise fault or disruption injected into the targets. Actions can execute sequentially or concurrently. AWS FIS provides pre-packaged action plugins for compute disruption, network impairment, and Systems Manager command execution.
Stop Conditions: Optional in the template syntax (a template can specify none) but essential for any production-like experiment. Stop conditions are linked directly to Amazon CloudWatch alarms . If an experiment causes unintended collateral damage—such as customer-facing 5xx error rates spiking, synthetic transaction latency exceeding thresholds, or unhandled exceptions—the linked CloudWatch alarm transitions to the ALARM state. FIS stops the experiment ; a stopped experiment cannot be resumed.
Service Role: An IAM service role assumed by fis.amazonaws.com that grants FIS the explicit permissions required to manipulate the target resources and invoke Systems Manager documents.
Specific FIS Experiments for Security Readiness
Security teams configure specialized FIS actions to validate detection and response runbooks:
1. Terminating Security and Endpoint Protection Agents
Adversaries often attempt to disable host-based security agents (such as antivirus daemons, file integrity monitors, or the Amazon CloudWatch agent) upon compromising an instance. Responders use the aws:ssm:send-command FIS action to target running instances and execute the AWSFIS-Run-Kill-Process SSM document: {
- "description": "Simulate Malicious Termination of Endpoint Security Agent",
- "targets": {
- "AppInstances": {
- "resourceType": "aws:ec2:instance",
- "resourceTags": {
- "Environment": "Staging",
- "Tier": "Application"
- },
- "selectionMode": "COUNT(1)"
- }
- },
- "actions": {
- "KillSecurityAgent": {
- "actionId": "aws:ssm:send-command",
- "parameters": {
- "documentArn": "arn:aws:ssm:us-east-1::document/AWSFIS-Run-Kill-Process",
- "documentParameters": "{\"ProcessName\": \"security-agent-daemon\"}",
- "duration": "PT5M"
- },
- "targets": {
- "Instances": "AppInstances"
- }
- }
- },
- "stopConditions": [
- {
- "source": "aws:cloudwatch:alarm",
- "value": "arn:aws:cloudwatch:us-east-1:123456789012:alarm:Application5xxErrorRateExceeded"
- }
- ],
- "roleArn": "arn:aws:iam::123456789012:role/FISSecurityExperimentRole"
- }
Validation Goal: Does the absence of heartbeats trigger a CloudWatch alarm? Does an automated Systems Manager runbook restart the agent or quarantine the instance?
2. Network Disruption & Isolation Simulation
Using the aws:network:disrupt-connectivity action, FIS blocks traffic for target subnets (all traffic, or traffic to a specific destination such as Amazon S3 or DynamoDB). Latency and packet-loss faults come from SSM-based actions such as AWSFIS-Run-Network-Latency . This validates whether out-of-band security logging continues streaming when an application's primary egress path is degraded.
3. Resource Starvation (CPU & Memory Spikes)
Adversaries running cryptomining payloads saturate CPU cores. Using AWSFIS-Run-CPU-Stress , FIS forces 100% CPU utilization across target instances. This verifies that CPU alarms, anomaly detection bands, and Auto Scaling or containment workflows respond correctly under heavy load. It does not produce GuardDuty cryptocurrency findings, which depend on network and DNS indicators such as mining-pool lookups.
4. Disabling IAM Credentials and Simulating Policy Revocation
Security runbooks often involve revoking IAM credentials or modifying security group rules during containment. FIS experiments can simulate permission loss or security group changes to verify whether applications degrade gracefully and whether alerting systems notify the SOC of administrative tampering.
AWS Resilience Hub: Assessing Resiliency Policies & Drift
While FIS actively injects faults, AWS Resilience Hub provides a centralized control plane to define, assess, and track the resilience of cloud applications against declared business targets. +-----------------------+ +-----------------------+ +-----------------------+
- | 1. Model Application | ---> | 2. Define Policy | ---> | 3. Assess & Discover |
- | • CloudFormation | | • Target RTO | | • Calculate Est. RTO |
- | • AppRegistry | | • Target RPO | | • Identify Gaps/Drift |
- +-----------------------+ +-----------------------+ +-----------------------+
- |
- v
- +-----------------------+ +-----------------------+ +-----------------------+
- | 6. Re-assess & Track | <--- | 5. Run FIS Chaos Test | <--- | 4. Generate Artifacts |
- | • Continuous Baseline | | • Validate Hypotheses | | • FIS Templates |
- +-----------------------+ +-----------------------+ | • Standard Ops (SOPs) |
- +-----------------------+
- 1. Application Modeling
Resilience Hub discovers and groups application components from multiple AWS sources, including AWS CloudFormation stacks , Terraform state files , AWS Service Catalog AppRegistry , or resource tags. It decomposes the application into functional components (compute, database, storage, networking).
2. Defining Resiliency Policies
Organizations establish explicit business targets for two foundational metrics:
Recovery Time Objective (RTO): The maximum acceptable duration of downtime following a disruption before service must be restored.
Recovery Point Objective (RPO): The maximum acceptable data loss measured in time (e.g., no more than 5 minutes of transactional data lost).
Resilience Hub evaluates these metrics across four distinct disruption scopes :
Application Component: Software bugs, container crashes, or unhandled exceptions.
Infrastructure: Virtual machine hardware failure, underlying EBS volume degradation.
Availability Zone (AZ): Datacenter failure or total AZ connectivity loss.
Region: Comprehensive disaster recovery across geographic areas.
3. Assessment & Gap Identification
When an assessment executes, Resilience Hub compares the actual architectural configuration against the declared resiliency policy. It calculates an Estimated RTO and Estimated RPO .
If a critical relational database is configured as a Single-AZ instance, but the AZ policy requires an RTO of 15 minutes, Resilience Hub flags a policy breach because failing over a Single-AZ database manually requires hours.
It detects architectural drift : when developers deploy new unbacked-up S3 buckets or unclustered compute instances, Resilience Hub surfaces these components as unmanaged risks.
4. Generating FIS Experiment Recommendations
Crucially, Resilience Hub does not just generate static reports; it exports actionable operational code :
Standard Operating Procedures (SOPs): Pre-built Systems Manager Automation runbooks to execute failover or recovery procedures.
Recommended FIS Experiment Templates: Resilience Hub generates ready-to-deploy AWS FIS experiment templates tailored specifically to test the failure modes evaluated during the assessment. Running these experiments empirically proves whether the system satisfies its declared RTO/RPO targets.
GameDays and Tabletop Exercises
Validating incident readiness requires exercising both technical automation and human decision-making. Organizations employ two complementary simulation methodologies:
Tabletop Exercises (Discussion-Based)
A Tabletop Exercise (TTX) is a structured, scenario-driven discussion bringing together cross-functional stakeholders—including security engineers, legal counsel, compliance officers, human resources, public relations, and executive leadership—in a collaborative setting.
Scope: Evaluates decision-making hierarchies, legal disclosure requirements, communication protocols, and executive escalations.
Scenario Examples: A major ransomware attack threatening public data exfiltration; an insider threat leaking AWS root account credentials; discovery of an active zero-day vulnerability in a third-party dependency requiring emergency patching.
Key Questions Explored:
Who has the legal authority to shut down a revenue-generating production system to contain an attack?
What are the regulatory reporting deadlines (e.g., GDPR 72-hour notification, SEC Form 8-K 4-day disclosure rule for material cyber incidents)?
How do we communicate with customers and law enforcement without tipping off the adversary?
Technical GameDays (Live-Fire Simulations)
A Technical GameDay is a hands-on, live-action operational exercise conducted against a production-like staging environment (or controlled production slice). During a GameDay, engineers face realistic, unannounced technical failures or synthetic adversary attacks.
Feature Tabletop Exercise (TTX) Technical GameDay Automated FIS Experiment
Primary Objective Validate governance, communication, and decision policy Validate technical runbooks, detection telemetry, and containment Validate infrastructure self-healing and alert thresholds
Participants Cross-functional leaders (Legal, PR, Execs, SecOps) Hands-on responders (SOC, DevOps, Cloud Engineers) Fully automated (FIS service and CloudWatch)
Environment Conference room / virtual discussion (No live infrastructure) Staging or isolated production sandbox environment Staging or production environments with stop conditions
Duration 2 to 4 hours Half-day to full-day event Minutes (bounded by experiment duration)
Artifact Produced Updated escalation policies, legal playbooks, communication trees Verified runbooks, patched IAM policies, updated alert rules Automated pass/fail metrics, RTO/RPO validation data
The Red, Blue, and White Team Model
Technical GameDays typically organize participants into three structured teams:
Red Team (Adversary Simulation): Injects synthetic attacks, runs FIS templates, terminates security processes, or simulates credential exfiltration. The Red Team must adhere to strict rules of engagement.
Blue Team (Defenders): The active incident response engineers and SOC analysts who must detect, investigate, and contain the simulated intrusion using existing tools (CloudTrail, GuardDuty, Security Hub, Athena, runbooks).
White Team (Referees & Observers): Impartial facilitators who define the exercise boundaries, monitor safety stop conditions, inject situational clues if defenders become completely stuck, and record objective timelines for the debrief.
Identifying Runbook Drift & Operational Gaps
When a GameDay or FIS experiment concludes, the most valuable output is the catalog of discovered operational failures . Common operational gaps surfaced during testing include:
IAM Permission Decay: An automated remediation runbook fails because an administrator updated an IAM permissions boundary or SCP three months earlier, inadvertently revoking the runbook's ability to call ec2:ModifyInstanceAttribute or s3:PutBucketPublicAccessBlock .
Stale Notification Routing: Alert notifications fail to deliver because an Amazon SNS topic is subscribed to an unmonitored distribution list or SMS phone numbers belonging to departed personnel.
EventBridge Schema Mismatches: An automated remediation Lambda function fails because an upstream AWS service updated its finding JSON format, breaking a hardcoded JSON path parser in the custom script.
Telemetry Ingestion Lag: The Blue Team takes 45 minutes to detect an attack because CloudTrail management event delivery to S3 experienced normal propagation delay, revealing that the team should have configured real-time CloudWatch Logs metric filters or EventBridge rules instead of relying on batch S3 queries.
Operationalizing Continuous Validation
To ensure runbooks do not drift, forward-leaning organizations embed chaos testing directly into their CI/CD deployment pipelines :
When a cloud engineering team updates a Terraform or CloudFormation stack, an automated staging pipeline deploys the infrastructure, triggers an AWS FIS experiment to simulate security agent failure, verifies that the SOC alerting pipeline receives the event within 120 seconds, and aborts the release if validation fails.
Exam Tips & Common Traps
Important
FIS Stop Conditions Are the Safety Net: Exam scenarios frequently ask how to safely execute chaos testing in production without risking widespread outages. The key mechanism is the CloudWatch alarm stop condition . If an option mentions running FIS experiments without stop conditions or relying on manual console monitoring to stop an experiment, it is incorrect. FIS stops the experiment as soon as a stop-condition alarm enters the ALARM state.
Warning
Common Trap on Resilience Hub Capabilities: Do not confuse AWS Resilience Hub with AWS Backup or AWS Fault Injection Service. Resilience Hub does not perform data backups, and it does not directly execute chaos attacks. Instead, Resilience Hub assesses application architectures against declared RTO/RPO policies, detects drift, and generates recommended FIS experiment templates and SSM automation SOPs.
Tip
Selecting the Right Exercise Type: On the SCS-C03 exam, pay close attention to what the question asks you to validate:
If the scenario requires validating executive communication, regulatory breach notification timelines (e.g., SEC/GDPR), and legal authorities , choose a Tabletop Exercise .
If the scenario requires validating real-time alerting, engineer triage speed, and hands-on runbook execution under simulated adversary pressure , choose a Technical GameDay .
If the scenario requires continuous, programmatic validation of infrastructure resilience and automated failover bounded by strict error rate alarms , choose AWS Fault Injection Service (FIS) .