<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1435670003051_29779"><span></span></div><div id="yui_3_16_0_1_1435670003051_29783" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"><div id="yui_3_16_0_1_1435670003051_29782" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"><div id="yui_3_16_0_1_1435670003051_29784" class="y_msg_container"><div id="yiv3236810008"><div id="yui_3_16_0_1_1435670003051_29879"><div id="yui_3_16_0_1_1435670003051_29878" style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yiv3236810008yui_3_16_0_1_1435670003051_16936"><span></span></div><br><div id="yiv3236810008yui_3_16_0_1_1435670003051_16939" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yiv3236810008yui_3_16_0_1_1435670003051_16938" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yiv3236810008yui_3_16_0_1_1435670003051_16940" class="yiv3236810008y_msg_container"><div id="yiv3236810008">
<style><!--
#yiv3236810008
filtered {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;}
#yiv3236810008 filtered {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}
#yiv3236810008 filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
#yiv3236810008
p.yiv3236810008MsoNormal, #yiv3236810008 li.yiv3236810008MsoNormal, #yiv3236810008 div.yiv3236810008MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}
#yiv3236810008 a:link, #yiv3236810008 span.yiv3236810008MsoHyperlink
{color:#0563C1;text-decoration:underline;}
#yiv3236810008 a:visited, #yiv3236810008 span.yiv3236810008MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}
#yiv3236810008 span.yiv3236810008EmailStyle17
{font-family:"Calibri", sans-serif;color:windowtext;}
#yiv3236810008 .yiv3236810008MsoChpDefault
{font-family:"Calibri", sans-serif;}
#yiv3236810008 filtered {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv3236810008 div.yiv3236810008WordSection1
{}
--></style>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16943">
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16942" class="yiv3236810008WordSection1">
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16941" class="yiv3236810008MsoNormal">HI Everyone,</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16974" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16973" class="yiv3236810008MsoNormal">I truly hope someone can assist since I’ve hardly met a problem I can’t solve but I’ve spent a lot of time on this one.</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16966" class="yiv3236810008MsoNormal">Ubuntu 12.04 LTS </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16967" class="yiv3236810008MsoNormal">Suricata is working since I tried to enable fast.log and eve.json so I know the events are coming in from eth1 / span port.</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16972" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16968" class="yiv3236810008MsoNormal"><div id="yui_3_16_0_1_1435670003051_29951">The most that makes it to the SIEM is “snort open log source message” from the suricata host – but no actual events.</div><div id="yui_3_16_0_1_1435670003051_29963" dir="ltr">I have seen events coming into the fast.log, etc. I just cannot get them over to the SIEM.<br></div></div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16969" class="yiv3236810008MsoNormal">Below are the relevant configuration files. Suricata.yaml /etc/rsyslog.conf</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16970" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16971" class="yiv3236810008MsoNormal">Not sure I understand clearly how to use syslog to get the events over to the SIEM?</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16991" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16992" class="yiv3236810008MsoNormal">Charles</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16993" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16994" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16995" class="yiv3236810008MsoNormal">Snipped from bottom of rsyslog.conf<span style="font-family:Wingdings;">à</span> (tried using user.alert)</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16996" class="yiv3236810008MsoNormal">$IncludeConfig /etc/rsyslog.d/*.conf</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_16997" class="yiv3236810008MsoNormal">*.* @172.18.1.155:514</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_17026" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20000" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20098" class="yiv3236810008MsoNormal">#user.alert @172.18.1.155:514;rsyslogd</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20001" class="yiv3236810008MsoNormal"> </div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20002" class="yiv3236810008MsoNormal">#user.alert @172.18.1.155:514</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20100" class="yiv3236810008MsoNormal">root@bco10214:/admin#</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20102" style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in;">
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20101" class="yiv3236810008MsoNormal" style="border:none;padding:0in;"> </div>
</div>
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20104" style="border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in;">
<div id="yiv3236810008yui_3_16_0_1_1435670003051_20103" class="yiv3236810008MsoNormal" style="border:none;padding:0in;">suricata.yaml below</div>
</div><br></div></div></div>%YAML 1.1<br class="yiv3236810008">---<br class="yiv3236810008"><br class="yiv3236810008"># Suricata configuration file. In addition to the comments describing all<br class="yiv3236810008"># options in this file, full documentation can be found at:<br class="yiv3236810008"># https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricatayaml<br class="yiv3236810008"><br class="yiv3236810008"><br class="yiv3236810008"># Number of packets allowed to be processed simultaneously. Default is a<br class="yiv3236810008"># conservative 1024. A higher number will make sure CPU's/CPU cores will be<br class="yiv3236810008"># more easily kept busy, but may negatively impact caching.<br class="yiv3236810008">#<br class="yiv3236810008"># If you are using the CUDA pattern matcher (mpm-algo: ac-cuda), different rules<br class="yiv3236810008"># apply. In that case try something like 60000 or more. This is because the CUDA<br class="yiv3236810008"># pattern matcher buffers and scans as many packets as possible in parallel.<br class="yiv3236810008">#max-pending-packets: 1024<br class="yiv3236810008"><br class="yiv3236810008"># Runmode the engine should use. Please check --list-runmodes to get the available<br class="yiv3236810008"># runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned<br class="yiv3236810008"># load balancing).<br class="yiv3236810008">#runmode: autofp<br class="yiv3236810008"><br class="yiv3236810008"># Specifies the kind of flow load balancer used by the flow pinned autofp mode.<br class="yiv3236810008">#<br class="yiv3236810008"># Supported schedulers are:<br class="yiv3236810008">#<br class="yiv3236810008"># round-robin - Flows assigned to threads in a round robin fashion.<br class="yiv3236810008"># active-packets - Flows assigned to threads that have the lowest number of<br class="yiv3236810008"># unprocessed packets (default).<br class="yiv3236810008"># hash - Flow alloted usihng the address hash. More of a random<br class="yiv3236810008"># technique. Was the default in Suricata 1.2.1 and older.<br class="yiv3236810008">#<br class="yiv3236810008">#autofp-scheduler: active-packets<br class="yiv3236810008"><br class="yiv3236810008"># If suricata box is a router for the sniffed networks, set it to 'router'. If<br class="yiv3236810008"># it is a pure sniffing setup, set it to 'sniffer-only'.<br class="yiv3236810008"># If set to auto, the variable is internally switch to 'router' in IPS mode<br class="yiv3236810008"># and 'sniffer-only' in IDS mode.<br class="yiv3236810008"># This feature is currently only used by the reject* keywords.<br class="yiv3236810008">host-mode: auto<br class="yiv3236810008"><br class="yiv3236810008"># Run suricata as user and group.<br class="yiv3236810008">#run-as:<br class="yiv3236810008"># user: suri<br class="yiv3236810008"># group: suri<br class="yiv3236810008"><br class="yiv3236810008"># Default pid file.<br class="yiv3236810008"># Will use this file if no --pidfile in command options.<br class="yiv3236810008">#pid-file: /var/run/suricata.pid<br class="yiv3236810008"><br class="yiv3236810008"># Daemon working directory<br class="yiv3236810008"># Suricata will change directory to this one if provided<br class="yiv3236810008"># Default: "/"<br class="yiv3236810008">#daemon-directory: "/"<br class="yiv3236810008"><br class="yiv3236810008"># Preallocated size for packet. Default is 1514 which is the classical<br class="yiv3236810008"># size for pcap on ethernet. You should adjust this value to the highest<br class="yiv3236810008"># packet size (MTU + hardware header) on your system.<br class="yiv3236810008">#default-packet-size: 1514<br class="yiv3236810008"><br class="yiv3236810008"># The default logging directory. Any log or output file will be<br class="yiv3236810008"># placed here if its not specified with a full path name. This can be<br class="yiv3236810008"># overridden with the -l command line parameter.<br class="yiv3236810008">default-log-dir: /var/log/suricata/<br class="yiv3236810008"><br class="yiv3236810008"># Unix command socket can be used to pass commands to suricata.<br class="yiv3236810008"># An external tool can then connect to get information from suricata<br class="yiv3236810008"># or trigger some modifications of the engine. Set enabled to yes<br class="yiv3236810008"># to activate the feature. You can use the filename variable to set<br class="yiv3236810008"># the file name of the socket.<br class="yiv3236810008">unix-command:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> #filename: custom.socket<br class="yiv3236810008"><br class="yiv3236810008"># Configure the type of alert (and other) logging you would like.<br class="yiv3236810008">outputs:<br class="yiv3236810008"><br class="yiv3236810008"> # a line based alerts log similar to Snort's fast.log<br class="yiv3236810008"> - fast:<br class="yiv3236810008"> enabled: yes <br class="yiv3236810008"> filename: fast.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> # Extensible Event Format (nicknamed EVE) event log in JSON format<br class="yiv3236810008"> - eve-log:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> type: file <br class="yiv3236810008"> filename: eve.json<br class="yiv3236810008"> # the following are valid when type: syslog above<br class="yiv3236810008"> # identity: "suricata"<br class="yiv3236810008"> facility: local7<br class="yiv3236810008"> level: Info ## possible levels: Emergency, Alert, Critical,<br class="yiv3236810008"> ## Error, Warning, Notice, Info, Debug<br class="yiv3236810008"> types:<br class="yiv3236810008"> - alert<br class="yiv3236810008"> - http:<br class="yiv3236810008"> extended: yes # enable this for extended logging information<br class="yiv3236810008"> # custom allows additional http fields to be included in eve-log<br class="yiv3236810008"> # the example below adds three additional fields when uncommented<br class="yiv3236810008"> #custom: [Accept-Encoding, Accept-Language, Authorization]<br class="yiv3236810008"> - dns<br class="yiv3236810008"> - tls:<br class="yiv3236810008"> extended: yes # enable this for extended logging information<br class="yiv3236810008"> - files:<br class="yiv3236810008"> force-magic: no # force logging magic on all logged files<br class="yiv3236810008"> force-md5: no # force logging of md5 checksums<br class="yiv3236810008"> #- drop<br class="yiv3236810008"> - ssh<br class="yiv3236810008"><br class="yiv3236810008"> # alert output for use with Barnyard2<br class="yiv3236810008"> - unified2-alert:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: unified2.alert<br class="yiv3236810008"><br class="yiv3236810008"> # File size limit. Can be specified in kb, mb, gb. Just a number<br class="yiv3236810008"> # is parsed as bytes.<br class="yiv3236810008"> #limit: 32mb<br class="yiv3236810008"><br class="yiv3236810008"> # Sensor ID field of unified2 alerts.<br class="yiv3236810008"> #sensor-id: 0<br class="yiv3236810008"><br class="yiv3236810008"> # HTTP X-Forwarded-For support by adding the unified2 extra header that<br class="yiv3236810008"> # will contain the actual client IP address or by overwriting the source<br class="yiv3236810008"> # IP address (helpful when inspecting traffic that is being reversed<br class="yiv3236810008"> # proxied).<br class="yiv3236810008"> xff:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> # Two operation modes are available, "extra-data" and "overwrite". Note<br class="yiv3236810008"> # that in the "overwrite" mode, if the reported IP address in the HTTP<br class="yiv3236810008"> # X-Forwarded-For header is of a different version of the packet<br class="yiv3236810008"> # received, it will fall-back to "extra-data" mode.<br class="yiv3236810008"> mode: extra-data<br class="yiv3236810008"> # Header name were the actual IP address will be reported, if more than<br class="yiv3236810008"> # one IP address is present, the last IP address will be the one taken<br class="yiv3236810008"> # into consideration.<br class="yiv3236810008"> header: X-Forwarded-For <br class="yiv3236810008"><br class="yiv3236810008"> # a line based log of HTTP requests (no alerts)<br class="yiv3236810008"> - http-log:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> filename: http.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #extended: yes # enable this for extended logging information<br class="yiv3236810008"> #custom: yes # enabled the custom logging format (defined by customformat)<br class="yiv3236810008"> #customformat: "%{%D-%H:%M:%S}t.%z %{X-Forwarded-For}i %H %m %h %u %s %B %a:%p -> %A:%P"<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> # a line based log of TLS handshake parameters (no alerts)<br class="yiv3236810008"> - tls-log:<br class="yiv3236810008"> enabled: no # Log TLS connections.<br class="yiv3236810008"> filename: tls.log # File to store TLS logs.<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"> #extended: yes # Log extended information like fingerprint<br class="yiv3236810008"> certs-log-dir: certs # directory to store the certificates files<br class="yiv3236810008"><br class="yiv3236810008"> # a line based log of DNS requests and/or replies (no alerts)<br class="yiv3236810008"> - dns-log:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: dns.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> # a line based log to used with pcap file study.<br class="yiv3236810008"> # this module is dedicated to offline pcap parsing (empty output<br class="yiv3236810008"> # if used with another kind of input). It can interoperate with<br class="yiv3236810008"> # pcap parser like wireshark via the suriwire plugin.<br class="yiv3236810008"> - pcap-info:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"><br class="yiv3236810008"> # Packet log... log packets in pcap format. 2 modes of operation: "normal"<br class="yiv3236810008"> # and "sguil".<br class="yiv3236810008"> #<br class="yiv3236810008"> # In normal mode a pcap file "filename" is created in the default-log-dir,<br class="yiv3236810008"> # or are as specified by "dir". In Sguil mode "dir" indicates the base directory.<br class="yiv3236810008"> # In this base dir the pcaps are created in th directory structure Sguil expects:<br class="yiv3236810008"> #<br class="yiv3236810008"> # $sguil-base-dir/YYYY-MM-DD/$filename.<timestamp><br class="yiv3236810008"> #<br class="yiv3236810008"> # By default all packets are logged except:<br class="yiv3236810008"> # - TCP streams beyond stream.reassembly.depth<br class="yiv3236810008"> # - encrypted streams after the key exchange<br class="yiv3236810008"> #<br class="yiv3236810008"> - pcap-log:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: log.pcap<br class="yiv3236810008"><br class="yiv3236810008"> # File size limit. Can be specified in kb, mb, gb. Just a number<br class="yiv3236810008"> # is parsed as bytes.<br class="yiv3236810008"> limit: 1000mb<br class="yiv3236810008"><br class="yiv3236810008"> # If set to a value will enable ring buffer mode. Will keep Maximum of "max-files" of size "limit"<br class="yiv3236810008"> max-files: 2000<br class="yiv3236810008"><br class="yiv3236810008"> mode: normal # normal or sguil.<br class="yiv3236810008"> #sguil-base-dir: /nsm_data/<br class="yiv3236810008"> #ts-format: usec # sec or usec second format (default) is filename.sec usec is filename.sec.usec<br class="yiv3236810008"> use-stream-depth: no #If set to "yes" packets seen after reaching stream inspection depth are ignored. "no" logs all packets<br class="yiv3236810008"><br class="yiv3236810008"> # a full alerts log containing much information for signature writers<br class="yiv3236810008"> # or for investigating suspected false positives.<br class="yiv3236810008"> - alert-debug:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: alert-debug.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> # alert output to prelude (http://www.prelude-technologies.com/) only<br class="yiv3236810008"> # available if Suricata has been compiled with --enable-prelude<br class="yiv3236810008"> - alert-prelude:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> profile: suricata<br class="yiv3236810008"> log-packet-content: no<br class="yiv3236810008"> log-packet-header: yes<br class="yiv3236810008"><br class="yiv3236810008"> # Stats.log contains data from various counters of the suricata engine.<br class="yiv3236810008"> # The interval field (in seconds) tells after how long output will be written<br class="yiv3236810008"> # on the log file.<br class="yiv3236810008"> - stats:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> filename: stats.log<br class="yiv3236810008"> interval: 8<br class="yiv3236810008"><br class="yiv3236810008"> # a line based alerts log similar to fast.log into syslog<br class="yiv3236810008"> - syslog:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> # reported identity to syslog. If ommited the program name (usually<br class="yiv3236810008"> # suricata) will be used.<br class="yiv3236810008"> # identity: "suricata"<br class="yiv3236810008"> # facility: local5<br class="yiv3236810008"> level: Info ## possible levels: Emergency, Alert, Critical,<br class="yiv3236810008"> ## Error, Warning, Notice, Info, Debug<br class="yiv3236810008"><br class="yiv3236810008"> # a line based information for dropped packets in IPS mode<br class="yiv3236810008"> - drop:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: drop.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> # output module to store extracted files to disk<br class="yiv3236810008"> #<br class="yiv3236810008"> # The files are stored to the log-dir in a format "file.<id>" where <id> is<br class="yiv3236810008"> # an incrementing number starting at 1. For each file "file.<id>" a meta<br class="yiv3236810008"> # file "file.<id>.meta" is created.<br class="yiv3236810008"> #<br class="yiv3236810008"> # File extraction depends on a lot of things to be fully done:<br class="yiv3236810008"> # - stream reassembly depth. For optimal results, set this to 0 (unlimited)<br class="yiv3236810008"> # - http request / response body sizes. Again set to 0 for optimal results.<br class="yiv3236810008"> # - rules that contain the "filestore" keyword.<br class="yiv3236810008"> - file-store:<br class="yiv3236810008"> enabled: no # set to yes to enable<br class="yiv3236810008"> log-dir: files # directory to store the files<br class="yiv3236810008"> force-magic: no # force logging magic on all stored files<br class="yiv3236810008"> force-md5: no # force logging of md5 checksums<br class="yiv3236810008"> #waldo: file.waldo # waldo file to store the file_id across runs<br class="yiv3236810008"><br class="yiv3236810008"> # output module to log files tracked in a easily parsable json format<br class="yiv3236810008"> - file-log:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: files-json.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"> #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'<br class="yiv3236810008"><br class="yiv3236810008"> force-magic: no # force logging magic on all logged files<br class="yiv3236810008"> force-md5: no # force logging of md5 checksums<br class="yiv3236810008"><br class="yiv3236810008"># Magic file. The extension .mgc is added to the value here.<br class="yiv3236810008">#magic-file: /usr/share/file/magic<br class="yiv3236810008">magic-file: /usr/share/file/magic<br class="yiv3236810008"><br class="yiv3236810008"># When running in NFQ inline mode, it is possible to use a simulated<br class="yiv3236810008"># non-terminal NFQUEUE verdict.<br class="yiv3236810008"># This permit to do send all needed packet to suricata via this a rule:<br class="yiv3236810008"># iptables -I FORWARD -m mark ! --mark $MARK/$MASK -j NFQUEUE<br class="yiv3236810008"># And below, you can have your standard filtering ruleset. To activate<br class="yiv3236810008"># this mode, you need to set mode to 'repeat'<br class="yiv3236810008"># If you want packet to be sent to another queue after an ACCEPT decision<br class="yiv3236810008"># set mode to 'route' and set next-queue value.<br class="yiv3236810008"># On linux >= 3.1, you can set batchcount to a value > 1 to improve performance<br class="yiv3236810008"># by processing several packets before sending a verdict (worker runmode only).<br class="yiv3236810008"># On linux >= 3.6, you can set the fail-open option to yes to have the kernel<br class="yiv3236810008"># accept the packet if suricata is not able to keep pace.<br class="yiv3236810008">nfq:<br class="yiv3236810008"># mode: accept<br class="yiv3236810008"># repeat-mark: 1<br class="yiv3236810008"># repeat-mask: 1<br class="yiv3236810008"># route-queue: 2<br class="yiv3236810008"># batchcount: 20<br class="yiv3236810008"># fail-open: yes<br class="yiv3236810008"><br class="yiv3236810008">#nflog support<br class="yiv3236810008">nflog:<br class="yiv3236810008"> # netlink multicast group<br class="yiv3236810008"> # (the same as the iptables --nflog-group param)<br class="yiv3236810008"> # Group 0 is used by the kernel, so you can't use it<br class="yiv3236810008"> - group: 2<br class="yiv3236810008"> # netlink buffer size<br class="yiv3236810008"> buffer-size: 18432<br class="yiv3236810008"> # put default value here<br class="yiv3236810008"> - group: default<br class="yiv3236810008"> # set number of packet to queue inside kernel<br class="yiv3236810008"> qthreshold: 1<br class="yiv3236810008"> # set the delay before flushing packet in the queue inside kernel<br class="yiv3236810008"> qtimeout: 100<br class="yiv3236810008"> # netlink max buffer size<br class="yiv3236810008"> max-size: 20000<br class="yiv3236810008"><br class="yiv3236810008"># af-packet support<br class="yiv3236810008"># Set threads to > 1 to use PACKET_FANOUT support<br class="yiv3236810008">af-packet:<br class="yiv3236810008"> - interface: eth1<br class="yiv3236810008"> # Number of receive threads (>1 will enable experimental flow pinned<br class="yiv3236810008"> # runmode)<br class="yiv3236810008"> threads: 1<br class="yiv3236810008"> # Default clusterid. AF_PACKET will load balance packets based on flow.<br class="yiv3236810008"> # All threads/processes that will participate need to have the same<br class="yiv3236810008"> # clusterid.<br class="yiv3236810008"> cluster-id: 99<br class="yiv3236810008"> # Default AF_PACKET cluster type. AF_PACKET can load balance per flow or per hash.<br class="yiv3236810008"> # This is only supported for Linux kernel > 3.1<br class="yiv3236810008"> # possible value are:<br class="yiv3236810008"> # * cluster_round_robin: round robin load balancing<br class="yiv3236810008"> # * cluster_flow: all packets of a given flow are send to the same socket<br class="yiv3236810008"> # * cluster_cpu: all packets treated in kernel by a CPU are send to the same socket<br class="yiv3236810008"> cluster-type: cluster_flow<br class="yiv3236810008"> # In some fragmentation case, the hash can not be computed. If "defrag" is set<br class="yiv3236810008"> # to yes, the kernel will do the needed defragmentation before sending the packets.<br class="yiv3236810008"> defrag: yes<br class="yiv3236810008"> # To use the ring feature of AF_PACKET, set 'use-mmap' to yes<br class="yiv3236810008"> use-mmap: yes<br class="yiv3236810008"> # Ring size will be computed with respect to max_pending_packets and number<br class="yiv3236810008"> # of threads. You can set manually the ring size in number of packets by setting<br class="yiv3236810008"> # the following value. If you are using flow cluster-type and have really network<br class="yiv3236810008"> # intensive single-flow you could want to set the ring-size independantly of the number<br class="yiv3236810008"> # of threads:<br class="yiv3236810008"> #ring-size: 2048<br class="yiv3236810008"> # On busy system, this could help to set it to yes to recover from a packet drop<br class="yiv3236810008"> # phase. This will result in some packets (at max a ring flush) being non treated.<br class="yiv3236810008"> #use-emergency-flush: yes<br class="yiv3236810008"> # recv buffer size, increase value could improve performance<br class="yiv3236810008"> # buffer-size: 32768<br class="yiv3236810008"> # Set to yes to disable promiscuous mode<br class="yiv3236810008"> # disable-promisc: no<br class="yiv3236810008"> # Choose checksum verification mode for the interface. At the moment<br class="yiv3236810008"> # of the capture, some packets may be with an invalid checksum due to<br class="yiv3236810008"> # offloading to the network card of the checksum computation.<br class="yiv3236810008"> # Possible values are:<br class="yiv3236810008"> # - kernel: use indication sent by kernel for each packet (default)<br class="yiv3236810008"> # - yes: checksum validation is forced<br class="yiv3236810008"> # - no: checksum validation is disabled<br class="yiv3236810008"> # - auto: suricata uses a statistical approach to detect when<br class="yiv3236810008"> # checksum off-loading is used.<br class="yiv3236810008"> # Warning: 'checksum-validation' must be set to yes to have any validation<br class="yiv3236810008"> #checksum-checks: kernel<br class="yiv3236810008"> # BPF filter to apply to this interface. The pcap filter syntax apply here.<br class="yiv3236810008"> #bpf-filter: port 80 or udp<br class="yiv3236810008"> # You can use the following variables to activate AF_PACKET tap od IPS mode.<br class="yiv3236810008"> # If copy-mode is set to ips or tap, the traffic coming to the current<br class="yiv3236810008"> # interface will be copied to the copy-iface interface. If 'tap' is set, the<br class="yiv3236810008"> # copy is complete. If 'ips' is set, the packet matching a 'drop' action<br class="yiv3236810008"> # will not be copied.<br class="yiv3236810008"> #copy-mode: ips<br class="yiv3236810008"> #copy-iface: eth1<br class="yiv3236810008"> - interface: eth1<br class="yiv3236810008"> threads: 1<br class="yiv3236810008"> cluster-id: 98<br class="yiv3236810008"> cluster-type: cluster_flow<br class="yiv3236810008"> defrag: yes<br class="yiv3236810008"> # buffer-size: 32768<br class="yiv3236810008"> # disable-promisc: no<br class="yiv3236810008"> # Put default values here<br class="yiv3236810008"> - interface: default<br class="yiv3236810008"> #threads: 2<br class="yiv3236810008"> #use-mmap: yes<br class="yiv3236810008"><br class="yiv3236810008">legacy:<br class="yiv3236810008"> uricontent: enabled<br class="yiv3236810008"><br class="yiv3236810008"># You can specify a threshold config file by setting "threshold-file"<br class="yiv3236810008"># to the path of the threshold config file:<br class="yiv3236810008"># threshold-file: /etc/suricata/threshold.config<br class="yiv3236810008"><br class="yiv3236810008"># The detection engine builds internal groups of signatures. The engine<br class="yiv3236810008"># allow us to specify the profile to use for them, to manage memory on an<br class="yiv3236810008"># efficient way keeping a good performance. For the profile keyword you<br class="yiv3236810008"># can use the words "low", "medium", "high" or "custom". If you use custom<br class="yiv3236810008"># make sure to define the values at "- custom-values" as your convenience.<br class="yiv3236810008"># Usually you would prefer medium/high/low.<br class="yiv3236810008">#<br class="yiv3236810008"># "sgh mpm-context", indicates how the staging should allot mpm contexts for<br class="yiv3236810008"># the signature groups. "single" indicates the use of a single context for<br class="yiv3236810008"># all the signature group heads. "full" indicates a mpm-context for each<br class="yiv3236810008"># group head. "auto" lets the engine decide the distribution of contexts<br class="yiv3236810008"># based on the information the engine gathers on the patterns from each<br class="yiv3236810008"># group head.<br class="yiv3236810008">#<br class="yiv3236810008"># The option inspection-recursion-limit is used to limit the recursive calls<br class="yiv3236810008"># in the content inspection code. For certain payload-sig combinations, we<br class="yiv3236810008"># might end up taking too much time in the content inspection code.<br class="yiv3236810008"># If the argument specified is 0, the engine uses an internally defined<br class="yiv3236810008"># default limit. On not specifying a value, we use no limits on the recursion.<br class="yiv3236810008">detect-engine:<br class="yiv3236810008"> - profile: medium<br class="yiv3236810008"> - custom-values:<br class="yiv3236810008"> toclient-src-groups: 2<br class="yiv3236810008"> toclient-dst-groups: 2<br class="yiv3236810008"> toclient-sp-groups: 2<br class="yiv3236810008"> toclient-dp-groups: 3<br class="yiv3236810008"> toserver-src-groups: 2<br class="yiv3236810008"> toserver-dst-groups: 4<br class="yiv3236810008"> toserver-sp-groups: 2<br class="yiv3236810008"> toserver-dp-groups: 25<br class="yiv3236810008"> - sgh-mpm-context: auto<br class="yiv3236810008"> - inspection-recursion-limit: 3000<br class="yiv3236810008"> # When rule-reload is enabled, sending a USR2 signal to the Suricata process<br class="yiv3236810008"> # will trigger a live rule reload. Experimental feature, use with care.<br class="yiv3236810008"> #- rule-reload: true<br class="yiv3236810008"> # If set to yes, the loading of signatures will be made after the capture<br class="yiv3236810008"> # is started. This will limit the downtime in IPS mode.<br class="yiv3236810008"> #- delayed-detect: yes<br class="yiv3236810008"><br class="yiv3236810008"># Suricata is multi-threaded. Here the threading can be influenced.<br class="yiv3236810008">threading:<br class="yiv3236810008"> # On some cpu's/architectures it is beneficial to tie individual threads<br class="yiv3236810008"> # to specific CPU's/CPU cores. In this case all threads are tied to CPU0,<br class="yiv3236810008"> # and each extra CPU/core has one "detect" thread.<br class="yiv3236810008"> #<br class="yiv3236810008"> # On Intel Core2 and Nehalem CPU's enabling this will degrade performance.<br class="yiv3236810008"> #<br class="yiv3236810008"> set-cpu-affinity: no<br class="yiv3236810008"> # Tune cpu affinity of suricata threads. Each family of threads can be bound<br class="yiv3236810008"> # on specific CPUs.<br class="yiv3236810008"> cpu-affinity:<br class="yiv3236810008"> - management-cpu-set:<br class="yiv3236810008"> cpu: [ 0 ] # include only these cpus in affinity settings<br class="yiv3236810008"> - receive-cpu-set:<br class="yiv3236810008"> cpu: [ 0 ] # include only these cpus in affinity settings<br class="yiv3236810008"> - decode-cpu-set:<br class="yiv3236810008"> cpu: [ 0, 1 ]<br class="yiv3236810008"> mode: "balanced"<br class="yiv3236810008"> - stream-cpu-set:<br class="yiv3236810008"> cpu: [ "0-1" ]<br class="yiv3236810008"> - detect-cpu-set:<br class="yiv3236810008"> cpu: [ "all" ]<br class="yiv3236810008"> mode: "exclusive" # run detect threads in these cpus<br class="yiv3236810008"> # Use explicitely 3 threads and don't compute number by using<br class="yiv3236810008"> # detect-thread-ratio variable:<br class="yiv3236810008"> # threads: 3<br class="yiv3236810008"> prio:<br class="yiv3236810008"> low: [ 0 ]<br class="yiv3236810008"> medium: [ "1-2" ]<br class="yiv3236810008"> high: [ 3 ]<br class="yiv3236810008"> default: "medium"<br class="yiv3236810008"> - verdict-cpu-set:<br class="yiv3236810008"> cpu: [ 0 ]<br class="yiv3236810008"> prio:<br class="yiv3236810008"> default: "high"<br class="yiv3236810008"> - reject-cpu-set:<br class="yiv3236810008"> cpu: [ 0 ]<br class="yiv3236810008"> prio:<br class="yiv3236810008"> default: "low"<br class="yiv3236810008"> - output-cpu-set:<br class="yiv3236810008"> cpu: [ "all" ]<br class="yiv3236810008"> prio:<br class="yiv3236810008"> default: "medium"<br class="yiv3236810008"> #<br class="yiv3236810008"> # By default Suricata creates one "detect" thread per available CPU/CPU core.<br class="yiv3236810008"> # This setting allows controlling this behaviour. A ratio setting of 2 will<br class="yiv3236810008"> # create 2 detect threads for each CPU/CPU core. So for a dual core CPU this<br class="yiv3236810008"> # will result in 4 detect threads. If values below 1 are used, less threads<br class="yiv3236810008"> # are created. So on a dual core CPU a setting of 0.5 results in 1 detect<br class="yiv3236810008"> # thread being created. Regardless of the setting at a minimum 1 detect<br class="yiv3236810008"> # thread will always be created.<br class="yiv3236810008"> #<br class="yiv3236810008"> detect-thread-ratio: 1.5<br class="yiv3236810008"><br class="yiv3236810008"># Cuda configuration.<br class="yiv3236810008">cuda:<br class="yiv3236810008"> # The "mpm" profile. On not specifying any of these parameters, the engine's<br class="yiv3236810008"> # internal default values are used, which are same as the ones specified in<br class="yiv3236810008"> # in the default conf file.<br class="yiv3236810008"> mpm:<br class="yiv3236810008"> # The minimum length required to buffer data to the gpu.<br class="yiv3236810008"> # Anything below this is MPM'ed on the CPU.<br class="yiv3236810008"> # Can be specified in kb, mb, gb. Just a number indicates it's in bytes.<br class="yiv3236810008"> # A value of 0 indicates there's no limit.<br class="yiv3236810008"> data-buffer-size-min-limit: 0<br class="yiv3236810008"> # The maximum length for data that we would buffer to the gpu.<br class="yiv3236810008"> # Anything over this is MPM'ed on the CPU.<br class="yiv3236810008"> # Can be specified in kb, mb, gb. Just a number indicates it's in bytes.<br class="yiv3236810008"> data-buffer-size-max-limit: 1500<br class="yiv3236810008"> # The ring buffer size used by the CudaBuffer API to buffer data.<br class="yiv3236810008"> cudabuffer-buffer-size: 500mb<br class="yiv3236810008"> # The max chunk size that can be sent to the gpu in a single go.<br class="yiv3236810008"> gpu-transfer-size: 50mb<br class="yiv3236810008"> # The timeout limit for batching of packets in microseconds.<br class="yiv3236810008"> batching-timeout: 2000<br class="yiv3236810008"> # The device to use for the mpm. Currently we don't support load balancing<br class="yiv3236810008"> # on multiple gpus. In case you have multiple devices on your system, you<br class="yiv3236810008"> # can specify the device to use, using this conf. By default we hold 0, to<br class="yiv3236810008"> # specify the first device cuda sees. To find out device-id associated with<br class="yiv3236810008"> # the card(s) on the system run "suricata --list-cuda-cards".<br class="yiv3236810008"> device-id: 0<br class="yiv3236810008"> # No of Cuda streams used for asynchronous processing. All values > 0 are valid.<br class="yiv3236810008"> # For this option you need a device with Compute Capability > 1.0.<br class="yiv3236810008"> cuda-streams: 2<br class="yiv3236810008"><br class="yiv3236810008"># Select the multi pattern algorithm you want to run for scan/search the<br class="yiv3236810008"># in the engine. The supported algorithms are b2g, b2gc, b2gm, b3g, wumanber,<br class="yiv3236810008"># ac and ac-gfbs.<br class="yiv3236810008">#<br class="yiv3236810008"># The mpm you choose also decides the distribution of mpm contexts for<br class="yiv3236810008"># signature groups, specified by the conf - "detect-engine.sgh-mpm-context".<br class="yiv3236810008"># Selecting "ac" as the mpm would require "detect-engine.sgh-mpm-context"<br class="yiv3236810008"># to be set to "single", because of ac's memory requirements, unless the<br class="yiv3236810008"># ruleset is small enough to fit in one's memory, in which case one can<br class="yiv3236810008"># use "full" with "ac". Rest of the mpms can be run in "full" mode.<br class="yiv3236810008">#<br class="yiv3236810008"># There is also a CUDA pattern matcher (only available if Suricata was<br class="yiv3236810008"># compiled with --enable-cuda: b2g_cuda. Make sure to update your<br class="yiv3236810008"># max-pending-packets setting above as well if you use b2g_cuda.<br class="yiv3236810008"><br class="yiv3236810008">mpm-algo: ac<br class="yiv3236810008"><br class="yiv3236810008"># The memory settings for hash size of these algorithms can vary from lowest<br class="yiv3236810008"># (2048) - low (4096) - medium (8192) - high (16384) - higher (32768) - max<br class="yiv3236810008"># (65536). The bloomfilter sizes of these algorithms can vary from low (512) -<br class="yiv3236810008"># medium (1024) - high (2048).<br class="yiv3236810008">#<br class="yiv3236810008"># For B2g/B3g algorithms, there is a support for two different scan/search<br class="yiv3236810008"># algorithms. For B2g the scan algorithms are B2gScan & B2gScanBNDMq, and<br class="yiv3236810008"># search algorithms are B2gSearch & B2gSearchBNDMq. For B3g scan algorithms<br class="yiv3236810008"># are B3gScan & B3gScanBNDMq, and search algorithms are B3gSearch &<br class="yiv3236810008"># B3gSearchBNDMq.<br class="yiv3236810008">#<br class="yiv3236810008"># For B2g the different scan/search algorithms and, hash and bloom<br class="yiv3236810008"># filter size settings. For B3g the different scan/search algorithms and, hash<br class="yiv3236810008"># and bloom filter size settings. For wumanber the hash and bloom filter size<br class="yiv3236810008"># settings.<br class="yiv3236810008"><br class="yiv3236810008">pattern-matcher:<br class="yiv3236810008"> - b2gc:<br class="yiv3236810008"> search-algo: B2gSearchBNDMq<br class="yiv3236810008"> hash-size: low<br class="yiv3236810008"> bf-size: medium<br class="yiv3236810008"> - b2gm:<br class="yiv3236810008"> search-algo: B2gSearchBNDMq<br class="yiv3236810008"> hash-size: low<br class="yiv3236810008"> bf-size: medium<br class="yiv3236810008"> - b2g:<br class="yiv3236810008"> search-algo: B2gSearchBNDMq<br class="yiv3236810008"> hash-size: low<br class="yiv3236810008"> bf-size: medium<br class="yiv3236810008"> - b3g:<br class="yiv3236810008"> search-algo: B3gSearchBNDMq<br class="yiv3236810008"> hash-size: low<br class="yiv3236810008"> bf-size: medium<br class="yiv3236810008"> - wumanber:<br class="yiv3236810008"> hash-size: low<br class="yiv3236810008"> bf-size: medium<br class="yiv3236810008"><br class="yiv3236810008"># Defrag settings:<br class="yiv3236810008"><br class="yiv3236810008">defrag:<br class="yiv3236810008"> memcap: 32mb<br class="yiv3236810008"> hash-size: 65536<br class="yiv3236810008"> trackers: 65535 # number of defragmented flows to follow<br class="yiv3236810008"> max-frags: 65535 # number of fragments to keep (higher than trackers)<br class="yiv3236810008"> prealloc: yes<br class="yiv3236810008"> timeout: 60<br class="yiv3236810008"><br class="yiv3236810008"># Enable defrag per host settings<br class="yiv3236810008"># host-config:<br class="yiv3236810008">#<br class="yiv3236810008"># - dmz:<br class="yiv3236810008"># timeout: 30<br class="yiv3236810008"># address: [192.168.1.0/24, 127.0.0.0/8, 1.1.1.0/24, 2.2.2.0/24, "1.1.1.1", "2.2.2.2", "::1"]<br class="yiv3236810008">#<br class="yiv3236810008"># - lan:<br class="yiv3236810008"># timeout: 45<br class="yiv3236810008"># address:<br class="yiv3236810008"># - 192.168.0.0/24<br class="yiv3236810008"># - 192.168.10.0/24<br class="yiv3236810008"># - 172.16.14.0/24<br class="yiv3236810008"><br class="yiv3236810008"># Flow settings:<br class="yiv3236810008"># By default, the reserved memory (memcap) for flows is 32MB. This is the limit<br class="yiv3236810008"># for flow allocation inside the engine. You can change this value to allow<br class="yiv3236810008"># more memory usage for flows.<br class="yiv3236810008"># The hash-size determine the size of the hash used to identify flows inside<br class="yiv3236810008"># the engine, and by default the value is 65536.<br class="yiv3236810008"># At the startup, the engine can preallocate a number of flows, to get a better<br class="yiv3236810008"># performance. The number of flows preallocated is 10000 by default.<br class="yiv3236810008"># emergency-recovery is the percentage of flows that the engine need to<br class="yiv3236810008"># prune before unsetting the emergency state. The emergency state is activated<br class="yiv3236810008"># when the memcap limit is reached, allowing to create new flows, but<br class="yiv3236810008"># prunning them with the emergency timeouts (they are defined below).<br class="yiv3236810008"># If the memcap is reached, the engine will try to prune flows<br class="yiv3236810008"># with the default timeouts. If it doens't find a flow to prune, it will set<br class="yiv3236810008"># the emergency bit and it will try again with more agressive timeouts.<br class="yiv3236810008"># If that doesn't work, then it will try to kill the last time seen flows<br class="yiv3236810008"># not in use.<br class="yiv3236810008"># The memcap can be specified in kb, mb, gb. Just a number indicates it's<br class="yiv3236810008"># in bytes.<br class="yiv3236810008"><br class="yiv3236810008">flow:<br class="yiv3236810008"> memcap: 64mb<br class="yiv3236810008"> hash-size: 65536<br class="yiv3236810008"> prealloc: 10000<br class="yiv3236810008"> emergency-recovery: 30<br class="yiv3236810008"><br class="yiv3236810008"># This option controls the use of vlan ids in the flow (and defrag)<br class="yiv3236810008"># hashing. Normally this should be enabled, but in some (broken)<br class="yiv3236810008"># setups where both sides of a flow are not tagged with the same vlan<br class="yiv3236810008"># tag, we can ignore the vlan id's in the flow hashing.<br class="yiv3236810008">vlan:<br class="yiv3236810008"> use-for-tracking: true<br class="yiv3236810008"><br class="yiv3236810008"># Specific timeouts for flows. Here you can specify the timeouts that the<br class="yiv3236810008"># active flows will wait to transit from the current state to another, on each<br class="yiv3236810008"># protocol. The value of "new" determine the seconds to wait after a hanshake or<br class="yiv3236810008"># stream startup before the engine free the data of that flow it doesn't<br class="yiv3236810008"># change the state to established (usually if we don't receive more packets<br class="yiv3236810008"># of that flow). The value of "established" is the amount of<br class="yiv3236810008"># seconds that the engine will wait to free the flow if it spend that amount<br class="yiv3236810008"># without receiving new packets or closing the connection. "closed" is the<br class="yiv3236810008"># amount of time to wait after a flow is closed (usually zero).<br class="yiv3236810008">#<br class="yiv3236810008"># There's an emergency mode that will become active under attack circumstances,<br class="yiv3236810008"># making the engine to check flow status faster. This configuration variables<br class="yiv3236810008"># use the prefix "emergency-" and work similar as the normal ones.<br class="yiv3236810008"># Some timeouts doesn't apply to all the protocols, like "closed", for udp and<br class="yiv3236810008"># icmp.<br class="yiv3236810008"><br class="yiv3236810008">flow-timeouts:<br class="yiv3236810008"><br class="yiv3236810008"> default:<br class="yiv3236810008"> new: 30<br class="yiv3236810008"> established: 300<br class="yiv3236810008"> closed: 0<br class="yiv3236810008"> emergency-new: 10<br class="yiv3236810008"> emergency-established: 100<br class="yiv3236810008"> emergency-closed: 0<br class="yiv3236810008"> tcp:<br class="yiv3236810008"> new: 60<br class="yiv3236810008"> established: 3600<br class="yiv3236810008"> closed: 120<br class="yiv3236810008"> emergency-new: 10<br class="yiv3236810008"> emergency-established: 300<br class="yiv3236810008"> emergency-closed: 20<br class="yiv3236810008"> udp:<br class="yiv3236810008"> new: 30<br class="yiv3236810008"> established: 300<br class="yiv3236810008"> emergency-new: 10<br class="yiv3236810008"> emergency-established: 100<br class="yiv3236810008"> icmp:<br class="yiv3236810008"> new: 30<br class="yiv3236810008"> established: 300<br class="yiv3236810008"> emergency-new: 10<br class="yiv3236810008"> emergency-established: 100<br class="yiv3236810008"><br class="yiv3236810008"># Stream engine settings. Here the TCP stream tracking and reassembly<br class="yiv3236810008"># engine is configured.<br class="yiv3236810008">#<br class="yiv3236810008"># stream:<br class="yiv3236810008"># memcap: 32mb # Can be specified in kb, mb, gb. Just a<br class="yiv3236810008"># # number indicates it's in bytes.<br class="yiv3236810008"># checksum-validation: yes # To validate the checksum of received<br class="yiv3236810008"># # packet. If csum validation is specified as<br class="yiv3236810008"># # "yes", then packet with invalid csum will not<br class="yiv3236810008"># # be processed by the engine stream/app layer.<br class="yiv3236810008"># # Warning: locally generated trafic can be<br class="yiv3236810008"># # generated without checksum due to hardware offload<br class="yiv3236810008"># # of checksum. You can control the handling of checksum<br class="yiv3236810008"># # on a per-interface basis via the 'checksum-checks'<br class="yiv3236810008"># # option<br class="yiv3236810008"># prealloc-sessions: 2k # 2k sessions prealloc'd per stream thread<br class="yiv3236810008"># midstream: false # don't allow midstream session pickups<br class="yiv3236810008"># async-oneside: false # don't enable async stream handling<br class="yiv3236810008"># inline: no # stream inline mode<br class="yiv3236810008"># max-synack-queued: 5 # Max different SYN/ACKs to queue<br class="yiv3236810008">#<br class="yiv3236810008"># reassembly:<br class="yiv3236810008"># memcap: 64mb # Can be specified in kb, mb, gb. Just a number<br class="yiv3236810008"># # indicates it's in bytes.<br class="yiv3236810008"># depth: 1mb # Can be specified in kb, mb, gb. Just a number<br class="yiv3236810008"># # indicates it's in bytes.<br class="yiv3236810008"># toserver-chunk-size: 2560 # inspect raw stream in chunks of at least<br class="yiv3236810008"># # this size. Can be specified in kb, mb,<br class="yiv3236810008"># # gb. Just a number indicates it's in bytes.<br class="yiv3236810008"># # The max acceptable size is 4024 bytes.<br class="yiv3236810008"># toclient-chunk-size: 2560 # inspect raw stream in chunks of at least<br class="yiv3236810008"># # this size. Can be specified in kb, mb,<br class="yiv3236810008"># # gb. Just a number indicates it's in bytes.<br class="yiv3236810008"># # The max acceptable size is 4024 bytes.<br class="yiv3236810008"># randomize-chunk-size: yes # Take a random value for chunk size around the specified value.<br class="yiv3236810008"># # This lower the risk of some evasion technics but could lead<br class="yiv3236810008"># # detection change between runs. It is set to 'yes' by default.<br class="yiv3236810008"># randomize-chunk-range: 10 # If randomize-chunk-size is active, the value of chunk-size is<br class="yiv3236810008"># # a random value between (1 - randomize-chunk-range/100)*randomize-chunk-size<br class="yiv3236810008"># # and (1 + randomize-chunk-range/100)*randomize-chunk-size. Default value<br class="yiv3236810008"># # of randomize-chunk-range is 10.<br class="yiv3236810008">#<br class="yiv3236810008"># raw: yes # 'Raw' reassembly enabled or disabled.<br class="yiv3236810008"># # raw is for content inspection by detection<br class="yiv3236810008"># # engine.<br class="yiv3236810008">#<br class="yiv3236810008"># chunk-prealloc: 250 # Number of preallocated stream chunks. These<br class="yiv3236810008"># # are used during stream inspection (raw).<br class="yiv3236810008"># segments: # Settings for reassembly segment pool.<br class="yiv3236810008"># - size: 4 # Size of the (data)segment for a pool<br class="yiv3236810008"># prealloc: 256 # Number of segments to prealloc and keep<br class="yiv3236810008"># # in the pool.<br class="yiv3236810008">#<br class="yiv3236810008">stream:<br class="yiv3236810008"> memcap: 32mb<br class="yiv3236810008"> checksum-validation: yes # reject wrong csums<br class="yiv3236810008"> inline: auto # auto will use inline mode in IPS mode, yes or no set it statically<br class="yiv3236810008"> reassembly:<br class="yiv3236810008"> memcap: 128mb<br class="yiv3236810008"> depth: 1mb # reassemble 1mb into a stream<br class="yiv3236810008"> toserver-chunk-size: 2560<br class="yiv3236810008"> toclient-chunk-size: 2560<br class="yiv3236810008"> randomize-chunk-size: yes<br class="yiv3236810008"> #randomize-chunk-range: 10<br class="yiv3236810008"> #raw: yes<br class="yiv3236810008"> #chunk-prealloc: 250<br class="yiv3236810008"> #segments:<br class="yiv3236810008"> # - size: 4<br class="yiv3236810008"> # prealloc: 256<br class="yiv3236810008"> # - size: 16<br class="yiv3236810008"> # prealloc: 512<br class="yiv3236810008"> # - size: 112<br class="yiv3236810008"> # prealloc: 512<br class="yiv3236810008"> # - size: 248<br class="yiv3236810008"> # prealloc: 512<br class="yiv3236810008"> # - size: 512<br class="yiv3236810008"> # prealloc: 512<br class="yiv3236810008"> # - size: 768<br class="yiv3236810008"> # prealloc: 1024<br class="yiv3236810008"> # - size: 1448<br class="yiv3236810008"> # prealloc: 1024<br class="yiv3236810008"> # - size: 65535<br class="yiv3236810008"> # prealloc: 128<br class="yiv3236810008"><br class="yiv3236810008"># Host table:<br class="yiv3236810008">#<br class="yiv3236810008"># Host table is used by tagging and per host thresholding subsystems.<br class="yiv3236810008">#<br class="yiv3236810008">host:<br class="yiv3236810008"> hash-size: 4096<br class="yiv3236810008"> prealloc: 1000<br class="yiv3236810008"> memcap: 16777216<br class="yiv3236810008"><br class="yiv3236810008"># Logging configuration. This is not about logging IDS alerts, but<br class="yiv3236810008"># IDS output about what its doing, errors, etc.<br class="yiv3236810008">logging:<br class="yiv3236810008"><br class="yiv3236810008"> # The default log level, can be overridden in an output section.<br class="yiv3236810008"> # Note that debug level logging will only be emitted if Suricata was<br class="yiv3236810008"> # compiled with the --enable-debug configure option.<br class="yiv3236810008"> #<br class="yiv3236810008"> # This value is overriden by the SC_LOG_LEVEL env var.<br class="yiv3236810008"> default-log-level: notice<br class="yiv3236810008"><br class="yiv3236810008"> # The default output format. Optional parameter, should default to<br class="yiv3236810008"> # something reasonable if not provided. Can be overriden in an<br class="yiv3236810008"> # output section. You can leave this out to get the default.<br class="yiv3236810008"> #<br class="yiv3236810008"> # This value is overriden by the SC_LOG_FORMAT env var.<br class="yiv3236810008"> #default-log-format: "[%i] %t - (%f:%l) <%d> (%n) -- "<br class="yiv3236810008"><br class="yiv3236810008"> # A regex to filter output. Can be overridden in an output section.<br class="yiv3236810008"> # Defaults to empty (no filter).<br class="yiv3236810008"> #<br class="yiv3236810008"> # This value is overriden by the SC_LOG_OP_FILTER env var.<br class="yiv3236810008"> default-output-filter:<br class="yiv3236810008"><br class="yiv3236810008"> # Define your logging outputs. If none are defined, or they are all<br class="yiv3236810008"> # disabled you will get the default - console output.<br class="yiv3236810008"> outputs:<br class="yiv3236810008"> - console:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> - file:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: /var/log/suricata.log<br class="yiv3236810008"> - syslog:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> facility: local7<br class="yiv3236810008"> format: "[%i] <%d> -- "<br class="yiv3236810008"><br class="yiv3236810008"># Tilera mpipe configuration. for use on Tilera TILE-Gx.<br class="yiv3236810008">mpipe:<br class="yiv3236810008"><br class="yiv3236810008"> # Load balancing modes: "static", "dynamic", "sticky", or "round-robin".<br class="yiv3236810008"> load-balance: dynamic<br class="yiv3236810008"><br class="yiv3236810008"> # Number of Packets in each ingress packet queue. Must be 128, 512, 2028 or 65536<br class="yiv3236810008"> iqueue-packets: 2048<br class="yiv3236810008"><br class="yiv3236810008"> # List of interfaces we will listen on.<br class="yiv3236810008"> inputs:<br class="yiv3236810008"> - interface: xgbe2<br class="yiv3236810008"> - interface: xgbe3<br class="yiv3236810008"> - interface: xgbe4<br class="yiv3236810008"><br class="yiv3236810008"><br class="yiv3236810008"> # Relative weight of memory for packets of each mPipe buffer size.<br class="yiv3236810008"> stack:<br class="yiv3236810008"> size128: 0<br class="yiv3236810008"> size256: 9<br class="yiv3236810008"> size512: 0<br class="yiv3236810008"> size1024: 0<br class="yiv3236810008"> size1664: 7<br class="yiv3236810008"> size4096: 0<br class="yiv3236810008"> size10386: 0<br class="yiv3236810008"> size16384: 0<br class="yiv3236810008"><br class="yiv3236810008"># PF_RING configuration. for use with native PF_RING support<br class="yiv3236810008"># for more info see http://www.ntop.org/PF_RING.html<br class="yiv3236810008">pfring:<br class="yiv3236810008"> - interface: eth1<br class="yiv3236810008"> # Number of receive threads (>1 will enable experimental flow pinned<br class="yiv3236810008"> # runmode)<br class="yiv3236810008"> threads: 1<br class="yiv3236810008"><br class="yiv3236810008"> # Default clusterid. PF_RING will load balance packets based on flow.<br class="yiv3236810008"> # All threads/processes that will participate need to have the same<br class="yiv3236810008"> # clusterid.<br class="yiv3236810008"> cluster-id: 99<br class="yiv3236810008"><br class="yiv3236810008"> # Default PF_RING cluster type. PF_RING can load balance per flow or per hash.<br class="yiv3236810008"> # This is only supported in versions of PF_RING > 4.1.1.<br class="yiv3236810008"> cluster-type: cluster_flow<br class="yiv3236810008"> # bpf filter for this interface<br class="yiv3236810008"> #bpf-filter: tcp<br class="yiv3236810008"> # Choose checksum verification mode for the interface. At the moment<br class="yiv3236810008"> # of the capture, some packets may be with an invalid checksum due to<br class="yiv3236810008"> # offloading to the network card of the checksum computation.<br class="yiv3236810008"> # Possible values are:<br class="yiv3236810008"> # - rxonly: only compute checksum for packets received by network card.<br class="yiv3236810008"> # - yes: checksum validation is forced<br class="yiv3236810008"> # - no: checksum validation is disabled<br class="yiv3236810008"> # - auto: suricata uses a statistical approach to detect when<br class="yiv3236810008"> # checksum off-loading is used. (default)<br class="yiv3236810008"> # Warning: 'checksum-validation' must be set to yes to have any validation<br class="yiv3236810008"> #checksum-checks: auto<br class="yiv3236810008"> # Second interface<br class="yiv3236810008"> #- interface: eth1<br class="yiv3236810008"> # threads: 3<br class="yiv3236810008"> # cluster-id: 93<br class="yiv3236810008"> # cluster-type: cluster_flow<br class="yiv3236810008"> # Put default values here<br class="yiv3236810008"> - interface: default<br class="yiv3236810008"> #threads: 2<br class="yiv3236810008"><br class="yiv3236810008">pcap:<br class="yiv3236810008"> - interface: eth1<br class="yiv3236810008"> # On Linux, pcap will try to use mmaped capture and will use buffer-size<br class="yiv3236810008"> # as total of memory used by the ring. So set this to something bigger<br class="yiv3236810008"> # than 1% of your bandwidth.<br class="yiv3236810008"> #buffer-size: 16777216<br class="yiv3236810008"> #bpf-filter: "tcp and port 25"<br class="yiv3236810008"> # Choose checksum verification mode for the interface. At the moment<br class="yiv3236810008"> # of the capture, some packets may be with an invalid checksum due to<br class="yiv3236810008"> # offloading to the network card of the checksum computation.<br class="yiv3236810008"> # Possible values are:<br class="yiv3236810008"> # - yes: checksum validation is forced<br class="yiv3236810008"> # - no: checksum validation is disabled<br class="yiv3236810008"> # - auto: suricata uses a statistical approach to detect when<br class="yiv3236810008"> # checksum off-loading is used. (default)<br class="yiv3236810008"> # Warning: 'checksum-validation' must be set to yes to have any validation<br class="yiv3236810008"> #checksum-checks: auto<br class="yiv3236810008"> # With some accelerator cards using a modified libpcap (like myricom), you<br class="yiv3236810008"> # may want to have the same number of capture threads as the number of capture<br class="yiv3236810008"> # rings. In this case, set up the threads variable to N to start N threads<br class="yiv3236810008"> # listening on the same interface.<br class="yiv3236810008"> #threads: 16<br class="yiv3236810008"> # set to no to disable promiscuous mode:<br class="yiv3236810008"> #promisc: no<br class="yiv3236810008"> # set snaplen, if not set it defaults to MTU if MTU can be known<br class="yiv3236810008"> # via ioctl call and to full capture if not.<br class="yiv3236810008"> #snaplen: 1518<br class="yiv3236810008"> # Put default values here<br class="yiv3236810008"> - interface: default<br class="yiv3236810008"> #checksum-checks: auto<br class="yiv3236810008"><br class="yiv3236810008">pcap-file:<br class="yiv3236810008"> # Possible values are:<br class="yiv3236810008"> # - yes: checksum validation is forced<br class="yiv3236810008"> # - no: checksum validation is disabled<br class="yiv3236810008"> # - auto: suricata uses a statistical approach to detect when<br class="yiv3236810008"> # checksum off-loading is used. (default)<br class="yiv3236810008"> # Warning: 'checksum-validation' must be set to yes to have checksum tested<br class="yiv3236810008"> checksum-checks: auto<br class="yiv3236810008"><br class="yiv3236810008"># For FreeBSD ipfw(8) divert(4) support.<br class="yiv3236810008"># Please make sure you have ipfw_load="YES" and ipdivert_load="YES"<br class="yiv3236810008"># in /etc/loader.conf or kldload'ing the appropriate kernel modules.<br class="yiv3236810008"># Additionally, you need to have an ipfw rule for the engine to see<br class="yiv3236810008"># the packets from ipfw. For Example:<br class="yiv3236810008">#<br class="yiv3236810008"># ipfw add 100 divert 8000 ip from any to any<br class="yiv3236810008">#<br class="yiv3236810008"># The 8000 above should be the same number you passed on the command<br class="yiv3236810008"># line, i.e. -d 8000<br class="yiv3236810008">#<br class="yiv3236810008">ipfw:<br class="yiv3236810008"><br class="yiv3236810008"> # Reinject packets at the specified ipfw rule number. This config<br class="yiv3236810008"> # option is the ipfw rule number AT WHICH rule processing continues<br class="yiv3236810008"> # in the ipfw processing system after the engine has finished<br class="yiv3236810008"> # inspecting the packet for acceptance. If no rule number is specified,<br class="yiv3236810008"> # accepted packets are reinjected at the divert rule which they entered<br class="yiv3236810008"> # and IPFW rule processing continues. No check is done to verify<br class="yiv3236810008"> # this will rule makes sense so care must be taken to avoid loops in ipfw.<br class="yiv3236810008"> #<br class="yiv3236810008"> ## The following example tells the engine to reinject packets<br class="yiv3236810008"> # back into the ipfw firewall AT rule number 5500:<br class="yiv3236810008"> #<br class="yiv3236810008"> # ipfw-reinjection-rule-number: 5500<br class="yiv3236810008"><br class="yiv3236810008"># Set the default rule path here to search for the files.<br class="yiv3236810008"># if not set, it will look at the current working dir<br class="yiv3236810008">default-rule-path: /etc/suricata/rules<br class="yiv3236810008">rule-files:<br class="yiv3236810008"> - botcc.rules<br class="yiv3236810008"> - ciarmy.rules<br class="yiv3236810008"> - compromised.rules<br class="yiv3236810008"> - drop.rules<br class="yiv3236810008"> - dshield.rules<br class="yiv3236810008"> - emerging-activex.rules<br class="yiv3236810008"> - emerging-attack_response.rules<br class="yiv3236810008"> - emerging-chat.rules<br class="yiv3236810008"> - emerging-current_events.rules<br class="yiv3236810008"> - emerging-dns.rules<br class="yiv3236810008"> - emerging-dos.rules<br class="yiv3236810008"> - emerging-exploit.rules<br class="yiv3236810008"> - emerging-ftp.rules<br class="yiv3236810008"> - emerging-games.rules<br class="yiv3236810008"> - emerging-icmp_info.rules<br class="yiv3236810008"># - emerging-icmp.rules<br class="yiv3236810008"> - emerging-imap.rules<br class="yiv3236810008"> - emerging-inappropriate.rules<br class="yiv3236810008"> - emerging-malware.rules<br class="yiv3236810008"> - emerging-misc.rules<br class="yiv3236810008"> - emerging-mobile_malware.rules<br class="yiv3236810008"> - emerging-netbios.rules<br class="yiv3236810008"> - emerging-p2p.rules<br class="yiv3236810008"> - emerging-policy.rules<br class="yiv3236810008"> - emerging-pop3.rules<br class="yiv3236810008"> - emerging-rpc.rules<br class="yiv3236810008"> - emerging-scada.rules<br class="yiv3236810008"> - emerging-scan.rules<br class="yiv3236810008"> - emerging-shellcode.rules<br class="yiv3236810008"> - emerging-smtp.rules<br class="yiv3236810008"> - emerging-snmp.rules<br class="yiv3236810008"> - emerging-sql.rules<br class="yiv3236810008"> - emerging-telnet.rules<br class="yiv3236810008"> - emerging-tftp.rules<br class="yiv3236810008"> - emerging-trojan.rules<br class="yiv3236810008"> - emerging-user_agents.rules<br class="yiv3236810008"> - emerging-voip.rules<br class="yiv3236810008"> - emerging-web_client.rules<br class="yiv3236810008"> - emerging-web_server.rules<br class="yiv3236810008"> - emerging-web_specific_apps.rules<br class="yiv3236810008"> - emerging-worm.rules<br class="yiv3236810008"> - tor.rules<br class="yiv3236810008"> - decoder-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"> - stream-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"> - http-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"> - smtp-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"> - dns-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"> - tls-events.rules # available in suricata sources under rules dir<br class="yiv3236810008"><br class="yiv3236810008">classification-file: /etc/suricata/classification.config<br class="yiv3236810008">reference-config-file: /etc/suricata/reference.config<br class="yiv3236810008"><br class="yiv3236810008"># Holds variables that would be used by the engine.<br class="yiv3236810008">vars:<br class="yiv3236810008"><br class="yiv3236810008"> # Holds the address group vars that would be passed in a Signature.<br class="yiv3236810008"> # These would be retrieved during the Signature address parsing stage.<br class="yiv3236810008"> address-groups:<br class="yiv3236810008"><br class="yiv3236810008"> HOME_NET: "[172.18.1.0/24, 192.168.0.0/16,10.0.0.0/8,172.16.0.0/12]"<br class="yiv3236810008"><br class="yiv3236810008"> EXTERNAL_NET: "!$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> HTTP_SERVERS: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> SMTP_SERVERS: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> SQL_SERVERS: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> DNS_SERVERS: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> TELNET_SERVERS: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> AIM_SERVERS: "$EXTERNAL_NET"<br class="yiv3236810008"><br class="yiv3236810008"> DNP3_SERVER: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> DNP3_CLIENT: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> MODBUS_CLIENT: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> MODBUS_SERVER: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> ENIP_CLIENT: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> ENIP_SERVER: "$HOME_NET"<br class="yiv3236810008"><br class="yiv3236810008"> # Holds the port group vars that would be passed in a Signature.<br class="yiv3236810008"> # These would be retrieved during the Signature port parsing stage.<br class="yiv3236810008"> port-groups:<br class="yiv3236810008"><br class="yiv3236810008"> HTTP_PORTS: "80"<br class="yiv3236810008"><br class="yiv3236810008"> SHELLCODE_PORTS: "!80"<br class="yiv3236810008"><br class="yiv3236810008"> ORACLE_PORTS: 1521<br class="yiv3236810008"><br class="yiv3236810008"> SSH_PORTS: 22<br class="yiv3236810008"><br class="yiv3236810008"> DNP3_PORTS: 20000<br class="yiv3236810008"><br class="yiv3236810008"># Set the order of alerts bassed on actions<br class="yiv3236810008"># The default order is pass, drop, reject, alert<br class="yiv3236810008">action-order:<br class="yiv3236810008"> - pass<br class="yiv3236810008"> - drop<br class="yiv3236810008"> - reject<br class="yiv3236810008"> - alert<br class="yiv3236810008"><br class="yiv3236810008"># IP Reputation<br class="yiv3236810008">#reputation-categories-file: /etc/suricata/iprep/categories.txt<br class="yiv3236810008">#default-reputation-path: /etc/suricata/iprep<br class="yiv3236810008">#reputation-files:<br class="yiv3236810008"># - reputation.list<br class="yiv3236810008"><br class="yiv3236810008"># Host specific policies for defragmentation and TCP stream<br class="yiv3236810008"># reassembly. The host OS lookup is done using a radix tree, just<br class="yiv3236810008"># like a routing table so the most specific entry matches.<br class="yiv3236810008">host-os-policy:<br class="yiv3236810008"> # Make the default policy windows.<br class="yiv3236810008"> windows: [0.0.0.0/0]<br class="yiv3236810008"> bsd: []<br class="yiv3236810008"> bsd-right: []<br class="yiv3236810008"> old-linux: []<br class="yiv3236810008"> linux: [10.0.0.0/8, 192.168.1.100, "8762:2352:6241:7245:E000:0000:0000:0000"]<br class="yiv3236810008"> old-solaris: []<br class="yiv3236810008"> solaris: ["::1"]<br class="yiv3236810008"> hpux10: []<br class="yiv3236810008"> hpux11: []<br class="yiv3236810008"> irix: []<br class="yiv3236810008"> macos: []<br class="yiv3236810008"> vista: []<br class="yiv3236810008"> windows2k3: []<br class="yiv3236810008"><br class="yiv3236810008"><br class="yiv3236810008"># Limit for the maximum number of asn1 frames to decode (default 256)<br class="yiv3236810008">asn1-max-frames: 256<br class="yiv3236810008"><br class="yiv3236810008"># When run with the option --engine-analysis, the engine will read each of<br class="yiv3236810008"># the parameters below, and print reports for each of the enabled sections<br class="yiv3236810008"># and exit. The reports are printed to a file in the default log dir<br class="yiv3236810008"># given by the parameter "default-log-dir", with engine reporting<br class="yiv3236810008"># subsection below printing reports in its own report file.<br class="yiv3236810008">engine-analysis:<br class="yiv3236810008"> # enables printing reports for fast-pattern for every rule.<br class="yiv3236810008"> rules-fast-pattern: yes<br class="yiv3236810008"> # enables printing reports for each rule<br class="yiv3236810008"> rules: yes<br class="yiv3236810008"><br class="yiv3236810008">#recursion and match limits for PCRE where supported<br class="yiv3236810008">pcre:<br class="yiv3236810008"> match-limit: 3500<br class="yiv3236810008"> match-limit-recursion: 1500<br class="yiv3236810008"><br class="yiv3236810008"># Holds details on the app-layer. The protocols section details each protocol.<br class="yiv3236810008"># Under each protocol, the default value for detection-enabled and "<br class="yiv3236810008"># parsed-enabled is yes, unless specified otherwise.<br class="yiv3236810008"># Each protocol covers enabling/disabling parsers for all ipprotos<br class="yiv3236810008"># the app-layer protocol runs on. For example "dcerpc" refers to the tcp<br class="yiv3236810008"># version of the protocol as well as the udp version of the protocol.<br class="yiv3236810008"># The option "enabled" takes 3 values - "yes", "no", "detection-only".<br class="yiv3236810008"># "yes" enables both detection and the parser, "no" disables both, and<br class="yiv3236810008"># "detection-only" enables detection only(parser disabled).<br class="yiv3236810008">app-layer:<br class="yiv3236810008"> protocols:<br class="yiv3236810008"> tls:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> detection-ports:<br class="yiv3236810008"> dp: 443<br class="yiv3236810008"><br class="yiv3236810008"> #no-reassemble: yes<br class="yiv3236810008"> dcerpc:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> ftp:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> ssh:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> smtp:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> imap:<br class="yiv3236810008"> enabled: detection-only<br class="yiv3236810008"> msn:<br class="yiv3236810008"> enabled: detection-only<br class="yiv3236810008"> smb:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> detection-ports:<br class="yiv3236810008"> dp: 139<br class="yiv3236810008"> # smb2 detection is disabled internally inside the engine.<br class="yiv3236810008"> #smb2:<br class="yiv3236810008"> # enabled: yes<br class="yiv3236810008"> dns:<br class="yiv3236810008"> # memcaps. Globally and per flow/state.<br class="yiv3236810008"> #global-memcap: 16mb<br class="yiv3236810008"> #state-memcap: 512kb<br class="yiv3236810008"><br class="yiv3236810008"> # How many unreplied DNS requests are considered a flood.<br class="yiv3236810008"> # If the limit is reached, app-layer-event:dns.flooded; will match.<br class="yiv3236810008"> #request-flood: 500<br class="yiv3236810008"><br class="yiv3236810008"> tcp:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> detection-ports:<br class="yiv3236810008"> dp: 53<br class="yiv3236810008"> udp:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> detection-ports:<br class="yiv3236810008"> dp: 53<br class="yiv3236810008"> http:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> # memcap: 64mb<br class="yiv3236810008"><br class="yiv3236810008"> ###########################################################################<br class="yiv3236810008"> # Configure libhtp.<br class="yiv3236810008"> #<br class="yiv3236810008"> #<br class="yiv3236810008"> # default-config: Used when no server-config matches<br class="yiv3236810008"> # personality: List of personalities used by default<br class="yiv3236810008"> # request-body-limit: Limit reassembly of request body for inspection<br class="yiv3236810008"> # by http_client_body & pcre /P option.<br class="yiv3236810008"> # response-body-limit: Limit reassembly of response body for inspection<br class="yiv3236810008"> # by file_data, http_server_body & pcre /Q option.<br class="yiv3236810008"> # double-decode-path: Double decode path section of the URI<br class="yiv3236810008"> # double-decode-query: Double decode query section of the URI<br class="yiv3236810008"> #<br class="yiv3236810008"> # server-config: List of server configurations to use if address matches<br class="yiv3236810008"> # address: List of ip addresses or networks for this block<br class="yiv3236810008"> # personalitiy: List of personalities used by this block<br class="yiv3236810008"> # request-body-limit: Limit reassembly of request body for inspection<br class="yiv3236810008"> # by http_client_body & pcre /P option.<br class="yiv3236810008"> # response-body-limit: Limit reassembly of response body for inspection<br class="yiv3236810008"> # by file_data, http_server_body & pcre /Q option.<br class="yiv3236810008"> # double-decode-path: Double decode path section of the URI<br class="yiv3236810008"> # double-decode-query: Double decode query section of the URI<br class="yiv3236810008"> #<br class="yiv3236810008"> # uri-include-all: Include all parts of the URI. By default the<br class="yiv3236810008"> # 'scheme', username/password, hostname and port<br class="yiv3236810008"> # are excluded. Setting this option to true adds<br class="yiv3236810008"> # all of them to the normalized uri as inspected<br class="yiv3236810008"> # by http_uri, urilen, pcre with /U and the other<br class="yiv3236810008"> # keywords that inspect the normalized uri.<br class="yiv3236810008"> # Note that this does not affect http_raw_uri.<br class="yiv3236810008"> # Also, note that including all was the default in<br class="yiv3236810008"> # 1.4 and 2.0beta1.<br class="yiv3236810008"> #<br class="yiv3236810008"> # meta-field-limit: Hard size limit for request and response size<br class="yiv3236810008"> # limits. Applies to request line and headers,<br class="yiv3236810008"> # response line and headers. Does not apply to<br class="yiv3236810008"> # request or response bodies. Default is 18k.<br class="yiv3236810008"> # If this limit is reached an event is raised.<br class="yiv3236810008"> #<br class="yiv3236810008"> # Currently Available Personalities:<br class="yiv3236810008"> # Minimal<br class="yiv3236810008"> # Generic<br class="yiv3236810008"> # IDS (default)<br class="yiv3236810008"> # IIS_4_0<br class="yiv3236810008"> # IIS_5_0<br class="yiv3236810008"> # IIS_5_1<br class="yiv3236810008"> # IIS_6_0<br class="yiv3236810008"> # IIS_7_0<br class="yiv3236810008"> # IIS_7_5<br class="yiv3236810008"> # Apache_2<br class="yiv3236810008"> ###########################################################################<br class="yiv3236810008"> libhtp:<br class="yiv3236810008"><br class="yiv3236810008"> default-config:<br class="yiv3236810008"> personality: IDS<br class="yiv3236810008"><br class="yiv3236810008"> # Can be specified in kb, mb, gb. Just a number indicates<br class="yiv3236810008"> # it's in bytes.<br class="yiv3236810008"> request-body-limit: 3072<br class="yiv3236810008"> response-body-limit: 3072<br class="yiv3236810008"><br class="yiv3236810008"> # inspection limits<br class="yiv3236810008"> request-body-minimal-inspect-size: 32kb<br class="yiv3236810008"> request-body-inspect-window: 4kb<br class="yiv3236810008"> response-body-minimal-inspect-size: 32kb<br class="yiv3236810008"> response-body-inspect-window: 4kb<br class="yiv3236810008"> # Take a random value for inspection sizes around the specified value.<br class="yiv3236810008"> # This lower the risk of some evasion technics but could lead<br class="yiv3236810008"> # detection change between runs. It is set to 'yes' by default.<br class="yiv3236810008"> #randomize-inspection-sizes: yes<br class="yiv3236810008"> # If randomize-inspection-sizes is active, the value of various<br class="yiv3236810008"> # inspection size will be choosen in the [1 - range%, 1 + range%]<br class="yiv3236810008"> # range<br class="yiv3236810008"> # Default value of randomize-inspection-range is 10.<br class="yiv3236810008"> #randomize-inspection-range: 10<br class="yiv3236810008"><br class="yiv3236810008"> # decoding<br class="yiv3236810008"> double-decode-path: no<br class="yiv3236810008"> double-decode-query: no<br class="yiv3236810008"><br class="yiv3236810008"> server-config:<br class="yiv3236810008"><br class="yiv3236810008"> #- apache:<br class="yiv3236810008"> # address: [192.168.1.0/24, 127.0.0.0/8, "::1"]<br class="yiv3236810008"> # personality: Apache_2<br class="yiv3236810008"> # # Can be specified in kb, mb, gb. Just a number indicates<br class="yiv3236810008"> # # it's in bytes.<br class="yiv3236810008"> # request-body-limit: 4096<br class="yiv3236810008"> # response-body-limit: 4096<br class="yiv3236810008"> # double-decode-path: no<br class="yiv3236810008"> # double-decode-query: no<br class="yiv3236810008"><br class="yiv3236810008"> #- iis7:<br class="yiv3236810008"> # address:<br class="yiv3236810008"> # - 192.168.0.0/24<br class="yiv3236810008"> # - 192.168.10.0/24<br class="yiv3236810008"> # personality: IIS_7_0<br class="yiv3236810008"> # # Can be specified in kb, mb, gb. Just a number indicates<br class="yiv3236810008"> # # it's in bytes.<br class="yiv3236810008"> # request-body-limit: 4096<br class="yiv3236810008"> # response-body-limit: 4096<br class="yiv3236810008"> # double-decode-path: no<br class="yiv3236810008"> # double-decode-query: no<br class="yiv3236810008"><br class="yiv3236810008"># Profiling settings. Only effective if Suricata has been built with the<br class="yiv3236810008"># the --enable-profiling configure flag.<br class="yiv3236810008">#<br class="yiv3236810008">profiling:<br class="yiv3236810008"> # Run profiling for every xth packet. The default is 1, which means we<br class="yiv3236810008"> # profile every packet. If set to 1000, one packet is profiled for every<br class="yiv3236810008"> # 1000 received.<br class="yiv3236810008"> #sample-rate: 1000<br class="yiv3236810008"><br class="yiv3236810008"> # rule profiling<br class="yiv3236810008"> rules:<br class="yiv3236810008"><br class="yiv3236810008"> # Profiling can be disabled here, but it will still have a<br class="yiv3236810008"> # performance impact if compiled in.<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> filename: rule_perf.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"><br class="yiv3236810008"> # Sort options: ticks, avgticks, checks, matches, maxticks<br class="yiv3236810008"> sort: avgticks<br class="yiv3236810008"><br class="yiv3236810008"> # Limit the number of items printed at exit.<br class="yiv3236810008"> limit: 100<br class="yiv3236810008"><br class="yiv3236810008"> # per keyword profiling<br class="yiv3236810008"> keywords:<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> filename: keyword_perf.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"><br class="yiv3236810008"> # packet profiling<br class="yiv3236810008"> packets:<br class="yiv3236810008"><br class="yiv3236810008"> # Profiling can be disabled here, but it will still have a<br class="yiv3236810008"> # performance impact if compiled in.<br class="yiv3236810008"> enabled: yes<br class="yiv3236810008"> filename: packet_stats.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"><br class="yiv3236810008"> # per packet csv output<br class="yiv3236810008"> csv:<br class="yiv3236810008"><br class="yiv3236810008"> # Output can be disabled here, but it will still have a<br class="yiv3236810008"> # performance impact if compiled in.<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: packet_stats.csv<br class="yiv3236810008"><br class="yiv3236810008"> # profiling of locking. Only available when Suricata was built with<br class="yiv3236810008"> # --enable-profiling-locks.<br class="yiv3236810008"> locks:<br class="yiv3236810008"> enabled: no<br class="yiv3236810008"> filename: lock_stats.log<br class="yiv3236810008"> append: yes<br class="yiv3236810008"><br class="yiv3236810008"># Suricata core dump configuration. Limits the size of the core dump file to<br class="yiv3236810008"># approximately max-dump. The actual core dump size will be a multiple of the<br class="yiv3236810008"># page size. Core dumps that would be larger than max-dump are truncated. On<br class="yiv3236810008"># Linux, the actual core dump size may be a few pages larger than max-dump.<br class="yiv3236810008"># Setting max-dump to 0 disables core dumping.<br class="yiv3236810008"># Setting max-dump to 'unlimited' will give the full core dump file.<br class="yiv3236810008"># On 32-bit Linux, a max-dump value >= ULONG_MAX may cause the core dump size<br class="yiv3236810008"># to be 'unlimited'.<br class="yiv3236810008"><br class="yiv3236810008">coredump:<br class="yiv3236810008"> max-dump: unlimited<br class="yiv3236810008"><br class="yiv3236810008">napatech:<br class="yiv3236810008"> # The Host Buffer Allowance for all streams<br class="yiv3236810008"> # (-1 = OFF, 1 - 100 = percentage of the host buffer that can be held back)<br class="yiv3236810008"> hba: -1<br class="yiv3236810008"><br class="yiv3236810008"> # use_all_streams set to "yes" will query the Napatech service for all configured<br class="yiv3236810008"> # streams and listen on all of them. When set to "no" the streams config array<br class="yiv3236810008"> # will be used.<br class="yiv3236810008"> use-all-streams: yes<br class="yiv3236810008"><br class="yiv3236810008"> # The streams to listen on<br class="yiv3236810008"> streams: [1, 2, 3]<br class="yiv3236810008"><br class="yiv3236810008"># Includes. Files included here will be handled as if they were<br class="yiv3236810008"># inlined in this configuration file.<br class="yiv3236810008">#include: include1.yaml<br class="yiv3236810008"><div id="yiv3236810008yui_3_16_0_1_1435670003051_21461" dir="ltr">#include: include2.yaml</div></div> <div id="yiv3236810008yui_3_16_0_1_1435670003051_16940" class="yiv3236810008"><div class="yiv3236810008" id="yiv3236810008"> </div><br class="yiv3236810008"></div></div> </div> </div></div></div><br><br></div> </div> </div> </div></body></html>