Blame view

CEPTD/docker/logstash/dist/suricata.yaml 70.5 KB
0d8c0f816   Thanasis Naskos   initial commit
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
  %YAML 1.1
  ---
  
  # Suricata configuration file. In addition to the comments describing all
  # options in this file, full documentation can be found at:
  # https://suricata.readthedocs.io/en/latest/configuration/suricata-yaml.html
  
  ##
  ## Step 1: inform Suricata about your network
  ##
  
  vars:
    # more specific is better for alert accuracy and performance
    address-groups:
      HOME_NET: "[192.168.0.0/16,10.0.0.0/8,172.16.0.0/12]"
      #HOME_NET: "[192.168.0.0/16]"
      #HOME_NET: "[10.0.0.0/8]"
      #HOME_NET: "[172.16.0.0/12]"
      #HOME_NET: "any"
  
      #EXTERNAL_NET: "!$HOME_NET"
      EXTERNAL_NET: "any"
  
      HTTP_SERVERS: "$HOME_NET"
      SMTP_SERVERS: "$HOME_NET"
      SQL_SERVERS: "$HOME_NET"
      DNS_SERVERS: "$HOME_NET"
      TELNET_SERVERS: "$HOME_NET"
      AIM_SERVERS: "$EXTERNAL_NET"
      DC_SERVERS: "$HOME_NET"
      DNP3_SERVER: "$HOME_NET"
      DNP3_CLIENT: "$HOME_NET"
      MODBUS_CLIENT: "$HOME_NET"
      MODBUS_SERVER: "$HOME_NET"
      ENIP_CLIENT: "$HOME_NET"
      ENIP_SERVER: "$HOME_NET"
  
    port-groups:
      HTTP_PORTS: "80,8080,8081"
      SHELLCODE_PORTS: "!80,!8080,!8081"
      ORACLE_PORTS: "1433,1521,3306"
      SSH_PORTS: "22,64295"
      DNP3_PORTS: 20000
      MODBUS_PORTS: 502
      FILE_DATA_PORTS: "[$HTTP_PORTS,110,143]"
      FTP_PORTS: 21
      VXLAN_PORTS: 4789
  
  ##
  ## Step 2: select outputs to enable
  ##
  
  # The default logging directory.  Any log or output file will be
  # placed here if its not specified with a full path name. This can be
  # overridden with the -l command line parameter.
  default-log-dir: /var/log/suricata/
  
  # global stats configuration
  stats:
    enabled: no
    # The interval field (in seconds) controls at what interval
    # the loggers are invoked.
    interval: 8
    # Add decode events as stats.
    #decoder-events: true
    # Decoder event prefix in stats. Has been 'decoder' before, but that leads
    # to missing events in the eve.stats records. See issue #2225.
    decoder-events-prefix: "decoder.event"
    # Add stream events as stats.
    #stream-events: false
  
  # Configure the type of alert (and other) logging you would like.
  outputs:
    # a line based alerts log similar to Snort's fast.log
    - fast:
        enabled: no
        filename: fast.log
        append: yes
        #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
  
    # Extensible Event Format (nicknamed EVE) event log in JSON format
    - eve-log:
        enabled: yes
        filetype: regular #regular|syslog|unix_dgram|unix_stream|redis
        filename: eve.json
        #prefix: "@cee: " # prefix to prepend to each log entry
        # the following are valid when type: syslog above
        #identity: "suricata"
        #facility: local5
        #level: Info ## possible levels: Emergency, Alert, Critical,
                     ## Error, Warning, Notice, Info, Debug
        #redis:
        #  server: 127.0.0.1
        #  port: 6379
        #  async: true ## if redis replies are read asynchronously
        #  mode: list ## possible values: list|lpush (default), rpush, channel|publish
        #             ## lpush and rpush are using a Redis list. "list" is an alias for lpush
        #             ## publish is using a Redis channel. "channel" is an alias for publish
        #  key: suricata ## key or channel to use (default to suricata)
        # Redis pipelining set up. This will enable to only do a query every
        # 'batch-size' events. This should lower the latency induced by network
        # connection at the cost of some memory. There is no flushing implemented
        # so this setting as to be reserved to high traffic suricata.
        #  pipelining:
        #    enabled: yes ## set enable to yes to enable query pipelining
        #    batch-size: 10 ## number of entry to keep in buffer
  
        # Include top level metadata. Default yes.
        #metadata: no
  
        # include the name of the input pcap file in pcap file processing mode
        pcap-file: false
  
        # Community Flow ID
        # Adds a 'community_id' field to EVE records. These are meant to give
        # a records a predictable flow id that can be used to match records to
        # output of other tools such as Bro.
        #
        # Takes a 'seed' that needs to be same across sensors and tools
        # to make the id less predictable.
  
        # enable/disable the community id feature.
        community-id: false
        # Seed value for the ID output. Valid values are 0-65535.
        community-id-seed: 0
  
        # HTTP X-Forwarded-For support by adding an extra field or overwriting
        # the source or destination IP address (depending on flow direction)
        # with the one reported in the X-Forwarded-For HTTP header. This is
        # helpful when reviewing alerts for traffic that is being reverse
        # or forward proxied.
        xff:
          enabled: yes
          # Two operation modes are available, "extra-data" and "overwrite".
          mode: extra-data
          # Two proxy deployments are supported, "reverse" and "forward". In
          # a "reverse" deployment the IP address used is the last one, in a
          # "forward" deployment the first IP address is used.
          deployment: reverse
          # Header name where the actual IP address will be reported, if more
          # than one IP address is present, the last IP address will be the
          # one taken into consideration.
          header: X-Forwarded-For
  
        types:
          - alert:
              payload: yes             # enable dumping payload in Base64
              payload-buffer-size: 4kb # max size of payload buffer to output in eve-log
              payload-printable: yes   # enable dumping payload in printable (lossy) format
              # packet: yes              # enable dumping of packet (without stream segments)
              http-body: yes           # enable dumping of http body in Base64
              http-body-printable: yes # enable dumping of http body in printable format
              # metadata: no             # enable inclusion of app layer metadata with alert. Default yes
  
              # Enable the logging of tagged packets for rules using the
              # "tag" keyword.
              tagged-packets: yes
          - anomaly:
              # Anomaly log records describe unexpected conditions such
              # as truncated packets, packets with invalid IP/UDP/TCP
              # length values, and other events that render the packet
              # invalid for further processing or describe unexpected
              # behavior on an established stream. Networks which
              # experience high occurrences of anomalies may experience
              # packet processing degradation.
              #
              # Anomalies are reported for the following:
              # 1. Decode: Values and conditions that are detected while
              # decoding individual packets. This includes invalid or
              # unexpected values for low-level protocol lengths as well
              # as stream related events (TCP 3-way handshake issues,
              # unexpected sequence number, etc).
              # 2. Stream: This includes stream related events (TCP
              # 3-way handshake issues, unexpected sequence number,
              # etc).
              # 3. Application layer: These denote application layer
              # specific conditions that are unexpected, invalid or are
              # unexpected given the application monitoring state.
              #
              # By default, anomaly logging is disabled. When anomaly
              # logging is enabled, applayer anomaly reporting is
              # enabled.
              enabled: yes
              #
              # Choose one or more types of anomaly logging and whether to enable
              # logging of the packet header for packet anomalies.
              types:
                # decode: no
                # stream: no
                # applayer: yes
              #packethdr: no
          - http:
              extended: yes     # enable this for extended logging information
              # custom allows additional http fields to be included in eve-log
              # the example below adds three additional fields when uncommented
              custom: [Accept-Encoding, Accept-Language, Authorization, Forwarded, From, Referer, Via]
          - dns:
              # This configuration uses the new DNS logging format,
              # the old configuration is still available:
              # https://suricata.readthedocs.io/en/latest/output/eve/eve-json-output.html#dns-v1-format
  
              # As of Suricata 5.0, version 2 of the eve dns output
              # format is the default.
              version: 2
  
              # Enable/disable this logger. Default: enabled.
              #enabled: yes
  
              # Control logging of requests and responses:
              # - requests: enable logging of DNS queries
              # - responses: enable logging of DNS answers
              # By default both requests and responses are logged.
              #requests: no
              #responses: no
  
              # Format of answer logging:
              # - detailed: array item per answer
              # - grouped: answers aggregated by type
              # Default: all
              #formats: [detailed, grouped]
  
              # Types to log, based on the query type.
              # Default: all.
              #types: [a, aaaa, cname, mx, ns, ptr, txt]
          - tls:
              extended: yes     # enable this for extended logging information
              # output TLS transaction where the session is resumed using a
              # session id
              #session-resumption: no
              # custom allows to control which tls fields that are included
              # in eve-log
              custom: [subject, issuer, session_resumed, serial, fingerprint, sni, version, not_before, not_after, certificate, ja3, ja3s]
          - files:
              force-magic: yes   # force logging magic on all logged files
              # force logging of checksums, available hash functions are md5,
              # sha1 and sha256
              force-hash: [md5]
          #- drop:
          #    alerts: yes      # log alerts that caused drops
          #    flows: all       # start or all: 'start' logs only a single drop
          #                     # per flow direction. All logs each dropped pkt.
          - smtp:
              extended: yes # enable this for extended logging information
              # this includes: bcc, message-id, subject, x_mailer, user-agent
              # custom fields logging from the list:
              #  reply-to, bcc, message-id, subject, x-mailer, user-agent, received,
              #  x-originating-ip, in-reply-to, references, importance, priority,
              #  sensitivity, organization, content-md5, date
              custom: [reply-to, bcc, message-id, subject, x-mailer, user-agent, received, x-originating-ip, in-reply-to, references, organization, date]
              # output md5 of fields: body, subject
              # for the body you need to set app-layer.protocols.smtp.mime.body-md5
              # to yes
              md5: [body, subject]
  
          - dnp3
          - ftp
          - rdp
          - nfs
          - smb
          - tftp
          - ikev2
          - krb5
          - snmp
          - sip
          - dhcp:
              # DHCP logging requires Rust.
              enabled: no
              # When extended mode is on, all DHCP messages are logged
              # with full detail. When extended mode is off (the
              # default), just enough information to map a MAC address
              # to an IP address is logged.
              extended: no
          - ssh
          - stats:
              totals: yes       # stats for all threads merged together
              threads: no       # per thread stats
              deltas: no        # include delta values
          # bi-directional flows
          #- flow
          # uni-directional flows
          #- netflow
  
          # Metadata event type. Triggered whenever a pktvar is saved
          # and will include the pktvars, flowvars, flowbits and
          # flowints.
          #- metadata
  
    # deprecated - unified2 alert format for use with Barnyard2
    - unified2-alert:
        enabled: no
        # for further options see:
        # https://suricata.readthedocs.io/en/suricata-5.0.0/configuration/suricata-yaml.html#alert-output-for-use-with-barnyard2-unified2-alert
  
    # a line based log of HTTP requests (no alerts)
    - http-log:
        enabled: no
        filename: http.log
        append: yes
        #extended: yes     # enable this for extended logging information
        #custom: yes       # enabled the custom logging format (defined by customformat)
        #customformat: "%{%D-%H:%M:%S}t.%z %{X-Forwarded-For}i %H %m %h %u %s %B %a:%p -> %A:%P"
        #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
  
    # a line based log of TLS handshake parameters (no alerts)
    - tls-log:
        enabled: no  # Log TLS connections.
        filename: tls.log # File to store TLS logs.
        append: yes
        #extended: yes     # Log extended information like fingerprint
        #custom: yes       # enabled the custom logging format (defined by customformat)
        #customformat: "%{%D-%H:%M:%S}t.%z %a:%p -> %A:%P %v %n %d %D"
        #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
        # output TLS transaction where the session is resumed using a
        # session id
        #session-resumption: no
  
    # output module to store certificates chain to disk
    - tls-store:
        enabled: no
        #certs-log-dir: certs # directory to store the certificates files
  
    # Packet log... log packets in pcap format. 3 modes of operation: "normal"
    # "multi" and "sguil".
    #
    # In normal mode a pcap file "filename" is created in the default-log-dir,
    # or are as specified by "dir".
    # In multi mode, a file is created per thread. This will perform much
    # better, but will create multiple files where 'normal' would create one.
    # In multi mode the filename takes a few special variables:
    # - %n -- thread number
    # - %i -- thread id
    # - %t -- timestamp (secs or secs.usecs based on 'ts-format'
    # E.g. filename: pcap.%n.%t
    #
    # Note that it's possible to use directories, but the directories are not
    # created by Suricata. E.g. filename: pcaps/%n/log.%s will log into the
    # per thread directory.
    #
    # Also note that the limit and max-files settings are enforced per thread.
    # So the size limit when using 8 threads with 1000mb files and 2000 files
    # is: 8*1000*2000 ~ 16TiB.
    #
    # In Sguil mode "dir" indicates the base directory. In this base dir the
    # pcaps are created in th directory structure Sguil expects:
    #
    # $sguil-base-dir/YYYY-MM-DD/$filename.<timestamp>
    #
    # By default all packets are logged except:
    # - TCP streams beyond stream.reassembly.depth
    # - encrypted streams after the key exchange
    #
    - pcap-log:
        enabled: no
        filename: log.pcap
  
        # File size limit.  Can be specified in kb, mb, gb.  Just a number
        # is parsed as bytes.
        limit: 1000mb
  
        # If set to a value will enable ring buffer mode. Will keep Maximum of "max-files" of size "limit"
        max-files: 2000
  
        # Compression algorithm for pcap files. Possible values: none, lz4.
        # Enabling compression is incompatible with the sguil mode. Note also
        # that on Windows, enabling compression will *increase* disk I/O.
        compression: none
  
        # Further options for lz4 compression. The compression level can be set
        # to a value between 0 and 16, where higher values result in higher
        # compression.
        #lz4-checksum: no
        #lz4-level: 0
  
        mode: normal # normal, multi or sguil.
  
        # Directory to place pcap files. If not provided the default log
        # directory will be used. Required for "sguil" mode.
        #dir: /nsm_data/
  
        #ts-format: usec # sec or usec second format (default) is filename.sec usec is filename.sec.usec
        use-stream-depth: no #If set to "yes" packets seen after reaching stream inspection depth are ignored. "no" logs all packets
        honor-pass-rules: no # If set to "yes", flows in which a pass rule matched will stopped being logged.
  
    # a full alerts log containing much information for signature writers
    # or for investigating suspected false positives.
    - alert-debug:
        enabled: no
        filename: alert-debug.log
        append: yes
        #filetype: regular # 'regular', 'unix_stream' or 'unix_dgram'
  
    # alert output to prelude (https://www.prelude-siem.org/) only
    # available if Suricata has been compiled with --enable-prelude
    - alert-prelude:
        enabled: no
        profile: suricata
        log-packet-content: no
        log-packet-header: yes
  
    # Stats.log contains data from various counters of the Suricata engine.
    - stats:
        enabled: no
        filename: stats.log
        append: yes       # append to file (yes) or overwrite it (no)
        totals: yes       # stats for all threads merged together
        threads: no       # per thread stats
        #null-values: yes  # print counters that have value 0
  
    # a line based alerts log similar to fast.log into syslog
    - syslog:
        enabled: no
        # reported identity to syslog. If ommited the program name (usually
        # suricata) will be used.
        #identity: "suricata"
        facility: local5
        #level: Info ## possible levels: Emergency, Alert, Critical,
                     ## Error, Warning, Notice, Info, Debug
  
    # deprecated a line based information for dropped packets in IPS mode
    - drop:
        enabled: no
        # further options documented at:
        # https://suricata.readthedocs.io/en/suricata-5.0.0/configuration/suricata-yaml.html#drop-log-a-line-based-information-for-dropped-packets
  
    # Output module for storing files on disk. Files are stored in a
    # directory names consisting of the first 2 characters of the
    # SHA256 of the file. Each file is given its SHA256 as a filename.
    #
    # When a duplicate file is found, the existing file is touched to
    # have its timestamps updated.
    #
    # Unlike the older filestore, metadata is not written out by default
    # as each file should already have a "fileinfo" record in the
    # eve.log. If write-fileinfo is set to yes, the each file will have
    # one more associated .json files that consists of the fileinfo
    # record. A fileinfo file will be written for each occurrence of the
    # file seen using a filename suffix to ensure uniqueness.
    #
    # To prune the filestore directory see the "suricatactl filestore
    # prune" command which can delete files over a certain age.
  
    - file-store:
        version: 2
        enabled: no
  
        # Set the directory for the filestore. If the path is not
        # absolute will be be relative to the default-log-dir.
        #dir: filestore
  
        # Write out a fileinfo record for each occurrence of a
        # file. Disabled by default as each occurrence is already logged
        # as a fileinfo record to the main eve-log.
        #write-fileinfo: yes
  
        # Force storing of all files. Default: no.
        #force-filestore: yes
  
        # Override the global stream-depth for sessions in which we want
        # to perform file extraction. Set to 0 for unlimited.
        #stream-depth: 0
  
        # Uncomment the following variable to define how many files can
        # remain open for filestore by Suricata. Default value is 0 which
        # means files get closed after each write
        #max-open-files: 1000
  
        # Force logging of checksums, available hash functions are md5,
        # sha1 and sha256. Note that SHA256 is automatically forced by
        # the use of this output module as it uses the SHA256 as the
        # file naming scheme.
        #force-hash: [sha1, md5]
        # NOTE: X-Forwarded configuration is ignored if write-fileinfo is disabled
        # HTTP X-Forwarded-For support by adding an extra field or overwriting
        # the source or destination IP address (depending on flow direction)
        # with the one reported in the X-Forwarded-For HTTP header. This is
        # helpful when reviewing alerts for traffic that is being reverse
        # or forward proxied.
        xff:
          enabled: no
          # Two operation modes are available, "extra-data" and "overwrite".
          mode: extra-data
          # Two proxy deployments are supported, "reverse" and "forward". In
          # a "reverse" deployment the IP address used is the last one, in a
          # "forward" deployment the first IP address is used.
          deployment: reverse
          # Header name where the actual IP address will be reported, if more
          # than one IP address is present, the last IP address will be the
          # one taken into consideration.
          header: X-Forwarded-For
  
    # deprecated - file-store v1
    - file-store:
        enabled: no
        # further options documented at:
        # https://suricata.readthedocs.io/en/suricata-5.0.0/file-extraction/file-extraction.html#file-store-version-1
  
    # Log TCP data after stream normalization
    # 2 types: file or dir. File logs into a single logfile. Dir creates
    # 2 files per TCP session and stores the raw TCP data into them.
    # Using 'both' will enable both file and dir modes.
    #
    # Note: limited by stream.depth
    - tcp-data:
        enabled: no
        type: file
        filename: tcp-data.log
  
    # Log HTTP body data after normalization, dechunking and unzipping.
    # 2 types: file or dir. File logs into a single logfile. Dir creates
    # 2 files per HTTP session and stores the normalized data into them.
    # Using 'both' will enable both file and dir modes.
    #
    # Note: limited by the body limit settings
    - http-body-data:
        enabled: no
        type: file
        filename: http-data.log
  
    # Lua Output Support - execute lua script to generate alert and event
    # output.
    # Documented at:
    # https://suricata.readthedocs.io/en/latest/output/lua-output.html
    - lua:
        enabled: no
        #scripts-dir: /etc/suricata/lua-output/
        scripts:
        #   - script1.lua
  
  # Logging configuration.  This is not about logging IDS alerts/events, but
  # output about what Suricata is doing, like startup messages, errors, etc.
  logging:
    # The default log level, can be overridden in an output section.
    # Note that debug level logging will only be emitted if Suricata was
    # compiled with the --enable-debug configure option.
    #
    # This value is overridden by the SC_LOG_LEVEL env var.
    default-log-level: notice
  
    # The default output format.  Optional parameter, should default to
    # something reasonable if not provided.  Can be overridden in an
    # output section.  You can leave this out to get the default.
    #
    # This value is overridden by the SC_LOG_FORMAT env var.
    #default-log-format: "[%i] %t - (%f:%l) <%d> (%n) -- "
  
    # A regex to filter output.  Can be overridden in an output section.
    # Defaults to empty (no filter).
    #
    # This value is overridden by the SC_LOG_OP_FILTER env var.
    default-output-filter:
  
    # Define your logging outputs.  If none are defined, or they are all
    # disabled you will get the default - console output.
    outputs:
    - console:
        enabled: yes
        # type: json
    - file:
        enabled: yes
        level: info
        filename: /var/log/suricata/suricata.log
        # type: json
    - syslog:
        enabled: no
        facility: local5
        format: "[%i] <%d> -- "
        # type: json
  
  
  ##
  ## Step 4: configure common capture settings
  ##
  ## See "Advanced Capture Options" below for more options, including NETMAP
  ## and PF_RING.
  ##
  
  # Linux high speed capture support
  af-packet:
    - interface: eth0
      # Number of receive threads. "auto" uses the number of cores
      #threads: auto
      # Default clusterid. AF_PACKET will load balance packets based on flow.
      cluster-id: 99
      # Default AF_PACKET cluster type. AF_PACKET can load balance per flow or per hash.
      # This is only supported for Linux kernel > 3.1
      # possible value are:
      #  * cluster_round_robin: round robin load balancing
      #  * cluster_flow: all packets of a given flow are send to the same socket
      #  * cluster_cpu: all packets treated in kernel by a CPU are send to the same socket
      #  * cluster_qm: all packets linked by network card to a RSS queue are sent to the same
      #  socket. Requires at least Linux 3.14.
      #  * cluster_random: packets are sent randomly to sockets but with an equipartition.
      #  Requires at least Linux 3.14.
      #  * cluster_rollover: kernel rotates between sockets filling each socket before moving
      #  to the next. Requires at least Linux 3.10.
      #  * cluster_ebpf: eBPF file load balancing. See doc/userguide/capture-hardware/ebpf-xdp.rst for
      #  more info.
      # Recommended modes are cluster_flow on most boxes and cluster_cpu or cluster_qm on system
      # with capture card using RSS (require cpu affinity tuning and system irq tuning)
      cluster-type: cluster_flow
      # In some fragmentation case, the hash can not be computed. If "defrag" is set
      # to yes, the kernel will do the needed defragmentation before sending the packets.
      defrag: yes
      # After Linux kernel 3.10 it is possible to activate the rollover option: if a socket is
      # full then kernel will send the packet on the next socket with room available. This option
      # can minimize packet drop and increase the treated bandwidth on single intensive flow.
      #rollover: yes
      # To use the ring feature of AF_PACKET, set 'use-mmap' to yes
      #use-mmap: yes
      # Lock memory map to avoid it goes to swap. Be careful that over subscribing could lock
      # your system
      #mmap-locked: yes
      # Use tpacket_v3 capture mode, only active if use-mmap is true
      # Don't use it in IPS or TAP mode as it causes severe latency
      #tpacket-v3: yes
      # Ring size will be computed with respect to max_pending_packets and number
      # of threads. You can set manually the ring size in number of packets by setting
      # the following value. If you are using flow cluster-type and have really network
      # intensive single-flow you could want to set the ring-size independently of the number
      # of threads:
      #ring-size: 2048
      # Block size is used by tpacket_v3 only. It should set to a value high enough to contain
      # a decent number of packets. Size is in bytes so please consider your MTU. It should be
      # a power of 2 and it must be multiple of page size (usually 4096).
      #block-size: 32768
      # tpacket_v3 block timeout: an open block is passed to userspace if it is not
      # filled after block-timeout milliseconds.
      #block-timeout: 10
      # On busy system, this could help to set it to yes to recover from a packet drop
      # phase. This will result in some packets (at max a ring flush) being non treated.
      #use-emergency-flush: yes
      # recv buffer size, increase value could improve performance
      # buffer-size: 32768
      # Set to yes to disable promiscuous mode
      # disable-promisc: no
      # Choose checksum verification mode for the interface. At the moment
      # of the capture, some packets may be with an invalid checksum due to
      # offloading to the network card of the checksum computation.
      # Possible values are:
      #  - kernel: use indication sent by kernel for each packet (default)
      #  - yes: checksum validation is forced
      #  - no: checksum validation is disabled
      #  - auto: suricata uses a statistical approach to detect when
      #  checksum off-loading is used.
      # Warning: 'checksum-validation' must be set to yes to have any validation
      #checksum-checks: kernel
      # BPF filter to apply to this interface. The pcap filter syntax apply here.
      #bpf-filter: port 80 or udp
      # You can use the following variables to activate AF_PACKET tap or IPS mode.
      # If copy-mode is set to ips or tap, the traffic coming to the current
      # interface will be copied to the copy-iface interface. If 'tap' is set, the
      # copy is complete. If 'ips' is set, the packet matching a 'drop' action
      # will not be copied.
      #copy-mode: ips
      #copy-iface: eth1
      #  For eBPF and XDP setup including bypass, filter and load balancing, please
      #  see doc/userguide/capture/ebpf-xdt.rst for more info.
  
    # Put default values here. These will be used for an interface that is not
    # in the list above.
    - interface: default
      #threads: auto
      #use-mmap: no
      #rollover: yes
      #tpacket-v3: yes
  
  # Cross platform libpcap capture support
  pcap:
    - interface: eth0
      # On Linux, pcap will try to use mmaped capture and will use buffer-size
      # as total of memory used by the ring. So set this to something bigger
      # than 1% of your bandwidth.
      #buffer-size: 16777216
      #bpf-filter: "tcp and port 25"
      # Choose checksum verification mode for the interface. At the moment
      # of the capture, some packets may be with an invalid checksum due to
      # offloading to the network card of the checksum computation.
      # Possible values are:
      #  - yes: checksum validation is forced
      #  - no: checksum validation is disabled
      #  - auto: Suricata uses a statistical approach to detect when
      #  checksum off-loading is used. (default)
      # Warning: 'checksum-validation' must be set to yes to have any validation
      #checksum-checks: auto
      # With some accelerator cards using a modified libpcap (like myricom), you
      # may want to have the same number of capture threads as the number of capture
      # rings. In this case, set up the threads variable to N to start N threads
      # listening on the same interface.
      #threads: 16
      # set to no to disable promiscuous mode:
      #promisc: no
      # set snaplen, if not set it defaults to MTU if MTU can be known
      # via ioctl call and to full capture if not.
      #snaplen: 1518
    # Put default values here
    - interface: default
      #checksum-checks: auto
  
  # Settings for reading pcap files
  pcap-file:
    # Possible values are:
    #  - yes: checksum validation is forced
    #  - no: checksum validation is disabled
    #  - auto: Suricata uses a statistical approach to detect when
    #  checksum off-loading is used. (default)
    # Warning: 'checksum-validation' must be set to yes to have checksum tested
    checksum-checks: auto
  
  # See "Advanced Capture Options" below for more options, including NETMAP
  # and PF_RING.
  
  
  ##
  ## Step 5: App Layer Protocol Configuration
  ##
  
  # Configure the app-layer parsers. The protocols section details each
  # protocol.
  #
  # The option "enabled" takes 3 values - "yes", "no", "detection-only".
  # "yes" enables both detection and the parser, "no" disables both, and
  # "detection-only" enables protocol detection only (parser disabled).
  app-layer:
    protocols:
      krb5:
        enabled: yes
      snmp:
        enabled: yes
      ikev2:
        enabled: yes
      tls:
        enabled: yes
        detection-ports:
          dp: 443
  
        # Generate JA3 fingerprint from client hello
        ja3-fingerprints: yes
  
        # What to do when the encrypted communications start:
        # - default: keep tracking TLS session, check for protocol anomalies,
        #            inspect tls_* keywords. Disables inspection of unmodified
        #            'content' signatures.
        # - bypass:  stop processing this flow as much as possible. No further
        #            TLS parsing and inspection. Offload flow bypass to kernel
        #            or hardware if possible.
        # - full:    keep tracking and inspection as normal. Unmodified content
        #            keyword signatures are inspected as well.
        #
        # For best performance, select 'bypass'.
        #
        #encrypt-handling: default
  
      dcerpc:
        enabled: yes
      ftp:
        enabled: yes
        # memcap: 64mb
      rdp:
        enabled: yes
      ssh:
        enabled: yes
      smtp:
        enabled: yes
        # Configure SMTP-MIME Decoder
        mime:
          # Decode MIME messages from SMTP transactions
          # (may be resource intensive)
          # This field supercedes all others because it turns the entire
          # process on or off
          decode-mime: yes
  
          # Decode MIME entity bodies (ie. base64, quoted-printable, etc.)
          decode-base64: yes
          decode-quoted-printable: yes
  
          # Maximum bytes per header data value stored in the data structure
          # (default is 2000)
          header-value-depth: 2000
  
          # Extract URLs and save in state data structure
          extract-urls: yes
          # Set to yes to compute the md5 of the mail body. You will then
          # be able to journalize it.
          body-md5: yes
        # Configure inspected-tracker for file_data keyword
        inspected-tracker:
          content-limit: 100000
          content-inspect-min-size: 32768
          content-inspect-window: 4096
      imap:
        enabled: detection-only
      # Note: --enable-rust is required for full SMB1/2 support. W/o rust
      # only minimal SMB1 support is available.
      smb:
        enabled: yes
        detection-ports:
          dp: 139, 445
  
        # Stream reassembly size for SMB streams. By default track it completely.
        #stream-depth: 0
  
      # Note: NFS parser depends on Rust support: pass --enable-rust
      # to configure.
      nfs:
        enabled: yes
      tftp:
        enabled: yes
      dns:
        # memcaps. Globally and per flow/state.
        global-memcap: 16mb
        state-memcap: 512kb
  
        # How many unreplied DNS requests are considered a flood.
        # If the limit is reached, app-layer-event:dns.flooded; will match.
        request-flood: 500
  
        tcp:
          enabled: yes
          detection-ports:
            dp: 53
        udp:
          enabled: yes
          detection-ports:
            dp: 53
      http:
        enabled: yes
        # memcap:                   Maximum memory capacity for http
        #                           Default is unlimited, value can be such as 64mb
  
        # default-config:           Used when no server-config matches
        #   personality:            List of personalities used by default
        #   request-body-limit:     Limit reassembly of request body for inspection
        #                           by http_client_body & pcre /P option.
        #   response-body-limit:    Limit reassembly of response body for inspection
        #                           by file_data, http_server_body & pcre /Q option.
        #
        #   For advanced options, see the user guide
  
  
        # server-config:            List of server configurations to use if address matches
        #   address:                List of IP addresses or networks for this block
        #   personalitiy:           List of personalities used by this block
        #
        #                           Then, all the fields from default-config can be overloaded
        #
        # Currently Available Personalities:
        #   Minimal, Generic, IDS (default), IIS_4_0, IIS_5_0, IIS_5_1, IIS_6_0,
        #   IIS_7_0, IIS_7_5, Apache_2
        libhtp:
           default-config:
             personality: IDS
  
             # Can be specified in kb, mb, gb.  Just a number indicates
             # it's in bytes.
             request-body-limit: 100kb
             response-body-limit: 100kb
  
             # inspection limits
             request-body-minimal-inspect-size: 32kb
             request-body-inspect-window: 4kb
             response-body-minimal-inspect-size: 40kb
             response-body-inspect-window: 16kb
  
             # response body decompression (0 disables)
             response-body-decompress-layer-limit: 2
  
             # auto will use http-body-inline mode in IPS mode, yes or no set it statically
             http-body-inline: auto
  
             # Decompress SWF files.
             # 2 types: 'deflate', 'lzma', 'both' will decompress deflate and lzma
             # compress-depth:
             # Specifies the maximum amount of data to decompress,
             # set 0 for unlimited.
             # decompress-depth:
             # Specifies the maximum amount of decompressed data to obtain,
             # set 0 for unlimited.
             swf-decompression:
               enabled: yes
               type: both
               compress-depth: 0
               decompress-depth: 0
  
             # Take a random value for inspection sizes around the specified value.
             # This lower the risk of some evasion technics but could lead
             # detection change between runs. It is set to 'yes' by default.
             #randomize-inspection-sizes: yes
             # If randomize-inspection-sizes is active, the value of various
             # inspection size will be choosen in the [1 - range%, 1 + range%]
             # range
             # Default value of randomize-inspection-range is 10.
             #randomize-inspection-range: 10
  
             # decoding
             double-decode-path: no
             double-decode-query: no
  
           server-config:
  
             #- apache:
             #    address: [192.168.1.0/24, 127.0.0.0/8, "::1"]
             #    personality: Apache_2
             #    # Can be specified in kb, mb, gb.  Just a number indicates
             #    # it's in bytes.
             #    request-body-limit: 4096
             #    response-body-limit: 4096
             #    double-decode-path: no
             #    double-decode-query: no
  
             #- iis7:
             #    address:
             #      - 192.168.0.0/24
             #      - 192.168.10.0/24
             #    personality: IIS_7_0
             #    # Can be specified in kb, mb, gb.  Just a number indicates
             #    # it's in bytes.
             #    request-body-limit: 4096
             #    response-body-limit: 4096
             #    double-decode-path: no
             #    double-decode-query: no
  
      # Note: Modbus probe parser is minimalist due to the poor significant field
      # Only Modbus message length (greater than Modbus header length)
      # And Protocol ID (equal to 0) are checked in probing parser
      # It is important to enable detection port and define Modbus port
      # to avoid false positive
      modbus:
        # How many unreplied Modbus requests are considered a flood.
        # If the limit is reached, app-layer-event:modbus.flooded; will match.
        #request-flood: 500
  
        enabled: yes
        detection-ports:
          dp: 502
        # According to MODBUS Messaging on TCP/IP Implementation Guide V1.0b, it
        # is recommended to keep the TCP connection opened with a remote device
        # and not to open and close it for each MODBUS/TCP transaction. In that
        # case, it is important to set the depth of the stream reassembling as
        # unlimited (stream.reassembly.depth: 0)
  
        # Stream reassembly size for modbus. By default track it completely.
        stream-depth: 0
  
      # DNP3
      dnp3:
        enabled: yes
        detection-ports:
          dp: 20000
  
      # SCADA EtherNet/IP and CIP protocol support
      enip:
        enabled: no
        detection-ports:
          dp: 44818
          sp: 44818
  
      # Note: parser depends on Rust support
      ntp:
        enabled: yes
  
      dhcp:
        enabled: no
  
      # SIP, disabled by default.
      sip:
        enabled: yes
  
  
  # Limit for the maximum number of asn1 frames to decode (default 256)
  asn1-max-frames: 256
  
  
  ##############################################################################
  ##
  ## Advanced settings below
  ##
  ##############################################################################
  
  ##
  ## Run Options
  ##
  
  # Run suricata as user and group.
  #run-as:
  #  user: suri
  #  group: suri
  
  # Some logging module will use that name in event as identifier. The default
  # value is the hostname
  #sensor-name: suricata
  
  # Default location of the pid file. The pid file is only used in
  # daemon mode (start Suricata with -D). If not running in daemon mode
  # the --pidfile command line option must be used to create a pid file.
  #pid-file: /var/run/suricata.pid
  
  # Daemon working directory
  # Suricata will change directory to this one if provided
  # Default: "/"
  #daemon-directory: "/"
  
  # Umask.
  # Suricata will use this umask if it is provided. By default it will use the
  # umask passed on by the shell.
  #umask: 022
  
  # Suricata core dump configuration. Limits the size of the core dump file to
  # approximately max-dump. The actual core dump size will be a multiple of the
  # page size. Core dumps that would be larger than max-dump are truncated. On
  # Linux, the actual core dump size may be a few pages larger than max-dump.
  # Setting max-dump to 0 disables core dumping.
  # Setting max-dump to 'unlimited' will give the full core dump file.
  # On 32-bit Linux, a max-dump value >= ULONG_MAX may cause the core dump size
  # to be 'unlimited'.
  
  coredump:
    max-dump: unlimited
  
  # If Suricata box is a router for the sniffed networks, set it to 'router'. If
  # it is a pure sniffing setup, set it to 'sniffer-only'.
  # If set to auto, the variable is internally switch to 'router' in IPS mode
  # and 'sniffer-only' in IDS mode.
  # This feature is currently only used by the reject* keywords.
  host-mode: auto
  
  # Number of packets preallocated per thread. The default is 1024. A higher number 
  # will make sure each CPU will be more easily kept busy, but may negatively 
  # impact caching.
  #max-pending-packets: 1024
  
  # Runmode the engine should use. Please check --list-runmodes to get the available
  # runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned
  # load balancing).
  #runmode: autofp
  
  # Specifies the kind of flow load balancer used by the flow pinned autofp mode.
  #
  # Supported schedulers are:
  #
  # round-robin       - Flows assigned to threads in a round robin fashion.
  # active-packets    - Flows assigned to threads that have the lowest number of
  #                     unprocessed packets (default).
  # hash              - Flow allocated using the address hash. More of a random
  #                     technique. Was the default in Suricata 1.2.1 and older.
  #
  #autofp-scheduler: active-packets
  
  # Preallocated size for packet. Default is 1514 which is the classical
  # size for pcap on ethernet. You should adjust this value to the highest
  # packet size (MTU + hardware header) on your system.
  #default-packet-size: 1514
  
  # Unix command socket can be used to pass commands to Suricata.
  # An external tool can then connect to get information from Suricata
  # or trigger some modifications of the engine. Set enabled to yes
  # to activate the feature. In auto mode, the feature will only be
  # activated in live capture mode. You can use the filename variable to set
  # the file name of the socket.
  unix-command:
    enabled: no
    #filename: custom.socket
  
  # Magic file. The extension .mgc is added to the value here.
  #magic-file: /usr/share/file/magic
  magic-file: /usr/share/misc/magic.mgc 
  
  legacy:
    uricontent: enabled
  
  ##
  ## Detection settings
  ##
  
  # Set the order of alerts based on actions
  # The default order is pass, drop, reject, alert
  # action-order:
  #   - pass
  #   - drop
  #   - reject
  #   - alert
  
  # IP Reputation
  #reputation-categories-file: /etc/suricata/iprep/categories.txt
  #default-reputation-path: /etc/suricata/iprep
  #reputation-files:
  # - reputation.list
  
  # When run with the option --engine-analysis, the engine will read each of
  # the parameters below, and print reports for each of the enabled sections
  # and exit.  The reports are printed to a file in the default log dir
  # given by the parameter "default-log-dir", with engine reporting
  # subsection below printing reports in its own report file.
  engine-analysis:
    # enables printing reports for fast-pattern for every rule.
    rules-fast-pattern: yes
    # enables printing reports for each rule
    rules: yes
  
  #recursion and match limits for PCRE where supported
  pcre:
    match-limit: 3500
    match-limit-recursion: 1500
  
  ##
  ## Advanced Traffic Tracking and Reconstruction Settings
  ##
  
  # Host specific policies for defragmentation and TCP stream
  # reassembly. The host OS lookup is done using a radix tree, just
  # like a routing table so the most specific entry matches.
  host-os-policy:
    # Make the default policy windows.
    windows: [0.0.0.0/0]
    bsd: []
    bsd-right: []
    old-linux: []
    linux: []
    old-solaris: []
    solaris: []
    hpux10: []
    hpux11: []
    irix: []
    macos: []
    vista: []
    windows2k3: []
  
  # Defrag settings:
  
  defrag:
    memcap: 32mb
    hash-size: 65536
    trackers: 65535 # number of defragmented flows to follow
    max-frags: 65535 # number of fragments to keep (higher than trackers)
    prealloc: yes
    timeout: 60
  
  # Enable defrag per host settings
  #  host-config:
  #
  #    - dmz:
  #        timeout: 30
  #        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"]
  #
  #    - lan:
  #        timeout: 45
  #        address:
  #          - 192.168.0.0/24
  #          - 192.168.10.0/24
  #          - 172.16.14.0/24
  
  # Flow settings:
  # By default, the reserved memory (memcap) for flows is 32MB. This is the limit
  # for flow allocation inside the engine. You can change this value to allow
  # more memory usage for flows.
  # The hash-size determine the size of the hash used to identify flows inside
  # the engine, and by default the value is 65536.
  # At the startup, the engine can preallocate a number of flows, to get a better
  # performance. The number of flows preallocated is 10000 by default.
  # emergency-recovery is the percentage of flows that the engine need to
  # prune before unsetting the emergency state. The emergency state is activated
  # when the memcap limit is reached, allowing to create new flows, but
  # pruning them with the emergency timeouts (they are defined below).
  # If the memcap is reached, the engine will try to prune flows
  # with the default timeouts. If it doesn't find a flow to prune, it will set
  # the emergency bit and it will try again with more aggressive timeouts.
  # If that doesn't work, then it will try to kill the last time seen flows
  # not in use.
  # The memcap can be specified in kb, mb, gb.  Just a number indicates it's
  # in bytes.
  
  flow:
    memcap: 128mb
    hash-size: 65536
    prealloc: 10000
    emergency-recovery: 30
    #managers: 1 # default to one flow manager
    #recyclers: 1 # default to one flow recycler thread
  
  # This option controls the use of vlan ids in the flow (and defrag)
  # hashing. Normally this should be enabled, but in some (broken)
  # setups where both sides of a flow are not tagged with the same vlan
  # tag, we can ignore the vlan id's in the flow hashing.
  vlan:
    use-for-tracking: true
  
  # Specific timeouts for flows. Here you can specify the timeouts that the
  # active flows will wait to transit from the current state to another, on each
  # protocol. The value of "new" determine the seconds to wait after a handshake or
  # stream startup before the engine free the data of that flow it doesn't
  # change the state to established (usually if we don't receive more packets
  # of that flow). The value of "established" is the amount of
  # seconds that the engine will wait to free the flow if it spend that amount
  # without receiving new packets or closing the connection. "closed" is the
  # amount of time to wait after a flow is closed (usually zero). "bypassed"
  # timeout controls locally bypassed flows. For these flows we don't do any other
  # tracking. If no packets have been seen after this timeout, the flow is discarded.
  #
  # There's an emergency mode that will become active under attack circumstances,
  # making the engine to check flow status faster. This configuration variables
  # use the prefix "emergency-" and work similar as the normal ones.
  # Some timeouts doesn't apply to all the protocols, like "closed", for udp and
  # icmp.
  
  flow-timeouts:
  
    default:
      new: 30
      established: 300
      closed: 0
      bypassed: 100
      emergency-new: 10
      emergency-established: 100
      emergency-closed: 0
      emergency-bypassed: 50
    tcp:
      new: 60
      established: 600
      closed: 60
      bypassed: 100
      emergency-new: 5
      emergency-established: 100
      emergency-closed: 10
      emergency-bypassed: 50
    udp:
      new: 30
      established: 300
      bypassed: 100
      emergency-new: 10
      emergency-established: 100
      emergency-bypassed: 50
    icmp:
      new: 30
      established: 300
      bypassed: 100
      emergency-new: 10
      emergency-established: 100
      emergency-bypassed: 50
  
  # Stream engine settings. Here the TCP stream tracking and reassembly
  # engine is configured.
  #
  # stream:
  #   memcap: 32mb                # Can be specified in kb, mb, gb.  Just a
  #                               # number indicates it's in bytes.
  #   checksum-validation: yes    # To validate the checksum of received
  #                               # packet. If csum validation is specified as
  #                               # "yes", then packet with invalid csum will not
  #                               # be processed by the engine stream/app layer.
  #                               # Warning: locally generated traffic can be
  #                               # generated without checksum due to hardware offload
  #                               # of checksum. You can control the handling of checksum
  #                               # on a per-interface basis via the 'checksum-checks'
  #                               # option
  #   prealloc-sessions: 2k       # 2k sessions prealloc'd per stream thread
  #   midstream: false            # don't allow midstream session pickups
  #   async-oneside: false        # don't enable async stream handling
  #   inline: no                  # stream inline mode
  #   drop-invalid: yes           # in inline mode, drop packets that are invalid with regards to streaming engine
  #   max-synack-queued: 5        # Max different SYN/ACKs to queue
  #   bypass: no                  # Bypass packets when stream.depth is reached
  #
  #   reassembly:
  #     memcap: 64mb              # Can be specified in kb, mb, gb.  Just a number
  #                               # indicates it's in bytes.
  #     depth: 1mb                # Can be specified in kb, mb, gb.  Just a number
  #                               # indicates it's in bytes.
  #     toserver-chunk-size: 2560 # inspect raw stream in chunks of at least
  #                               # this size.  Can be specified in kb, mb,
  #                               # gb.  Just a number indicates it's in bytes.
  #     toclient-chunk-size: 2560 # inspect raw stream in chunks of at least
  #                               # this size.  Can be specified in kb, mb,
  #                               # gb.  Just a number indicates it's in bytes.
  #     randomize-chunk-size: yes # Take a random value for chunk size around the specified value.
  #                               # This lower the risk of some evasion technics but could lead
  #                               # detection change between runs. It is set to 'yes' by default.
  #     randomize-chunk-range: 10 # If randomize-chunk-size is active, the value of chunk-size is
  #                               # a random value between (1 - randomize-chunk-range/100)*toserver-chunk-size
  #                               # and (1 + randomize-chunk-range/100)*toserver-chunk-size and the same
  #                               # calculation for toclient-chunk-size.
  #                               # Default value of randomize-chunk-range is 10.
  #
  #     raw: yes                  # 'Raw' reassembly enabled or disabled.
  #                               # raw is for content inspection by detection
  #                               # engine.
  #
  #     segment-prealloc: 2048    # number of segments preallocated per thread
  #
  #     check-overlap-different-data: true|false
  #                               # check if a segment contains different data
  #                               # than what we've already seen for that
  #                               # position in the stream.
  #                               # This is enabled automatically if inline mode
  #                               # is used or when stream-event:reassembly_overlap_different_data;
  #                               # is used in a rule.
  #
  stream:
    memcap: 64mb
    checksum-validation: yes      # reject wrong csums
    inline: auto                  # auto will use inline mode in IPS mode, yes or no set it statically
    reassembly:
      memcap: 256mb
      depth: 1mb                  # reassemble 1mb into a stream
      toserver-chunk-size: 2560
      toclient-chunk-size: 2560
      randomize-chunk-size: yes
      #randomize-chunk-range: 10
      #raw: yes
      #segment-prealloc: 2048
      #check-overlap-different-data: true
  
  # Host table:
  #
  # Host table is used by tagging and per host thresholding subsystems.
  #
  host:
    hash-size: 4096
    prealloc: 1000
    memcap: 32mb
  
  # IP Pair table:
  #
  # Used by xbits 'ippair' tracking.
  #
  #ippair:
  #  hash-size: 4096
  #  prealloc: 1000
  #  memcap: 32mb
  
  # Decoder settings
  
  decoder:
    # Teredo decoder is known to not be completely accurate
    # it will sometimes detect non-teredo as teredo.
    teredo:
      enabled: true
  
  
  ##
  ## Performance tuning and profiling
  ##
  
  # The detection engine builds internal groups of signatures. The engine
  # allow us to specify the profile to use for them, to manage memory on an
  # efficient way keeping a good performance. For the profile keyword you
  # can use the words "low", "medium", "high" or "custom". If you use custom
  # make sure to define the values at "- custom-values" as your convenience.
  # Usually you would prefer medium/high/low.
  #
  # "sgh mpm-context", indicates how the staging should allot mpm contexts for
  # the signature groups.  "single" indicates the use of a single context for
  # all the signature group heads.  "full" indicates a mpm-context for each
  # group head.  "auto" lets the engine decide the distribution of contexts
  # based on the information the engine gathers on the patterns from each
  # group head.
  #
  # The option inspection-recursion-limit is used to limit the recursive calls
  # in the content inspection code.  For certain payload-sig combinations, we
  # might end up taking too much time in the content inspection code.
  # If the argument specified is 0, the engine uses an internally defined
  # default limit.  On not specifying a value, we use no limits on the recursion.
  detect:
    profile: medium
    custom-values:
      toclient-groups: 3
      toserver-groups: 25
    sgh-mpm-context: auto
    inspection-recursion-limit: 3000
    # If set to yes, the loading of signatures will be made after the capture
    # is started. This will limit the downtime in IPS mode.
    #delayed-detect: yes
  
    prefilter:
      # default prefiltering setting. "mpm" only creates MPM/fast_pattern
      # engines. "auto" also sets up prefilter engines for other keywords.
      # Use --list-keywords=all to see which keywords support prefiltering.
      default: mpm
  
    # the grouping values above control how many groups are created per
    # direction. Port whitelisting forces that port to get it's own group.
    # Very common ports will benefit, as well as ports with many expensive
    # rules.
    grouping:
      #tcp-whitelist: 53, 80, 139, 443, 445, 1433, 3306, 3389, 6666, 6667, 8080
      #udp-whitelist: 53, 135, 5060
  
    profiling:
      # Log the rules that made it past the prefilter stage, per packet
      # default is off. The threshold setting determines how many rules
      # must have made it past pre-filter for that rule to trigger the
      # logging.
      #inspect-logging-threshold: 200
      grouping:
        dump-to-disk: false
        include-rules: false      # very verbose
        include-mpm-stats: false
  
  # Select the multi pattern algorithm you want to run for scan/search the
  # in the engine.
  #
  # The supported algorithms are:
  # "ac"      - Aho-Corasick, default implementation
  # "ac-bs"   - Aho-Corasick, reduced memory implementation
  # "ac-ks"   - Aho-Corasick, "Ken Steele" variant
  # "hs"      - Hyperscan, available when built with Hyperscan support
  #
  # The default mpm-algo value of "auto" will use "hs" if Hyperscan is
  # available, "ac" otherwise.
  #
  # The mpm you choose also decides the distribution of mpm contexts for
  # signature groups, specified by the conf - "detect.sgh-mpm-context".
  # Selecting "ac" as the mpm would require "detect.sgh-mpm-context"
  # to be set to "single", because of ac's memory requirements, unless the
  # ruleset is small enough to fit in one's memory, in which case one can
  # use "full" with "ac".  Rest of the mpms can be run in "full" mode.
  
  mpm-algo: auto
  
  # Select the matching algorithm you want to use for single-pattern searches.
  #
  # Supported algorithms are "bm" (Boyer-Moore) and "hs" (Hyperscan, only
  # available if Suricata has been built with Hyperscan support).
  #
  # The default of "auto" will use "hs" if available, otherwise "bm".
  
  spm-algo: auto
  
  # Suricata is multi-threaded. Here the threading can be influenced.
  threading:
    set-cpu-affinity: no
    # Tune cpu affinity of threads. Each family of threads can be bound
    # on specific CPUs.
    #
    # These 2 apply to the all runmodes:
    # management-cpu-set is used for flow timeout handling, counters
    # worker-cpu-set is used for 'worker' threads
    #
    # Additionally, for autofp these apply:
    # receive-cpu-set is used for capture threads
    # verdict-cpu-set is used for IPS verdict threads
    #
    cpu-affinity:
      - management-cpu-set:
          cpu: [ 0 ]  # include only these CPUs in affinity settings
      - receive-cpu-set:
          cpu: [ 0 ]  # include only these CPUs in affinity settings
      - worker-cpu-set:
          cpu: [ "all" ]
          mode: "exclusive"
          # Use explicitely 3 threads and don't compute number by using
          # detect-thread-ratio variable:
          # threads: 3
          prio:
            low: [ 0 ]
            medium: [ "1-2" ]
            high: [ 3 ]
            default: "medium"
      #- verdict-cpu-set:
      #    cpu: [ 0 ]
      #    prio:
      #      default: "high"
    #
    # By default Suricata creates one "detect" thread per available CPU/CPU core.
    # This setting allows controlling this behaviour. A ratio setting of 2 will
    # create 2 detect threads for each CPU/CPU core. So for a dual core CPU this
    # will result in 4 detect threads. If values below 1 are used, less threads
    # are created. So on a dual core CPU a setting of 0.5 results in 1 detect
    # thread being created. Regardless of the setting at a minimum 1 detect
    # thread will always be created.
    #
    detect-thread-ratio: 1.0
  
  # Luajit has a strange memory requirement, it's 'states' need to be in the
  # first 2G of the process' memory.
  #
  # 'luajit.states' is used to control how many states are preallocated.
  # State use: per detect script: 1 per detect thread. Per output script: 1 per
  # script.
  luajit:
    states: 128
  
  # Profiling settings. Only effective if Suricata has been built with the
  # the --enable-profiling configure flag.
  #
  profiling:
    # Run profiling for every xth packet. The default is 1, which means we
    # profile every packet. If set to 1000, one packet is profiled for every
    # 1000 received.
    #sample-rate: 1000
  
    # rule profiling
    rules:
  
      # Profiling can be disabled here, but it will still have a
      # performance impact if compiled in.
      enabled: no
      filename: rule_perf.log
      append: yes
  
      # Sort options: ticks, avgticks, checks, matches, maxticks
      # If commented out all the sort options will be used.
      #sort: avgticks
  
      # Limit the number of sids for which stats are shown at exit (per sort).
      limit: 10
  
      # output to json
      json: no
  
    # per keyword profiling
    keywords:
      enabled: no
      filename: keyword_perf.log
      append: yes
  
    prefilter:
      enabled: no
      filename: prefilter_perf.log
      append: yes
  
    # per rulegroup profiling
    rulegroups:
      enabled: no
      filename: rule_group_perf.log
      append: yes
  
    # packet profiling
    packets:
  
      # Profiling can be disabled here, but it will still have a
      # performance impact if compiled in.
      enabled: no
      filename: packet_stats.log
      append: yes
  
      # per packet csv output
      csv:
  
        # Output can be disabled here, but it will still have a
        # performance impact if compiled in.
        enabled: no
        filename: packet_stats.csv
  
    # profiling of locking. Only available when Suricata was built with
    # --enable-profiling-locks.
    locks:
      enabled: no
      filename: lock_stats.log
      append: yes
  
    pcap-log:
      enabled: no
      filename: pcaplog_stats.log
      append: yes
  
  ##
  ## Netfilter integration
  ##
  
  # When running in NFQ inline mode, it is possible to use a simulated
  # non-terminal NFQUEUE verdict.
  # This permit to do send all needed packet to Suricata via this a rule:
  #        iptables -I FORWARD -m mark ! --mark $MARK/$MASK -j NFQUEUE
  # And below, you can have your standard filtering ruleset. To activate
  # this mode, you need to set mode to 'repeat'
  # If you want packet to be sent to another queue after an ACCEPT decision
  # set mode to 'route' and set next-queue value.
  # On linux >= 3.1, you can set batchcount to a value > 1 to improve performance
  # by processing several packets before sending a verdict (worker runmode only).
  # On linux >= 3.6, you can set the fail-open option to yes to have the kernel
  # accept the packet if Suricata is not able to keep pace.
  # bypass mark and mask can be used to implement NFQ bypass. If bypass mark is
  # set then the NFQ bypass is activated. Suricata will set the bypass mark/mask
  # on packet of a flow that need to be bypassed. The Nefilter ruleset has to
  # directly accept all packets of a flow once a packet has been marked.
  nfq:
  #  mode: accept
  #  repeat-mark: 1
  #  repeat-mask: 1
  #  bypass-mark: 1
  #  bypass-mask: 1
  #  route-queue: 2
  #  batchcount: 20
  #  fail-open: yes
  
  #nflog support
  nflog:
      # netlink multicast group
      # (the same as the iptables --nflog-group param)
      # Group 0 is used by the kernel, so you can't use it
    - group: 2
      # netlink buffer size
      buffer-size: 18432
      # put default value here
    - group: default
      # set number of packet to queue inside kernel
      qthreshold: 1
      # set the delay before flushing packet in the queue inside kernel
      qtimeout: 100
      # netlink max buffer size
      max-size: 20000
  
  ##
  ## Advanced Capture Options
  ##
  
  # general settings affecting packet capture
  capture:
    # disable NIC offloading. It's restored when Suricata exits.
    # Enabled by default.
    #disable-offloading: false
    #
    # disable checksum validation. Same as setting '-k none' on the
    # commandline.
    #checksum-validation: none
  
  # Netmap support
  #
  # Netmap operates with NIC directly in driver, so you need FreeBSD which have
  # built-in netmap support or compile and install netmap module and appropriate
  # NIC driver on your Linux system.
  # To reach maximum throughput disable all receive-, segmentation-,
  # checksum- offloadings on NIC.
  # Disabling Tx checksum offloading is *required* for connecting OS endpoint
  # with NIC endpoint.
  # You can find more information at https://github.com/luigirizzo/netmap
  #
  netmap:
     # To specify OS endpoint add plus sign at the end (e.g. "eth0+")
   - interface: eth2
     # Number of receive threads. "auto" uses number of RSS queues on interface.
     #threads: auto
     # You can use the following variables to activate netmap tap or IPS mode.
     # If copy-mode is set to ips or tap, the traffic coming to the current
     # interface will be copied to the copy-iface interface. If 'tap' is set, the
     # copy is complete. If 'ips' is set, the packet matching a 'drop' action
     # will not be copied.
     # To specify the OS as the copy-iface (so the OS can route packets, or forward
     # to a service running on the same machine) add a plus sign at the end
     # (e.g. "copy-iface: eth0+"). Don't forget to set up a symmetrical eth0+ -> eth0
     # for return packets. Hardware checksumming must be *off* on the interface if
     # using an OS endpoint (e.g. 'ifconfig eth0 -rxcsum -txcsum -rxcsum6 -txcsum6' for FreeBSD
     # or 'ethtool -K eth0 tx off rx off' for Linux).
     #copy-mode: tap
     #copy-iface: eth3
     # Set to yes to disable promiscuous mode
     # disable-promisc: no
     # Choose checksum verification mode for the interface. At the moment
     # of the capture, some packets may be with an invalid checksum due to
     # offloading to the network card of the checksum computation.
     # Possible values are:
     #  - yes: checksum validation is forced
     #  - no: checksum validation is disabled
     #  - auto: Suricata uses a statistical approach to detect when
     #  checksum off-loading is used.
     # Warning: 'checksum-validation' must be set to yes to have any validation
     #checksum-checks: auto
     # BPF filter to apply to this interface. The pcap filter syntax apply here.
     #bpf-filter: port 80 or udp
   #- interface: eth3
     #threads: auto
     #copy-mode: tap
     #copy-iface: eth2
     # Put default values here
   - interface: default
  
  # PF_RING configuration. for use with native PF_RING support
  # for more info see http://www.ntop.org/products/pf_ring/
  pfring:
    - interface: eth0
      # Number of receive threads. If set to 'auto' Suricata will first try
      # to use CPU (core) count and otherwise RSS queue count.
      threads: auto
  
      # Default clusterid.  PF_RING will load balance packets based on flow.
      # All threads/processes that will participate need to have the same
      # clusterid.
      cluster-id: 99
  
      # Default PF_RING cluster type. PF_RING can load balance per flow.
      # Possible values are cluster_flow or cluster_round_robin.
      cluster-type: cluster_flow
  
      # bpf filter for this interface
      #bpf-filter: tcp
  
      # If bypass is set then the PF_RING hw bypass is activated, when supported
      # by the interface in use. Suricata will instruct the interface to bypass
      # all future packets for a flow that need to be bypassed.
      #bypass: yes
  
      # Choose checksum verification mode for the interface. At the moment
      # of the capture, some packets may be with an invalid checksum due to
      # offloading to the network card of the checksum computation.
      # Possible values are:
      #  - rxonly: only compute checksum for packets received by network card.
      #  - yes: checksum validation is forced
      #  - no: checksum validation is disabled
      #  - auto: Suricata uses a statistical approach to detect when
      #  checksum off-loading is used. (default)
      # Warning: 'checksum-validation' must be set to yes to have any validation
      #checksum-checks: auto
    # Second interface
    #- interface: eth1
    #  threads: 3
    #  cluster-id: 93
    #  cluster-type: cluster_flow
    # Put default values here
    - interface: default
      #threads: 2
  
  # For FreeBSD ipfw(8) divert(4) support.
  # Please make sure you have ipfw_load="YES" and ipdivert_load="YES"
  # in /etc/loader.conf or kldload'ing the appropriate kernel modules.
  # Additionally, you need to have an ipfw rule for the engine to see
  # the packets from ipfw.  For Example:
  #
  #   ipfw add 100 divert 8000 ip from any to any
  #
  # The 8000 above should be the same number you passed on the command
  # line, i.e. -d 8000
  #
  ipfw:
  
    # Reinject packets at the specified ipfw rule number.  This config
    # option is the ipfw rule number AT WHICH rule processing continues
    # in the ipfw processing system after the engine has finished
    # inspecting the packet for acceptance.  If no rule number is specified,
    # accepted packets are reinjected at the divert rule which they entered
    # and IPFW rule processing continues.  No check is done to verify
    # this will rule makes sense so care must be taken to avoid loops in ipfw.
    #
    ## The following example tells the engine to reinject packets
    # back into the ipfw firewall AT rule number 5500:
    #
    # ipfw-reinjection-rule-number: 5500
  
  
  napatech:
      # The Host Buffer Allowance for all streams
      # (-1 = OFF, 1 - 100 = percentage of the host buffer that can be held back)
      # This may be enabled when sharing streams with another application.
      # Otherwise, it should be turned off.
      hba: -1
  
      # use_all_streams set to "yes" will query the Napatech service for all configured
      # streams and listen on all of them. When set to "no" the streams config array
      # will be used.
      use-all-streams: yes
  
      # The streams to listen on.  This can be either:
      #   a list of individual streams (e.g. streams: [0,1,2,3])
      # or
      #   a range of streams (e.g. streams: ["0-3"])
      streams: ["0-3"]
  
      # When auto-config is enabled the streams will be created and assigned
      # automatically to the NUMA node where the thread resides.  If cpu-affinity
      # is enabled in the threading section.  Then the streams will be created
      # according to the number of worker threads specified in the worker cpu set.
      # Otherwise, the streams array is used to define the streams.
      #
      # This option cannot be used simultaneous with "use-all-streams".
      #
      auto-config: yes
  
      # Ports indicates which napatech ports are to be used in auto-config mode.
      # these are the port ID's of the ports that will be merged prior to the
      # traffic being distributed to the streams.
      #
      # This can be specified in any of the following ways:
      #
      #   a list of individual ports (e.g. ports: [0,1,2,3])
      #
      #   a range of ports (e.g. ports: [0-3])
      #
      #   "all" to indicate that all ports are to be merged together
      #   (e.g. ports: [all])
      #
      # This has no effect if auto-config is disabled.
      #
      ports: [all]
  
      # When auto-config is enabled the hashmode specifies the algorithm for
      # determining to which stream a given packet is to be delivered.
      # This can be any valid Napatech NTPL hashmode command.
      #
      # The most common hashmode commands are:  hash2tuple, hash2tuplesorted,
      # hash5tuple, hash5tuplesorted and roundrobin.
      #
      # See Napatech NTPL documentation other hashmodes and details on their use.
      #
      # This has no effect if auto-config is disabled.
      #
      hashmode: hash5tuplesorted
  
  ##
  ## Configure Suricata to load Suricata-Update managed rules.
  ##
  ## If this section is completely commented out move down to the "Advanced rule
  ## file configuration".
  ##
  
  #default-rule-path: /var/lib/suricata/rules
  #rule-files:
  # - suricata.rules
  
  ##
  ## Advanced rule file configuration.
  ##
  ## If this section is completely commented out then your configuration
  ## is setup for suricata-update as it was most likely bundled and
  ## installed with Suricata.
  ##
  
  default-rule-path: /etc/suricata/rules
  
  rule-files:
   - botcc.rules
   - botcc.portgrouped.rules
   - ciarmy.rules
   - compromised.rules
   - drop.rules
   - dshield.rules
   - emerging-activex.rules
   - emerging-adware_pup.rules
   - emerging-attack_response.rules
   - emerging-chat.rules
   - emerging-coinminer.rules
   - emerging-current_events.rules
   - emerging-dns.rules
   - emerging-dos.rules
   - emerging-exploit.rules
   - emerging-exploit_kit.rules
   - emerging-ftp.rules
   - emerging-games.rules
   - emerging-hunting.rules
   - emerging-icmp_info.rules
   - emerging-icmp.rules
   - emerging-imap.rules
   - emerging-inappropriate.rules
   - emerging-info.rules
   - emerging-ja3.rules
   - emerging-malware.rules
   - emerging-misc.rules
   - emerging-mobile_malware.rules
   - emerging-netbios.rules
   - emerging-p2p.rules
   - emerging-phishing.rules
   - emerging-policy.rules
   - emerging-pop3.rules
   - emerging-rpc.rules
   - emerging-scada.rules
   - emerging-scan.rules
   - emerging-shellcode.rules
   - emerging-smtp.rules
   - emerging-snmp.rules
   - emerging-sql.rules
   - emerging-telnet.rules
   - emerging-tftp.rules
  # - emerging-trojan.rules
   - emerging-user_agents.rules
   - emerging-voip.rules
   - emerging-web_client.rules
   - emerging-web_server.rules
   - emerging-web_specific_apps.rules
   - emerging-worm.rules
   - tor.rules
   - decoder-events.rules # available in suricata sources under rules dir
   - stream-events.rules  # available in suricata sources under rules dir
   - http-events.rules    # available in suricata sources under rules dir
   - smtp-events.rules    # available in suricata sources under rules dir
   - dns-events.rules     # available in suricata sources under rules dir
   - tls-events.rules     # available in suricata sources under rules dir
   - modbus-events.rules  # available in suricata sources under rules dir
   - app-layer-events.rules  # available in suricata sources under rules dir
   - dnp3-events.rules       # available in suricata sources under rules dir
   - ntp-events.rules       # available in suricata sources under rules dir
   - ipsec-events.rules       # available in suricata sources under rules dir
   - kerberos-events.rules       # available in suricata sources under rules dir
  
  ##
  ## Auxiliary configuration files.
  ##
  
  classification-file: /etc/suricata/rules/classification.config
  reference-config-file: /etc/suricata/reference.config
  # threshold-file: /etc/suricata/threshold.config
  
  ##
  ## Include other configs
  ##
  
  # Includes.  Files included here will be handled as if they were
  # inlined in this configuration file.
  #include: include1.yaml
  #include: include2.yaml