Endpoint Denial of Service T1499
Tactic: Impact
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.
Events covered
11 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 38 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (55 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (108 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (4 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 9 rules
- Apache Segmentation Fault
- Audit CVE Event
- CVE-2024-49113 Exploitation Attempt - LDAP Nightmare
- LSASS Crash Via Netlogon Stack Buffer Overflow - CVE-2026-41089
- MFA attack - bombarding a user with SMS for MFA
- Nginx Core Dump
- NTFS Vulnerability Exploitation
- Potential Abuse of Linux Magic System Request Key
- Rapid creation of clients with the dynamic client registration endpoint
Elastic 5 rules
- Abnormally Large DNS Response
- Decline in host-based traffic
- Possible Okta DoS Attack
- Spike in Firewall Denies
- Spike in host-based traffic
Splunk 5 rules
- Cisco Secure Firewall - Static Tundra Smart Install Abuse
- ESXi Bulk VM Termination
- Linux Magic SysRq Key Abuse
- Ollama Possible Memory Exhaustion Resource Abuse
- Potential CVE-2024-49113 - LDAPNightmare (Windows Event Log)
Kusto 14 rules
- API - Rate limiting
- Critical Severity Detection
- Excessive Amount of Denied Connections from a Single Source
- Excessive number of failed connections from a single source (ASIM Network Session schema)
- Missing Domain Controller Heartbeat
- NGINX - Core Dump
- Snowflake - Abnormal query process time
- Tomcat - Multiple empty requests from same IP
- Vectra Account's Behaviors
- Vectra AI Detect - Detections with High Severity
- Vectra AI Detect - Suspected Compromised Account
- Vectra AI Detect - Suspected Compromised Host
- Vectra AI Detect - Suspicious Behaviors by Category
- Vectra Host's Behaviors