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