CIS Amazon Web Services Foundations Benchmark v1.2.0/Logging/31 of 49
2.9Ensure VPC flow logging is enabled in all VPCs
Control family: Logging
Control description
VPC Flow Logs is a feature that enables you to capture information about the IP traffic going to and from network interfaces in your VPC. After you've created a flow log, you can view and retrieve its data in Amazon CloudWatch Logs. It is recommended that VPC Flow Logs be enabled for packet "Rejects" for VPCs.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Flow logs record the connections going in and out of the network interfaces in a VPC. Even if you only keep rejected connections, as the benchmark asks at the minimum, you can see scanning, blocked attacks and misconfigured rules, and you have the data you need to tighten security groups (see 4.3).
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which traffic to record (rejected at least, or all), where flow logs go and how long they are kept.
- Agree who reviews them and how they are used in investigations.
Evidence
- The flow log standard: scope, destination, retention and reviewer
Not applicable. This benchmark covers AWS only.
On AWS the tasks create a flow log on each VPC that sends to CloudWatch Logs, then add the AWS Config rule that checks every VPC has one.
Task 1Create a flow log for a VPC
- Sign in to the AWS Management Console at console.aws.amazon.com and open VPC.
- In the navigation pane, choose Your VPCs and select the VPC.
- Choose Actions > Create flow log.
- For Filter, choose Reject at the least, or All if you also want accepted traffic.
- For Destination, choose Send to CloudWatch Logs, and for Destination log group enter a name such as vpc-flow-logs.
- For Service access, choose an existing service role that can publish to CloudWatch Logs, or create a new one.
- Keep AWS default format for Log record format and choose Create flow log.
- Repeat for every VPC in every Region, including the default VPCs.
- Check it: the VPC's Flow logs tab lists the flow log as active, and records appear in the log group.
Task 2Keep it checked with the AWS Config rule vpc-flow-logs-enabled
- Open AWS Config and choose Rules > Add rule.
- On Specify rule type, search for vpc-flow-logs-enabled, select it and choose Next.
- On Configure rule, under Parameters, set trafficType to REJECT (or leave it empty to accept any filter), then choose Next.
- On Review and create, check the settings and add the rule.
- Check it: once the rule has finished Evaluating..., every VPC shows as compliant.
Evidence
- Each VPC's Flow logs tab, showing an active flow log
- The vpc-flow-logs-enabled rule, showing every VPC compliant, and Security Hub CSPM control EC2.6 showing passed
Not applicable. This benchmark covers AWS only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.