Endpoint Denial of Service: Application or System Exploitation T1499.004

Tactic: Impact

Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users. Some systems may automatically restart critical applications and services when crashes occur, but they can likely be re-exploited to cause a persistent denial of service (DoS) condition.

Events covered

1 catalog event is tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 4 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 (7 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.

FieldRulesHowSample values
DestinationPort1eq 153
DestinationPortName1eq 1dns
Provider_Name1eq 1Audit-CVE, Microsoft-Windows-Audit-CVE
data_stream.dataset1in 1network_traffic.dns, zeek.dns
destination.bytes1ge 165000
event.category1in 1network, network_traffic
event.type1in 1allowed, end, protocol

Top indicator values (13 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.

FieldKindValueRules (here)Corpus reach
DestinationPorteq
53
1
DestinationPortNameeq
dns
15
Provider_Nameeq
Audit-CVE
1
Provider_Nameeq
Microsoft-Windows-Audit-CVE
12
data_stream.datasetin
network_traffic.dns
1
data_stream.datasetin
zeek.dns
1
destination.bytesge
65000
1
event.categoryin
network
115
event.categoryin
network_traffic
115
event.typein
allowed
1
event.typein
end
1
event.typein
protocol
1
event.typein
start
142

Exclusions (3 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.

FieldKindValueRules excluding
EventTypein
flow_terminated
1
EventTypein
network_flow
1
event.durationgt
60000000000
1

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.

Platform (all)
Domain (all)

Sigma 3 rules

Elastic 1 rule