Network Firewall logging should be enabled
Checks that the Network Firewall firewall sends at least one log type (Alert, Flow or TLS) to a destination, recording the traffic its stateful engine sees and the rule actions taken, for investigations. Only traffic forwarded to the stateful engine is logged, and whether the destination still exists is not checked.
- service
- NetworkFirewall
- severity
- Medium
- scope
- evaluated in every region
How to fix it
In the console
VPC → Network Firewall → Firewalls → the firewall → Firewall details → Logging
- Log type
- Alert, Flow or both; any one with a destination passes, and TLS logs only with TLS inspection
- Log destination type
- An S3 bucket, a CloudWatch log group or a Firehose stream; any one passes
With the AWS CLI
- Overwrites existing settings: The call sets the whole logging configuration and adds only one log type at a time, so add Flow in a second call that repeats the Alert entry.
aws network-firewall update-logging-configuration --firewall-arn <firewall-arn> --logging-configuration '{"LogDestinationConfigs":[{"LogType":"ALERT","LogDestinationType":"CloudWatchLogs","LogDestination":{"logGroup":"<log-group-name>"}}]}' --region <region>With Terraform
resource "aws_networkfirewall_logging_configuration" "this" {
firewall_arn = var.firewall_arn
logging_configuration {
log_destination_config {
log_destination = {
logGroup = var.log_group_name
}
log_destination_type = "CloudWatchLogs"
log_type = "ALERT"
}
}
}
See which of your accounts this check is failing on.
Book a live scan