Elektrine lite

← Feed

@jgamblin@infosec.exchange

2026-08-24 20:53 UTC

"Do we have detection for this CVE?" is normally the first question after a CVE lands on CISA's KEV list. Six times in ten, nothing public can even tell you. I checked the 554 KEV CVEs published in the last three years against Emerging Threats Open, SigmaHQ, and Elastic detection rules, counting a hit if a rule file cites the CVE ID. 329 have none. None of Apple's 31. None of Google's 24, every one of those a Chromium bug. Microsoft: 20 of 95. The split tracks how a bug is reached, not how well it is defended. Network-reachable bugs get network signatures, and a signature carries the CVE number: Apache 9 for 9, then SolarWinds, Ivanti, and Fortinet all above 70%. Endpoint rules match attacker techniques instead, so a browser or kernel bug almost never carries its CVE, even when the EDR catches the attack. The CVE is the identifier the due date arrives in, the identifier the auditor asks for, and the identifier your dashboard tracks. For 60% of these CVEs, there are no detection rules to track against.

Replies (0)

No replies.