Map your assets to the KEV. Practical howto: export what you actually run, cross-reference it against CISA's Known Exploited Vulnerabilities CSV or JSON feeds, then apply BOD 26-04-style tiers with internet-facing systems first.
Quin Halberg · Saturday 12 September 2026
Step by step
- Build an inventory
Pull installed software from endpoint management, MDM, scanners, SBOMs and network device inventories, and normalise vendor and product names so they can match KEV rows.
- Fetch the KEV feed
Download the CSV or JSON feed from cisa.gov/known-exploited-vulnerabilities-catalog, snapshot it and diff today against yesterday.
- Join inventory to KEV
Match on CVE or on vendor and product, and list asset, owner, CVE, internet-facing yes or no, and last seen. Keep legacy systems in the join.
- Apply risk tiers
Set due dates with BOD 26-04-style factors: exposure, KEV status, whether exploitation can be automated, and impact. Put internet-facing assets first in each tier.
- Patch and verify
Open changes with the CVE and tier due date in the title, then validate with version strings and config state after the vendor fix.
This desk has not corrected this file. Corrections.






The paper
Comments
No notes on this story yet.
Sign in to comment