defensive-reportinglisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Detection and Incident Reporting - Defensive Methodology
> **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet.
## TL;DR
A report is only as strong as the evidence under it, and an attacker who has read your playbook attacks that evidence before you can write it. Two disciplines, one skill. First, the reporting discipline: every finding in an incident or detection report points to a specific log source, event ID, timestamp, and immutable artifact, so a reader can retrace it without taking your word for anything. Second, the detection discipline: watch for the anti-forensic moves that break that chain, above all **Windows Security Event ID 1102** (audit log cleared), **System Event ID 104** (an event log cleared), **4719** (audit policy changed), **1100** (event logging service shut down), and Sysmon **Event ID 2** (file creation time changed, the timestomp signal). A report that says "logs show X" without a retraceable pointer, and a log pipeline that cannot prove it was not tampered with, both fail the same test.
## What it looks like, defender view
In telemetry, evidence tampe