30.01.2015 Views

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Firewall and Intrusion Prevention System<br />

Ignored intrusions<br />

In some cases, legitimate traffic may be detected as an intrusion. If this happens<br />

frequently or even regularly, it may be helpful to define an exception for the particular<br />

intrusion. Exceptions are defined by adding the rule ID number in the list. Identifier<br />

of the rule can be found in the Security log (see chapter 22.11), or in the Snort system<br />

documentation (http://www.snort.org/).<br />

Note: Exceptions are helpful only in cases where legitimate traffic is detected as an<br />

intrusion repeatedly or even better — regularly. It may be harmful to define exceptions<br />

after the first time such a problem is detected.<br />

Protocol-specific intrusions<br />

Some intrusions may target security weaknesses in specific application protocols.<br />

Therefore, it is usually not helpful to detect these intrusions in traffic of other application<br />

protocols. For individual protocols recognized by the intrusion detection system, lists of<br />

standard and frequently used ports are predefined. The lists may include individual port<br />

numbers separated by commas or port ranges (initial and final port separated by a dash,<br />

non-spaced).<br />

If an application is available from the Internet that uses any of the listed protocols on<br />

a non-standard port (e.g. HTTP on port 10000), it can be helpful to add this port in list<br />

of ports on which HTTP-specific intrusions will be detected.<br />

If, on the other hand, an application using a different protocol is used on a listed port<br />

(e.g. VPN server on port 8000), it is recommended to remove this port from the list of<br />

ports for the particular protocol — it is meaningless to perform detection on the port, the<br />

detection process would be a redundant load for the firewall and false positives might<br />

also occur.<br />

8.2 MAC address filtering<br />

Besides Traffic Rules that filter network traffic by using IP addresses, protocols and ports (see<br />

chapter 7), <strong>Kerio</strong> Control also allows “low-level” filtering by hardware addresses (so called MAC<br />

addresses) of individual computers and network devices. Filtering of physical address helps<br />

for example prevent users from undesirable connections to the network or get around the<br />

firewall traffic policy by changing IP address of their device.<br />

Note: The MAC address filter works on lower level than the firewall’s traffic rules (see<br />

chapter 7) and it is therefore applied earlier than traffic rules.<br />

MAC address filtering can be configured under Configuration → Traffic Policy → Security Options.<br />

Network interfaces<br />

The MAC address filter can be applied on any network Ethernet or WiFi interface of the<br />

firewall. However, it is recommended to select only such interface on which network<br />

traffic should be filtered. If you want to block unwanted devices in local network, there<br />

is no reason to use filtering of MAC addresses on web interfaces. This might mean<br />

a redundant load on the firewall and it can also cause blocking of Internet traffic.<br />

116

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!