Implement Centralized Network Firewall for Egress/Ingress
Specification & Description
Establish a centralized inspection VPC with AWS Network Firewall in the dedicated Network account to inspect and filter all ingress, egress, and east-west traffic.
Technical Specifications
Distributing individual firewall instances across separate application VPCs multiplies operational overhead, licensing complexity, and configuration drift. A centralized architecture directs traffic through a dedicated inspection VPC in the Network account using AWS Transit Gateway route tables. AWS Network Firewall endpoints deployed across availability zones execute stateful and stateless inspection, applying Suricata-compatible IPS rules, domain blocklists, and protocol anomaly detection before traffic leaves or enters the landing zone.
Security Rationale
Centralizing inspection into a dedicated firewall VPC ensures uniform security controls for all member accounts. It provides deep packet inspection, TLS SNI domain filtering, and centralized intrusion detection while eliminating redundant egress gateways.
Business & Security Impact
Uninspected egress and ingress paths leave the environment vulnerable to command-and-control communications, data exfiltration, and unmonitored external network attacks. Fragmented per-account firewall deployments increase operational error rates and blind spots.
Compliance Framework Mappings (4)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | SC-7AU-12 | 2 |
PCI DSS v4.0PCI DSS | 1.2.11.3.1 | 2 |
ISO 27001:2022ISO 27001 | A.8.20A.8.22 | 2 |
SOC 2SOC 2 | CC6.6 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
List active Network Firewalls in the Network account, verify that operational state is available and firewall endpoints are synchronized across subnets, and confirm that alert and flow logging destinations are active.
Remediation Guide & Automation
Deploy an inspection VPC in the Network account with dedicated firewall subnets. Create stateless and stateful rule groups, assemble an AWS Network Firewall policy, deploy the firewall with delete protection, configure alert and flow logging to CloudWatch Logs or S3, and route traffic via Transit Gateway route tables.
Step-by-Step Instructions
- Create dedicated firewall subnets in an Inspection VPC within the Network account across multiple Availability Zones.
- Create stateful and stateless rule groups enforcing domain filtering and IPS signatures.
- Create an AWS Network Firewall policy referencing the inspection rule groups.
- Deploy AWS Network Firewall in the dedicated subnets with delete protection enabled.
- Configure logging for ALERT and FLOW logs to Amazon CloudWatch Logs or Amazon S3.
- Configure Transit Gateway route tables to steer spoke VPC traffic to the Inspection VPC firewall endpoints.