Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
networkfirewall_multi_azProvider: AWS
Service:
networkfirewallSeverity: HIGH
Categories:
resilienceResource type:
AwsNetworkFirewallFirewallWhat this check verifies
AWS Network Firewall firewalls are assessed for multi-AZ deployment, expecting subnet mappings in more than one Availability Zone. A configuration with only one subnet mapping indicates a single-AZ firewall.Risk
Single-AZ firewalls are a single point of failure. An AZ outage can drop or blackhole traffic, degrading availability, or prompt route changes that bypass inspection, exposing confidentiality and integrity to unfiltered access, data exfiltration, and lateral movement.Recommendation
Deploy firewalls across>=2 AZs with a dedicated subnet in each used AZ. Maintain per-AZ, symmetric routing to the local endpoint to preserve stateful inspection. Apply defense in depth and automate drift controls and AZ failover tests to sustain resilience.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/id_id/network-firewall/latest/developerguide/arch-two-zone-igw.html
- https://aws.amazon.com/es/blogs/networking-and-content-delivery/deployment-models-for-aws-network-firewall/
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/arch-two-zone-igw.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/networkfirewall-controls.html#networkfirewall-1
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_multi_az. 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