Why do two KEV statistics posts disagree about the same year?
Two KEV counts for one year can both be right: one buckets by dateAdded, the other by CVE ID year. Here is how to tell which one you are reading.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Two KEV counts for one year can both be right: one buckets by dateAdded, the other by CVE ID year. Here is how to tell which one you are reading.
Every KEV entry in the 2026.10.16 feed had notes, each with an NVD link. Here is what else the notes point to and how to use them as primary sources.
Plain answers to ten common questions about tokens, plans, limits, caching and batch, each tied to provider documentation and linked to a deeper guide.
RASP sits in the request path of live apps, so ownership affects uptime. A practical split of duties across security, platform and application teams.
A limitations paragraph says what your data cannot show. Here are the specific caveats for KEV, EPSS and OSV, with wording you can adapt to your own post.
No. In KEV, EPSS and OSV data an Unknown or missing value means not recorded. Treat it as its own category or your statistics will understate risk.
When security news breaks, several people check the same thing and miss others. A simple claim, split and merge routine to avoid duplicate work.
A 60 second explanation of supply chain attacks for a boss or board, plus five questions leaders should ask and a one page brief you can adapt.
Compare self-hosted and hosted AI by listing every cost line: hardware, utilization, people, security work and the hosted meters. A neutral worksheet.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.