A financial services company hosts a critical transaction application on Amazon EC2 instances within a private subnet. The security team must implement a solution to monitor all inbound and outbound network traffic at the subnet level to detect network anomalies, such as active port scanning and unauthorized SSH connection attempts, without impacting application performance. Which solution meets these requirements?
- Enable VPC Flow Logs on the subnet to capture traffic data, and enable Amazon GuardDuty to analyze the flow logs and generate security findings.Answer
- BConfigure stateful Network ACLs at the subnet level to log all rejected traffic, and use AWS Shield Standard to analyze the logs for network anomalies.
- CDeploy AWS WAF at the subnet level to inspect all inbound TCP packets, and configure a custom rule to detect and block port scanning.
- DConfigure Security Groups to statelessly log traffic at the subnet level, and use Amazon CloudWatch Logs to trigger alerts for unauthorized SSH attempts.
Answer
Enable VPC Flow Logs on the subnet to capture traffic data, and enable Amazon GuardDuty to analyze the flow logs and generate security findings.
The correct solution involves enabling VPC Flow Logs and Amazon GuardDuty. VPC Flow Logs capture network traffic data at the subnet level without introducing any performance overhead on the EC2 instances. Amazon GuardDuty automatically processes these flow logs out-of-band to identify malicious activity, such as port scanning or unauthorized SSH brute-force attempts.
Step-by-Step Solution
Key Concept
Out-of-band network threat detection using VPC Flow Logs and Amazon GuardDuty
Estimated Time:2m 0s