Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
networkfirewall_policy_rule_group_associatedProvider: AWS
Service:
networkfirewallSeverity: HIGH
Categories:
trust-boundariesResource type:
AwsNetworkFirewallFirewallWhat this check verifies
Network Firewall policies have one or more stateful or stateless rule groups associated to define packet inspection and handling. Policies with no rule groups are identified.Risk
Without rule groups, traffic isn’t meaningfully inspected, allowing unauthorized flows across VPC boundaries. Impacts:- Confidentiality: data exfiltration
- Integrity: unauthorized changes via exposed services
- Availability: C2, scanning, or DoS traffic passes; enables lateral movement
Recommendation
Associate appropriate stateful and stateless rule groups with every policy.- Enforce a deny-by-default posture (least privilege)
- Use vetted managed rule groups as a baseline, then tailor to workloads
- Review and test regularly; version rules, monitor logs, and require change control
Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/rule-groups.html
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-policy-updating.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/networkfirewall-controls.html#networkfirewall-3
- https://medium.com/slalom-blog/secure-internet-access-egress-filtering-with-aws-network-firewall-ddf52ae121f9
- https://docs.aws.amazon.com/de_de/network-firewall/latest/developerguide/nwfw-using-managed-rule-groups-add-to-policy.html
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_policy_rule_group_associated. 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