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"
34 SHELLCODE_PORTS: "!80"
39 FILE_DATA_PORTS: "[$HTTP_PORTS,110,143]"
43 ## Ruleset specific options.
45 default-rule-path: /var/lib/suricata
47 # Include enabled ruleset files from external file.
48 include: /var/ipfire/suricata/suricata-used-rulefiles.yaml
50 classification-file: /var/lib/suricata/classification.config
51 reference-config-file: /var/lib/suricata/reference.config
52 threshold-file: /var/lib/suricata/threshold.config
58 default-log-dir: /var/log/suricata/
60 # global stats configuration
63 # The interval field (in seconds) controls at what interval
64 # the loggers are invoked.
67 # Add decode events as stats.
69 # Decoder event prefix in stats. Has been 'decoder' before, but that leads
70 # to missing events in the eve.stats records. See issue #2225.
71 decoder-events-prefix: "decoder.event"
72 # Add stream events as stats.
75 # Configure the type of alert (and other) logging you would like.
77 # a line based alerts log similar to Snort's fast.log
82 #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
84 # Stats.log contains data from various counters of the suricata engine.
88 append: no # append to file (yes) or overwrite it (no)
89 totals: yes # stats for all threads merged together
90 threads: no # per thread stats
91 #null-values: yes # print counters that have value 0
93 # Extensible Event Format (nicknamed EVE) event log in JSON format
96 filetype: regular #regular|syslog|unix_dgram|unix_stream|redis
98 #prefix: "@cee: " # prefix to prepend to each log entry
99 # the following are valid when type: syslog above
100 #identity: "suricata"
102 #level: Info ## possible levels: Emergency, Alert, Critical,
103 ## Error, Warning, Notice, Info, Debug
107 # async: true ## if redis replies are read asynchronously
108 # mode: list ## possible values: list|lpush (default), rpush, channel|publish
109 # ## lpush and rpush are using a Redis list. "list" is an alias for lpush
110 # ## publish is using a Redis channel. "channel" is an alias for publish
111 # key: suricata ## key or channel to use (default to suricata)
112 # Redis pipelining set up. This will enable to only do a query every
113 # 'batch-size' events. This should lower the latency induced by network
114 # connection at the cost of some memory. There is no flushing implemented
115 # so this setting as to be reserved to high traffic suricata.
117 # enabled: yes ## set enable to yes to enable query pipelining
118 # batch-size: 10 ## number of entry to keep in buffer
120 # Include top level metadata. Default yes.
123 # include the name of the input pcap file in pcap file processing mode
127 # Adds a 'community_id' field to EVE records. These are meant to give
128 # a records a predictable flow id that can be used to match records to
129 # output of other tools such as Bro.
131 # Takes a 'seed' that needs to be same across sensors and tools
132 # to make the id less predictable.
134 # enable/disable the community id feature.
136 # Seed value for the ID output. Valid values are 0-65535.
139 # HTTP X-Forwarded-For support by adding an extra field or overwriting
140 # the source or destination IP address (depending on flow direction)
141 # with the one reported in the X-Forwarded-For HTTP header. This is
142 # helpful when reviewing alerts for traffic that is being reverse
143 # or forward proxied.
146 # Two operation modes are available, "extra-data" and "overwrite".
148 # Two proxy deployments are supported, "reverse" and "forward". In
149 # a "reverse" deployment the IP address used is the last one, in a
150 # "forward" deployment the first IP address is used.
152 # Header name where the actual IP address will be reported, if more
153 # than one IP address is present, the last IP address will be the
154 # one taken into consideration.
155 header: X-Forwarded-For
159 # payload: yes # enable dumping payload in Base64
160 # payload-buffer-size: 4kb # max size of payload buffer to output in eve-log
161 # payload-printable: yes # enable dumping payload in printable (lossy) format
162 # packet: yes # enable dumping of packet (without stream segments)
163 # metadata: no # enable inclusion of app layer metadata with alert. Default yes
164 # http-body: yes # Requires metadata; enable dumping of http body in Base64
165 # http-body-printable: yes # Requires metadata; enable dumping of http body in printable format
167 # Enable the logging of tagged packets for rules using the
171 # Anomaly log records describe unexpected conditions such
172 # as truncated packets, packets with invalid IP/UDP/TCP
173 # length values, and other events that render the packet
174 # invalid for further processing or describe unexpected
175 # behavior on an established stream. Networks which
176 # experience high occurrences of anomalies may experience
177 # packet processing degradation.
179 # Anomalies are reported for the following:
180 # 1. Decode: Values and conditions that are detected while
181 # decoding individual packets. This includes invalid or
182 # unexpected values for low-level protocol lengths as well
183 # as stream related events (TCP 3-way handshake issues,
184 # unexpected sequence number, etc).
185 # 2. Stream: This includes stream related events (TCP
186 # 3-way handshake issues, unexpected sequence number,
188 # 3. Application layer: These denote application layer
189 # specific conditions that are unexpected, invalid or are
190 # unexpected given the application monitoring state.
192 # By default, anomaly logging is disabled. When anomaly
193 # logging is enabled, applayer anomaly reporting is
197 # Choose one or more types of anomaly logging and whether to enable
198 # logging of the packet header for packet anomalies.
205 extended: yes # enable this for extended logging information
206 # custom allows additional http fields to be included in eve-log
207 # the example below adds three additional fields when uncommented
208 #custom: [Accept-Encoding, Accept-Language, Authorization]
209 # set this value to one and only one among {both, request, response}
210 # to dump all http headers for every http request and/or response
211 # dump-all-headers: none
213 # This configuration uses the new DNS logging format,
214 # the old configuration is still available:
215 # https://suricata.readthedocs.io/en/latest/output/eve/eve-json-output.html#dns-v1-format
217 # As of Suricata 5.0, version 2 of the eve dns output
218 # format is the default.
221 # Enable/disable this logger. Default: enabled.
224 # Control logging of requests and responses:
225 # - requests: enable logging of DNS queries
226 # - responses: enable logging of DNS answers
227 # By default both requests and responses are logged.
231 # Format of answer logging:
232 # - detailed: array item per answer
233 # - grouped: answers aggregated by type
235 #formats: [detailed, grouped]
237 # Types to log, based on the query type.
239 #types: [a, aaaa, cname, mx, ns, ptr, txt]
241 extended: yes # enable this for extended logging information
242 # output TLS transaction where the session is resumed using a
244 #session-resumption: no
245 # custom allows to control which tls fields that are included
247 #custom: [subject, issuer, session_resumed, serial, fingerprint, sni, version, not_before, not_after, certificate, chain, ja3, ja3s]
249 force-magic: no # force logging magic on all logged files
250 # force logging of checksums, available hash functions are md5,
254 # alerts: yes # log alerts that caused drops
255 # flows: all # start or all: 'start' logs only a single drop
256 # # per flow direction. All logs each dropped pkt.
258 #extended: yes # enable this for extended logging information
259 # this includes: bcc, message-id, subject, x_mailer, user-agent
260 # custom fields logging from the list:
261 # reply-to, bcc, message-id, subject, x-mailer, user-agent, received,
262 # x-originating-ip, in-reply-to, references, importance, priority,
263 # sensitivity, organization, content-md5, date
264 #custom: [received, x-mailer, x-originating-ip, relays, reply-to, bcc]
265 # output md5 of fields: body, subject
266 # for the body you need to set app-layer.protocols.smtp.mime.body-md5
268 #md5: [body, subject]
282 # When extended mode is on, all DHCP messages are logged
283 # with full detail. When extended mode is off (the
284 # default), just enough information to map a MAC address
285 # to an IP address is logged.
289 totals: yes # stats for all threads merged together
290 threads: no # per thread stats
291 deltas: no # include delta values
292 # bi-directional flows
294 # uni-directional flows
297 # Metadata event type. Triggered whenever a pktvar is saved
298 # and will include the pktvars, flowvars, flowbits and
303 # The default log level, can be overridden in an output section.
304 # Note that debug level logging will only be emitted if Suricata was
305 # compiled with the --enable-debug configure option.
307 # This value is overriden by the SC_LOG_LEVEL env var.
308 default-log-level: notice
310 # A regex to filter output. Can be overridden in an output section.
311 # Defaults to empty (no filter).
313 # This value is overriden by the SC_LOG_OP_FILTER env var.
314 default-output-filter:
316 # Define your logging outputs. If none are defined, or they are all
317 # disabled you will get the default - console output.
325 filename: /var/log/suricata/suricata.log
334 ## Netfilter configuration
339 repeat-mark: 1879048192
340 repeat-mask: 1879048192
348 ## Step 5: App Layer Protocol Configuration
351 # Configure the app-layer parsers. The protocols section details each
354 # The option "enabled" takes 3 values - "yes", "no", "detection-only".
355 # "yes" enables both detection and the parser, "no" disables both, and
356 # "detection-only" enables protocol detection only (parser disabled).
368 dp: "[443,444,465,853,993,995]"
370 # Generate JA3 fingerprint from client hello. If not specified it
371 # will be disabled by default, but enabled if rules require it.
372 #ja3-fingerprints: auto
373 # Generate JA3 fingerprint from client hello
376 # Completely stop processing TLS/SSL session after the handshake
377 # completed. If bypass is enabled this will also trigger flow
378 # bypass. If disabled (the default), TLS/SSL session is still
379 # tracked for Heartbleed and other anomalies.
391 # Configure SMTP-MIME Decoder
393 # Decode MIME messages from SMTP transactions
394 # (may be resource intensive)
395 # This field supercedes all others because it turns the entire
399 # Decode MIME entity bodies (ie. base64, quoted-printable, etc.)
401 decode-quoted-printable: yes
403 # Maximum bytes per header data value stored in the data structure
405 header-value-depth: 2000
407 # Extract URLs and save in state data structure
409 # Set to yes to compute the md5 of the mail body. You will then
410 # be able to journalize it.
412 # Configure inspected-tracker for file_data keyword
414 content-limit: 100000
415 content-inspect-min-size: 32768
416 content-inspect-window: 4096
430 # memcaps. Globally and per flow/state.
434 # How many unreplied DNS requests are considered a flood.
435 # If the limit is reached, app-layer-event:dns.flooded; will match.
450 # default-config: Used when no server-config matches
451 # personality: List of personalities used by default
452 # request-body-limit: Limit reassembly of request body for inspection
453 # by http_client_body & pcre /P option.
454 # response-body-limit: Limit reassembly of response body for inspection
455 # by file_data, http_server_body & pcre /Q option.
456 # double-decode-path: Double decode path section of the URI
457 # double-decode-query: Double decode query section of the URI
458 # response-body-decompress-layer-limit:
459 # Limit to how many layers of compression will be
460 # decompressed. Defaults to 2.
462 # Currently Available Personalities:
463 # Minimal, Generic, IDS (default), IIS_4_0, IIS_5_0, IIS_5_1, IIS_6_0,
464 # IIS_7_0, IIS_7_5, Apache_2
469 # Can be specified in kb, mb, gb. Just a number indicates
471 request-body-limit: 0
472 response-body-limit: 0
474 # response body decompression (0 disables)
475 response-body-decompress-layer-limit: 2
477 # auto will use http-body-inline mode in IPS mode, yes or no set it statically
478 http-body-inline: auto
480 # Take a random value for inspection sizes around the specified value.
481 # This lower the risk of some evasion technics but could lead
482 # detection change between runs. It is set to 'yes' by default.
483 randomize-inspection-sizes: yes
484 # If randomize-inspection-sizes is active, the value of various
485 # inspection size will be choosen in the [1 - range%, 1 + range%]
487 # Default value of randomize-inspection-range is 10.
488 randomize-inspection-range: 10
491 double-decode-path: no
492 double-decode-query: no
501 # Limit for the maximum number of asn1 frames to decode (default 256)
505 ##############################################################################
507 ## Advanced settings below
509 ##############################################################################
515 # Run suricata as user and group.
520 # Suricata core dump configuration. Limits the size of the core dump file to
521 # approximately max-dump. The actual core dump size will be a multiple of the
522 # page size. Core dumps that would be larger than max-dump are truncated. On
523 # Linux, the actual core dump size may be a few pages larger than max-dump.
524 # Setting max-dump to 0 disables core dumping.
525 # Setting max-dump to 'unlimited' will give the full core dump file.
526 # On 32-bit Linux, a max-dump value >= ULONG_MAX may cause the core dump size
532 # If suricata box is a router for the sniffed networks, set it to 'router'. If
533 # it is a pure sniffing setup, set it to 'sniffer-only'.
534 # If set to auto, the variable is internally switch to 'router' in IPS mode
535 # and 'sniffer-only' in IDS mode.
536 # This feature is currently only used by the reject* keywords.
539 # Number of packets preallocated per thread. The default is 1024. A higher number
540 # will make sure each CPU will be more easily kept busy, but may negatively
542 max-pending-packets: 1024
544 # Runmode the engine should use. Please check --list-runmodes to get the available
545 # runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned
549 # Specifies the kind of flow load balancer used by the flow pinned autofp mode.
551 # Supported schedulers are:
553 # round-robin - Flows assigned to threads in a round robin fashion.
554 # active-packets - Flows assigned to threads that have the lowest number of
555 # unprocessed packets (default).
556 # hash - Flow alloted usihng the address hash. More of a random
557 # technique. Was the default in Suricata 1.2.1 and older.
559 #autofp-scheduler: active-packets
561 # Preallocated size for packet. Default is 1514 which is the classical
562 # size for pcap on ethernet. You should adjust this value to the highest
563 # packet size (MTU + hardware header) on your system.
564 default-packet-size: 1514
566 # Unix command socket can be used to pass commands to suricata.
567 # An external tool can then connect to get information from suricata
568 # or trigger some modifications of the engine. Set enabled to yes
569 # to activate the feature. In auto mode, the feature will only be
570 # activated in live capture mode. You can use the filename variable to set
571 # the file name of the socket.
574 #filename: custom.socket
577 magic-file: /usr/share/misc/magic.mgc
583 ## Detection settings
586 # Set the order of alerts bassed on actions
587 # The default order is pass, drop, reject, alert
594 # When run with the option --engine-analysis, the engine will read each of
595 # the parameters below, and print reports for each of the enabled sections
596 # and exit. The reports are printed to a file in the default log dir
597 # given by the parameter "default-log-dir", with engine reporting
598 # subsection below printing reports in its own report file.
600 # enables printing reports for fast-pattern for every rule.
601 rules-fast-pattern: yes
602 # enables printing reports for each rule
605 #recursion and match limits for PCRE where supported
608 match-limit-recursion: 1500
611 ## Advanced Traffic Tracking and Reconstruction Settings
614 # Host specific policies for defragmentation and TCP stream
615 # reassembly. The host OS lookup is done using a radix tree, just
616 # like a routing table so the most specific entry matches.
618 # Make the default policy windows.
638 trackers: 65535 # number of defragmented flows to follow
639 max-frags: 65535 # number of fragments to keep (higher than trackers)
644 # By default, the reserved memory (memcap) for flows is 32MB. This is the limit
645 # for flow allocation inside the engine. You can change this value to allow
646 # more memory usage for flows.
647 # The hash-size determine the size of the hash used to identify flows inside
648 # the engine, and by default the value is 65536.
649 # At the startup, the engine can preallocate a number of flows, to get a better
650 # performance. The number of flows preallocated is 10000 by default.
651 # emergency-recovery is the percentage of flows that the engine need to
652 # prune before unsetting the emergency state. The emergency state is activated
653 # when the memcap limit is reached, allowing to create new flows, but
654 # prunning them with the emergency timeouts (they are defined below).
655 # If the memcap is reached, the engine will try to prune flows
656 # with the default timeouts. If it doens't find a flow to prune, it will set
657 # the emergency bit and it will try again with more agressive timeouts.
658 # If that doesn't work, then it will try to kill the last time seen flows
660 # The memcap can be specified in kb, mb, gb. Just a number indicates it's
667 emergency-recovery: 30
671 # This option controls the use of vlan ids in the flow (and defrag)
672 # hashing. Normally this should be enabled, but in some (broken)
673 # setups where both sides of a flow are not tagged with the same vlan
674 # tag, we can ignore the vlan id's in the flow hashing.
676 use-for-tracking: true
678 # Specific timeouts for flows. Here you can specify the timeouts that the
679 # active flows will wait to transit from the current state to another, on each
680 # protocol. The value of "new" determine the seconds to wait after a hanshake or
681 # stream startup before the engine free the data of that flow it doesn't
682 # change the state to established (usually if we don't receive more packets
683 # of that flow). The value of "established" is the amount of
684 # seconds that the engine will wait to free the flow if it spend that amount
685 # without receiving new packets or closing the connection. "closed" is the
686 # amount of time to wait after a flow is closed (usually zero). "bypassed"
687 # timeout controls locally bypassed flows. For these flows we don't do any other
688 # tracking. If no packets have been seen after this timeout, the flow is discarded.
690 # There's an emergency mode that will become active under attack circumstances,
691 # making the engine to check flow status faster. This configuration variables
692 # use the prefix "emergency-" and work similar as the normal ones.
693 # Some timeouts doesn't apply to all the protocols, like "closed", for udp and
704 emergency-established: 100
706 emergency-bypassed: 50
713 emergency-established: 100
715 emergency-bypassed: 50
721 emergency-established: 100
722 emergency-bypassed: 50
728 emergency-established: 100
729 emergency-bypassed: 50
731 # Stream engine settings. Here the TCP stream tracking and reassembly
732 # engine is configured.
735 # memcap: 32mb # Can be specified in kb, mb, gb. Just a
736 # # number indicates it's in bytes.
737 # checksum-validation: yes # To validate the checksum of received
738 # # packet. If csum validation is specified as
739 # # "yes", then packet with invalid csum will not
740 # # be processed by the engine stream/app layer.
741 # # Warning: locally generated trafic can be
742 # # generated without checksum due to hardware offload
743 # # of checksum. You can control the handling of checksum
744 # # on a per-interface basis via the 'checksum-checks'
746 # prealloc-sessions: 2k # 2k sessions prealloc'd per stream thread
747 # midstream: false # don't allow midstream session pickups
748 # async-oneside: false # don't enable async stream handling
749 # inline: no # stream inline mode
750 # drop-invalid: yes # in inline mode, drop packets that are invalid with regards to streaming engine
751 # max-synack-queued: 5 # Max different SYN/ACKs to queue
752 # bypass: no # Bypass packets when stream.depth is reached
755 # memcap: 64mb # Can be specified in kb, mb, gb. Just a number
756 # # indicates it's in bytes.
757 # depth: 1mb # Can be specified in kb, mb, gb. Just a number
758 # # indicates it's in bytes.
759 # toserver-chunk-size: 2560 # inspect raw stream in chunks of at least
760 # # this size. Can be specified in kb, mb,
761 # # gb. Just a number indicates it's in bytes.
762 # toclient-chunk-size: 2560 # inspect raw stream in chunks of at least
763 # # this size. Can be specified in kb, mb,
764 # # gb. Just a number indicates it's in bytes.
765 # randomize-chunk-size: yes # Take a random value for chunk size around the specified value.
766 # # This lower the risk of some evasion technics but could lead
767 # # detection change between runs. It is set to 'yes' by default.
768 # randomize-chunk-range: 10 # If randomize-chunk-size is active, the value of chunk-size is
769 # # a random value between (1 - randomize-chunk-range/100)*toserver-chunk-size
770 # # and (1 + randomize-chunk-range/100)*toserver-chunk-size and the same
771 # # calculation for toclient-chunk-size.
772 # # Default value of randomize-chunk-range is 10.
774 # raw: yes # 'Raw' reassembly enabled or disabled.
775 # # raw is for content inspection by detection
778 # segment-prealloc: 2048 # number of segments preallocated per thread
780 # check-overlap-different-data: true|false
781 # # check if a segment contains different data
782 # # than what we've already seen for that
783 # # position in the stream.
784 # # This is enabled automatically if inline mode
785 # # is used or when stream-event:reassembly_overlap_different_data;
786 # # is used in a rule.
790 prealloc-sessions: 4096
791 checksum-validation: yes # reject wrong csums
792 inline: auto # auto will use inline mode in IPS mode, yes or no set it statically
795 depth: 1mb # reassemble 1mb into a stream
796 toserver-chunk-size: 2560
797 toclient-chunk-size: 2560
798 randomize-chunk-size: yes
800 segment-prealloc: 2048
801 check-overlap-different-data: true
805 # Host table is used by tagging and per host thresholding subsystems.
814 # Used by xbits 'ippair' tracking.
824 # Teredo decoder is known to not be completely accurate
825 # it will sometimes detect non-teredo as teredo.
831 ## Performance tuning and profiling
834 # The detection engine builds internal groups of signatures. The engine
835 # allow us to specify the profile to use for them, to manage memory on an
836 # efficient way keeping a good performance. For the profile keyword you
837 # can use the words "low", "medium", "high" or "custom". If you use custom
838 # make sure to define the values at "- custom-values" as your convenience.
839 # Usually you would prefer medium/high/low.
841 # "sgh mpm-context", indicates how the staging should allot mpm contexts for
842 # the signature groups. "single" indicates the use of a single context for
843 # all the signature group heads. "full" indicates a mpm-context for each
844 # group head. "auto" lets the engine decide the distribution of contexts
845 # based on the information the engine gathers on the patterns from each
848 # The option inspection-recursion-limit is used to limit the recursive calls
849 # in the content inspection code. For certain payload-sig combinations, we
850 # might end up taking too much time in the content inspection code.
851 # If the argument specified is 0, the engine uses an internally defined
852 # default limit. On not specifying a value, we use no limits on the recursion.
858 sgh-mpm-context: auto
859 inspection-recursion-limit: 3000
861 # If set to yes, the loading of signatures will be made after the capture
862 # is started. This will limit the downtime in IPS mode.
866 # default prefiltering setting. "mpm" only creates MPM/fast_pattern
867 # engines. "auto" also sets up prefilter engines for other keywords.
868 # Use --list-keywords=all to see which keywords support prefiltering.
871 # the grouping values above control how many groups are created per
872 # direction. Port whitelisting forces that port to get it's own group.
873 # Very common ports will benefit, as well as ports with many expensive
876 #tcp-whitelist: 53, 80, 139, 443, 445, 1433, 3306, 3389, 6666, 6667, 8080
877 #udp-whitelist: 53, 135, 5060
880 # Log the rules that made it past the prefilter stage, per packet
881 # default is off. The threshold setting determines how many rules
882 # must have made it past pre-filter for that rule to trigger the
884 #inspect-logging-threshold: 200
887 include-rules: false # very verbose
888 include-mpm-stats: false
890 # Select the multi pattern algorithm you want to run for scan/search the
893 # The supported algorithms are:
894 # "ac" - Aho-Corasick, default implementation
895 # "ac-bs" - Aho-Corasick, reduced memory implementation
896 # "ac-cuda" - Aho-Corasick, CUDA implementation
897 # "ac-ks" - Aho-Corasick, "Ken Steele" variant
898 # "hs" - Hyperscan, available when built with Hyperscan support
900 # The default mpm-algo value of "auto" will use "hs" if Hyperscan is
901 # available, "ac" otherwise.
903 # The mpm you choose also decides the distribution of mpm contexts for
904 # signature groups, specified by the conf - "detect.sgh-mpm-context".
905 # Selecting "ac" as the mpm would require "detect.sgh-mpm-context"
906 # to be set to "single", because of ac's memory requirements, unless the
907 # ruleset is small enough to fit in one's memory, in which case one can
908 # use "full" with "ac". Rest of the mpms can be run in "full" mode.
910 # There is also a CUDA pattern matcher (only available if Suricata was
911 # compiled with --enable-cuda: b2g_cuda. Make sure to update your
912 # max-pending-packets setting above as well if you use b2g_cuda.
916 # Select the matching algorithm you want to use for single-pattern searches.
918 # Supported algorithms are "bm" (Boyer-Moore) and "hs" (Hyperscan, only
919 # available if Suricata has been built with Hyperscan support).
921 # The default of "auto" will use "hs" if available, otherwise "bm".
925 # Suricata is multi-threaded. Here the threading can be influenced.
928 # Tune cpu affinity of threads. Each family of threads can be bound
931 # These 2 apply to the all runmodes:
932 # management-cpu-set is used for flow timeout handling, counters
933 # worker-cpu-set is used for 'worker' threads
935 # Additionally, for autofp these apply:
936 # receive-cpu-set is used for capture threads
937 # verdict-cpu-set is used for IPS verdict threads
940 - management-cpu-set:
941 cpu: [ 0 ] # include only these cpus in affinity settings
943 cpu: [ 0 ] # include only these cpus in affinity settings
957 # By default Suricata creates one "detect" thread per available CPU/CPU core.
958 # This setting allows controlling this behaviour. A ratio setting of 2 will
959 # create 2 detect threads for each CPU/CPU core. So for a dual core CPU this
960 # will result in 4 detect threads. If values below 1 are used, less threads
961 # are created. So on a dual core CPU a setting of 0.5 results in 1 detect
962 # thread being created. Regardless of the setting at a minimum 1 detect
963 # thread will always be created.
965 detect-thread-ratio: 1.0