suricata(8) [debian man page]
SURICATA(8) System Manager's Manual SURICATA(8) NAME
suricata - Next Generation Intrusion Detection and Prevention Tool SYNOPSIS
suricata [options] DESCRIPTION
suricata is a network Intrusion Detection System (IDS). It is based on rules (and is fully compatible with snort rules) to detect a variety of attacks / probes by searching packet content. This new Engine supports Multi-Threading, Automatic Protocol Detection (IP, TCP, UDP, ICMP, HTTP, TLS, FTP and SMB), Gzip Decompression, Fast IP Matching and coming soon hardware acceleration on CUDA and OpenCL GPU cards. It supports acquiring packets through NFQUEUE, PCAP (live or offline) etc. OPTIONS
-c config_file Use configuration file config_file -i interface Sniff packets on interface. -r file Read the tcpdump-formatted file tcpdump-file. This will cause Suricata to read and process the file fed to it. This is useful for offline analysis. -q queue_id Sniff packets sent by the kernel through NFQUEUE. This allows running Suricata in inline mode (IPS) for packets captured by iptables using the NFQUEUE target. -s signatures Path to the signatures file. -l log_dir Path to the default log directory. -D Run as daemon --init-errors-fatal Enable fatal failure on signature init error. SEE ALSO
tcpdump(1), pcap(3). AUTHOR
suricata was written by the Open Information Security Foundation. This manual page was written by Pierre Chifflier <pollux@debian.org>, for the Debian project (and may be used by others). February 2010 SURICATA(8)
Check Out this Related Man Page
PADS(8) System Manager's Manual PADS(8) NAME
pads - Passive Asset Detection System SYNOPSIS
pads <DhUvV> <-c file > <-d file > <-g group > <-i interface > <-n network(s) > <-p file > <-r file > <-u file > <-w file > <expression> DESCRIPTION
PADS is a libpcap based detection engine used to passively detect network assets. It is designed to complement IDS technology by providing context to IDS alerts. Goals: - Passive: Records and identifies traffic seen on a network without actively "scanning" a system. There will never be a packet sent from the pads application. - Portable: Has the ability to be placed easily on a remote system. Does not require additional external libraries other than those associated with libpcap. - Lightweight: Logging is sent to a simple CSV file. There is no need for a database or other data repository installed on the local machine. All correlation is done outside of the pads program. OPTIONS
-h Display help / usage information. -D Run PADS in the background (daemon mode). -d file Dump banner data into a libpcap formatted file. This feature will dump the matched packet or the first 4 packets of an unmatched connection into a specified file. This can be used to further identify a service and also aid with signature development. Please keep in mind that this feature must be compiled into the application in order to use it. This can be done by adding '--enable-banner-grab' to the 'configure' step. -g group This switch allows you to specify a group that PADS will drop to after the libpcap interface has been initialized. -h Display help -i interface Specify an interface to be used. -n network list Specify a set of networks to be monitored. Only assets that exist within these networks will be recorded. The networks should be specified in the following format: 10.10.10.0/24,192.168.0.0/16 . -p pid file This switch allows you to specify a PID file to be used in conjunction with daemon (-D) mode. -r file Read packets from a libpcap formatted file. -u user This switch allows you to specify a user that PADS will drop to after the libpcap interface has been initialized. -w file Dump data into a file other than assets.csv. expression selects which packets will be processed. Please see tcpdump(1) for details on the libpcap primitives. SEE ALSO
pads.conf(8), pads-report(8), pads-archiver(8), tcpdump(8), pcre(3) COPYRIGHT
Copyright (C) 2004 Matt Shelton <matt@mattshelton.com> BUGS
Please send bug reports to the author. AUTHORS
Matt Shelton <matt@mattshelton.com> 2005/06/17 PADS(8)