Files
DECNET/rules/ttp/R0032.yaml
anti eff3e4bce7 feat(ttp): E.3.9 BehavioralLifter (R0031-R0040)
Reads pre-shaped session aggregates from TaggerEvent.payload and emits
techniques per Appendix A behavior tables. Per-rule predicates dispatch
on match.kind (lifter:behavioral_<name>); the lifter holds its own
RuleIndex watching the same RuleStore as the engine, so disable / clip /
TTL state reaches lifter-bound rules through the same atomic-swap path.

R0032/R0036/R0037/R0040 YAMLs had over-escaped regex strings (\\
instead of \\) — fixed in place.

Factory wired so default get_tagger() returns CompositeTagger with
BehavioralLifter shipped; remaining three lifters (E.3.10-E.3.12) land
in subsequent commits.

E.2.6 contract preserved via TolerantTagger: empty payload steady-state
yields [] with zero ERROR records. Disabled / clipped / expired state
verified.
2026-05-01 20:17:59 -04:00

25 lines
585 B
YAML

rule_id: R0032
rule_version: 1
name: data_destruction
description: |
Mass destructive ops: Redis FLUSHALL, SQL DROP DATABASE, MongoDB
dropDatabase(), bulk DELETE without WHERE. Cross-event because we
want to confirm the verb landed on real data, not just a parse.
applies_to:
- session
match:
kind: lifter:behavioral_data_destruction
patterns:
- 'FLUSHALL'
- 'DROP\s+DATABASE'
- 'TRUNCATE\s+TABLE'
- 'dropDatabase\(\)'
- 'DELETE\s+/\_all'
emits:
- tactic: TA0040
technique_id: T1485
confidence: 0.95
evidence_fields:
- matched_op
- target