PIVTR-D
RCloud playbooks

AWS playbooks

This page covers AWS accounts and the organization above them: the logs to keep, what to search, and the playbooks for 22 incident types in seven categories. Each playbook lists where to look and the commands to contain it. Commands use AWS CLI v2.

Searches run against CloudTrail event history or a CloudTrail Lake event data store. CloudTrail Lake closed to new customers on May 31, 2026, and existing customers keep using it. Without an event data store, run the same searches in Amazon Athena over the trail's S3 logs, or in CloudWatch, which AWS names as the replacement.

Playbooks

Identity and access

Stolen credentials, taken-over accounts and the access an attacker leaves behind.

Compute and containers

Workloads, servers and clusters used or abused by an attacker.

Data and storage

Exposed, copied, encrypted or deleted data, and stolen secrets.

Network and edge

Attacks on availability and on names and endpoints you own.

Pipelines and supply chain

Build systems and image registries that reach production.

Evasion and guardrails

Logging and controls turned off to hide an attack.

Provider and accidental

Incidents with no attacker: a vendor's bug, a provider's or operator's mistake, or a provider outage.

First 15 minutes, any incident

#Item
1Work from a responder role in a separate security account that the suspect identity cannot modify
2Confirm the trail is logging. List trails with aws cloudtrail describe-trails, then check IsLogging in the status: aws cloudtrail get-trail-status --name <trail>
3Export event history from us-east-1 and from every Region in use. IAM, STS global endpoint and Organizations events land in us-east-1. See Evidence
4Record the access key ID or the role's Amazon Resource Name (ARN) from the alert. AKIA keys are long-term user keys. ASIA keys are temporary STS credentials
5Pull GuardDuty findings, highest severity first: aws guardduty list-findings --detector-id <id> --sort-criteria '{"AttributeName":"severity","OrderBy":"DESC"}'
6Check the AWS Health Dashboard and Support Center for a notice and case about exposed credentials
7Snapshot volumes of involved instances and tag them with the case number before any isolation

Native detections to playbooks

Each row names a native finding, the service that raises it, and the playbook to open first.

DetectionSourceOpen
CredentialAccess:IAMUser/CompromisedCredentialsGuardDutyIAM user access keys
AttackSequence:IAM/CompromisedCredentialsGuardDutyIAM user access keys
UnauthorizedAccess:IAMUser/ConsoleLoginSuccess.BGuardDutyConsole or Identity Center user
InitialAccess:IAMUser/AnomalousBehaviorGuardDutyConsole or Identity Center user
Persistence:IAMUser/AnomalousBehaviorGuardDutyRoles, keys, trust policies
Policy:IAMUser/RootCredentialUsageGuardDutyRoot or management account
External access finding on an IAM role, with principal.AWS outside the zone of trustIAM Access AnalyzerCross-account roles
UnauthorizedAccess:IAMUser/InstanceCredentialExfiltration.OutsideAWSGuardDutyEC2 instance role
UnauthorizedAccess:IAMUser/InstanceCredentialExfiltration.InsideAWSGuardDutyEC2 instance role
Backdoor:EC2/C&CActivity.BGuardDutyEC2 instance
AttackSequence:EKS/CompromisedClusterGuardDuty (EKS Protection)Amazon EKS
PrivilegeEscalation:Kubernetes/AnomalousBehavior.WorkloadDeployed!PrivilegedContainerGuardDuty (EKS Protection)Amazon EKS
CryptoCurrency:EC2/BitcoinTool.B!DNSGuardDutyEC2 and quota abuse
Policy:S3/BucketPublicAccessGrantedGuardDutyS3
Exfiltration:S3/AnomalousBehaviorGuardDuty (S3 Protection)S3
CredentialAccess:RDS/AnomalousBehavior.SuccessfulLoginGuardDuty (RDS Protection)RDS and snapshots
External access finding on an RDS DB snapshot or DB cluster snapshotIAM Access AnalyzerRDS and snapshots
Impact:S3/AnomalousBehavior.DeleteGuardDuty (S3 Protection)Deletion and ransomware
For GetSecretValue or BatchGetSecretValue: CredentialAccess:IAMUser/AnomalousBehaviorGuardDutySecrets Manager and SSM
DDoSDetected metric above zeroShield Advanced (CloudWatch AWS/DDoSProtection)Shield and WAF
External access finding on an IAM role, with principal.Federated set to an OIDC providerIAM Access AnalyzerCI/CD and OIDC trust
External access finding on an ECR repositoryIAM Access AnalyzerECR images
Stealth:IAMUser/CloudTrailLoggingDisabledGuardDutyCloudTrail, GuardDuty, SCPs
DefenseEvasion:IAMUser/AnomalousBehaviorGuardDutyCloudTrail, GuardDuty, SCPs
Impact:IAMUser/AnomalousModelInvocationGuardDuty AI ProtectionAmazon Bedrock
Impact:IAMUser/CostHarvestingGuardDuty AI ProtectionAmazon Bedrock
Impact:IAMUser/PromptInjection.DirectGuardDuty AI ProtectionAmazon Bedrock

AWS documentation: GuardDuty active finding types and IAM finding types; IAM Access Analyzer supported resource types and filter keys; Shield Advanced CloudWatch metrics. GuardDuty finding types, including AI Protection, checked October 2026; other topics checked September 2026.

Before an incident

LogDefault retentionTurn on / keep
CloudTrail event history90 days, management events only, per RegionNothing to turn on. It keeps recording when a trail is stopped. Export what you need before day 90
CloudTrail trailSet by lifecycle rules on the destination S3 bucketAn organization trail for all Regions, created in the management account or a delegated administrator account. Member accounts cannot stop or change it. Turn on log file validation with --enable-log-file-validation
CloudTrail Lake event data storeOne-year extendable pricing: 366 days default, up to 3,653. Seven-year pricing: 2,557 daysClosed to new customers since May 31, 2026. Existing customers keep SQL search across accounts and Regions. An organization event data store also covers new member accounts. AWS recommends CloudWatch for new setups
CloudTrail data events for S3 (AWS::S3::Object) and Lambda (AWS::Lambda::Function)Not logged by default. Not shown in event historyAdd advanced event selectors on sensitive buckets and functions. Data events cost extra
S3 server access logsDisabled by default. Delivery is best effortEnable on sensitive buckets as a second record of object access
VPC Flow LogsNone until you create a flow log. Retention is set at the destinationFlow logs contain no packet content. Create one per VPC: aws ec2 create-flow-logs --resource-type VPC --resource-ids <vpc-id> --traffic-type ALL --log-destination-type s3 --log-destination arn:aws:s3:::<bucket>/<prefix>/
GuardDuty findings90 daysEnable in every Region. Add a publishing destination to S3 so findings outlive 90 days. Enable S3 Protection for findings built on S3 data events, and AI Protection where you use Bedrock or SageMaker AI
IAM Access AnalyzerShows current access. External access analysis is freeCreate an external access analyzer with the organization as zone of trust, in each Region you use
Organizations service control policies (SCPs)Policy changes appear in CloudTrail in us-east-1 onlyKeep SCPs that deny changes to CloudTrail, GuardDuty and AWS Config, and a Region deny for Regions you do not use

AWS documentation: CloudTrail event history, concepts, data events, organization trails, log file validation and Lake pricing; S3 server access logging; VPC Flow Logs; GuardDuty findings export; IAM Access Analyzer; Organizations CloudTrail logging. CloudTrail Lake availability change checked October 2026; other topics checked September 2026.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.