5 ## IPFire specific configuration file - an untouched example configuration
6 ## can be found in suricata-example.yaml.
11 # Include HOME_NET declaration from external file.
12 include: /var/ipfire/suricata/suricata-homenet.yaml
14 # Include DNS_SERVERS declaration from external file.
15 include: /var/ipfire/suricata/suricata-dns-servers.yaml
19 HTTP_SERVERS: "$HOME_NET"
20 SMTP_SERVERS: "$HOME_NET"
21 SQL_SERVERS: "$HOME_NET"
22 TELNET_SERVERS: "$HOME_NET"
23 AIM_SERVERS: "$EXTERNAL_NET"
24 DC_SERVERS: "$HOME_NET"
25 DNP3_SERVER: "$HOME_NET"
26 DNP3_CLIENT: "$HOME_NET"
27 MODBUS_CLIENT: "$HOME_NET"
28 MODBUS_SERVER: "$HOME_NET"
29 ENIP_CLIENT: "$HOME_NET"
30 ENIP_SERVER: "$HOME_NET"
33 # Incluse HTTP_PORTS declaration from external file.
34 include: /var/ipfire/suricata/suricata-http-ports.yaml
36 SHELLCODE_PORTS: "!80"
41 FILE_DATA_PORTS: "[$HTTP_PORTS,110,143]"
45 ## Ruleset specific options.
47 default-rule-path: /var/lib/suricata
49 # Include enabled ruleset files from external file.
50 include: /var/ipfire/suricata/suricata-used-rulefiles.yaml
52 classification-file: /var/lib/suricata/classification.config
53 reference-config-file: /var/lib/suricata/reference.config
54 threshold-file: /var/lib/suricata/threshold.config
60 default-log-dir: /var/log/suricata/
62 # global stats configuration
65 # The interval field (in seconds) controls at what interval
66 # the loggers are invoked.
69 # Add decode events as stats.
71 # Decoder event prefix in stats. Has been 'decoder' before, but that leads
72 # to missing events in the eve.stats records. See issue #2225.
73 decoder-events-prefix: "decoder.event"
74 # Add stream events as stats.
77 # Configure the type of alert (and other) logging you would like.
79 # a line based alerts log similar to Snort's fast.log
84 #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
86 # Stats.log contains data from various counters of the suricata engine.
90 append: no # append to file (yes) or overwrite it (no)
91 totals: yes # stats for all threads merged together
92 threads: no # per thread stats
93 #null-values: yes # print counters that have value 0
95 # Extensible Event Format (nicknamed EVE) event log in JSON format
98 filetype: regular #regular|syslog|unix_dgram|unix_stream|redis
100 #prefix: "@cee: " # prefix to prepend to each log entry
101 # the following are valid when type: syslog above
102 #identity: "suricata"
104 #level: Info ## possible levels: Emergency, Alert, Critical,
105 ## Error, Warning, Notice, Info, Debug
109 # async: true ## if redis replies are read asynchronously
110 # mode: list ## possible values: list|lpush (default), rpush, channel|publish
111 # ## lpush and rpush are using a Redis list. "list" is an alias for lpush
112 # ## publish is using a Redis channel. "channel" is an alias for publish
113 # key: suricata ## key or channel to use (default to suricata)
114 # Redis pipelining set up. This will enable to only do a query every
115 # 'batch-size' events. This should lower the latency induced by network
116 # connection at the cost of some memory. There is no flushing implemented
117 # so this setting as to be reserved to high traffic suricata.
119 # enabled: yes ## set enable to yes to enable query pipelining
120 # batch-size: 10 ## number of entry to keep in buffer
122 # Include top level metadata. Default yes.
125 # include the name of the input pcap file in pcap file processing mode
129 # Adds a 'community_id' field to EVE records. These are meant to give
130 # a records a predictable flow id that can be used to match records to
131 # output of other tools such as Bro.
133 # Takes a 'seed' that needs to be same across sensors and tools
134 # to make the id less predictable.
136 # enable/disable the community id feature.
138 # Seed value for the ID output. Valid values are 0-65535.
141 # HTTP X-Forwarded-For support by adding an extra field or overwriting
142 # the source or destination IP address (depending on flow direction)
143 # with the one reported in the X-Forwarded-For HTTP header. This is
144 # helpful when reviewing alerts for traffic that is being reverse
145 # or forward proxied.
148 # Two operation modes are available, "extra-data" and "overwrite".
150 # Two proxy deployments are supported, "reverse" and "forward". In
151 # a "reverse" deployment the IP address used is the last one, in a
152 # "forward" deployment the first IP address is used.
154 # Header name where the actual IP address will be reported, if more
155 # than one IP address is present, the last IP address will be the
156 # one taken into consideration.
157 header: X-Forwarded-For
161 # payload: yes # enable dumping payload in Base64
162 # payload-buffer-size: 4kb # max size of payload buffer to output in eve-log
163 # payload-printable: yes # enable dumping payload in printable (lossy) format
164 # packet: yes # enable dumping of packet (without stream segments)
165 # metadata: no # enable inclusion of app layer metadata with alert. Default yes
166 # http-body: yes # Requires metadata; enable dumping of http body in Base64
167 # http-body-printable: yes # Requires metadata; enable dumping of http body in printable format
169 # Enable the logging of tagged packets for rules using the
173 # Anomaly log records describe unexpected conditions such
174 # as truncated packets, packets with invalid IP/UDP/TCP
175 # length values, and other events that render the packet
176 # invalid for further processing or describe unexpected
177 # behavior on an established stream. Networks which
178 # experience high occurrences of anomalies may experience
179 # packet processing degradation.
181 # Anomalies are reported for the following:
182 # 1. Decode: Values and conditions that are detected while
183 # decoding individual packets. This includes invalid or
184 # unexpected values for low-level protocol lengths as well
185 # as stream related events (TCP 3-way handshake issues,
186 # unexpected sequence number, etc).
187 # 2. Stream: This includes stream related events (TCP
188 # 3-way handshake issues, unexpected sequence number,
190 # 3. Application layer: These denote application layer
191 # specific conditions that are unexpected, invalid or are
192 # unexpected given the application monitoring state.
194 # By default, anomaly logging is disabled. When anomaly
195 # logging is enabled, applayer anomaly reporting is
199 # Choose one or more types of anomaly logging and whether to enable
200 # logging of the packet header for packet anomalies.
207 extended: yes # enable this for extended logging information
208 # custom allows additional http fields to be included in eve-log
209 # the example below adds three additional fields when uncommented
210 #custom: [Accept-Encoding, Accept-Language, Authorization]
211 # set this value to one and only one among {both, request, response}
212 # to dump all http headers for every http request and/or response
213 # dump-all-headers: none
215 # This configuration uses the new DNS logging format,
216 # the old configuration is still available:
217 # https://suricata.readthedocs.io/en/latest/output/eve/eve-json-output.html#dns-v1-format
219 # As of Suricata 5.0, version 2 of the eve dns output
220 # format is the default.
223 # Enable/disable this logger. Default: enabled.
226 # Control logging of requests and responses:
227 # - requests: enable logging of DNS queries
228 # - responses: enable logging of DNS answers
229 # By default both requests and responses are logged.
233 # Format of answer logging:
234 # - detailed: array item per answer
235 # - grouped: answers aggregated by type
237 #formats: [detailed, grouped]
239 # Types to log, based on the query type.
241 #types: [a, aaaa, cname, mx, ns, ptr, txt]
243 extended: yes # enable this for extended logging information
244 # output TLS transaction where the session is resumed using a
246 #session-resumption: no
247 # custom allows to control which tls fields that are included
249 #custom: [subject, issuer, session_resumed, serial, fingerprint, sni, version, not_before, not_after, certificate, chain, ja3, ja3s]
251 force-magic: no # force logging magic on all logged files
252 # force logging of checksums, available hash functions are md5,
256 # alerts: yes # log alerts that caused drops
257 # flows: all # start or all: 'start' logs only a single drop
258 # # per flow direction. All logs each dropped pkt.
260 #extended: yes # enable this for extended logging information
261 # this includes: bcc, message-id, subject, x_mailer, user-agent
262 # custom fields logging from the list:
263 # reply-to, bcc, message-id, subject, x-mailer, user-agent, received,
264 # x-originating-ip, in-reply-to, references, importance, priority,
265 # sensitivity, organization, content-md5, date
266 #custom: [received, x-mailer, x-originating-ip, relays, reply-to, bcc]
267 # output md5 of fields: body, subject
268 # for the body you need to set app-layer.protocols.smtp.mime.body-md5
270 #md5: [body, subject]
286 # When extended mode is on, all DHCP messages are logged
287 # with full detail. When extended mode is off (the
288 # default), just enough information to map a MAC address
289 # to an IP address is logged.
293 # passwords: yes # enable output of passwords
294 # HTTP2 logging. HTTP2 support is currently experimental and
295 # disabled by default. To enable, uncomment the following line
296 # and be sure to enable http2 in the app-layer section.
299 totals: yes # stats for all threads merged together
300 threads: no # per thread stats
301 deltas: no # include delta values
302 # bi-directional flows
304 # uni-directional flows
307 # Metadata event type. Triggered whenever a pktvar is saved
308 # and will include the pktvars, flowvars, flowbits and
313 # The default log level, can be overridden in an output section.
314 # Note that debug level logging will only be emitted if Suricata was
315 # compiled with the --enable-debug configure option.
317 # This value is overriden by the SC_LOG_LEVEL env var.
318 default-log-level: notice
320 # A regex to filter output. Can be overridden in an output section.
321 # Defaults to empty (no filter).
323 # This value is overriden by the SC_LOG_OP_FILTER env var.
324 default-output-filter:
326 # Define your logging outputs. If none are defined, or they are all
327 # disabled you will get the default - console output.
335 filename: /var/log/suricata/suricata.log
344 ## Netfilter configuration
349 repeat-mark: 2147483648
350 repeat-mask: 2147483648
351 bypass-mark: 1073741824
352 bypass-mask: 1073741824
358 ## Step 5: App Layer Protocol Configuration
361 # Configure the app-layer parsers. The protocols section details each
364 # The option "enabled" takes 3 values - "yes", "no", "detection-only".
365 # "yes" enables both detection and the parser, "no" disables both, and
366 # "detection-only" enables protocol detection only (parser disabled).
372 dp: 5900, 5901, 5902, 5903, 5904, 5905, 5906, 5907, 5908, 5909
373 # MQTT, disabled by default.
376 # max-msg-length: 1mb
386 dp: "[443,444,465,853,993,995]"
388 # Generate JA3 fingerprint from client hello. If not specified it
389 # will be disabled by default, but enabled if rules require it.
390 ja3-fingerprints: auto
392 # What to do when the encrypted communications start:
393 # - default: keep tracking TLS session, check for protocol anomalies,
394 # inspect tls_* keywords. Disables inspection of unmodified
395 # 'content' signatures.
396 # - bypass: stop processing this flow as much as possible. No further
397 # TLS parsing and inspection. Offload flow bypass to kernel
398 # or hardware if possible.
399 # - full: keep tracking and inspection as normal. Unmodified content
400 # keyword signatures are inspected as well.
402 # For best performance, select 'bypass'.
404 encryption-handling: bypass
414 # HTTP2: Experimental HTTP 2 support. Disabled by default.
419 # Configure SMTP-MIME Decoder
421 # Decode MIME messages from SMTP transactions
422 # (may be resource intensive)
423 # This field supercedes all others because it turns the entire
427 # Decode MIME entity bodies (ie. base64, quoted-printable, etc.)
429 decode-quoted-printable: yes
431 # Maximum bytes per header data value stored in the data structure
433 header-value-depth: 2000
435 # Extract URLs and save in state data structure
437 # Set to yes to compute the md5 of the mail body. You will then
438 # be able to journalize it.
440 # Configure inspected-tracker for file_data keyword
442 content-limit: 100000
443 content-inspect-min-size: 32768
444 content-inspect-window: 4096
458 # memcaps. Globally and per flow/state.
462 # How many unreplied DNS requests are considered a flood.
463 # If the limit is reached, app-layer-event:dns.flooded; will match.
478 # default-config: Used when no server-config matches
479 # personality: List of personalities used by default
480 # request-body-limit: Limit reassembly of request body for inspection
481 # by http_client_body & pcre /P option.
482 # response-body-limit: Limit reassembly of response body for inspection
483 # by file_data, http_server_body & pcre /Q option.
484 # double-decode-path: Double decode path section of the URI
485 # double-decode-query: Double decode query section of the URI
486 # response-body-decompress-layer-limit:
487 # Limit to how many layers of compression will be
488 # decompressed. Defaults to 2.
490 # Currently Available Personalities:
491 # Minimal, Generic, IDS (default), IIS_4_0, IIS_5_0, IIS_5_1, IIS_6_0,
492 # IIS_7_0, IIS_7_5, Apache_2
497 # Can be specified in kb, mb, gb. Just a number indicates
499 request-body-limit: 0
500 response-body-limit: 0
502 # response body decompression (0 disables)
503 response-body-decompress-layer-limit: 2
505 # auto will use http-body-inline mode in IPS mode, yes or no set it statically
506 http-body-inline: auto
508 # Take a random value for inspection sizes around the specified value.
509 # This lower the risk of some evasion technics but could lead
510 # detection change between runs. It is set to 'yes' by default.
511 randomize-inspection-sizes: yes
512 # If randomize-inspection-sizes is active, the value of various
513 # inspection size will be choosen in the [1 - range%, 1 + range%]
515 # Default value of randomize-inspection-range is 10.
516 randomize-inspection-range: 10
519 double-decode-path: no
520 double-decode-query: no
529 # Limit for the maximum number of asn1 frames to decode (default 256)
533 ##############################################################################
535 ## Advanced settings below
537 ##############################################################################
543 # Run suricata as user and group.
548 # Suricata core dump configuration. Limits the size of the core dump file to
549 # approximately max-dump. The actual core dump size will be a multiple of the
550 # page size. Core dumps that would be larger than max-dump are truncated. On
551 # Linux, the actual core dump size may be a few pages larger than max-dump.
552 # Setting max-dump to 0 disables core dumping.
553 # Setting max-dump to 'unlimited' will give the full core dump file.
554 # On 32-bit Linux, a max-dump value >= ULONG_MAX may cause the core dump size
560 # If suricata box is a router for the sniffed networks, set it to 'router'. If
561 # it is a pure sniffing setup, set it to 'sniffer-only'.
562 # If set to auto, the variable is internally switch to 'router' in IPS mode
563 # and 'sniffer-only' in IDS mode.
564 # This feature is currently only used by the reject* keywords.
567 # Number of packets preallocated per thread. The default is 1024. A higher number
568 # will make sure each CPU will be more easily kept busy, but may negatively
570 max-pending-packets: 1024
572 # Runmode the engine should use. Please check --list-runmodes to get the available
573 # runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned
577 # Specifies the kind of flow load balancer used by the flow pinned autofp mode.
579 # Supported schedulers are:
581 # round-robin - Flows assigned to threads in a round robin fashion.
582 # active-packets - Flows assigned to threads that have the lowest number of
583 # unprocessed packets (default).
584 # hash - Flow alloted usihng the address hash. More of a random
585 # technique. Was the default in Suricata 1.2.1 and older.
587 #autofp-scheduler: active-packets
589 # Preallocated size for packet. Default is 1514 which is the classical
590 # size for pcap on ethernet. You should adjust this value to the highest
591 # packet size (MTU + hardware header) on your system.
592 default-packet-size: 1514
594 # Unix command socket can be used to pass commands to suricata.
595 # An external tool can then connect to get information from suricata
596 # or trigger some modifications of the engine. Set enabled to yes
597 # to activate the feature. In auto mode, the feature will only be
598 # activated in live capture mode. You can use the filename variable to set
599 # the file name of the socket.
602 #filename: custom.socket
605 magic-file: /usr/share/misc/magic.mgc
611 ## Detection settings
614 # Set the order of alerts bassed on actions
615 # The default order is pass, drop, reject, alert
622 # When run with the option --engine-analysis, the engine will read each of
623 # the parameters below, and print reports for each of the enabled sections
624 # and exit. The reports are printed to a file in the default log dir
625 # given by the parameter "default-log-dir", with engine reporting
626 # subsection below printing reports in its own report file.
628 # enables printing reports for fast-pattern for every rule.
629 rules-fast-pattern: yes
630 # enables printing reports for each rule
633 #recursion and match limits for PCRE where supported
636 match-limit-recursion: 1500
639 ## Advanced Traffic Tracking and Reconstruction Settings
642 # Host specific policies for defragmentation and TCP stream
643 # reassembly. The host OS lookup is done using a radix tree, just
644 # like a routing table so the most specific entry matches.
646 # Make the default policy windows.
666 trackers: 65535 # number of defragmented flows to follow
667 max-frags: 65535 # number of fragments to keep (higher than trackers)
672 # By default, the reserved memory (memcap) for flows is 32MB. This is the limit
673 # for flow allocation inside the engine. You can change this value to allow
674 # more memory usage for flows.
675 # The hash-size determine the size of the hash used to identify flows inside
676 # the engine, and by default the value is 65536.
677 # At the startup, the engine can preallocate a number of flows, to get a better
678 # performance. The number of flows preallocated is 10000 by default.
679 # emergency-recovery is the percentage of flows that the engine need to
680 # prune before unsetting the emergency state. The emergency state is activated
681 # when the memcap limit is reached, allowing to create new flows, but
682 # prunning them with the emergency timeouts (they are defined below).
683 # If the memcap is reached, the engine will try to prune flows
684 # with the default timeouts. If it doens't find a flow to prune, it will set
685 # the emergency bit and it will try again with more agressive timeouts.
686 # If that doesn't work, then it will try to kill the last time seen flows
688 # The memcap can be specified in kb, mb, gb. Just a number indicates it's
695 emergency-recovery: 30
699 # This option controls the use of vlan ids in the flow (and defrag)
700 # hashing. Normally this should be enabled, but in some (broken)
701 # setups where both sides of a flow are not tagged with the same vlan
702 # tag, we can ignore the vlan id's in the flow hashing.
704 use-for-tracking: true
706 # Specific timeouts for flows. Here you can specify the timeouts that the
707 # active flows will wait to transit from the current state to another, on each
708 # protocol. The value of "new" determine the seconds to wait after a hanshake or
709 # stream startup before the engine free the data of that flow it doesn't
710 # change the state to established (usually if we don't receive more packets
711 # of that flow). The value of "established" is the amount of
712 # seconds that the engine will wait to free the flow if it spend that amount
713 # without receiving new packets or closing the connection. "closed" is the
714 # amount of time to wait after a flow is closed (usually zero). "bypassed"
715 # timeout controls locally bypassed flows. For these flows we don't do any other
716 # tracking. If no packets have been seen after this timeout, the flow is discarded.
718 # There's an emergency mode that will become active under attack circumstances,
719 # making the engine to check flow status faster. This configuration variables
720 # use the prefix "emergency-" and work similar as the normal ones.
721 # Some timeouts doesn't apply to all the protocols, like "closed", for udp and
732 emergency-established: 100
734 emergency-bypassed: 50
741 emergency-established: 100
743 emergency-bypassed: 50
749 emergency-established: 100
750 emergency-bypassed: 50
756 emergency-established: 100
757 emergency-bypassed: 50
759 # Stream engine settings. Here the TCP stream tracking and reassembly
760 # engine is configured.
763 # memcap: 32mb # Can be specified in kb, mb, gb. Just a
764 # # number indicates it's in bytes.
765 # checksum-validation: yes # To validate the checksum of received
766 # # packet. If csum validation is specified as
767 # # "yes", then packet with invalid csum will not
768 # # be processed by the engine stream/app layer.
769 # # Warning: locally generated trafic can be
770 # # generated without checksum due to hardware offload
771 # # of checksum. You can control the handling of checksum
772 # # on a per-interface basis via the 'checksum-checks'
774 # prealloc-sessions: 2k # 2k sessions prealloc'd per stream thread
775 # midstream: false # don't allow midstream session pickups
776 # async-oneside: false # don't enable async stream handling
777 # inline: no # stream inline mode
778 # drop-invalid: yes # in inline mode, drop packets that are invalid with regards to streaming engine
779 # max-synack-queued: 5 # Max different SYN/ACKs to queue
780 # bypass: no # Bypass packets when stream.depth is reached
783 # memcap: 64mb # Can be specified in kb, mb, gb. Just a number
784 # # indicates it's in bytes.
785 # depth: 1mb # Can be specified in kb, mb, gb. Just a number
786 # # indicates it's in bytes.
787 # toserver-chunk-size: 2560 # inspect raw stream in chunks of at least
788 # # this size. Can be specified in kb, mb,
789 # # gb. Just a number indicates it's in bytes.
790 # toclient-chunk-size: 2560 # inspect raw stream in chunks of at least
791 # # this size. Can be specified in kb, mb,
792 # # gb. Just a number indicates it's in bytes.
793 # randomize-chunk-size: yes # Take a random value for chunk size around the specified value.
794 # # This lower the risk of some evasion technics but could lead
795 # # detection change between runs. It is set to 'yes' by default.
796 # randomize-chunk-range: 10 # If randomize-chunk-size is active, the value of chunk-size is
797 # # a random value between (1 - randomize-chunk-range/100)*toserver-chunk-size
798 # # and (1 + randomize-chunk-range/100)*toserver-chunk-size and the same
799 # # calculation for toclient-chunk-size.
800 # # Default value of randomize-chunk-range is 10.
802 # raw: yes # 'Raw' reassembly enabled or disabled.
803 # # raw is for content inspection by detection
806 # segment-prealloc: 2048 # number of segments preallocated per thread
808 # check-overlap-different-data: true|false
809 # # check if a segment contains different data
810 # # than what we've already seen for that
811 # # position in the stream.
812 # # This is enabled automatically if inline mode
813 # # is used or when stream-event:reassembly_overlap_different_data;
814 # # is used in a rule.
818 prealloc-sessions: 4096
819 checksum-validation: yes # reject wrong csums
820 inline: auto # auto will use inline mode in IPS mode, yes or no set it statically
821 bypass: yes # Bypass packets when stream.reassembly.depth is reached.
824 depth: 1mb # reassemble 1mb into a stream
825 toserver-chunk-size: 2560
826 toclient-chunk-size: 2560
827 randomize-chunk-size: yes
829 segment-prealloc: 2048
830 check-overlap-different-data: true
834 # Host table is used by tagging and per host thresholding subsystems.
843 # Used by xbits 'ippair' tracking.
853 # Teredo decoder is known to not be completely accurate
854 # it will sometimes detect non-teredo as teredo.
860 ## Performance tuning and profiling
863 # The detection engine builds internal groups of signatures. The engine
864 # allow us to specify the profile to use for them, to manage memory on an
865 # efficient way keeping a good performance. For the profile keyword you
866 # can use the words "low", "medium", "high" or "custom". If you use custom
867 # make sure to define the values at "- custom-values" as your convenience.
868 # Usually you would prefer medium/high/low.
870 # "sgh mpm-context", indicates how the staging should allot mpm contexts for
871 # the signature groups. "single" indicates the use of a single context for
872 # all the signature group heads. "full" indicates a mpm-context for each
873 # group head. "auto" lets the engine decide the distribution of contexts
874 # based on the information the engine gathers on the patterns from each
877 # The option inspection-recursion-limit is used to limit the recursive calls
878 # in the content inspection code. For certain payload-sig combinations, we
879 # might end up taking too much time in the content inspection code.
880 # If the argument specified is 0, the engine uses an internally defined
881 # default limit. On not specifying a value, we use no limits on the recursion.
887 sgh-mpm-context: auto
888 inspection-recursion-limit: 3000
890 # If set to yes, the loading of signatures will be made after the capture
891 # is started. This will limit the downtime in IPS mode.
895 # default prefiltering setting. "mpm" only creates MPM/fast_pattern
896 # engines. "auto" also sets up prefilter engines for other keywords.
897 # Use --list-keywords=all to see which keywords support prefiltering.
900 # the grouping values above control how many groups are created per
901 # direction. Port whitelisting forces that port to get it's own group.
902 # Very common ports will benefit, as well as ports with many expensive
905 #tcp-whitelist: 53, 80, 139, 443, 445, 1433, 3306, 3389, 6666, 6667, 8080
906 #udp-whitelist: 53, 135, 5060
909 # Log the rules that made it past the prefilter stage, per packet
910 # default is off. The threshold setting determines how many rules
911 # must have made it past pre-filter for that rule to trigger the
913 #inspect-logging-threshold: 200
916 include-rules: false # very verbose
917 include-mpm-stats: false
919 # Select the multi pattern algorithm you want to run for scan/search the
922 # The supported algorithms are:
923 # "ac" - Aho-Corasick, default implementation
924 # "ac-bs" - Aho-Corasick, reduced memory implementation
925 # "ac-cuda" - Aho-Corasick, CUDA implementation
926 # "ac-ks" - Aho-Corasick, "Ken Steele" variant
927 # "hs" - Hyperscan, available when built with Hyperscan support
929 # The default mpm-algo value of "auto" will use "hs" if Hyperscan is
930 # available, "ac" otherwise.
932 # The mpm you choose also decides the distribution of mpm contexts for
933 # signature groups, specified by the conf - "detect.sgh-mpm-context".
934 # Selecting "ac" as the mpm would require "detect.sgh-mpm-context"
935 # to be set to "single", because of ac's memory requirements, unless the
936 # ruleset is small enough to fit in one's memory, in which case one can
937 # use "full" with "ac". Rest of the mpms can be run in "full" mode.
939 # There is also a CUDA pattern matcher (only available if Suricata was
940 # compiled with --enable-cuda: b2g_cuda. Make sure to update your
941 # max-pending-packets setting above as well if you use b2g_cuda.
945 # Select the matching algorithm you want to use for single-pattern searches.
947 # Supported algorithms are "bm" (Boyer-Moore) and "hs" (Hyperscan, only
948 # available if Suricata has been built with Hyperscan support).
950 # The default of "auto" will use "hs" if available, otherwise "bm".
954 # Suricata is multi-threaded. Here the threading can be influenced.
957 # Tune cpu affinity of threads. Each family of threads can be bound
960 # These 2 apply to the all runmodes:
961 # management-cpu-set is used for flow timeout handling, counters
962 # worker-cpu-set is used for 'worker' threads
964 # Additionally, for autofp these apply:
965 # receive-cpu-set is used for capture threads
966 # verdict-cpu-set is used for IPS verdict threads
969 - management-cpu-set:
970 cpu: [ 0 ] # include only these cpus in affinity settings
972 cpu: [ 0 ] # include only these cpus in affinity settings
986 # By default Suricata creates one "detect" thread per available CPU/CPU core.
987 # This setting allows controlling this behaviour. A ratio setting of 2 will
988 # create 2 detect threads for each CPU/CPU core. So for a dual core CPU this
989 # will result in 4 detect threads. If values below 1 are used, less threads
990 # are created. So on a dual core CPU a setting of 0.5 results in 1 detect
991 # thread being created. Regardless of the setting at a minimum 1 detect
992 # thread will always be created.
994 detect-thread-ratio: 1.0