← ClaudeAtlas

monitor-external-attack-surfacelisted

Monitoring the internet-facing attack surface against the CISA Known Exploited Vulnerabilities (KEV) catalog, so a public advisory for a service you run becomes an alert instead of a breach (MITRE ATT&CK T1595, T1596.005, T1592, leading to T1190; MITRE D3FEND D3-AI, D3-AVE). Ships the UMBRASEC kev-watch exposure-check procedure keyed to the CISA KEV JSON feed, plus a Sigma rule for exploitation attempts in webserver, WAF, and reverse-proxy logs, with tuning, false-positive notes, and Essential Eight / ISO 27001:2022 / NIST CSF 2.0 mappings. Use when building an external attack-surface monitor, cross-referencing your stack against CISA KEV, triaging whether a new KEV CVE affects something you expose, hunting for scanning or exploitation of an internet-facing app, or asking 'what are we exposed to that is being exploited in the wild'.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# External Attack Surface - KEV Exposure Monitoring An attacker's first move against an organization is rarely an exploit; it is reconnaissance. Public search engines such as Shodan and Censys, certificate-transparency logs, DNS records, and a plain port scan tell an adversary exactly which internet-facing services you run and roughly which versions they are, long before anything is sent at them. When one of those services carries a vulnerability that is already being exploited in the wild - the kind CISA records in its Known Exploited Vulnerabilities (KEV) catalog - the gap between a public advisory and your patch is the whole attack. The Metabase case took sixteen days from KEV listing to a million-record exfiltration, and every date was public before the data moved; the failure was that nothing connected the advisory to the asset. This skill is defensive: it watches the same external surface an attacker enumerates, matches it against KEV, and detects exploitation while a window is still open. It explains reconnaissance only as far as monitoring and mitigation require, and ships no scanning or exploitation tooling. ## TL;DR for defenders Keep a live inventory of everything you expose to the internet, then run the UMBRASEC [kev-watch](https://github.com/umbrasec-labs/umbrasec.dev/tree/master/tools/kev-watch) tool daily against the CISA KEV feed, filtered to the vendors and products you actually run, so a newly exploited CVE in your stack pages you the morning it lands. Pa