18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

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.

Chapter 20: IPS Attack and System Event Responses<br />

Creating IPS attack responses<br />

570<br />

In this configuration, if an intruder launches 5 probe attempts in a 30 second<br />

period, a response is triggered. However, if the intruder sends 5 more<br />

probe attempts during the next 30 seconds, <strong>Sidewinder</strong> <strong>G2</strong> will not send<br />

another alert. However, if the response calls for a Strikeback (see next section),<br />

traffic will continue to be blackholed.<br />

After five minutes, if the threshold is again reached, another alert will be<br />

triggered.<br />

• Configure Strikeback — <strong>Sidewinder</strong> <strong>G2</strong> can blackhole, or ignore, traffic<br />

from a host that is sending suspect traffic.<br />

Caution:<strong>Sidewinder</strong> <strong>G2</strong> blackholes based on source address, as opposed to<br />

traffic type. If you choose to blackhole a host, all traffic from that host will be<br />

ignored.<br />

– Blackhole: Select this option to ignore all traffic from the suspect traffic’s<br />

source(s) for a set time period. The source <strong>of</strong> the attack is recorded in<br />

the audit event’s attack_ip field. The source <strong>of</strong> the suspect traffic may<br />

be the connection’s source IP address (a peer or a client) or destination<br />

IP address (if a server is attacking a client). If <strong>Sidewinder</strong> <strong>G2</strong> considers<br />

it likely that the source IP address could have been forged, it will leave<br />

the attack_ip field blank and not blackhole any IP address for this audit<br />

event. The apparent source and destination IP address is still recorded<br />

in the audit event.<br />

If you select the Blackhole option, you must also specify for how long<br />

you want to blackhole traffic.<br />

• Blackhole packets for x seconds where x is a value between 1 and<br />

100000.<br />

Tip: If you find you need to blackhole traffic for more than 100,000<br />

seconds (a little over 24 hours), consider creating an IP Filter deny rule for<br />

that traffic.<br />

– All attacking hosts: Select this option to blackhole all hosts involved in<br />

triggering the alert. For example, if you want an alert after 5 occurrences<br />

in 30 seconds and host A sent 4 occurrences and host B sent 1, all<br />

traffic from hosts A and B would be ignored for the set amount <strong>of</strong> time.<br />

– Each host responsible for y% <strong>of</strong> the attacks: Select this option to limit<br />

blackholing on a percentage basis. For example, if you set the<br />

percentage at 50% and host A caused 4 out <strong>of</strong> 5 attacks and host B<br />

caused 1 out <strong>of</strong> 5 attacks, only traffic from host A would be ignored.

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

Saved successfully!

Ooh no, something went wrong!