
•
Protect - Drop the triggering connection.
Logging would be the preferred option if the appropriate triggering value cannot be determined
beforehand. Multiple Actions for a given rule might consist of Audit for a given threshold while the
action might become Protect for a higher threshold.
10.3.5. Multiple Triggered Actions
When a rule is triggered then NetDefendOS will perform the associated rule Actions that match the
condition that has occurred. If more than one Action matches the condition then those matching
Actions are applied in the order they appear in the user interface.
If several Actions that have the same combination of Type and Grouping (see above for the
definition of these terms) are triggered at the same time, only the Action with the highest threshold
value will be logged.
10.3.6. Exempted Connections
It should be noted that some advanced settings, known as Before Rules settings, can exempt certain
types of connections for remote management from examination by the NetDefendOS IP rule set if
they are enabled. These Before Rules settings will also exempt the connections from Threshold
Rules if they are enabled.
10.3.7. Threshold Rules and ZoneDefense
Threshold Rules are used in the D-Link ZoneDefense feature to block the source of excessive
connection attmepts from internal hosts. For more information on this refer to Chapter 12,
ZoneDefense.
10.3.8. Threshold Rule Blacklisting
If the Protect option is used, Threshold Rules can be configured so that the source that triggered the
rule, is added automatically to a Blacklist of IP addresses or networks. If several Protect Actions
with blacklisting enabled are triggered at the same time, only the first triggered blacklisting Action
will be executed by NetDefendOS.
A host based Action with blacklisting enabled will blacklist a single host when triggered. A network
based action with blacklisting enabled will blacklist the source network associated with the rule. If
the Threshold Rule is linked to a service then it is possible to block only that service.
When Blacklisting is selected, the administrator can choose to leave pre-existing connections from
the triggering source unaffected, or can alternatively choose to have the connections dropped by
NetDefendOS.
The length of time, in seconds, for which the source is blacklisted can also be set.
This feature is discussed further in Section 6.7, “Blacklisting Hosts and Networks”.
10.3.5. Multiple Triggered Actions
Chapter 10. Traffic Management
400
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...