detect-phishinglisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Phishing - 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 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. The one exception is the consent-phishing variant, which already has a Tier 1 sibling: [detect-oauth-consent-phishing](../../auth/detect-oauth-consent-phishing/SKILL.md) ships tuned KQL for that path, and this skill defers to it instead of duplicating it.
## TL;DR for defenders
Phishing is a delivery technique, not a single artifact, so detection works best as a chain across three moments: the message arriving, the user acting on it, and the account being abused afterward. In a Microsoft 365 estate, confirm Defender for Office 365 advanced-hunting is retained and then watch **EmailEvents** and **EmailUrlInfo** for lures that passed filtering, **UrlClickEvents** for the click that turned a delivered mail into an active one, and **SigninLogs** plus the Unified Audit Log for the aftermath: a sign-in from new infrastructure followed by a **New-InboxRule** forwarding or deleting mail is the classic attacker-in-the-middle and business-email-compromise tell. Treat SPF, DKIM, and DMARC result