Cross-source coverage
T1499 / ATT&CK
Endpoint Denial of Service
75 rules · 71 families across 7 sources.
Showing deprecated rules · back to the default
From MITRE ATT&CK 19.2
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users. Endpoint DoS can be performed by exhausting the system resources those services are hosted on or exploiting the system to cause a persistent crash condition. Example services include websites, email services, DNS, and web-based applications. Adversaries have been observed conducting DoS attacks for political purposes and to support other malicious activities, including distraction, hacktivism, and extortion.
An Endpoint DoS denies the availability of a service without saturating the network used to provide access to the service. Adversaries can target various layers of the application stack that is hosted on the system used to provide the service. These layers include the Operating Systems (OS), server applications such as web servers, DNS servers, databases, and the (typically web-based) applications that sit on top of them. Attacking each layer requires different techniques that take advantage of bottlenecks that are unique to the respective components. A DoS attack may 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 DoS attacks against endpoint resources, 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.
Botnets are commonly used to conduct DDoS attacks against networks and services. Large botnets can generate a significant amount of traffic from systems spread across the global internet. Adversaries may have the resources to build out and control their own botnet infrastructure or may rent time on an existing botnet to conduct an attack. In some of the worst cases for DDoS, so many systems are used to generate requests that each one only needs to send out a small amount of traffic to produce enough volume to exhaust the target's resources. In such circumstances, distinguishing DDoS traffic from legitimate clients becomes exceedingly difficult. Botnets have been used in some of the most high-profile DDoS attacks, such as the 2012 series of incidents that targeted major US banks.
In cases where traffic manipulation is used, there may be points in the global network (such as high traffic gateway routers) where packets can be altered and cause legitimate clients to execute code that directs network packets toward a target in high volume. This type of capability was previously used for the purposes of web censorship where client HTTP traffic was modified to include a reference to JavaScript that generated the DDoS code to overwhelm target web servers.
For attacks attempting to saturate the providing network, see Network Denial of Service.
- Tactics
- Impact
- Platforms
- Windows · Linux · macOS · Containers · IaaS
- Telemetry
-
WinEventLog:SysmonWinEventLog:ApplicationWinEventLog:Systemauditd:SYSCALLlinux:syslogjournald:systemdmacos:unifiedlogAWS:CloudWatchAWS:CloudTrailVPCFlowLogs:Allkubernetes:eventsdocker:events
How MITRE says to detect it DET0208
Endpoint Resource Saturation and Crash Pattern Detection Across Platforms
Windows Analytic 0584
Excessive resource exhaustion or service crash induced by processes launched by users or scripts that rapidly consume CPU/memory or attempt malformed service interactions.
WinEventLog:SysmonEventCode=1WinEventLog:ApplicationService crash, unhandled exception, or application hang warnings for critical services (e.g., IIS, DNS, SQL Server)WinEventLog:SystemSystem shutdowns due to bugcheck (Event ID 1001) or watchdog timer expirations
Linux Analytic 0585
Malicious script or binary causes repeated kernel panics, OOM kills, or systemd service restarts targeting services like nginx, httpd, sshd.
auditd:SYSCALLexecvelinux:syslogOut of memory killer invoked or kernel panic entriesjournald:systemdRepeated service restart attempts or unit failures
macOS Analytic 0586
Adversary launches high-entropy process or malformed app bundle causing repeated application crashes and system slowdowns.
macos:unifiedlogRepeated process crashes logged by CrashReporter or system instability logs in com.apple.consolemacos:unifiedlogSpike in CPU or memory use from non-user-initiated processes
IaaS Analytic 0587
Instance enters degraded/unhealthy state due to abnormal process load or memory exhaustion, often caused by automation or script-based attacks.
AWS:CloudWatchStatusCheckFailed or StatusCheckFailed_System for burstable instances (t2/t3)AWS:CloudTrailStartInstancesVPCFlowLogs:AllHigh volume internal traffic with low entropy indicating looped or malicious DoS script
Containers Analytic 0588
Container orchestrator logs show crashlooping pods, repeated resource exhaustion, or malicious binaries with infinite loops consuming systemd/cgroup limits.
kubernetes:eventsCrashLoopBackOff, OOMKilled, container restart count exceeds thresholddocker:eventsContainer exited with non-zero code repeatedly in short period
Sub-techniques with coverage
Counted in the 75 above — a rule tagged a sub-technique covers this technique too.
Wazuh Core Ruleset
48 rules · 44 families| Detection | Severity | Format |
|---|---|---|
| browsers. Possible attack. | Critical | Wazuh XML |
| Non standard syslog message (size too large). | Critical | Wazuh XML |
| Possible buffer overflow attempt. | Critical | Wazuh XML |
| Apache: Multiple Invalid URI requests from same source. 2 variants | High | Wazuh XML |
| Apache: Multiple Invalid URI requests from same source. 2 variants | High | Wazuh XML |
| Availability of the system is in risk. | High | Wazuh XML |
| black-listed IP address (blocked). | High | Wazuh XML |
| Buffer overflow attempt (probably on yppasswd). | High | Wazuh XML |
| cimserver: Compaq Insight Manager stopped. | High | Wazuh XML |
| F5 BigIP: Critical error for TMM. It restarts. Attempts to reconnect will be made after that. | High | Wazuh XML |
+ 38 more from Wazuh Core Ruleset → showing the 10 highest-severity
SigmaHQ/sigma
7 rules| Detection | Severity | Format |
|---|---|---|
| Audit CVE Event | Critical | Sigma |
| Apache Segmentation Fault | High | Sigma |
| CVE-2024-49113 Exploitation Attempt - LDAP Nightmare | High | Sigma |
| LSASS Crash Via Netlogon Stack Buffer Overflow - CVE-2026-41089 | High | Sigma |
| Nginx Core Dump | High | Sigma |
| NTFS Vulnerability Exploitation | High | Sigma |
| Potential Abuse of Linux Magic System Request Key | Medium | Sigma |
elastic/detection-rules
6 rules| Detection | Severity | Format |
|---|---|---|
| Abnormally Large DNS Response | Medium | Elastic TOML |
| Possible Okta DoS Attack | Medium | Elastic TOML |
| Decline in host-based traffic | Low | Elastic TOML |
| Repeated Stalled TLS Handshakes via ALPN acme-tls/1 Extension | Low | Elastic TOML |
| Spike in Firewall Denies | Low | Elastic TOML |
| Spike in host-based traffic | Low | Elastic TOML |
panther-labs/panther-analysis
5 rules| Detection | Severity | Format |
|---|---|---|
| Slack Denial of Service via Session Invalidation | Critical | Panther Python |
| Azure Virtual Network Deleted | High | Panther Python |
| AWS RDS Cluster Failover Initiated | Medium | Panther Python |
| AWS RDS Instance or Cluster Rebooted | Medium | Panther Python |
| AWS WAF Managed Anti-DDoS Passthrough Rule | Low | Panther Python |
Azure/Azure-Sentinel
4 rules| Detection | Severity | Format |
|---|---|---|
| Missing Domain Controller Heartbeat | High | KQL |
| AI Agents - Missing Tools in Instructions | Undefined | KQL |
| AI Agents - Published Agents without Instructions | Undefined | KQL |
| AI Agents - Published Agents with Short Instructions | Undefined | KQL |
splunk/security_content
4 rules| Detection | Severity | Format |
|---|---|---|
| Cisco Secure Firewall - Static Tundra Smart Install Abuse | Undefined | SPL |
| ESXi Bulk VM Termination | Undefined | SPL |
| Linux Magic SysRq Key Abuse | Undefined | SPL |
| Ollama Possible Memory Exhaustion Resource Abuse | Undefined | SPL |
chronicle/detection-rules
1 rule| Detection | Severity | Format |
|---|---|---|
| cve20201350_sigred__windows_dns_dos_exploit_nslookup_cli | Undefined | YARA-L |