6.7. Blacklisting Hosts and Networks
Overview
NetDefendOS implements a Blacklist of host or network IP addresses which can be utilized to
protect against traffic coming from specific Internet sources.
Certain NetDefendOS subsystems have the ability to optionally blacklist a host or network when
certain conditions are encountered. These subsystems are:
•
Intrusion Detection and Prevention (IDP).
•
Threshold Rules. (Available on certain models only - see Section 10.3, “Threshold Rules” for
details.)
Blacklisting Options
The automatic blacklisting of a host or network can be enabled in IDP and in Threshold Rules by
specifying the Protect action for when a rule is triggered. Once enabled there are three blacklisting
options:
Time to Block Host/Network in
seconds
The host or network which is the source of the traffic will
stay on the blacklist for the specified time and then be
removed. If the same source triggers another entry to the
blacklist then the blocking time is renewed to its original, full
value (in other words, it is not cumulative).
Block only this Service
By default Blacklisting blocks all Services for the triggering
host.
Exempt already established
connections from Blacklisting
If there are established connections that have the same source
as this new Blacklist entry then they will not be dropped if
this option is set.
IP addresses or networks are added to the list then the traffic from these sources is then blocked for
the period of time specified.
Note: Restarts do not effect the blacklist
The contents of the blacklist is not lost if the D-Link Firewall shuts down and restarts.
Whitelisting
To ensure that Internet traffic coming from trusted sources, such as the management workstation,
are not blacklisted under any circumstances, a Whitelist is also maintained by NetDefendOS. Any IP
address object can be added to this whitelist
Tip: Important IP addresses should be whitelisted
It is recommended to add the D-Link Firewall itself to the whitelist as well as the IP
address or network of the management workstation since blacklisting of either could
have serious consequences for network operations.
It is also important to understand that although whitelisting prevents a particular source from being
blacklisted, it still does not prevent NetDefendOS mechanisms such as Threshold Rules from
dropping or denying connections from that source. What whitelisting does is prevent a source being
added to a blacklist if that is the action a rule has specified.
6.7. Blacklisting Hosts and Networks
Chapter 6. Security Mechanisms
280
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 ...