Deception/ Observability
D033F2 Observability

📊 Honey Log Group

Decoy CloudWatch/Azure Monitor log groups.

What it is

A log group named like a security log, with a little plausible content. Attackers delete or shorten logs to hide their tracks, often in bulk. Deleting the decoy log group or changing its retention are logged control-plane events, so log tampering touches the decoy along with real logs.

Implementation requirements

Technologies

AWSAzure

ATT&CK coverage 5

TechniqueTacticStatusConfidenceTier
T1685
Disable or Modify Tools
Defense Impairment theoretical moderate
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)
T1685.002
Disable or Modify Cloud Log
Defense Impairment theoretical moderate
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)
T1526
Cloud Service Discovery
Discovery theoretical moderate T1
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)

Moderate: discovering that a service exists does not necessarily touch a decoy resource in it.

T1654
Log Enumeration
Discovery theoretical moderate T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Reading a decoy log is logged only where read access is audited.

T1070
Indicator Removal
Stealth theoretical moderate T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Deleting a decoy log group or alarm is a logged management event.

↳ Good fit (tampering with decoy logs is a clean signal); technique evidence is industry-only.

Evidence