Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
networkfirewall_logging_enabledProvider: AWS
Service:
networkfirewallSeverity: HIGH
Categories:
loggingResource type:
AwsNetworkFirewallFirewallWhat this check verifies
AWS Network Firewall has stateful engine logging configured with at least one log type (FLOW, ALERT, or TLS) and an active log destination
Risk
Absent Network Firewall logs reduce visibility and forensics. Malicious flows, C2 traffic, and data exfiltration can go undetected, impacting:- Confidentiality (leakage)
- Integrity (unauthorized traffic allowed)
- Availability (DDoS patterns unnoticed)
Recommendation
Enable comprehensive firewall logging and sendFLOW, ALERT, and when applicable TLS events to a centralized, tamper-resistant destination. Apply least privilege to writers/readers, enforce encryption and retention, and integrate alerts with monitoring for defense in depth.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-logging.html
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-update-logging-configuration.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/networkfirewall-controls.html#networkfirewall-2
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_logging_enabled. 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