← ClaudeAtlas

defensive-fast-triagelisted

Fast blue-team triage checklist for a SOC analyst working an alert queue under time pressure, the defensive answer to a speed-run recon and quick-win scan (MITRE ATT&CK T1595 Active Scanning, T1595.002 Vulnerability Scanning, T1595.003 Wordlist Scanning, T1592 Gather Victim Host Information). Shows how that activity presents in web server and WAF access logs, proxy and firewall egress, Zeek conn metadata, and SIEM tables (Microsoft Sentinel W3CIISLog, AzureDiagnostics WAF, CommonSecurityLog; Splunk web access), then gives a repeatable scope-enrich-pivot-decide workflow, the reputation and enrichment sources to pull, a hunt for the scan that turned into a hit, and escalation hardening mapped to ISO 27001:2022 and NIST CSF 2.0. Use when triaging a SOC alert fast, building an alert triage runbook or playbook, deciding true positive versus false positive, working a noisy scanner or directory-brute-force alert, or standing up a blue-team fast triage checklist.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Fast Blue-Team Triage - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's triage method, the log sources and signals, the hunt, and the escalation 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 Triage is a decision discipline, not a tool. When an alert fires, the analyst's job is to decide fast and correctly: true positive, false positive, or benign, and whether to escalate. Run the same four gates every time, in order: **scope** (what fired, on which asset, at what confidence), **enrich** (reputation and context on the source and target), **pivot** (did the same actor touch anything else, and did any probe succeed), **decide** (verdict, severity, escalate or close, with notes). The highest-value habit is to always pivot from the noisy signal to the success signal: a thousand blocked scans are low severity, but one `200 OK` on `/admin` or one successful logon from the scanning source changes the whole call. Speed comes from a fixed checklist and pre-wired enrichment, not from skipping steps. ## What it looks like, defender view The offensive counterpart to this skill is a speed-run assessment: map the surface, brut