monitor-external-attack-surfacelisted
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