AWS Network Firewall adds a next-generation firewall policy
AWS Network Firewall now offers a next-generation firewall policy with layered firewall and intrusion prevention rules and independent rule capacity. It costs nothing extra and existing policies keep working.
By JetherVerse News

AWS announced on November 10, 2026 a next-generation firewall policy model for AWS Network Firewall. The model gives security teams a simpler policy structure and higher rule capacity. AWS Network Firewall filters traffic in and out of your virtual private clouds.
The new model layers firewall and intrusion prevention protections instead of combining them. Firewall rules deny traffic by default and allow only approved access, such as traffic to approved domains. Intrusion prevention rules use managed rule groups from AWS or AWS Marketplace partners, which update automatically as new threats appear. You also write custom rule groups. All rules are stateful and evaluate with full connection context.
Capacity changes as well. Firewall rules and intrusion prevention rules each get their own capacity, so adding one no longer reduces the other. Embedded rule groups, meant for rules not shared across policies, draw capacity on demand without pre-allocation.
The model is available in all commercial AWS Regions and AWS GovCloud (US) Regions. AWS charges nothing extra for the NGFW policy. Existing policies keep working without changes and intrusion prevention rules stay backward compatible. The announcement gives no setup steps. AWS points to the product page and the developer guide on firewall policies, version 2.
A default deny setup is basic security hygiene for any workload on AWS. Start with a list of the domains your application calls. For example, a store talking to a payment provider, an email service and a shipping API needs three allowed domains. Write those as allow rules and block the rest. Then review the managed intrusion prevention groups and pick the ones matching your stack.
Check your current policies before you migrate. Nothing forces a change today, so move one non-critical environment first and watch the logs.
If you run client workloads on AWS, firewall rules belong in your monthly maintenance review.
Source: Amazon Web Services
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

