T1499

Endpoint Denial of Service

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 system resources (CPU, memory, disk, network connections) or exploiting the system to cause a persistent crash condition. Unlike network-saturating DDoS, Endpoint DoS targets the application stack layers hosted on the victim system — including OS, web servers, DNS, databases, and web applications. Attackers may use IP spoofing, botnets, or direct tools such as hping3, stress-ng, Apache Bench, and custom scripts to generate floods. Observed threat actors include Sandworm Team (disrupting Georgian government websites) and ZxShell malware (SYN flood capability). This detection covers the execution of known DoS tools, abnormal network connection volume from single processes, and resource exhaustion indicators.

Microsoft Sentinel / Defender
kusto
let KnownDoSTools = dynamic([
  "hping3", "hping", "stress-ng", "stress", "memtester",
  "ab.exe", "ab", "siege", "wrk", "wrk2", "slowloris",
  "loic", "hoic", "goldeneye", "hulk", "pyloris",
  "torsocks", "rudy", "xerxes", "torshammer",
  "mz", "ncrack", "thc-ssl-dos"
]);
let DoSCommandPatterns = dynamic([
  "--flood", "--syn", "-S --flood", "--icmp --flood",
  "stress --cpu", "stress --vm", "stress --io", "stress-ng --cpu",
  "stress-ng --vm", "stress-ng --sock", "--workers",
  ":(){ :|:", "fork bomb",
  "-c 10000", "-n 100000", "--concurrency 5000"
]);
let HighConnectionThreshold = 500;
// Detection 1: Known DoS tool execution
let DoSToolExecution =
DeviceProcessEvents
| where Timestamp > ago(1h)
| where FileName has_any (KnownDoSTools)
   or ProcessCommandLine has_any (DoSCommandPatterns)
| extend DetectionType = "KnownDoSTool"
| extend RiskIndicator = strcat(FileName, " | ", ProcessCommandLine);
// Detection 2: Abnormal outbound connection volume from a single process (potential flood)
let NetworkFlood =
DeviceNetworkEvents
| where Timestamp > ago(10m)
| where ActionType in ("ConnectionSuccess", "ConnectionRequest", "ConnectionFailed")
| summarize
    ConnectionCount = count(),
    UniqueDestIPs = dcount(RemoteIP),
    UniqueDestPorts = dcount(RemotePort),
    Protocols = make_set(Protocol),
    EarliestConn = min(Timestamp),
    LatestConn = max(Timestamp)
  by DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountName
| where ConnectionCount > HighConnectionThreshold
| extend DetectionType = "NetworkFlood"
| extend RiskIndicator = strcat("ConnectionCount=", ConnectionCount, " UniqueIPs=", UniqueDestIPs);
// Detection 3: Rapid fork / process spawning (potential fork bomb or process exhaustion)
let ProcessExhaustion =
DeviceProcessEvents
| where Timestamp > ago(5m)
| summarize
    ProcessCount = count(),
    UniqueExecutables = dcount(FileName),
    ParentProcesses = make_set(InitiatingProcessFileName, 5)
  by DeviceName, InitiatingProcessFileName, InitiatingProcessAccountName
| where ProcessCount > 200 and UniqueExecutables < 3
| extend DetectionType = "ProcessSpawnExhaustion"
| extend RiskIndicator = strcat("ProcessCount=", ProcessCount, " UniqueExe=", UniqueExecutables);
// Union all detections
DoSToolExecution
| project Timestamp, DeviceName, AccountName=InitiatingProcessAccountName,
          DetectionType, FileName, ProcessCommandLine, InitiatingProcessFileName,
          InitiatingProcessCommandLine, RiskIndicator
| union (
    NetworkFlood
    | project
        Timestamp=EarliestConn, DeviceName,
        AccountName=InitiatingProcessAccountName,
        DetectionType,
        FileName=InitiatingProcessFileName,
        ProcessCommandLine=InitiatingProcessCommandLine,
        InitiatingProcessFileName="",
        InitiatingProcessCommandLine="",
        RiskIndicator
)
| union (
    ProcessExhaustion
    | project
        Timestamp=now(), DeviceName,
        AccountName=InitiatingProcessAccountName,
        DetectionType,
        FileName=InitiatingProcessFileName,
        ProcessCommandLine="",
        InitiatingProcessFileName="",
        InitiatingProcessCommandLine="",
        RiskIndicator
)
| sort by Timestamp desc
high severity medium confidence

Data Sources

Process: Process Creation Network Traffic: Network Connection Creation Microsoft Defender for Endpoint

Required Tables

DeviceProcessEvents DeviceNetworkEvents

False Positives

  • Performance testing teams running Apache Bench (ab), wrk, or siege against internal load balancers or staging environments during authorized load tests
  • Site reliability engineers running stress-ng or stress on Linux servers to validate autoscaling or hardware under controlled conditions
  • Security teams using hping3 for legitimate network diagnostic or firewall rule testing in authorized environments
  • High-throughput legitimate services (CDN proxies, load balancers, streaming servers) that maintain large persistent connection pools
  • Deployment automation or CI/CD pipeline jobs that spawn many short-lived processes in rapid succession during build or test phases

Unlock Pro Content

Get the full detection package for T1499 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections