Skip to content

Technical white paper

BreachSpider technical white paper, second edition, 8 November 2026.

How the engine decides, where its evidence comes from, how the product is built, how tenants are kept apart, how the documents vault seals files with hybrid post-quantum signatures, what was measured, and what is still open. Every number was measured or read from the system; database counts were read on 8 November 2026.

Contents

  1. Summary
  2. Data at a glance
  3. The problem
  4. Architecture
  5. How the engine decides
  6. Evidence and sources
  7. The web app
  8. Documents vault and post-quantum seals
  9. Integrations
  10. Security model
  11. How data quality is kept
  12. Measured performance
  13. Limits and open work

Data at a glance (8 November 2026)

Measure Count
CVE records (rejected identifiers excluded) 401,879
CVEs linked to 42 industrial automation vendors 21,401 (90% with version-bounded data)
Known-exploited CVEs 1,769
Catalog products 169,612
Vendors 36,712
CVE to product links 1,595,047
Affected-version rows 3,457,347 (about 229,600 from numbering authority, government or vendor advisories)
Microsoft fix records 235,387
Products with a vendor lifecycle fact 1,957, plus 43,007 part numbers and models, from 96 vendors
Firmware currency 6 vendors, 1,329 firmware lines, 8,481 releases

The pages in this documentation explain the same material step by step: start with What BreachSpider does.