SCS-C02 · Question #32
A security engineer needs to develop a process to investigate and respond to potential security events on a company's Amazon EC2 instances. All the EC2 instances are backed by Amazon Elastic Block Sto
The correct answer is A. Gather any relevant metadata for the compromised EC2 instance. Enable termination protection. C. Use Systems Manager Run Command to invoke scripts that collect volatile data. E. Create a snapshot of the compromised EC2 instance's EBS volume for follow-up investigations.. A proper EC2 forensic investigation requires isolating the instance with a security group, collecting volatile memory via SSM Run Command, and snapshotting EBS volumes for non-volatile evidence.
Question
A security engineer needs to develop a process to investigate and respond to potential security events on a company's Amazon EC2 instances. All the EC2 instances are backed by Amazon Elastic Block Store (Amazon EBS). The company uses AWS Systems Manager to manage all the EC2 instances and has installed Systems Manager Agent (SSM Agent) on all the EC2 instances. The process that the security engineer is developing must comply with AWS security best practices and must meet the following requirements:
- A compromised EC2 instance's volatile memory and non-volatile memory must be preserved for
forensic purposes.
- A compromised EC2 instance's metadata must be updated with corresponding incident ticket
information.
- A compromised EC2 instance must remain online during the investigation but must be isolated
to prevent the spread of malware.
- Any investigative activity during the collection of volatile data must be captured as part of the
process. Which combination of steps should the security engineer take to meet these requirements with the LEAST operational overhead? (Choose three.)
Options
- AGather any relevant metadata for the compromised EC2 instance. Enable termination protection.
- BGather any relevant metadata for the compromised EC2 instance. Enable termination protection.
- CUse Systems Manager Run Command to invoke scripts that collect volatile data.
- DEstablish a Linux SSH or Windows Remote Desktop Protocol (RDP) session to the compromised
- ECreate a snapshot of the compromised EC2 instance's EBS volume for follow-up investigations.
- FCreate a Systems Manager State Manager association to generate an EBS volume snapshot of
How the community answered
(37 responses)- A68% (25)
- B8% (3)
- D19% (7)
- F5% (2)
Why each option
A proper EC2 forensic investigation requires isolating the instance with a security group, collecting volatile memory via SSM Run Command, and snapshotting EBS volumes for non-volatile evidence.
Gathering metadata and enabling termination protection prevents accidental or automated termination of the compromised instance, preserving forensic evidence. Applying an isolation security group (with no inbound/outbound rules) cuts off network communication without shutting the instance down, keeping volatile memory intact while meeting the requirement to remain online.
This option describes a different sequence or set of actions that does not fully satisfy the stated requirements for isolation and evidence preservation in the correct order.
AWS Systems Manager Run Command allows scripts to execute on the instance without opening SSH or RDP, which could alter volatile memory. This method safely captures volatile data such as running processes, network connections, and memory contents in accordance with forensic best practices.
Establishing an SSH or RDP session to a compromised instance is a forensic anti-pattern because interactive logins modify volatile memory, update file access times, and can inadvertently destroy evidence or allow lateral movement by an attacker.
Creating an EBS snapshot captures the non-volatile state of all attached volumes at a point in time, preserving the file system, logs, and other disk artifacts needed for forensic analysis. Snapshots can be analyzed in a separate, clean environment without modifying the original evidence.
A Systems Manager State Manager association creates scheduled associations, not immediate one-time actions. Using it for forensic snapshot capture introduces unnecessary delay and is designed for ongoing configuration management, not incident response.
Concept tested: EC2 forensic isolation and evidence preservation
Source: https://docs.aws.amazon.com/security/incident-response/latest/userguide/ir-cloud-best-practices.html
Community Discussion
No community discussion yet for this question.