Detection rules for NIDS / Suricata Data sources. Every rule contains its MITRE ATT&CK mapping, an impact rating, and details on what it identifies.
This category lists 33 detection rules.
| Rule | Category | Technique | Impact (C/I/A) |
|---|---|---|---|
| ARP Spoofing Detection | Network Attack | T1557.002 - Adversary-in-the-Middle: ARP Cache Poisoning | C:3 / I:3 / A:2 |
| Baby Shark C2 Communication Pattern Detected | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:3 / I:3 / A:2 |
| Base64-Encoded DNS Query Detected | Exfiltration | T1048.003 - Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted Non-C2 Protocol | C:3 / I:2 / A:1 |
| Base64-Encoded User Agent String Detected | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:2 / I:2 / A:1 |
| Cobalt Strike DNS Beacon Pattern Detected | Command and Control | T1071.004 - Application Layer Protocol: DNS | C:3 / I:3 / A:2 |
| Cobalt Strike Malleable C2 Profile Detected | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:3 / I:3 / A:2 |
| Command and Control Traffic Detection | Command and Control | T1095 - Non-Application Layer Protocol | C:3 / I:3 / A:2 |
| Covert Channel Detection | Exfiltration | Covert Channel Communication | C:3 / I:2 / A:1 |
| Cryptocurrency Mining Pool DNS Lookup Detected | Resource Hijacking | T1496 - Resource Hijacking | C:1 / I:1 / A:3 |
| DDoS Attack Patterns | Impact | T1498 - Network Denial of Service | C:1 / I:2 / A:3 |
| DNS Query to Out-of-Band Interaction Domain | Initial Access | T1190 - Exploit Public-Facing Application | C:3 / I:2 / A:1 |
| DNS TXT Record Contains Execution Strings | Command and Control | T1071.004 - Application Layer Protocol: DNS | C:3 / I:3 / A:2 |
| DNS Tunneling Detection | Command and Control | T1071.004 - Application Layer Protocol: DNS | C:2 / I:2 / A:1 |
| Data Exfiltration Pattern Detection | Exfiltration | T1048 - Exfiltration Over Alternative Protocol | C:3 / I:1 / A:1 |
| Exploit Attempt Detection | Lateral Movement | T1210 - Exploitation of Remote Services | C:3 / I:3 / A:2 |
| Exploit Framework User Agent Detected in HTTP Traffic | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:3 / I:3 / A:2 |
| Hack Tool User Agent Detected in HTTP Traffic | Reconnaissance | T1595.002 - Active Scanning: Vulnerability Scanning | C:2 / I:2 / A:1 |
| ICMP Tunneling Detection via Suricata | Command and Control | T1572 - Protocol Tunneling | C:3 / I:2 / A:2 |
| IPFS-Based Credential Harvesting Page Access | Credential Access | T1056 - Input Capture | C:3 / I:2 / A:0 |
| JA3 Fingerprint Threat Intelligence Match | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:3 / I:2 / A:1 |
| Known Malware User Agent String Detected | Command and Control | T1071.001 - Application Layer Protocol: Web Protocols | C:3 / I:3 / A:2 |
| Lateral Movement Indicators | Lateral Movement | T1021 - Remote Services | C:3 / I:3 / A:2 |
| Malicious File Download Detection | Execution | T1105 - Ingress Tool Transfer | C:3 / I:3 / A:2 |
| Malware Callback Detection | Command and Control | T1071 - Application Layer Protocol | C:3 / I:3 / A:2 |
| NKN Blockchain C2 Communication Detected | Command and Control | T1071 - Application Layer Protocol | C:3 / I:3 / A:2 |
| Port Scan Detection | Discovery | T1046 - Network Service Scanning | C:2 / I:1 / A:1 |
| PwnDrop File Hosting Server Access Detected | Command and Control | T1102 - Web Service | C:2 / I:3 / A:1 |
| Rclone Data Exfiltration Tool Detected | Exfiltration | T1567.002 - Exfiltration Over Web Service: Exfiltration to Cloud Storage | C:3 / I:2 / A:1 |
| SSH Brute Force and Tunneling Detection | Lateral Movement | T1021.004 - Remote Services: SSH | C:3 / I:2 / A:2 |
| TLS Certificate Anomaly Detection | Defense Evasion | T1573 - Encrypted Channel | C:3 / I:2 / A:1 |
| Threat Intelligence IOC Match | Command and Control | Command and Control | C:3 / I:2 / A:2 |
| Tor Proxy/Gateway DNS Lookup Detected | Command and Control | T1090.003 - Proxy: Multi-hop Proxy | C:3 / I:2 / A:1 |
| Tunneling Detection | Command and Control | T1572 - Protocol Tunneling | C:3 / I:2 / A:1 |
Rule Example
Below is an example of a rule definition for ARP Spoofing Detection (view in repository):
# Rule version v1.0.0
dataTypes:
- suricata
name: ARP Spoofing Detection
impact:
confidentiality: 3
integrity: 3
availability: 2
category: Network Attack
technique: "T1557.002 - Adversary-in-the-Middle: ARP Cache Poisoning"
adversary: origin
references:
- https://suricata.readthedocs.io/en/latest/rules/index.html
- https://attack.mitre.org/techniques/T1557/002/
description: |
Detects ARP spoofing and ARP cache poisoning attacks identified by Suricata. ARP spoofing allows attackers to intercept traffic between hosts on the same network segment, enabling man-in-the-middle attacks, credential theft, and session hijacking.
Next Steps:
1. Identify the source MAC address involved in the ARP spoofing
2. Locate the physical port and switch where the spoofing originates
3. Check if the ARP responses are claiming to be the default gateway
4. Review affected hosts for intercepted credentials or modified traffic
5. Enable Dynamic ARP Inspection (DAI) on switches if not configured
6. Investigate the device for attack tools (Ettercap, Bettercap, arpspoof)
where: |
equals("log.eventType", "alert") &&
(contains("log.alert.signature", ["ARP", "arp"]) &&
contains("log.alert.signature", ["spoof", "poison", "duplicate", "conflict", "gratuitous"])) &&
exists("origin.ip")
groupBy:
- adversary.ip
- adversary.mac
Rule Details
ARP Spoofing Detection
Identifies ARP spoofing and ARP cache poisoning attacks flagged by Suricata. Through ARP spoofing, attackers can intercept traffic among hosts on the same network segment, which facilitates man-in-the-middle attacks, credential theft, and session hijacking.
Category: Network Attack
Technique: T1557.002 - Adversary-in-the-Middle: ARP Cache Poisoning
Impact: C:3 / I:3 / A:2
Rule file: nids_arp_spoofing.yml
Reference: https://suricata.readthedocs.io/en/latest/rules/index.html
Baby Shark C2 Communication Pattern Detected
Identifies HTTP traffic that matches the Baby Shark C2 framework URL pattern. Baby Shark is a reconnaissance tool and C2 framework employed mainly by North Korean APT groups (Kimsuky/Thallium). The unique URL pattern momyshark?key= is specific to this framework and produces very few false positives.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:3 / I:3 / A:2
Rule file: baby_shark_c2.yml
Reference: https://unit42.paloaltonetworks.com/new-babyshark-malware-targets-u-s-national-security-think-tanks/
Base64-Encoded DNS Query Detected
Identifies DNS queries that carry base64-encoded data, recognized by == padding followed by a dot separator. This pattern frequently appears in DNS-based data exfiltration, in which stolen data is base64-encoded and divided across DNS query subdomains. Genuine DNS queries almost never include base64 padding characters.
Category: Exfiltration
Technique: T1048.003 - Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted Non-C2 Protocol
Impact: C:3 / I:2 / A:1
Rule file: base64_dns_queries.yml
Base64-Encoded User Agent String Detected
Identifies HTTP traffic in which the user agent string looks like a base64-encoded value. Certain malware families, notably YamaBot/Torisma linked to North Korean APT Lazarus, employ base64-encoded browser strings as user agents. This evasion method seeks to avoid detection based on user agents while remaining detectable through the base64 encoding pattern.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:2 / I:2 / A:1
Rule file: base64_encoded_user_agent.yml
Cobalt Strike DNS Beacon Pattern Detected
Identifies DNS queries that match known Cobalt Strike DNS beacon patterns. For its DNS-based C2 channel, Cobalt Strike uses specific DNS query prefixes, such as aaa.stage. for staging and post.1 for data exfiltration. These patterns are highly specific to Cobalt Strike and seldom occur in legitimate DNS traffic.
Category: Command and Control
Technique: T1071.004 - Application Layer Protocol: DNS
Impact: C:3 / I:3 / A:2
Rule file: cobalt_strike_dns_beacon.yml
Reference: https://blog.sekoia.io/hunting-and-detecting-cobalt-strike/
Cobalt Strike Malleable C2 Profile Detected
Identifies HTTP traffic patterns that match known Cobalt Strike malleable C2 profiles. Cobalt Strike operators rely on malleable C2 profiles to make their C2 traffic look like legitimate services (Amazon, OCSP, OneDrive, jQuery). This rule detects particular URI patterns, HTTP headers, and user agent combinations typical of common malleable C2 profiles.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:3 / I:3 / A:2
Rule file: cobalt_strike_malleable_c2.yml
Command and Control Traffic Detection
Identifies command and control (C2) communication patterns, such as suspicious periodic connections, non-standard ports, encrypted channels on unusual ports, DNS tunneling, and known C2 infrastructure indicators. This rule detects malicious communications between compromised systems and command and control servers using multiple techniques, including signature-based detection, protocol analysis, and behavioral indicators.
Category: Command and Control
Technique: T1095 - Non-Application Layer Protocol
Impact: C:3 / I:3 / A:2
Rule file: command_and_control_traffic.yml
Reference: https://attack.mitre.org/techniques/T1095/
Reference: https://attack.mitre.org/techniques/T1571/
Reference: https://www.snort.org/rule_docs/
Covert Channel Detection
Identifies possible covert channel communication via unusual protocols, DNS tunneling, or ICMP data exfiltration patterns. This rule detects suspicious network communications that could be used to evade security controls and exfiltrate data through traffic that appears legitimate.
Category: Exfiltration
Technique: Covert Channel Communication
Impact: C:3 / I:2 / A:1
Rule file: covert_channel_detection.yml
Reference: https://attack.mitre.org/techniques/T1048/
Reference: https://docs.suricata.io/en/latest/output/eve/eve-json-format.html
Cryptocurrency Mining Pool DNS Lookup Detected
Identifies DNS queries to recognized cryptocurrency mining pool domains. Unauthorized mining software on corporate systems signals a compromise, because attackers deploy cryptominers for profit using stolen compute resources. This reduces system performance and raises energy costs.
Category: Resource Hijacking
Technique: T1496 - Resource Hijacking
Impact: C:1 / I:1 / A:3
Rule file: dns_mining_pool_lookups.yml
Reference: https://attack.mitre.org/techniques/T1496/
DDoS Attack Patterns
Identifies multiple DDoS attack patterns, such as SYN floods, UDP floods, ICMP floods, HTTP floods, and amplification attacks, based on Suricata network intrusion detection system alerts and traffic patterns.
Category: Impact
Technique: T1498 - Network Denial of Service
Impact: C:1 / I:2 / A:3
Rule file: ddos_attack_patterns.yml
Reference: https://attack.mitre.org/techniques/T1498/
Reference: https://attack.mitre.org/techniques/T1499/
Reference: https://docs.suricata.io/en/latest/output/eve/eve-json-format.html
DNS Query to Out-of-Band Interaction Domain
Identifies DNS queries to known out-of-band (OOB) interaction testing domains associated with penetration testing tools and exploit frameworks. These domains (Burp Collaborator, interactsh, dnslog.cn, canarytokens) are used almost exclusively during active exploitation attempts, including SSRF, RCE, XXE, and Log4Shell attacks. Legitimate use is exceedingly rare outside authorized security testing.
Category: Initial Access
Technique: T1190 - Exploit Public-Facing Application
Impact: C:3 / I:2 / A:1
Rule file: dns_oob_interaction_domains.yml
Reference: https://attack.mitre.org/techniques/T1190/
Reference: https://portswigger.net/burp/documentation/collaborator
DNS TXT Record Contains Execution Strings
Identifies DNS TXT record responses that contain Windows command execution strings, such as IEX, Invoke-Expression, cmd.exe, powershell, and other execution indicators. This technique supports DNS-based C2 payload delivery, in which commands are encoded in DNS TXT records and executed by the compromised host.
Category: Command and Control
Technique: T1071.004 - Application Layer Protocol: DNS
Impact: C:3 / I:3 / A:2
Rule file: dns_txt_execution_strings.yml
DNS Tunneling Detection
Identifies possible DNS tunneling activity through abnormal DNS query patterns, such as unusually long domain names, a high frequency of DNS requests, or suspicious TXT record queries. Attackers use DNS tunneling to exfiltrate data or establish command and control channels by encoding data within DNS queries and responses.
Category: Command and Control
Technique: T1071.004 - Application Layer Protocol: DNS
Impact: C:2 / I:2 / A:1
Rule file: dns_tunneling_detection.yml
Reference: https://www.sans.org/reading-room/whitepapers/dns/detecting-dns-tunneling-34152
Data Exfiltration Pattern Detection
Identifies possible data exfiltration activities via unusual outbound traffic patterns, large data transfers, suspicious protocols, base64 encoded data, and connections to external file sharing services. This rule detects several indicators of data theft, including large uploads, connections to file sharing services, DNS tunneling, and TOR usage.
Category: Exfiltration
Technique: T1048 - Exfiltration Over Alternative Protocol
Impact: C:3 / I:1 / A:1
Rule file: data_exfiltration_patterns.yml
Reference: https://attack.mitre.org/techniques/T1048/
Reference: https://attack.mitre.org/techniques/T1041/
Reference: https://www.snort.org/rule_docs/
Exploit Attempt Detection
Identifies possible exploit attempts through suspicious payload patterns, buffer overflow indicators, shellcode execution attempts, and known vulnerability signatures in network traffic. This rule triggers on Suricata IDS alerts that signal active exploitation attempts against network services.
Category: Lateral Movement
Technique: T1210 - Exploitation of Remote Services
Impact: C:3 / I:3 / A:2
Rule file: exploit_attempt_detection.yml
Reference: https://attack.mitre.org/techniques/T1210/
Reference: https://www.snort.org/rule_docs/
Exploit Framework User Agent Detected in HTTP Traffic
Identifies HTTP traffic that contains user agent strings from known C2 frameworks and exploit tools, including Cobalt Strike, Metasploit, Empire, Havoc, Sliver, Brute Ratel, Mythic, and other offensive security frameworks. These user agents strongly indicate active command and control communication or exploitation attempts.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:3 / I:3 / A:2
Rule file: exploit_framework_user_agents.yml
Hack Tool User Agent Detected in HTTP Traffic
Identifies HTTP traffic that contains user agent strings from known offensive security and hacking tools, including vulnerability scanners, brute force tools, SQL injection tools, and web application testing tools. These tools are often used during the reconnaissance and exploitation phases of attacks.
Category: Reconnaissance
Technique: T1595.002 - Active Scanning: Vulnerability Scanning
Impact: C:2 / I:2 / A:1
Rule file: hacktool_user_agents.yml
ICMP Tunneling Detection via Suricata
Identifies possible ICMP tunneling activity through abnormal ICMP packet patterns, such as oversized ICMP packets, unusual ICMP types, high payload entropy, or abnormal ICMP codes. ICMP tunneling is a covert channel technique that attackers use to evade network security controls and establish command and control communications.
Category: Command and Control
Technique: T1572 - Protocol Tunneling
Impact: C:3 / I:2 / A:2
Rule file: icmp_tunneling_detection.yml
Reference: https://attack.mitre.org/techniques/T1572/
Reference: https://www.sans.org/reading-room/whitepapers/covert/icmp-tunneling-is-is-secure-1857
IPFS-Based Credential Harvesting Page Access
Identifies HTTP access to IPFS (InterPlanetary File System) URLs that include email parameters, a strong sign of credential harvesting phishing pages. Attackers host phishing pages on IPFS because the content is decentralized and very hard to take down. Email parameters in IPFS URLs indicate that the page is pre-populated with the victim's email for credential theft.
Category: Credential Access
Technique: T1056 - Input Capture
Impact: C:3 / I:2 / A:0
Rule file: ipfs_credential_harvesting.yml
Reference: https://attack.mitre.org/techniques/T1056/
Reference: https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/ipfs-abuse-in-phishing-campaigns/
JA3 Fingerprint Threat Intelligence Match
Identifies TLS client fingerprints (JA3 hashes) that match known malicious software, C2 frameworks, or threat intelligence feeds. JA3 fingerprinting detects distinctive TLS client behaviors independent of destination IP.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:3 / I:2 / A:1
Rule file: nids_ja3_threat_matching.yml
Reference: https://suricata.readthedocs.io/en/latest/rules/ja3-keywords.html
Known Malware User Agent String Detected
Identifies HTTP traffic that carries user agent strings linked to known malware families, such as RATs, stealers, ransomware, and other malicious software. Such user agents are either hardcoded or generated by particular malware families, making them strong indicators of compromise.
Category: Command and Control
Technique: T1071.001 - Application Layer Protocol: Web Protocols
Impact: C:3 / I:3 / A:2
Rule file: malware_user_agent_strings.yml
Lateral Movement Indicators
Identifies signs of lateral movement inside the network, such as SMB/RDP scanning, authentication attempts against multiple systems, suspicious remote access activity, and use of administrative tools. This rule detects several lateral movement techniques, including PsExec usage, WMI commands, RDP brute force attempts, SMB scanning, and connections to common administrative ports.
Category: Lateral Movement
Technique: T1021 - Remote Services
Impact: C:3 / I:3 / A:2
Rule file: lateral_movement_indicators.yml
Reference: https://attack.mitre.org/techniques/T1021/
Reference: https://attack.mitre.org/tactics/TA0008/
Reference: https://www.snort.org/rule_docs/
Malicious File Download Detection
Identifies HTTP downloads of executable files that may be malicious, as detected through Suricata file inspection. This covers PE executables, scripts, and other suspicious file types transferred from external sources.
Category: Execution
Technique: T1105 - Ingress Tool Transfer
Impact: C:3 / I:3 / A:2
Rule file: nids_malicious_file_downloads.yml
Reference: https://suricata.readthedocs.io/en/latest/rules/file-keywords.html
Reference: https://attack.mitre.org/techniques/T1105/
Malware Callback Detection
Identifies possible malware callback activity, such as beaconing behavior, known malicious domains, suspicious user agents, and communication patterns common to command and control infrastructure.
Category: Command and Control
Technique: T1071 - Application Layer Protocol
Impact: C:3 / I:3 / A:2
Rule file: malware_callbacks.yml
Reference: https://attack.mitre.org/techniques/T1071/
Reference: https://www.virustotal.com/gui/home/upload
Reference: https://www.snort.org/rule_docs/
NKN Blockchain C2 Communication Detected
Identifies DNS queries directed to NKN (New Kind of Network) blockchain seed nodes. NKN is a blockchain-based overlay network that has been used abusively by malware as a decentralized C2 channel. Using blockchain-based C2 makes takedown very difficult and gives malware communications high resilience.
Category: Command and Control
Technique: T1071 - Application Layer Protocol
Impact: C:3 / I:3 / A:2
Rule file: nkn_blockchain_c2.yml
Reference: https://attack.mitre.org/techniques/T1071/
Reference: https://research.checkpoint.com/2023/cloud-based-botnet-used-nkn-for-its-c2-communication/
Port Scan Detection
Identifies multiple port scanning techniques, such as TCP SYN scans, connect scans, UDP scans, NULL scans, FIN scans, and XMAS scans. Port scanning is a reconnaissance method that attackers use to find open ports and services on target systems, which can help identify potential attack vectors.
This rule detects port scans through multiple indicators:
Suricata alert signatures containing scan-related keywords
TCP SYN packets with short duration flows (SYN scan)
TCP packets with unusual flag combinations (NULL, FIN, XMAS scans)
Anomaly events indicating scan activity
Category: Discovery
Technique: T1046 - Network Service Scanning
Impact: C:2 / I:1 / A:1
Rule file: port_scan_detection.yml
Reference: https://attack.mitre.org/techniques/T1046/
Reference: https://docs.suricata.io/en/latest/output/eve/eve-json-format.html
PwnDrop File Hosting Server Access Detected
Identifies HTTP access to PwnDrop file hosting servers. PwnDrop is a self-hosted file hosting tool built for red teamers and attackers to serve payloads. The /pwndrop/ path in the URL is the default admin and API endpoint, and when it appears in web traffic it strongly suggests malicious file hosting or payload delivery.
Category: Command and Control
Technique: T1102 - Web Service
Impact: C:2 / I:3 / A:1
Rule file: pwndrop_file_hosting.yml
Reference: https://attack.mitre.org/techniques/T1102/
Rclone Data Exfiltration Tool Detected
Identifies HTTP traffic that contains the rclone user agent string. Rclone is a command-line program for managing files on cloud storage and is the most widely used data exfiltration tool in ransomware operations. Threat groups such as Conti, BlackMatter, LockBit, and many others use rclone to exfiltrate data before they deploy ransomware.
Category: Exfiltration
Technique: T1567.002 - Exfiltration Over Web Service: Exfiltration to Cloud Storage
Impact: C:3 / I:2 / A:1
Rule file: rclone_data_exfiltration.yml
Reference: https://research.nccgroup.com/2021/05/27/detecting-rclone-an-effective-tool-for-exfiltration/
SSH Brute Force and Tunneling Detection
Identifies SSH-based attacks, such as brute force attempts, signs of SSH tunneling, and anomalous SSH traffic patterns detected by Suricata. SSH is frequently abused for lateral movement and encrypted tunneling.
Category: Lateral Movement
Technique: T1021.004 - Remote Services: SSH
Impact: C:3 / I:2 / A:2
Rule file: nids_ssh_anomalies.yml
Reference: https://suricata.readthedocs.io/en/latest/rules/ssh-keywords.html
TLS Certificate Anomaly Detection
Identifies TLS certificate anomalies, such as self-signed certificates, expired certificates, certificate subject mismatches, and certificates from untrusted authorities. Such anomalies commonly indicate C2 infrastructure, man-in-the-middle attacks, or phishing sites.
Category: Defense Evasion
Technique: T1573 - Encrypted Channel
Impact: C:3 / I:2 / A:1
Rule file: nids_tls_certificate_anomalies.yml
Reference: https://suricata.readthedocs.io/en/latest/rules/tls-keywords.html
Reference: https://attack.mitre.org/techniques/T1573/
Threat Intelligence IOC Match
Identifies network traffic that matches known malicious indicators from threat intelligence feeds, such as malicious IPs, domains, and URLs. This rule triggers when Suricata detects traffic involving known threat actors, command and control servers, botnet infrastructure, or other malicious network indicators based on threat intelligence data.
Category: Command and Control
Technique: Command and Control
Impact: C:3 / I:2 / A:2
Rule file: threat_intelligence_iocs.yml
Reference: https://attack.mitre.org/techniques/T1071/
Reference: https://www.snort.org/faq/what-is-snort
Tor Proxy/Gateway DNS Lookup Detected
Identifies DNS lookups for known Tor proxy and gateway domains. These services let web traffic be routed through the Tor network without installing the Tor browser, and attackers commonly use them to anonymize C2 traffic or reach dark web resources from corporate networks.
Category: Command and Control
Technique: T1090.003 - Proxy: Multi-hop Proxy
Impact: C:3 / I:2 / A:1
Rule file: tor_proxy_dns_lookups.yml
Tunneling Detection
Identifies multiple tunneling techniques, such as SSH tunneling, HTTP tunneling, VPN over non-standard ports, and protocol mismatches. Attackers use tunneling to bypass network security controls and set up covert communication channels.
Category: Command and Control
Technique: T1572 - Protocol Tunneling
Impact: C:3 / I:2 / A:1
Rule file: tunneling_detection.yml
Reference: https://attack.mitre.org/techniques/T1572/
Reference: https://docs.suricata.io/en/latest/output/eve/eve-json-format.html