VPC Flow Logs Not Enabled

VPC Flow Logs are not enabled, so there is no record of network connections to and from resources in the VPC for investigating intrusions or data exfiltration.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator
CVSS 4.02.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-778: Insufficient Logging
OWASP Top 10A09:2025 Security Logging and Alerting Failures
CategoryInsufficient Logging

Description

VPC Flow Logs capture metadata about IP traffic through the network interfaces in a VPC: source and destination addresses and ports, protocol, packet and byte counts, and whether the traffic was accepted or rejected by security groups and network ACLs. They do not capture packet contents. A flow log can be created for a whole VPC, a subnet or a single network interface, and published to CloudWatch Logs, Amazon S3 or Amazon Data Firehose.

The finding is raised when VPCs hosting workloads have no flow log, or when flow logs record only rejected traffic, which shows blocked scanning but not the connections an attacker actually made. Without flow logs, investigators cannot establish which hosts a compromised instance connected to, whether data left the VPC and where it went, or which internal systems an attacker reached through lateral movement, and attempts to reach exposed services cannot be reviewed after the event. Amazon GuardDuty analyses flow data from its own stream even where flow logs are not enabled, but that data is not available to the organisation for its own investigations. The weakness gives no access on its own; it limits the organisation's ability to detect and scope a compromise.

The finding is confirmed with aws ec2 describe-flow-logs and aws ec2 describe-vpcs in each Region, and reported by Prowler, ScoutSuite and Security Hub.

Remediation

Enable flow logs for every VPC that hosts workloads, capturing all traffic:

aws ec2 create-flow-logs --resource-type VPC --resource-ids "$VPC_ID" --traffic-type ALL --log-destination-type s3 --log-destination "$LOG_BUCKET_ARN"
  • Send flow logs to a central S3 bucket in a log archive account, or to CloudWatch Logs where alerting is needed, and keep them for a period that meets the organisation's investigation and regulatory needs.
  • Consider a custom log format with fields beyond the default, such as pkt-srcaddr, pkt-dstaddr and flow-direction, which help where traffic passes through NAT gateways or load balancers.
  • Deploy flow logs centrally across accounts and Regions, for example with CloudFormation StackSets or an AWS Config remediation, so that new VPCs are covered automatically.
  • Make the logs searchable, for example with Amazon Athena or the organisation's SIEM, so that they can be used during an incident.

Confirm the fix with aws ec2 describe-flow-logs showing an active flow log with traffic type ALL for each VPC, and that records are arriving at the destination.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More AWS Findings

Every AWS finding