30 of 50 in All Controls
aws

Implement Centralized Network Firewall for Egress/Ingress

IDAWS-NET-002
Severity
high
Automation
Auto
Category
network
Enforcementrecommended
Complexity / Impact
high(disruptive impact)
Risk Profile
high likelihood(low residual)
Cloud Scopeaws:ou
Environments
productionnon-productionsandbox
Target Resources
AWS::NetworkFirewall::FirewallAWS::NetworkFirewall::FirewallPolicyAWS::NetworkFirewall::RuleGroupAWS::EC2::VPCEndpoint
Services
network-firewallec2transit-gatewaycloudwatch-logs
Tags
networkfirewallsecurity-architectureinspectionlanding-zone
Frameworks
NIST 800-53PCI DSSISO 27001SOC 2
Governance
Cloud Security (annually)
Created
2026-05-03
Last Updated
2026-11-16

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.

Beta
Framework / StandardMapped Requirements & ControlsControls
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.

Inspect Network Firewall Provisioning and Logging Statebash
# 1. Verify firewall deployment status and endpoint sync states
aws network-firewall describe-firewall \
  --firewall-name "Central-Network-Firewall" \
  --query "{Name:Firewall.FirewallName,Status:FirewallStatus.Status,PolicyArn:Firewall.FirewallPolicyArn,DeleteProtection:Firewall.DeleteProtection,SyncStates:FirewallStatus.SyncStates}" \
  --output json

# 2. Verify alert and flow logging destination configurations
aws network-firewall describe-logging-configuration \
  --firewall-name "Central-Network-Firewall" \
  --query "LoggingConfiguration.LogDestinationConfigs[*].{LogType:LogType,DestinationType:LogDestinationType,Destination:LogDestination}" \
  --output json

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

  1. Create dedicated firewall subnets in an Inspection VPC within the Network account across multiple Availability Zones.
  2. Create stateful and stateless rule groups enforcing domain filtering and IPS signatures.
  3. Create an AWS Network Firewall policy referencing the inspection rule groups.
  4. Deploy AWS Network Firewall in the dedicated subnets with delete protection enabled.
  5. Configure logging for ALERT and FLOW logs to Amazon CloudWatch Logs or Amazon S3.
  6. Configure Transit Gateway route tables to steer spoke VPC traffic to the Inspection VPC firewall endpoints.
Deploy AWS Network Firewall with Policy and Loggingbash
# 1. Create a stateful rule group with Suricata IPS rules
rule_group_arn=$(aws network-firewall create-rule-group \
  --rule-group-name "Central-IPS-RuleGroup" \
  --type STATEFUL \
  --capacity 100 \
  --rule-group 'RulesSource={RulesString="drop tcp $HOME_NET any -> $EXTERNAL_NET 443 (msg:\"Block unauthorized external command channel\"; tls.sni; content:\"bad-domain.internal\"; endswith; sid:100001; rev:1;)"}' \
  --tags Key=Environment,Value=Production \
  --query 'RuleGroupResponse.RuleGroupArn' \
  --output text)

# 2. Create firewall policy with stateful inspection forward action
policy_arn=$(aws network-firewall create-firewall-policy \
  --firewall-policy-name "Central-Inspection-Policy" \
  --firewall-policy "StatelessDefaultActions=[\"aws:forward_to_sfe\"],StatelessFragmentDefaultActions=[\"aws:forward_to_sfe\"],StatefulRuleGroupReferences=[{ResourceArn=\"$rule_group_arn\"}]" \
  --description "Centralized ingress and egress inspection policy" \
  --query 'FirewallPolicyResponse.FirewallPolicyArn' \
  --output text)

# 3. Deploy Network Firewall across dedicated subnets in the inspection VPC
aws network-firewall create-firewall \
  --firewall-name "Central-Network-Firewall" \
  --firewall-policy-arn "$policy_arn" \
  --vpc-id "vpc-0123456789abcdef0" \
  --subnet-mappings SubnetId=subnet-01111111111111111 SubnetId=subnet-02222222222222222 \
  --delete-protection \
  --description "Centralized egress and ingress inspection firewall"

# 4. Configure dual logging to CloudWatch Logs for real-time alerts and flow records
aws network-firewall update-logging-configuration \
  --firewall-name "Central-Network-Firewall" \
  --logging-configuration 'LogDestinationConfigs=[{LogType=ALERT,LogDestinationType=CloudWatchLogs,LogDestination={logGroup=/aws/network-firewall/alerts}},{LogType=FLOW,LogDestinationType=CloudWatchLogs,LogDestination={logGroup=/aws/network-firewall/flows}}]'

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.