A company's security team needs to monitor network traffic for a multi-tier web application. They suspect that a compromised Amazon EC2 instance in a private subnet is attempting to perform unauthorized network scans on other resources within the same Virtual Private Cloud (VPC). The team needs to capture the source IP, destination IP, source port, destination port, and protocol for all network traffic at the subnet level without installing any host-based software. Which solution will meet these requirements?
- ADeploy AWS WAF on the subnet to monitor and log all Layer 3 and Layer 4 IP traffic flowing between the EC2 instances.
- BConfigure Network ACLs on the private subnet to log all connection metadata directly to AWS CloudTrail.
- Enable VPC Flow Logs on the private subnet and publish the logs to an Amazon S3 bucket.Cevap
- DEnable AWS Shield Advanced on the VPC to log internal host-to-host traffic metadata.
Cevap
Enable VPC Flow Logs on the private subnet and publish the logs to an Amazon S3 bucket.
The correct solution is to enable VPC Flow Logs on the private subnet and publish the logs to an Amazon S3 bucket. VPC Flow Logs captures IP traffic metadata (source/destination IPs, ports, and protocol) at the Elastic Network Interface (ENI) level without needing any agents. It can deliver these logs to Amazon S3 or CloudWatch Logs.
Adım Adım Çözüm
Anahtar Kavram
Agentless network traffic metadata logging via VPC Flow Logs