An organization receives an alert that indicates that an EC2 instance behind an ELB Classic Load Balancer has been compromised. What techniques will limit lateral movement and allow evidence gathering?
A.
Remove the instance from the load balancer and terminate it.
B.
Remove the instance from the load balancer, and shut down access to the instance by tightening the security group.
C.
Reboot the instance and check for any Amazon CloudWatch alarms.
D.
Stop the instance and make a snapshot of the root EBS volume.
I think B is the best answer. Page 34
https://d1.awsstatic.com/whitepapers/aws_security_incident_response.pdf
No mention of stopping the EC2 instance. Just isolation so information can be gathered.
It is possible to do snapshot while the instance is running.
yes you're right (B is best). Page 36 shows option B and D are both correct, but option B will allow more evidences (volatile evidence ....such as memory or network traffic) to be gathered.
Also the question says "limit lateral movement" and not completely stop movement or access.
Agree. Answer is B.
Shutting down the instance will change the state of it and more probable destroy transient evidence. The snapshot must be done while the instance is on.
Ans is D, since B cannot interrupt the connection and doesn't mention how to gather evidence
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-connection-tracking.html
Removing the compromised instance from the load balancer prevents further traffic from reaching it. Adjusting the security group to shut down access helps to limit potential lateral movement, preventing the attacker from reaching other resources in your network. It also allows time for a detailed investigation to take place without the risk of ongoing malicious activity.
Please note, creating a snapshot of the EBS volume (option D) can be a part of an incident response process for deeper forensic analysis. However, the question specifically asked about techniques to "limit lateral movement and allow evidence gathering" without implying a detailed forensic analysis, thus making option B more suitable.
The questions specially states that we need to perform a cyber threat investigation. However once the endpoint is turned off or restarted the opportunity for forensic analysis will be taken away. B limits the lateral movement and still allows the security engineer to investigate the situation.
My anwser is D. It states to limit lateral movement so security groups will do nothing as they will not block any outbound traffic. I know memory dump is always best to gather all data for inspection, but the requirement is clear. "limit lateral movement" so we keep to the requirement while still be able to investigate the snapshot of the EBS.
B is correct Here. Question ask 2 requirements. Stop Bilateral movement and Evidence gathering. A shutdown system wont help much in evidence/forensic investigations.
C is correct, not sure anyone has faced a security incident before. i work regularly with security team....you NEVER reboot / Shutdown the instance in question while evidence gathering like collecting logs etc. as that affects evidence gathering
you remove it from LB and disable all services so it is not in production.
it's D - lateral movement means potential risk to the rest of the environment. Offline investigation (where instance is shut down) means that it can no longer affect the rest of the environment. Snapshot of EBS volume can be used to create new volumes that can be mounted onto a forensic EC2 instance for deep analysis offline.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mojoa
Highly Voted 3 years, 7 months agos3an
3 years, 7 months agojosellama2000
Highly Voted 3 years, 7 months agoa1234321606
Most Recent 5 months, 3 weeks agoOCHT
1 year, 10 months agoITGURU51
1 year, 11 months agoDmosh
2 years agoVijiTu
2 years, 7 months agopmjcr
3 years, 5 months agoryan112277
3 years, 5 months agodumma
3 years, 5 months agosanjaym
3 years, 5 months agoChinkSantana
3 years, 5 months agoargol
3 years, 6 months agoSitender
3 years, 6 months agood87
3 years, 6 months agood87
3 years, 6 months agoNANDY666
3 years, 6 months agoMelymel
3 years, 6 months agoshooricg
3 years, 6 months agodevjava
3 years, 6 months ago