A logistics company's security operations team suspects that an Amazon EC2 instance in a private subnet is compromised and communicating with a malicious command-and-control server. The team must capture network flow details, including source and destination IP addresses, ports, and protocols, to confirm this activity and analyze the connection patterns. The logging solution must capture all traffic without altering the existing network architecture or impacting network performance. Which strategy should the solutions architect recommend to monitor this network traffic?
- Enable VPC Flow Logs on the subnet, publishing the logs to an Amazon S3 bucket, and use Amazon Athena to query and analyze the traffic details.Answer
- BEnable logging on the subnet's Network ACLs to record all traffic flows, and configure security groups to dynamically track the stateful return traffic.
- CDeploy AWS WAF at the VPC subnet level to inspect all inbound and outbound traffic, and configure WAF logging to save network flows to Amazon S3.
- DEnable AWS Shield Advanced on the EC2 instances to monitor network-level flow data, and use the AWS Shield console to investigate outbound connections.
Answer
Enable VPC Flow Logs on the subnet, publishing the logs to an Amazon S3 bucket, and use Amazon Athena to query and analyze the traffic details.
Enabling VPC Flow Logs at the subnet level allows the security team to capture metadata about the IP traffic going to and from network interfaces in the subnet. Since VPC Flow Logs is an out-of-band feature, it has no impact on network latency or throughput. Storing these logs in Amazon S3 and querying them using Amazon Athena provides a highly scalable and cost-effective method to analyze the network flow data, locate the destination IP addresses, and verify whether the connections were accepted or rejected.
Step-by-Step Solution
Key Concept
VPC Flow Logs for network threat detection and monitoring
Estimated Time:2m 0s