Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
networkfirewall_in_all_vpcProvider: AWS
Service:
networkfirewallSeverity: MEDIUM
Categories:
trust-boundariesResource type:
AwsEc2VpcWhat this check verifies
VPCs with an AWS Network Firewall associated to the same VPC to inspect and filter network traffic. Identifies VPCs that do not have a Network Firewall resource linked to them.Risk
Without a Network Firewall, VPC traffic can bypass deep inspection and centralized policy enforcement, enabling data exfiltration, command-and-control, and lateral movement. Confidentiality is reduced by unmonitored flows; integrity and availability are threatened by malware and disruptive traffic.Recommendation
Deploy AWS Network Firewall in each VPC or centralize inspection through a dedicated hub VPC. Adopt adefault-deny posture with least-privilege rules, restrict egress to required destinations, segment workloads (defense in depth, zero trust), and enable logging to monitor and tune network policies.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/vpc-config.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/NetworkFirewall/network-firewall-in-use.html
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/setting-up.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = networkfirewall_in_all_vpc. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks