detect-redteam-ttpslisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Advanced Red Team TTPs - 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, the hunt, and the hardening, and points to public, maintained rule sources by URL. 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 red team engagement is not one technique, it is a chain across the ATT&CK tactics, and no single alert catches all of it. Build coverage per tactic instead: watch infrastructure and C2 at the network edge (DNS, proxy, TLS fingerprints), watch evasion and injection on the endpoint (EDR plus Sysmon image loads and process access), and watch collection and exfiltration where data is staged and leaves. The single highest-value move is to treat the engagement as a test: use the red team's own deconfliction log and purple-team debrief to find which links in the chain produced no telemetry, then close those gaps with public rules before calling the detection done. Coverage is measured end to end, not by counting alerts.
## What it looks like, defender view
Across an engagement the same shapes recur in telemetry. Infrastructure appears first as freshly categorized domains and valid-TLS hosts that your users have never visited before (Resource Deve