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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Firewall and Intrusion Prevention System<br />

• Log — detected intrusion will be only recorded in the Security log,<br />

• No action — the detected intrusion will be ignored.<br />

Default and recommended settings for individual intrusion severity levels:<br />

• High severity → Log and drop,<br />

• Medium severity → Log,<br />

• Low severity → No action (in case that there is a suspicion of too many false alarm<br />

cases, see also Advanced settings).<br />

Functionality of the intrusion prevention system can be tested by clicking on the link on<br />

a special web page on one of the <strong>Kerio</strong> Technologies servers. Upon startup of the test,<br />

three fake harmless intrusions of high, middle and low severity will be sent to the client’s<br />

address (i.e. to the IP address of your firewall). The test script then evaluates whether the<br />

firewall let the intrusion attempts in or blocked them. The Security log will also include<br />

three corresponding records informing of whether the firewall blocked, only logged or<br />

ignored the intrusions (for details, see chapter 22.11).<br />

Note: This test is designed only for purposes of the intrusion prevention system built in<br />

<strong>Kerio</strong> Control. It cannot be used for testing of other IDS/IPS.<br />

Use of known intruders databases (blacklists)<br />

In addition to detection of known intrusion types, it is also possible to detect and block<br />

traffic from IP addresses listed in web databases of known intruders (so called blacklists).<br />

In this case, all traffic from the IP address is logged and possibly blocked. Such<br />

method of detection and blocking of intruders is much faster and also less demanding<br />

than detection of individual intrusion types. However, there are also some disadvantages<br />

of this method. Blacklists cannot include IP addresses of all possible intruders as the<br />

intruders often use fake addresses. Blacklist also may include IP addresses of legitimate<br />

clients or servers. Therefore, it is possible to set the same actions for blacklists as for<br />

detected intrusions:<br />

• Log and drop — information about the detected traffic and blocked IP address<br />

will be recorded in the Security log and any network traffic from that IP address<br />

will be blocked.<br />

• Log — information about the detected traffic and blocked IP address will be only<br />

recorded in the Security log,<br />

• No action — the detected blacklisted IP address will not be considered as an<br />

intruder.<br />

Note: <strong>Kerio</strong> Control does not include the option of custom blacklist adding.<br />

Update of intrusions and known intruders databases<br />

For correct functionality of the intrusion detection system, it is necessary to update<br />

databases of known intrusions and intruder IP addresses regularly. <strong>Kerio</strong> Control allows<br />

to set an interval for regular automatic updates (the default value is 24 hours) and it is<br />

also possible to perform an immediate update if needed (e.g. after a longer electricity<br />

supply outage). Under usual circumstances there is no reason to disable automatic<br />

updates — non-updated databases decrease effectivity of the intrusion prevention<br />

114

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

Saved successfully!

Ooh no, something went wrong!