defend-social-engineeringlisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Social Engineering - 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.
## TL;DR for defenders
Social engineering attacks the human process, so most of the attack happens off your logs and the residue is an administrative action taken by a tricked insider. The three highest-value moments to watch in a Microsoft 365 estate are: a help-desk-initiated **password reset or MFA re-registration** in Entra ID **AuditLogs**, immediately followed by a sign-in from new infrastructure in **SigninLogs**; a **remote-support tool** (Quick Assist, AnyDesk, TeamViewer, ScreenConnect) launching on an endpoint shortly after an inbound phone call, visible in **EDR/Sysmon process creation**; and a **New-InboxRule** or a payment-detail change request that lands after an out-of-band pretext. Pair this telemetry with two process controls that no detection can substitute for: verify the caller before the help desk resets anything, and verify every bank-detail change through a second channel. None of these signals is a verdict alone; the tell is the sequence of a human a