Cross-source coverage

T1498 / ATT&CK

Network Denial of Service

35 rules across 7 sources.

From MITRE ATT&CK 19.2

Adversaries may perform Network Denial of Service (DoS) attacks to degrade or block the availability of targeted resources to users. Network DoS can be performed by exhausting the network bandwidth services rely on. Example resources include specific websites, email services, DNS, and web-based applications. Adversaries have been observed conducting network DoS attacks for political purposes and to support other malicious activities, including distraction, hacktivism, and extortion.

A Network DoS will occur when the bandwidth capacity of the network connection to a system is exhausted due to the volume of malicious traffic directed at the resource or the network connections and network devices the resource relies on. For example, an adversary may send 10Gbps of traffic to a server that is hosted by a network with a 1Gbps connection to the internet. This traffic can be generated by a single system or multiple systems spread across the internet, which is commonly referred to as a distributed DoS (DDoS).

To perform Network DoS attacks several aspects apply to multiple methods, including IP address spoofing, and botnets.

Adversaries may use the original IP address of an attacking system, or spoof the source IP address to make the attack traffic more difficult to trace back to the attacking system or to enable reflection. This can increase the difficulty defenders have in defending against the attack by reducing or eliminating the effectiveness of filtering by the source address on network defense devices.

For DoS attacks targeting the hosting system directly, see Endpoint Denial of Service.

Tactics
Impact
Platforms
Windows · IaaS · Linux · macOS · Containers
Telemetry
WinEventLog:Sysmonauditd:SYSCALLNSM:Flow

How MITRE says to detect it DET0518

Behavioral Detection of T1498 – Network Denial of Service Across Platforms

Windows Analytic 1434

Executable or script generating large outbound network traffic targeting remote hosts or known amplification ports

  • WinEventLog:Sysmon EventCode=3, 22
  • WinEventLog:Sysmon EventCode=1

Linux Analytic 1435

Flooding tools like hping3 or nping sending large volumes of packets across multiple ports or IPs

  • auditd:SYSCALL Execution of network stress tools or anomalies in socket/syscall behavior
  • NSM:Flow High volume flows with incomplete TCP sessions or single-packet bursts

Sub-techniques with coverage

Counted in the 35 above — a rule tagged a sub-technique covers this technique too.


Wazuh Core Ruleset

16 rules
Detection Severity Format
F5 BigIP: Detected a syncookie DOS attack. Activated hardware syncookie protection mode on the HSB. Critical Wazuh XML
F5 BigIP: Ongoing DDos attack. Critical Wazuh XML
F5 BigIP: Platform entered software SYN cookie protection mode. The system has detected a SYN flood attack. Critical Wazuh XML
F5 BigIP: Created/Updated (AFM) BDoS dynamic signature by the AFM bdosd daemon during an attack. High Wazuh XML
F5 BigIP: Number of allowed new connections per second for pool member has been exceeded. This is due to a normal spike in traffic or an attack. High Wazuh XML
F5 BigIP: Syncookie counter exceeded vip threshold. This is due to a normal spike in traffic or an attack. High Wazuh XML
F5 BigIP: Too many SIP media sessions have been established for the current configuration. High Wazuh XML
High amount of POST requests in a small period of time (likely bot). High Wazuh XML
MS-DHCP: Scope Full. High Wazuh XML
Multiple web server 503 error code (Service unavailable). High Wazuh XML

+ 6 more from Wazuh Core Ruleset → showing the 10 highest-severity

splunk/security_content

7 rules
Detection Severity Format
Detect ARP Poisoning Undefined SPL
Detect IPv6 Network Infrastructure Threats Undefined SPL
Detect Port Security Violation Undefined SPL
Detect Rogue DHCP Server Undefined SPL
Detect Traffic Mirroring Undefined SPL
Large Volume of DNS ANY Queries Undefined SPL
Ollama Excessive API Requests Undefined SPL

elastic/detection-rules

6 rules
Detection Severity Format
Nping Process Activity Medium Elastic TOML
Possible Okta DoS Attack Medium Elastic TOML
Potential DHCP Starvation via High Client MAC Cardinality Medium Elastic TOML
Spike in Firewall Denies Low Elastic TOML
Spike in host-based traffic Low Elastic TOML
Spike in Network Traffic Low Elastic TOML

SigmaHQ/sigma

3 rules
Detection Severity Format
OpenCanary - NTP Monlist Request High Sigma
Potential BlackByte Ransomware Activity High Sigma
Deployment Deleted From Kubernetes Cluster Low Sigma

Emerging Threats Open

1 rule
Detection Severity Format
ET EXPLOIT Microsoft LDAP Referral Response Inbound (CVE-2024-49113) High Suricata

chronicle/detection-rules

1 rule
Detection Severity Format
aws_guardduty_denial_of_service_activity_detected High YARA-L

panther-labs/panther-analysis

1 rule
Detection Severity Format
Okta Rate Limits Low Panther Python

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.