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.

Example 2: Filtering for services and users<br />

Chapter 19: Auditing and Reporting<br />

Auditing on the <strong>Sidewinder</strong> <strong>G2</strong><br />

The following example shows the format used to display HTTP network traffic<br />

audit records for a user named Lloyd:<br />

type t_attack and cmd httpp and username Lloyd<br />

where:<br />

• type t_attack — This field will filter audit records for all attack events.<br />

• cmd httpp — This field will filter the attack audit events to include only<br />

HTTP service records.<br />

• username Lloyd — This field will filter the HTTP attack events to include<br />

only events that are specific to actions performed by user name “Lloyd.”<br />

Example 3: Filtering for specific ports and IP addresses<br />

The following example shows the format used to display all network probe<br />

events on port 37337 and subnet 192.168.124.0/24 originating from burbs<br />

3 or 4. Enter text on one line:<br />

type t_netprobe and dst_port 37337 and dst_ip 192.168.124.0/<br />

24 and (src_burb 3 or src_burb 4)<br />

where:<br />

• type t_netprobe — This field will filter audit records for all network probe<br />

events.<br />

• dst_port 37337 — This field will filter the network probe events to include<br />

only records with a destination port <strong>of</strong> 37337.<br />

• dst_ip 192.168.124.0/24 — This field will filter the network probe events to<br />

include only records with a destination IP address <strong>of</strong> 192.168.124.0/24.<br />

• (src_burb 3 or src_burb 4) — This information will filter the network probe<br />

events to include only records with a source burb <strong>of</strong> 3 or 4.<br />

Example 4: Excluding information in a filter<br />

You can explicitly exclude certain types <strong>of</strong> audit information by placing the word<br />

“not” in front <strong>of</strong> a field. For example, the custom filter shown below will display<br />

all audit records EXCEPT attack records originating for the source IP address<br />

172.17.9.28:<br />

not type t_attack and src_ip 172.17.9.28<br />

where:<br />

• not type t_attack — This field will exclude any attack-based audit events.<br />

• src_ip 172.17.9.28 — This field will filter the non-attack audit events for<br />

records with a source address <strong>of</strong> 172.17.9.28.<br />

545

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

Saved successfully!

Ooh no, something went wrong!