%YAML 1.1 --- # The default logging directory. Any log or output file will be # placed here if its not specified with a full path name. This can be # overridden with the -l command line parameter. default-log-dir: /var/log/suricata outputs: - fast: enabled: yes filename: fast.log - unified-log: enabled: yes filename: unified.log - unified-alert: enabled: yes filename: unified.alert - unified2-alert: enabled: yes filename: unified2.alert - http-log: enabled: yes filename: http.log - alert-debug: enabled: yes filename: alert-debug.log defrag: max-frags: 65535 prealloc: yes timeout: 60 # Flow settings: # By default, the reserved memory (memcap) for flows is 32MB. This is the limit # for flow allocation inside the engine. You can change this value to allow # more memory usage for flows. # The hash_size determine the size of the hash used to identify flows inside # the engine, and by default the value is 65536. # At the startup, the engine can preallocate a number of flows, to get a better # performance. The number of flows preallocated is 10000 by default. flow: memcap: 33554432 hash_size: 65536 prealloc: 10000 # Specific timeouts for flows. Here you can specify the timeouts that the # active flows will wait to transit from the current state to another, on each # protocol. The value of "new" determine the seconds to wait after a hanshake or # stream startup before the engine free the data of that flow it doesn't # change the state to established (usually if we don't receive more packets # of that flow). The value of "established" is the amount of # seconds that the engine will wait to free the flow if it spend that amount # without receiving new packets or closing the connection. "closed" is the # amount of time to wait after a flow is closed (usually zero). # # There's an emergency mode that will become active under attack circumstances, # making the engine to check flow status faster. This configuration variables # use the prefix "emergency_" and work similar as the normal ones. # Some timeouts doesn't apply to all the protocols, like "closed", for udp and # icmp. flow-timeouts: - default: new: 30 established: 300 closed: 0 emergency_new: 10 emergency_established: 100 emergency_closed: 0 - tcp: new: 60 established: 3600 closed: 120 emergency_new: 10 emergency_established: 300 emergency_closed: 20 - udp: new: 30 established: 300 emergency_new: 10 emergency_established: 100 - icmp: new: 30 established: 300 emergency_new: 10 emergency_established: 100 # Stream engine settings. # stream: # memcap: 67108864 # 64mb memcap # max_sessions: 262144 # 256k concurrent sessions # prealloc_sessions: 32768 # 32k sessions prealloc'd # midstream: false # don't allow midstream session pickups # async_oneside: false # don't enable async stream handling stream: # Logging configuration. This is not about logging IDS alerts, but # IDS output about what its doing, errors, etc. logging: # The default log level, can be overridden in an output section. default-log-level: debug # The default output format. Optional parameter, should default to # something reasonable if not provided. Can be overriden in an # output section. default-format: "<%t> - <%l>" # Default startup message. Optional parameter, should default to # something reasonable if not provided. Can be overridden in an # output section. default-startup-message: Your IDS has started. # A regex to filter output. Can be overridden in an output section. # Defaults to empty (no filter). default-output-filter: # Configure the outputs. If no outputs are specified the engine # will log to the console with an error log level. output: # Enable logging to the console. Be a little more verbose than # default, log info and more critical. - interface: console log-level: error # Log to a file as well. No log level specified so level will be # set to the default-log-level. - interface: file filename: /var/log/suricata.log # Log to syslog with facility local5. Again, no level specified so # will level will be set to default-log-level. We also override the # format as we don't want to log a timestamp, syslog will do that # for us. - interface: syslog facility: local5 format: "%l" # PF_RING configuration. for use with native PF_RING support # for more info see http://www.ntop.org/PF_RING.html pfring: # Default interface we will listen on. interface: eth0 # Default clusterid. PR_RING will load balance packets based on flow. # All threads/processes that will participate need to have the same # clusterid. clusterid: 99 # For FreeBSD ipfw(8) divert(4) support. # Please make sure you have ipfw_load="YES" and ipdivert_load="YES" # in /etc/loader.conf or kldload'ing the appropriate kernel modules. # Additionally, you need to have an ipfw rule for the engine to see # the packets from ipfw. For Example: # # ipfw add 100 divert 8000 ip from any to any # # The 8000 above should be the same number you passed on the command # line, i.e. -d 8000 # ipfw: # Reinject packets at the specified ipfw rule number. This config # option is the ipfw rule number AT WHICH rule processing continues # in the ipfw processing system after the engine has finished # inspecting the packet for acceptance. If no rule number is specified, # accepted packets are reinjected at the divert rule which they entered # and IPFW rule processing continues. No check is done to verify # this will rule makes sense so care must be taken to avoid loops in ipfw. # ## The following example tells the engine to reinject packets # back into the ipfw firewall AT rule number 5500: # # ipfw-reinjection-rule-number: 5500 # Set the default rule path here to search for the files. # if not set, it will look at the current working dir default-rule-path: /etc/suricata/rules/ rule-files: - attack-responses.rules - backdoor.rules - bad-traffic.rules - chat.rules - ddos.rules - deleted.rules - dns.rules - dos.rules - experimental.rules - exploit.rules - finger.rules - ftp.rules - icmp-info.rules - icmp.rules - imap.rules - info.rules - local.rules - misc.rules - multimedia.rules - mysql.rules - netbios.rules - nntp.rules - oracle.rules - other-ids.rules - p2p.rules - policy.rules - pop2.rules - pop3.rules - porn.rules - rpc.rules - rservices.rules - scada.rules - scan.rules - shellcode.rules - smtp.rules - snmp.rules - specific-threats.rules - spyware-put.rules - sql.rules - telnet.rules - tftp.rules - virus.rules - voip.rules - web-activex.rules - web-attacks.rules - web-cgi.rules - web-client.rules - web-coldfusion.rules - web-frontpage.rules - web-iis.rules - web-misc.rules - web-php.rules - x11.rules - emerging-attack_response.rules - emerging-dos.rules - emerging-exploit.rules - emerging-game.rules - emerging-inappropriate.rules - emerging-malware.rules - emerging-p2p.rules - emerging-policy.rules - emerging-scan.rules - emerging-virus.rules - emerging-voip.rules - emerging-web.rules - emerging-web_client.rules - emerging-web_server.rules - emerging-web_specific_apps.rules - emerging-user_agents.rules - emerging-current_events.rules classification-file: /etc/suricata/classification.config # Holds variables that would be used by the engine. vars: # Holds the address group vars that would be passed in a Signature. # These would be retrieved during the Signature address parsing stage. address-groups: HOME_NET: "[192.168.0.0/16,10.0.0.0/8,172.16.0.0/12]" EXTERNAL_NET: any HTTP_SERVERS: "$HOME_NET" SMTP_SERVERS: "$HOME_NET" SQL_SERVERS: "$HOME_NET" DNS_SERVERS: "$HOME_NET" TELNET_SERVERS: "$HOME_NET" AIM_SERVERS: any # Holds the port group vars that would be passed in a Signature. # These would be retrieved during the Signature port parsing stage. port-groups: HTTP_PORTS: "80" SHELLCODE_PORTS: "!80" ORACLE_PORTS: 1521 SSH_PORTS: 22