VPC does not have flow logs enabled
- Severity
- Medium
- Service
- VPC
- Check ID
- VPC_FLOW_LOGS_DISABLED
What this check finds
VPC Flow Logs capture IP traffic metadata for network interfaces within a VPC. Without them, network-level security investigations (detecting lateral movement, scanning, data exfiltration) are impossible post-incident.
Passing looks like: VPC flow logs enabled.
How to fix it
Enable flow logs for the VPC and publish to CloudWatch Logs or S3.
AWS CLI
aws ec2 create-flow-logs --resource-type VPC --resource-ids VPC_ID --traffic-type ALL --log-destination-type cloud-watch-logs --log-destination LOG_GROUP_ARN --deliver-logs-permission-arn ROLE_ARN
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
VPC → Your VPCs → select VPC → Flow logs → Create flow log.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 |
|
| PCI-DSS v4.0.1 |
|
| HIPAA Security Rule |
|
| SOC 2 — Trust Services Criteria |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs