# Define Action options in Access rules

Action options define additional specific options for various features.

##

If no options are specified, the settings defined in Continue rules higher up in the policy are used.

- Allow — You can:
  - Forward traffic to a proxy, a host, or into a VPN.
  - Control stateful inspection by setting options for connection tracking, including idle timeouts and TCP segment size enforcement.
  - Enable or disable rate-based DoS protection and scan detection.
  - (License permitting) Enable deep inspection to match traffic against an Inspection Policy. You can check IPv4 traffic for malware by setting deep inspection and anti-malware options. If you use the IPS Template or the Layer 2 Firewall Template as the basis for your policy, deep inspection is enabled by default for all supported protocols (with Continue rules). Deep inspection can be disabled for a specific rule if necessary. Otherwise, make sure that your custom template policy directs all necessary Protocols to be inspected.
- Continue — You can set the default options for multiple rules. Options specified in the Continue rule are applied to any other Access rule that the same packet matches. However, if the Access rules have rule-specific definitions, those will be used instead.
- Discard — You can define a User Response to be shown to the user when an HTTP connection is discarded.
- Refuse — You can define a User Response to be shown to the user when an HTTP connection is refused.
- Jump — The rule processing jumps to a Sub-Policy to continue processing rules.
- Apply Blacklist — You can configure options that affect the reception of blacklist entries.

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. Select Configuration.
2. Browse to Policies > <Policy type>.
3. Right-click a policy, then select Edit <Policy name>.
4. Right-click the Action cell in an Access rule, then select <Action>.
5. Right-click the Action cell, then select Edit Options.
6. Configure the settings, then click OK.
   Note: When editing an IPS Policy or Layer 2 Firewall Policy, the number and names of the tabs in the dialog box might differ to what is referenced below.

## Select Rule Action Options dialog box (Allow)

Use this dialog box to override and specify the options for the Allow action in the Firewall Policy.

Option | Definition
--- | ---
General tab
Forward Traffic To (Firewall/VPN role only) | Select a Host or Proxy Server element to forward traffic to. Click Select to select an element. There are similar restrictions than when configuring destination NAT rules. For example, if you forward to a host, the IP address range in the Destination field of the rule must be an equivalent size to the IP address range of the host. If you forward traffic to a proxy or a host, the NAT rules are ignored. If you use NAT rules, you must configure forwarding in NAT rules rather than Access rules.

Option | Definition
--- | ---
General tab
VPN section
VPN Action (Firewall/VPN role only) | To forward traffic into a VPN, select from the following options: No VPN — No traffic is forwarded. Apply VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the rule does not match and the matching process continues with the next rule. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Enforce VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the connection is discarded. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Forward — Click Select to select the VPN to use. VPN traffic: The engine forwards the traffic from one VPN to another. If the traffic is not allowed in the VPN configuration, it is discarded. Other traffic: The traffic is sent through the specified VPN. If the traffic is not allowed in the VPN configuration, it is discarded. To apply the action to VPN client traffic in any mobile VPN, select Any Mobile VPN (IPv4 only).

Option | Definition
--- | ---
General tab
Inspection Options section
Deep Inspection | Selects traffic that matches this rule for checking against the Inspection Policy referenced by this policy. Traffic is inspected as the Protocol that is attached to the Service element in this rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
File Filtering | Selects traffic that matches this rule for checking against the File Filtering Policy referenced by this policy. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
Anti-Spam | The Anti-Spam feature is no longer supported in NGFW version 6.2.0 and higher.
Decryption | Defines whether traffic that matches the rule is decrypted for TLS inspection or by the SSM HTTP Proxy (NGFW Engines in the Firewall/VPN role only). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Allowed — Traffic that matches the rule is decrypted. Disallowed — Traffic that matches the rule is not decrypted.

Option | Definition
--- | ---
General tab
Snort Options section
Snort | Selects traffic that matches this rule for Snort inspection. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.

Option | Definition
--- | ---
Advanced tab
Connection Options section
Connection Tracking Mode | Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Off — Connection tracking is disabled. The NGFW Engine operates as a simple packet filter and allows packets based on their source, destination, and port. You must add separate Access rules that explicitly allow the reply packets. NAT cannot be applied to traffic allowed without connection tracking. Note: Turn off logging in the rule if you disable connection tracking. When connection tracking is off, a log entry is generated for each packet, leading to considerable resource use on the NGFW Engine, network, and Log Server. Defined in Engine Properties — The NGFW Engine allows or discards packets according to the connection tracking mode selected in the NGFW Engine properties. Reply packets are allowed as part of the allowed connection without an explicit Access rule. On Firewalls, protocols that use a dynamic port assignment must be allowed using a Service with the appropriate Protocol Agent for that protocol (in Access rules and NAT rules). Normal — (Default mode for Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine drops ICMP error messages related to connections that are not currently active in connection tracking (unless explicitly allowed by a rule in the policy). A valid, complete TCP handshake is required for TCP traffic. The NGFW Engine checks the traffic direction and the port parameters of UDP traffic. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates TCP and UDP traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Strict — Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows only TCP traffic that strictly adheres to the TCP standard as defined in RFC 793. The NGFW Engine also checks the sequence numbers of the packets in pre-connection establishment states and for RST and FIN packets, and drops packets that are out of sequence. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates the traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Loose — (Default mode for IPS engines and Layer 2 Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows some connection patterns and address translation operations that are not allowed in Normal mode. This mode can be used, for example, if routing is asymmetric and cannot be corrected or if the use of dynamic routing protocols causes the NGFW Engine to receive non-standard traffic patterns. Recommended when NGFW Engines are configured by default to only log connections instead of terminating them.
Idle Timeout | The timeout (in seconds) after which inactive connections are closed. This timeout concerns only idle connections. Connections are not cut because of timeouts while the hosts are still communicating. If you enter a timeout, this value overrides the setting defined in the NGFW Engine properties. CAUTION: Do not set long timeouts for many connections. Each connection that is kept active consumes resources on the NGFW Engine. Setting excessive timeouts for many connections can lead to serious performance problems. Generally, the idle timeout is not more than a few minutes.
Synchronize Connections | Defines whether connection information is synchronized between NGFW Engine cluster nodes. Disabling connection synchronization reduces the traffic volume on the active heartbeat interface, but it also prevents transparent failover of connections to other nodes. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties.
Enforce TCP MSS (IPv4 Only) | Defines whether TCP MSS is enforced. Headers are not included in the maximum segment size (MSS) value; MSS concerns only the payload of the packet. Usually, network equipment sends packets at the Ethernet-standard maximum transmission unit (MTU) size of 1500 (including both payload and headers). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — You can enter the minimum and maximum values for the MSS. If a TCP packet does not include an MSS value, the NGFW Engine does not add the MSS value to the packet, but enforces the minimum MSS.
Minimum | If a TCP packet has an MSS value smaller than the minimum you set here, the packet is dropped. The smaller the data content is, the less efficient the communications become due to the fixed-size headers. Limiting the minimum size can help alleviate certain types of network attacks. Typically, the value you enter is not larger than the default minimum TCP Maximum Segment Size (536).
Maximum | If a TCP packet has an MSS value larger than the maximum, the NGFW Engine overwrites the packet’s MSS with the maximum value you set here. Setting the maximum MSS size might be necessary to prevent fragmentation. Typically, the value you enter is lower than the standard Ethernet MTU (1500), taking the packet headers that are added to the MSS into account.

Option | Definition
--- | ---
Advanced tab
DoS Protection Options section
Concurrent Connection Limit per Source IP and Concurrent Connection Limit per Destination IP | Enter the maximum number of open connections from or to each IP address at any one time. These limits are enforced by rules that have their Action set to Allow or Continue, and when the VPN Action in an Action option is Apply VPN, Enforce VPN, or Forward. Be careful to apply the concurrent connection limits correctly for the types of communication that this rule handles to avoid cutting off connections unnecessarily.
Action | The Action that is applied to new connections if the limit is reached. Discard — The connection is dropped silently. Refuse — The connection is closed, and an ICMP error message is returned.
Rate-Based DoS Protection | Defines whether rate-based DoS protection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable rate-based DoS protection if the feature is disabled in the NGFW Engine properties.
Scan Detection | Defines whether scan detection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable scan detection if the feature is disabled in the NGFW Engine properties.

## Select Rule Action Options dialog box (Continue)

Use this dialog box to override and specify the options for the Continue action.

Option | Definition
--- | ---
General tab
Forward Traffic To (Firewall/VPN role only) | Select a Host or Proxy Server element to forward traffic to. Click Select to select an element. There are similar restrictions than when configuring destination NAT rules. For example, if you forward to a host, the IP address range in the Destination field of the rule must be an equivalent size to the IP address range of the host. If you forward traffic to a proxy or a host, the NAT rules are ignored. If you use NAT rules, you must configure forwarding in NAT rules rather than Access rules.

Option | Definition
--- | ---
General tab
VPN section
VPN Action (Firewall/VPN role only) | To forward traffic into a VPN, select from the following options: No VPN — No traffic is forwarded. Apply VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the rule does not match and the matching process continues with the next rule. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Enforce VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the connection is discarded. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Forward — Click Select to select the VPN to use. VPN traffic: The engine forwards the traffic from one VPN to another. If the traffic is not allowed in the VPN configuration, it is discarded. Other traffic: The traffic is sent through the specified VPN. If the traffic is not allowed in the VPN configuration, it is discarded. To apply the action to VPN client traffic in any mobile VPN, select Any Mobile VPN (IPv4 only).

Option | Definition
--- | ---
General tab
Inspection Options section
Deep Inspection | Selects traffic that matches this rule for checking against the Inspection Policy referenced by this policy. Traffic is inspected as the Protocol that is attached to the Service element in this rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
File Filtering | Selects traffic that matches this rule for checking against the File Filtering Policy referenced by this policy. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
Anti-Spam | The Anti-Spam feature is no longer supported in NGFW version 6.2.0 and higher.
Decryption | Defines whether traffic that matches the rule is decrypted for TLS inspection or by the SSM HTTP Proxy (NGFW Engines in the Firewall/VPN role only). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Allowed — Traffic that matches the rule is decrypted. Disallowed — Traffic that matches the rule is not decrypted.

Option | Definition
--- | ---
General tab
Snort Options section
Snort | Selects traffic that matches this rule for Snort inspection. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.

Option | Definition
--- | ---
Advanced tab
Connection Options section
Connection Tracking Mode | Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Off — Connection tracking is disabled. The NGFW Engine operates as a simple packet filter and allows packets based on their source, destination, and port. You must add separate Access rules that explicitly allow the reply packets. NAT cannot be applied to traffic allowed without connection tracking. Note: Turn off logging in the rule if you disable connection tracking. When connection tracking is off, a log entry is generated for each packet, leading to considerable resource use on the NGFW Engine, network, and Log Server. Defined in Engine Properties — The NGFW Engine allows or discards packets according to the connection tracking mode selected in the NGFW Engine properties. Reply packets are allowed as part of the allowed connection without an explicit Access rule. On Firewalls, protocols that use a dynamic port assignment must be allowed using a Service with the appropriate Protocol Agent for that protocol (in Access rules and NAT rules). Normal — (Default mode for Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine drops ICMP error messages related to connections that are not currently active in connection tracking (unless explicitly allowed by a rule in the policy). A valid, complete TCP handshake is required for TCP traffic. The NGFW Engine checks the traffic direction and the port parameters of UDP traffic. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates TCP and UDP traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Strict — Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows only TCP traffic that strictly adheres to the TCP standard as defined in RFC 793. The NGFW Engine also checks the sequence numbers of the packets in pre-connection establishment states and for RST and FIN packets, and drops packets that are out of sequence. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates the traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Loose — (Default mode for IPS engines and Layer 2 Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows some connection patterns and address translation operations that are not allowed in Normal mode. This mode can be used, for example, if routing is asymmetric and cannot be corrected or if the use of dynamic routing protocols causes the NGFW Engine to receive non-standard traffic patterns. Recommended when NGFW Engines are configured by default to only log connections instead of terminating them.
Idle Timeout | The timeout (in seconds) after which inactive connections are closed. This timeout concerns only idle connections. Connections are not cut because of timeouts while the hosts are still communicating. If you enter a timeout, this value overrides the setting defined in the NGFW Engine properties. CAUTION: Do not set long timeouts for many connections. Each connection that is kept active consumes resources on the NGFW Engine. Setting excessive timeouts for many connections can lead to serious performance problems. Generally, the idle timeout is not more than a few minutes.
Synchronize Connections | Defines whether connection information is synchronized between NGFW Engine cluster nodes. Disabling connection synchronization reduces the traffic volume on the active heartbeat interface, but it also prevents transparent failover of connections to other nodes. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties.
Enforce TCP MSS (IPv4 Only) | Defines whether TCP MSS is enforced. Headers are not included in the maximum segment size (MSS) value; MSS concerns only the payload of the packet. Usually, network equipment sends packets at the Ethernet-standard maximum transmission unit (MTU) size of 1500 (including both payload and headers). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — You can enter the minimum and maximum values for the MSS. If a TCP packet does not include an MSS value, the NGFW Engine does not add the MSS value to the packet, but enforces the minimum MSS.
Minimum | If a TCP packet has an MSS value smaller than the minimum you set here, the packet is dropped. The smaller the data content is, the less efficient the communications become due to the fixed-size headers. Limiting the minimum size can help alleviate certain types of network attacks. Typically, the value you enter is not larger than the default minimum TCP Maximum Segment Size (536).
Maximum | If a TCP packet has an MSS value larger than the maximum, the NGFW Engine overwrites the packet’s MSS with the maximum value you set here. Setting the maximum MSS size might be necessary to prevent fragmentation. Typically, the value you enter is lower than the standard Ethernet MTU (1500), taking the packet headers that are added to the MSS into account.

Option | Definition
--- | ---
Advanced tab
DoS Protection Options section
Concurrent Connection Limit per Source IP and Concurrent Connection Limit per Destination IP | Enter the maximum number of open connections from or to each IP address at any one time. These limits are enforced by rules that have their Action set to Allow or Continue, and when the VPN Action in an Action option is Apply VPN, Enforce VPN, or Forward. Be careful to apply the concurrent connection limits correctly for the types of communication that this rule handles to avoid cutting off connections unnecessarily.
Action | The Action that is applied to new connections if the limit is reached. Discard — The connection is dropped silently. Refuse — The connection is closed, and an ICMP error message is returned.
Rate-Based DoS Protection | Defines whether rate-based DoS protection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable rate-based DoS protection if the feature is disabled in the NGFW Engine properties.
Scan Detection | Defines whether scan detection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable scan detection if the feature is disabled in the NGFW Engine properties.

Option | Definition
--- | ---
Response tab
Override Settings Inherited from Continue Rule(s) | When selected, overrides settings defined in Continue rules higher up in the policy.
User Response (HTTP only) | Specifies the automatic response that is shown to the end user when a connection is discarded. Click Select to select an element. You can use the default response or create a custom response. User Responses are not supported on Virtual NGFW Engines.

## Select Rule Action Options dialog box (Discard or Refuse)

Use this dialog box to override and specify the options for the Discard or Refuse action.

Option | Definition
--- | ---
Advanced tab
Scan Detection | Defines whether scan detection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable scan detection if the feature is disabled in the NGFW Engine properties.

Option | Definition
--- | ---
Response tab
Override Settings Inherited from Continue Rule(s) | When selected, overrides settings defined in Continue rules higher up in the policy.
User Response (HTTP only) | Specifies the automatic response that is shown to the end user when a connection is discarded. Click Select to select an element. You can use the default response or create a custom response. User Responses are not supported on Virtual NGFW Engines.

## Select Rule Action Options dialog box (Jump)

Use this dialog box to override and specify the options for the Jump action.

Option | Definition
--- | ---
General tab
Forward Traffic To (Firewall/VPN role only) | Select a Host or Proxy Server element to forward traffic to. Click Select to select an element. There are similar restrictions than when configuring destination NAT rules. For example, if you forward to a host, the IP address range in the Destination field of the rule must be an equivalent size to the IP address range of the host. If you forward traffic to a proxy or a host, the NAT rules are ignored. If you use NAT rules, you must configure forwarding in NAT rules rather than Access rules.

Option | Definition
--- | ---
General tab
VPN section
VPN Action (Firewall/VPN role only) | To forward traffic into a VPN, select from the following options: No VPN — No traffic is forwarded. Apply VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the rule does not match and the matching process continues with the next rule. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Enforce VPN — Click Select to select the VPN to use. Incoming connections: The traffic is allowed if it arrives through the specified VPN. Otherwise, the connection is discarded. Outgoing connections: The traffic is sent through the specified VPN. If the connection is not allowed in the VPN configuration, it is discarded. Forward — Click Select to select the VPN to use. VPN traffic: The engine forwards the traffic from one VPN to another. If the traffic is not allowed in the VPN configuration, it is discarded. Other traffic: The traffic is sent through the specified VPN. If the traffic is not allowed in the VPN configuration, it is discarded. To apply the action to VPN client traffic in any mobile VPN, select Any Mobile VPN (IPv4 only).

Option | Definition
--- | ---
General tab
Inspection Options section
Deep Inspection | Selects traffic that matches this rule for checking against the Inspection Policy referenced by this policy. Traffic is inspected as the Protocol that is attached to the Service element in this rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
File Filtering | Selects traffic that matches this rule for checking against the File Filtering Policy referenced by this policy. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — The feature is enabled. Off — The feature is disabled.
Anti-Spam | The Anti-Spam feature is no longer supported in NGFW version 6.2.0 and higher.
Decryption | Defines whether traffic that matches the rule is decrypted for TLS inspection or by the SSM HTTP Proxy (NGFW Engines in the Firewall/VPN role only). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Allowed — Traffic that matches the rule is decrypted. Disallowed — Traffic that matches the rule is not decrypted.

Option | Definition
--- | ---
Advanced tab
Connection Options section
Connection Tracking Mode | Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Off — Connection tracking is disabled. The NGFW Engine operates as a simple packet filter and allows packets based on their source, destination, and port. You must add separate Access rules that explicitly allow the reply packets. NAT cannot be applied to traffic allowed without connection tracking. Note: Turn off logging in the rule if you disable connection tracking. When connection tracking is off, a log entry is generated for each packet, leading to considerable resource use on the NGFW Engine, network, and Log Server. Defined in Engine Properties — The NGFW Engine allows or discards packets according to the connection tracking mode selected in the NGFW Engine properties. Reply packets are allowed as part of the allowed connection without an explicit Access rule. On Firewalls, protocols that use a dynamic port assignment must be allowed using a Service with the appropriate Protocol Agent for that protocol (in Access rules and NAT rules). Normal — (Default mode for Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine drops ICMP error messages related to connections that are not currently active in connection tracking (unless explicitly allowed by a rule in the policy). A valid, complete TCP handshake is required for TCP traffic. The NGFW Engine checks the traffic direction and the port parameters of UDP traffic. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates TCP and UDP traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Strict — Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows only TCP traffic that strictly adheres to the TCP standard as defined in RFC 793. The NGFW Engine also checks the sequence numbers of the packets in pre-connection establishment states and for RST and FIN packets, and drops packets that are out of sequence. If the Service cell in the rule contains a Service that uses a Protocol Agent, the NGFW Engine also validates the traffic on the application layer. If a protocol violation occurs, the packet that violates the protocol is dropped. Loose — (Default mode for IPS engines and Layer 2 Firewalls) Reply packets are allowed as part of the allowed connection without an explicit Access rule. The NGFW Engine allows some connection patterns and address translation operations that are not allowed in Normal mode. This mode can be used, for example, if routing is asymmetric and cannot be corrected or if the use of dynamic routing protocols causes the NGFW Engine to receive non-standard traffic patterns. Recommended when NGFW Engines are configured by default to only log connections instead of terminating them.
Idle Timeout | The timeout (in seconds) after which inactive connections are closed. This timeout concerns only idle connections. Connections are not cut because of timeouts while the hosts are still communicating. If you enter a timeout, this value overrides the setting defined in the NGFW Engine properties. CAUTION: Do not set long timeouts for many connections. Each connection that is kept active consumes resources on the NGFW Engine. Setting excessive timeouts for many connections can lead to serious performance problems. Generally, the idle timeout is not more than a few minutes.
Synchronize Connections | Defines whether connection information is synchronized between NGFW Engine cluster nodes. Disabling connection synchronization reduces the traffic volume on the active heartbeat interface, but it also prevents transparent failover of connections to other nodes. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties.
Enforce TCP MSS (IPv4 Only) | Defines whether TCP MSS is enforced. Headers are not included in the maximum segment size (MSS) value; MSS concerns only the payload of the packet. Usually, network equipment sends packets at the Ethernet-standard maximum transmission unit (MTU) size of 1500 (including both payload and headers). Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. On — You can enter the minimum and maximum values for the MSS. If a TCP packet does not include an MSS value, the NGFW Engine does not add the MSS value to the packet, but enforces the minimum MSS.
Minimum | If a TCP packet has an MSS value smaller than the minimum you set here, the packet is dropped. The smaller the data content is, the less efficient the communications become due to the fixed-size headers. Limiting the minimum size can help alleviate certain types of network attacks. Typically, the value you enter is not larger than the default minimum TCP Maximum Segment Size (536).
Maximum | If a TCP packet has an MSS value larger than the maximum, the NGFW Engine overwrites the packet’s MSS with the maximum value you set here. Setting the maximum MSS size might be necessary to prevent fragmentation. Typically, the value you enter is lower than the standard Ethernet MTU (1500), taking the packet headers that are added to the MSS into account.

Option | Definition
--- | ---
Advanced tab
DoS Protection Options section
Concurrent Connection Limit per Source IP and Concurrent Connection Limit per Destination IP | Enter the maximum number of open connections from or to each IP address at any one time. These limits are enforced by rules that have their Action set to Allow or Continue, and when the VPN Action in an Action option is Apply VPN, Enforce VPN, or Forward. Be careful to apply the concurrent connection limits correctly for the types of communication that this rule handles to avoid cutting off connections unnecessarily.
Action | The Action that is applied to new connections if the limit is reached. Discard — The connection is dropped silently. Refuse — The connection is closed, and an ICMP error message is returned.
Rate-Based DoS Protection | Defines whether rate-based DoS protection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable rate-based DoS protection if the feature is disabled in the NGFW Engine properties.
Scan Detection | Defines whether scan detection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable scan detection if the feature is disabled in the NGFW Engine properties.

Option | Definition
--- | ---
Jump tab
Sub-Policy | Select a Sub-Policy. Connections that match the Jump rule are matched against the selected Sub-Policy. If the Sub-Policy rules do not match, processing continues with the next rule in the main policy. Click Select to select an element.

## Select Rule Action Options dialog box (Apply Blacklist)

Use this dialog box to override and specify the options for the Apply Blacklist action.

Option | Definition
--- | ---
Advanced tab
Scan Detection | Defines whether scan detection is applied to traffic that matches the rule. Inherited from Continue Rule(s) — The settings defined in Continue rules higher up in the policy are used. Defined in Engine Properties — The settings defined in the NGFW Engine properties are used. Off — The feature is disabled, overriding the setting defined in the NGFW Engine properties. You cannot use a rule to enable scan detection if the feature is disabled in the NGFW Engine properties.

Option | Definition
--- | ---
Blacklisting tab
Allowed Blacklisters for This Rule | Any — Blacklist entries are accepted from all components. Restricted — Blacklist entries are only accepted from the components you specify (and from the command line). NGFW Engines are always allowed to add entries to their own blacklists.
Available Blacklisters | Elements that you can add to the Allowed Blacklisters list.
Allowed Blacklisters | The elements that are allowed to add blacklist entries. Click Add to add an element to the list, or Remove to remove the selected element. Add the Management Server to allow manual blacklisting through the Management Client. Add the Log Server to allow it to relay blacklisting requests from other NGFW Engines.

Option | Definition
--- | ---
Response tab
Override Settings Inherited from Continue Rule(s) | When selected, overrides settings defined in Continue rules higher up in the policy.
User Response (HTTP only) | Specifies the automatic response that is shown to the end user when a connection is discarded. Click Select to select an element. You can use the default response or create a custom response. User Responses are not supported on Virtual NGFW Engines.