--- /dev/null
+alert dns any any -> any any (dns.query; datarep:dns_string, >, 200, load dns_string.rep, type string; sid:1;)
--- /dev/null
+Z29vZ2xlLm;NvbQ==,1
--- /dev/null
+%YAML 1.1
+---
+
+# Logging configuration. This is not about logging IDS alerts/events, but
+# output about what Suricata is doing, like startup messages, errors, etc.
+logging:
+ default-log-level: notice
+ outputs:
+ - console:
+ enabled: yes
+ # type: json
+ - file:
+ enabled: yes
+ level: info
+ filename: suricata.json
+ type: json
+ - syslog:
+ enabled: no
+ facility: local5
+ format: "[%i] <%d> -- "
--- /dev/null
+pcap: ../../flowbit-oring/input.pcap
+
+requires:
+ features:
+ - HAVE_LIBJANSSON
+ files:
+ - src/datasets.c
+
+args:
+ - -k none
+
+exit-code: 1
+
+checks:
+ - filter:
+ min-version: 8
+ filename: suricata.json
+ count: 1
+ match:
+ log_level: "Error"
+ event_type: "engine"
+ engine.message.__find: "bad base64 encoding dns_string"
--- /dev/null
+alert dns any any -> any any (dns.query; datarep:dns_string, >, 200, load dns_string.rep, type string; sid:1;)
--- /dev/null
+Z29vZ2xlLmNvbQ==,-1
--- /dev/null
+%YAML 1.1
+---
+
+# Logging configuration. This is not about logging IDS alerts/events, but
+# output about what Suricata is doing, like startup messages, errors, etc.
+logging:
+ default-log-level: notice
+ outputs:
+ - console:
+ enabled: yes
+ # type: json
+ - file:
+ enabled: yes
+ level: info
+ filename: suricata.json
+ type: json
+ - syslog:
+ enabled: no
+ facility: local5
+ format: "[%i] <%d> -- "
--- /dev/null
+pcap: ../../flowbit-oring/input.pcap
+
+requires:
+ features:
+ - HAVE_LIBJANSSON
+ files:
+ - src/datasets.c
+
+args:
+ - -k none
+
+exit-code: 1
+
+checks:
+ - filter:
+ min-version: 8
+ filename: suricata.json
+ count: 1
+ match:
+ log_level: "Error"
+ event_type: "engine"
+ engine.message.__find: "invalid datarep value dns_string"
--- /dev/null
+Y3VybC83LjQzLjA=
+YmxhaA==,1
--- /dev/null
+%YAML 1.1
+---
+
+# Logging configuration. This is not about logging IDS alerts/events, but
+# output about what Suricata is doing, like startup messages, errors, etc.
+logging:
+ default-log-level: notice
+ outputs:
+ - console:
+ enabled: yes
+ # type: json
+ - file:
+ enabled: yes
+ level: info
+ filename: suricata.json
+ type: json
+ - syslog:
+ enabled: no
+ facility: local5
+ format: "[%i] <%d> -- "
--- /dev/null
+alert http any any -> any any (http.user_agent; dataset:isset,ua-seen,type string,load datasets.csv; sid:1;)
+alert http any any -> any any (http.user_agent; dataset:isnotset,ua-seen,type string,load datasets.csv; sid:2;)
--- /dev/null
+pcap: ../../flowbit-oring/input.pcap
+
+requires:
+ min-version: 8
+
+args:
+ - -k none
+
+exit-code: 1
+
+checks:
+ - filter:
+ min-version: 8
+ filename: suricata.json
+ count: 1
+ match:
+ log_level: "Error"
+ event_type: "engine"
+ engine.message.__find: "Cannot mix dataset and datarep values for set ua-seen"
--- /dev/null
+alert dns any any -> any any (dns.query; datarep:dns_string, >, 200, load dns_string.rep, type string; sid:1;)
--- /dev/null
+Z29vZ2xlLmNvbQ==,1
+YmxhaA==
--- /dev/null
+%YAML 1.1
+---
+
+# Logging configuration. This is not about logging IDS alerts/events, but
+# output about what Suricata is doing, like startup messages, errors, etc.
+logging:
+ default-log-level: notice
+ outputs:
+ - console:
+ enabled: yes
+ # type: json
+ - file:
+ enabled: yes
+ level: info
+ filename: suricata.json
+ type: json
+ - syslog:
+ enabled: no
+ facility: local5
+ format: "[%i] <%d> -- "
--- /dev/null
+pcap: ../../flowbit-oring/input.pcap
+
+requires:
+ min-version: 8
+
+args:
+ - -k none
+
+exit-code: 1
+
+checks:
+ - filter:
+ min-version: 8
+ filename: suricata.json
+ count: 1
+ match:
+ log_level: "Error"
+ event_type: "engine"
+ engine.message.__find: "Cannot mix dataset and datarep values for set dns_string"