Study guide
4.1 Forensic Artifact Capture & Chain of Custody
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
4.1 Forensic Artifact Capture & Chain of Custody
Key Takeaways Explain This Topic AI
Volatile evidence collection must adhere to the RFC 3227 order of volatility; volatile system memory (RAM) must be acquired before stopping, rebooting, or detaching network interfaces.
AWS Systems Manager Run Command enables non-interactive, auditable memory acquisition with LiME (Linux) or WinPmem (Windows) onto a dedicated evidence volume and then Amazon S3, without interactive SSH sessions contaminating memory or shell history.
EBS snapshots encrypted with the default AWS-managed KMS key (aws/ebs) cannot be shared across accounts; snapshots must be encrypted or re-encrypted with a Customer Managed Key (CMK) prior to cross-account sharing.
In the target Forensics account, shared snapshots must be copied and re-encrypted with a local CMK to establish independent administrative custody and prevent deletion by the source account.
Amazon S3 Object Lock in Compliance mode enforces Write-Once-Read-Many (WORM) immutability that cannot be overwritten or deleted by any IAM principal or the root user, while Legal Holds provide open-ended preservation during active investigations.
Last updated: September 2026
4.1 Forensic Artifact Capture & Chain of Custody
Cloud incident response and digital forensics diverge fundamentally from traditional on-premises investigations. In an on-premises data center, digital forensic examiners often pull physical power cables to freeze machine state, connect hardware write-blockers to physical hard drives, or inspect network taps. In Amazon Web Services (AWS), the underlying physical infrastructure is managed entirely by AWS under the Shared Responsibility Model. Responders cannot physically access hypervisors, server chassis, or physical storage arrays. Instead, cloud forensics operates programmatically through software-defined application programming interfaces (APIs), hypervisor-level snapshotting, and managed orchestration services.
Executing forensic investigations in the cloud requires rigorous adherence to forensic science standards, specifically the RFC 3227 Order of Volatility , while preserving an unbroken, legally defensible chain of custody . A single misstep—such as prematurely rebooting an Amazon EC2 instance or using an interactive SSH session—can destroy vital volatile memory artifacts, alter disk access timestamps, and invalidate evidence in legal proceedings.
The RFC 3227 Order of Volatility in AWS
RFC 3227 ( Guidelines for Evidence Collection and Archiving ) establishes the principle that digital evidence must be captured starting with the most volatile data sources and proceeding to the least volatile. In AWS environments, the order of volatility maps directly to cloud primitives:
- Volatility Tier Evidence Artifact AWS / System Representation Risk of Data Loss
- 1. Highest CPU Registers & Cache Dynamic processor state Destroyed instantly on any state transition
2. High System Memory (RAM) Active processes, unencrypted keys, memory-only malware, open sockets Destroyed completely upon instance Stop , Reboot , or Terminate
3. High Network & Routing State ARP cache, TCP/UDP sockets, kernel conntrack tables Lost if network interfaces are detached or rebooted
4. Moderate Temporary File Systems /tmp , swap space, pagefiles, ephemeral instance stores Wiped on instance stop or hardware migration
5. Low Non-Volatile Block Storage Amazon EBS volumes, OS disk partitions Preserved on disk; captured via point-in-time EBS snapshots
6. Lowest Remote Telemetry & Logs AWS CloudTrail, VPC Flow Logs, DNS query logs, S3 access logs Persisted externally in centralized logging accounts
Exam Tip : The AWS Certified Security – Specialty exam frequently presents scenarios where an EC2 instance is suspected of being compromised or running cryptomining malware. Questions will offer options to immediately stop ( ec2:StopInstances ), reboot, or terminate the instance. Never choose to stop, reboot, or terminate an instance before capturing volatile RAM. Stopping an EC2 instance immediately purges the hypervisor-allocated physical memory, permanently destroying unencrypted encryption keys, running malware binaries injected into process memory, and active network connections.
Volatile Data Acquisition: Live Memory Capture Mechanics
Capturing the physical memory (RAM) of an EC2 instance running in production presents a technical challenge: how do responders acquire memory without altering the target system?
The Problem with Interactive Logins (SSH / RDP)
Connecting interactively to a compromised machine via SSH or Windows Remote Desktop (RDP) introduces severe forensic contamination:
Spawns interactive shells (e.g., bash , powershell.exe ), altering memory tables and overwriting processor registers.
Modifies access and change timestamps ( atime , ctime ) across system directories.
Appends commands to .bash_history or Windows Event Logs, potentially tipping off an adversary who may have active persistence or anti-forensic wiper scripts configured to execute upon administrative login.
Allocates memory pages that overwrite the very memory space where malware or cryptographic keys reside.
Non-Interactive Acquisition via AWS Systems Manager Run Command
To minimize forensic footprint and eliminate the need for open administrative network ports (such as TCP port 22 or 3389), security teams use AWS Systems Manager (SSM) Run Command .
Loading diagram...
SSM Run Command communicates with the pre-installed SSM Agent daemon over an outbound HTTPS channel (TCP port 443) via AWS PrivateLink VPC endpoints. This architecture allows command execution even after an instance has been isolated from the public internet.
Memory Acquisition Tooling: LiME and WinPmem
Linux Systems (LiME - Linux Memory Extractor) : LiME is an open-source kernel module that allows volatile memory acquisition from Linux-based devices. Because LiME operates inside kernel space, it minimizes interaction with user space processes. Pre-compiled LiME kernel modules matching the exact target kernel version (e.g., Amazon Linux 2, Amazon Linux 2023, Ubuntu, RHEL) can be retrieved from a central, read-only S3 repository and loaded via insmod . The memory dump can be written in raw or LiME format to a secondary, dedicated forensic EBS volume, or sent over a network socket (LiME's tcp: output) to a collection host, and then uploaded to Amazon S3.
Windows Systems (WinPmem) : WinPmem is an open-source physical memory acquisition driver and executable for Windows. It provides a read-only view of physical RAM through an acquisition driver, writing raw memory images ( .raw or .dmp ) directly to a storage target without requiring interactive desktop sessions.
Evidence-Volume Pipeline
Rather than saving a 64 GB or 128 GB memory dump to the compromised root volume (which would alter disk structures, overwrite deleted unallocated space, and potentially run out of disk space), the acquisition script writes the image to a separately attached evidence volume (or a network listener), hashes it, and then uploads it to Amazon S3: # Example conceptual snippet executed non-interactively via SSM Run Command
- # Loads LiME, writes the image to a separately attached evidence volume
- # (/mnt/evidence, not the suspect root disk), then hashes and uploads it
- insmod /mnt/evidence/lime-<kernel-release>.ko "path=/mnt/evidence/ram.raw format=raw"
- sha256sum /mnt/evidence/ram.raw > /mnt/evidence/ram.raw.sha256
- aws s3 cp /mnt/evidence/ram.raw s3://forensic-evidence-vault-111122223333/case-9021/ram.raw \
- -sse aws:kms \
- -sse-kms-key-id arn:aws:kms:us-east-1:111122223333:key/abc-123
- Automated EBS Snapshot Creation and Isolation
Once volatile memory is captured, the next priority is acquiring the non-volatile block storage volumes (Amazon EBS) attached to the compromised instance. EBS snapshots provide block-level, point-in-time, crash-consistent copies of EBS volumes backed by Amazon S3.
Crash-Consistent Multi-Volume Snapshots
Modern enterprise applications often stripe data across multiple EBS volumes (such as an OS volume, a transaction log volume, and a database data volume). Taking snapshots of individual volumes sequentially can introduce time skews, corrupting database consistency.
AWS provides the ec2:CreateSnapshots API (plural), which takes synchronized, multi-volume crash-consistent snapshots across all EBS volumes attached to an EC2 instance simultaneously. This guarantees that all snapshots share the exact same point-in-time boundary.
- Forensic Tagging and Metadata Preservation
- Snapshots must be tagged immediately upon creation to establish an auditable record: {
- "IncidentId": "INC-2026-0929-A",
- "SourceInstanceId": "i-0a1b2c3d4e5f67890",
- "SourceVolumeId": "vol-0123456789abcdef0",
- "Custodian": "arn:aws:iam::111122223333:role/ForensicsOrchestratorRole",
- "AcquisitionTimestamp": "2026-09-29T14:30:00Z",
- "EvidenceClassification": "Confidential-Legal-Hold"
- }
- Automated Forensics Orchestrator for Amazon EC2
Manual forensic acquisition during an active security incident is prone to human error, delays, and accidental evidence corruption. The Automated Forensics Orchestrator for Amazon EC2 (built upon AWS Step Functions, AWS Lambda, Amazon EventBridge, and SSM) implements an automated, repeatable forensic pipeline:
Loading diagram...
Orchestration Steps
Trigger : An Amazon GuardDuty high-severity finding (e.g., Backdoor:EC2/C&CActivity.B!DNS ) matches an EventBridge rule, passing the instance ID to AWS Step Functions.
Volatile Acquisition : Step Functions triggers an SSM Run Command document to extract RAM and volatile system artifacts directly to a centralized S3 evidence bucket.
Network Quarantine : The state machine swaps the instance's Security Groups to an isolated Quarantine Security Group.
Disk Snapshotting : The state machine invokes ec2:CreateSnapshots across all attached volumes.
Cross-Account Transfer : Snapshots are re-encrypted with a shared Customer Managed Key (CMK) and shared with the Forensics account.
Forensic Volume Reconstruction : In the Forensics account, an automated worker copies the snapshot, creates a new EBS volume, and attaches it as a non-boot secondary drive to an isolated forensic analysis workstation.
Cross-Account Snapshot Sharing and KMS Encryption Architecture
A critical requirement for secure investigations is moving evidence out of the compromised production account and into an isolated, air-gapped Forensics Account . This prevents an attacker who possesses administrative credentials in the production account from deleting snapshots, modifying forensic images, or monitoring the investigation.
However, EBS snapshot sharing across accounts is strictly governed by AWS Key Management Service (AWS KMS) cryptographic boundaries.
Loading diagram...
The Default AWS Managed Key ( aws/ebs ) Limitation
AWS encrypts EBS volumes by default using the AWS-managed key aws/ebs if no customer key is specified.
Caution
Critical Exam Rule : Snapshots encrypted with default AWS-managed KMS keys ( aws/ebs ) CANNOT be shared across AWS accounts. AWS explicitly prohibits modifying snapshot attributes or sharing keys owned by AWS. If an incident responder attempts to share a snapshot encrypted with alias/aws/ebs , the API call ec2:ModifySnapshotAttribute will fail with an AccessDeniedException .
The Re-Encryption and Sharing Workflow
To successfully transfer an EBS snapshot to an isolated Forensics account, the following sequence must be followed:
Re-encrypt in Source Account (if encrypted with aws/ebs or unencrypted) : Responders must copy the snapshot within the source account, specifying a Customer Managed Key (CMK) : ec2:CopySnapshot --source-snapshot-id snap-111 --kms-key-id arn:aws:kms:region:source-account:key/cmk-shared .
Configure Cross-Account KMS Key Policy : The CMK's key policy in the source account must explicitly grant permissions to the Forensics account (or a specific IAM role within the Forensics account): {
- "Sid": "AllowForensicsAccountToUseKey",
- "Effect": "Allow",
- "Principal": {
- "AWS": "arn:aws:iam::222233334444:root"
- },
- "Action": [
- "kms:DescribeKey",
- "kms:Decrypt",
- "kms:ReEncrypt*",
- "kms:CreateGrant"
- ],
- "Resource": "*"
- }
Share the Snapshot : The source account grants volume creation permission to the Forensics account: aws ec2 modify-snapshot-attribute \
- -snapshot-id snap-cmk-encrypted \
- -attribute createVolumePermission \
- -operation-type add \
- -user-ids 222233334444
Copy and Re-Encrypt in the Forensics Account : The Forensics account must immediately copy the shared snapshot into its own account, encrypting the copy with a local Customer Managed Key ( CMK-Forensics-Local ) owned exclusively by the Forensics account: aws ec2 copy-snapshot \
- -source-region us-east-1 \
- -source-snapshot-id snap-cmk-encrypted \
- -destination-region us-east-1 \
- -kms-key-id arn:aws:kms:us-east-1:222233334444:key/cmk-forensics-local
Why Is the Destination Copy Mandatory?
If the Forensics account simply creates an EBS volume directly from the shared snapshot without copying it, the source account retains ultimate ownership of the underlying snapshot and the source KMS key. If an adversary in the production account deletes the snapshot or alters the KMS key policy, the forensic volume and ongoing analysis in the Forensics account are disrupted. Copying and re-encrypting the snapshot establishes independent legal custody .
Evidence Preservation in Amazon S3: Object Lock and Legal Holds
Forensic artifacts—including memory dumps, process trees, network packet captures ( .pcap ), and disk bit-stream images ( .raw / .E01 )—must be protected against tampering, overwriting, and deletion. Amazon S3 provides hardware-grade WORM (Write Once, Read Many) protection via S3 Object Lock .
Prerequisites for S3 Object Lock
S3 Bucket Versioning : Must be permanently enabled. Object Lock operates by locking specific object versions.
Enabling Object Lock : You can turn it on when you create a bucket or later on an existing bucket (Amazon S3 enables versioning for you). Once enabled, Object Lock cannot be disabled and versioning cannot be suspended.
Compliance Mode vs. Governance Mode
Feature Governance Mode Compliance Mode
Protection Level Administrative protection against accidental deletion Strict WORM regulatory and legal immutability
Bypass Capability Users with s3:BypassGovernanceRetention permission can delete versions or disable lock NO ONE can bypass retention, including the AWS account root user or AWS Support
Retention Shortening Allowed by privileged IAM users Strictly prohibited ; retention periods can only be extended
Primary Use Case Operational backups, ransomware protection with administrative override Forensic evidence preservation , criminal investigation artifacts, regulatory compliance
Exam Tip : For legal proceedings and forensic integrity, S3 Object Lock in Compliance Mode is mandatory. If an exam question asks how to guarantee that neither a rogue administrator, compromised root user credentials, nor an external adversary can delete forensic evidence during an ongoing investigation, the answer is always Compliance Mode .
S3 Legal Holds
In addition to retention periods (which expire after a defined duration, such as 7 years), S3 Object Lock provides a Legal Hold mechanism:
A Legal Hold is an explicit binary toggle ( ON / OFF ) applied to an object version.
It does not have an expiration date; it remains active until explicitly removed by an authorized principal possessing the s3:PutObjectLegalHold permission.
A Legal Hold can be applied even if an object has no retention period or if its retention period has expired. This provides indefinite preservation while court litigation or regulatory inquiry is underway. {
- "Status": "ON"
- }
// Applied via: aws s3api put-object-legal-hold --bucket forensic-vault --key case-9021/ram.raw --legal-hold Status=ON
Cryptographic Hash Verification & Chain of Custody
A legally defensible digital investigation requires proving that evidence presented during trial or an executive audit is an exact bit-for-bit duplicate of the data that existed on the compromised machine at the moment of acquisition.
Cryptographic Hashing Standards
Responders calculate cryptographic hashes (typically SHA-256 ) at each stage of the evidence lifecycle:
At Inception (Source Instance) : When LiME streams memory or dcfldd / dd creates a disk image, the source tool computes a SHA-256 digest.
In S3 Vault : Amazon S3 natively supports checking object integrity using SHA-256 checksums ( x-amz-checksum-sha256 ) uploaded in the request header, verifying that zero network transit corruption occurred.
In the Forensics Account : When the forensic image or cloned EBS volume is attached to the analysis workstation, the examiner recalculates the SHA-256 checksum and compares it against the recorded manifest. Source Memory Capture SHA-256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
- Target Forensics S3 SHA-256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
- Result: Bit-for-Bit Integrity Cryptographically Verified (Match)
- The Chain of Custody Log
The chain of custody log is an auditable, tamper-resistant document that records:
Identity of Custodian : IAM Role ARN, SAML Federation Identity, or responder name.
Exact Timestamps : Coordinated Universal Time (UTC) timestamps of acquisition, transfer, and receipt.
Source Resource Identifiers : AWS Account ID, Region, Instance ID, Elastic Network Interface (ENI) ID, Volume ID, and Snapshot ID.
Tooling and Parameter Specifications : Exact version of LiME/WinPmem, kernel release version, command-line arguments.
Cryptographic Hashes : Initial SHA-256 checksum, intermediate transfer hashes, and destination validation hashes.
S3 Object Version ID and KMS Key ARN : Proving immutable location and cryptographic key custody.
Specialty Exam Pitfalls & Traps
Rebooting to "Clean Memory" : Never reboot an instance to inspect it. Stopping or rebooting an EC2 instance flushes volatile memory and releases the underlying physical host allocation, erasing all RAM artifacts.
Attempting to Share Snapshots Encrypted with aws/ebs : Default AWS-managed KMS keys do not support cross-account sharing. Snapshots must be copied to a Customer Managed Key (CMK) before sharing.
Failing to Copy Shared Snapshots in the Destination Account : Sharing a snapshot grants the destination account read access, but the source account retains ownership. The destination account must copy the snapshot and re-encrypt it with its own CMK to preserve evidence if the source account deletes the original snapshot.
Confusing Governance Mode with Compliance Mode : Governance mode allows privileged users with s3:BypassGovernanceRetention to overwrite or delete objects. Only Compliance mode prevents all users, including the root user, from deleting evidence.
Interactive SSH Usage : Logging in via SSH or RDP pollutes RAM, alters system files, and updates access timestamps. Always prefer non-interactive execution via AWS Systems Manager Run Command.