Loss of Availability T0826

ICS Tactic: Impact

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 (10 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
DeletedUsers2gt 210
EventOriginalType2eq 1, in 1CreateFlow, DeletePowerApp, EditFlow
AppCount1ge 125
DeletedUserName1is_not_null 1
EnvCount1ge 110
action1eq 1delete
impactedUser1is_not_null 1
object1contains 1, is_not_null 1delete, scim user
objectType1eq 1authorization
old1is_not_null 1

Top indicator values (10 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
DeletedUsersgt
10
22
AppCountge
25
1
EnvCountge
10
1
EventOriginalTypeeq
DeletePowerApp
1
EventOriginalTypein
CreateFlow
1
EventOriginalTypein
EditFlow
1
actioneq
delete
1
objectcontains
delete
1
objectcontains
scim user
1
objectTypeeq
authorization
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)

Kusto 4 rules