Loss of Productivity and Revenue T0828

ICS Tactic: Impact

Authoring guide

Patterns shared across the 2 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
Anomalies1ne 10
CurrentAccountNum1ne 1OldAccountNum
DeletedFlowCount1ge 110
EventOriginalType1eq 1DeleteFlow
LogType1eq 1Update
TableName1eq 1BankAccountTable
TimeGenerated1ge 1startTime

Top indicator values (7 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
Anomaliesne
0
1
CurrentAccountNumne
OldAccountNum
12
DeletedFlowCountge
10
1
EventOriginalTypeeq
DeleteFlow
1
LogTypeeq
Update
13
TableNameeq
BankAccountTable
12
TimeGeneratedge
startTime
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 2 rules