Limitations and caveats for firewall rules in a Next Generation policy
The IPS engine in a Next Generation policy uses the same Suricata compatible stateful rules as a Classic Network Firewall policy, so the limitations and caveats earlier in this section apply to IPS rules as well. The firewall engine in a Next Generation policy uses Suricata compatible firewall-mode rules, which have the following additional limitations. For the full reference on which actions, scopes, hooks, and keywords you can combine in a firewall rule, see Valid combinations and constraints for firewall rules.
-
The
configaction isn't supported. A firewall rule's primary action must beaccept,drop,reject,rejectdst, orrejectboth. The Suricata firewall-modeconfigaction isn't supported. -
passandalertaren't primary actions. A firewall rule can't usepassoralertas its primary action.passis available only as a secondary action that bypasses the IPS engine, andalertonly as a modifier that adds logging. -
An explicit action scope is required. Every firewall rule must specify an action scope, such as
accept:flowordrop:packet. The valid scopes depend on the action and the hook. For details, see Actions and scopes. -
A keyword is valid only at its own hook. A protocol matching keyword is valid only at the single hook where its data becomes available, not at any hook and not at every later hook. For example,
tls.sniis valid only attls:client_hello, andhttp.hostonly athttp1:request_headers. For details, see Matching a keyword at the right hook. -
Payload-matching keywords aren't valid on a packet hook. The keywords
content,pcre,byte_test,byte_jump, andisdataatare valid only at an application-layer hook, where they bind to a protocol buffer. They aren't valid at a packet hook such astcp:all. For details, see Payload matching and packet hooks. -
The HTTP/1.1 rule-header token is
http1, nothttp. A rule string that useshttp:is rejected. In a modeled rule, the protocolhookHTTPis the alias forhttp1. -
A modeled firewall rule compiles to a one-directional rule. A modeled rule always compiles to the forward (
->) form; you express inbound compared with outbound through the source and destination, not a separate direction field. Bidirectional (<>) rule strings aren't accepted for a modeled rule. -
PostgreSQL (
pgsql) support is limited. The firewall engine has limited support for the PostgreSQL protocol. For an example firewall rule that allows PostgreSQL traffic, see Troubleshooting.