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

Create successful ePaper yourself

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

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

Configuring new event types<br />

Configuring new<br />

event types<br />

Ignoring network<br />

probe attempts<br />

578<br />

You may decide that you would like to add a customized IPS attack or system<br />

event type to the pre-defined list. New entries can be created using the<br />

command line. Once added, the new event will appear on the appropriate list in<br />

the Admin Console. At that point, you may create new responses for that<br />

event.<br />

To add a new attack or system event type, do the following:<br />

1 Start a command line session with <strong>Sidewinder</strong> <strong>G2</strong> and log in.<br />

2 Use the srole command to switch to the administrator role.<br />

3 Enter the following command, using a single line:<br />

cf audit add filter name=name filter_type=system|attack<br />

sacap_filter=sacap_filter number=int comments=comments<br />

where:<br />

• name = name <strong>of</strong> the new event type.<br />

• system|attack = type <strong>of</strong> filter. This option determines if the new event<br />

type will appear on the IPS Response attack type list or the System<br />

Responses event list.<br />

• sacap_filter = string which identifies a sacap_filter expression to use<br />

• int = number <strong>of</strong> SNMP trap to use. See “<strong>Sidewinder</strong> <strong>G2</strong> SNMP traps”<br />

on page 579 for more information about SNMP traps.<br />

• comments = text that will appear in the Event tab’s Description field.<br />

Refer to the cf_audit and the sacap_filter man pages for information for<br />

configuring event types (referred to as filters) and responses (referred to as<br />

auditbots). Refer to acat -c for a list <strong>of</strong> current audit events.<br />

If a host on the network attempts to connect to the <strong>Sidewinder</strong> <strong>G2</strong> for a service<br />

that is not running, an audit record is generated and may trigger an alarm. An<br />

ignore list can be set up to ignore unimportant network probe audit events, but<br />

save the audit to keep track <strong>of</strong> the probe attempts. However, if connection<br />

attempts are frequent and are coming from a trusted network, then it may be<br />

desirable to ignore them completely and not audit the connection attempt by<br />

configuring the appropriate IP Filter rules.

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

Saved successfully!

Ooh no, something went wrong!