BreachSpiderBREACHSPIDER
Research Intel Features Docs About Trust Center Sign In Sign Up Free
Features

Version-precise OT vulnerability intelligence, wherever you work

Send a device's vendor, product and version. Get back only the vulnerabilities that apply to that exact version, the source behind each one, the action that clears them, and the vendor's own lifecycle and firmware facts. Use it as a managed service, from your own tools over the API, from your agent or assistant, inside a partner portal, or in the web app.

384,000+
CVEs
165,000+
Catalog products
1.4M+
CVE to product links
1,700+
Known-exploited CVEs, synced daily
Ways to connect
Our team

Managed service

Every engagement starts with an assessment of your OT environment. Then our team runs the program for you: assess, onboard, monitor and report. Built for operators without an in-house OT security team.

Book an assessment
Developers

REST API

Send devices or Windows hosts and get back the CVEs that affect that exact version, in fix-first order, with the evidence behind each one. A cheap check call tells you when a saved result has changed.

Read the API docs
Agents and assistants

MCP for agents and assistants

For Claude Code, Claude Desktop, Cursor and other MCP clients. A read-only server that runs locally with five tools: check devices, check what changed, get the fix plan, look up a CVE and check a Windows host.

Set up MCP
Python

Python SDK

An open SDK with typed models, automatic paging and retries that respect rate limits. Point your scripts, notebooks and pipelines at the same results the API returns.

Use the SDK
Partners

Embeddable device check

Put a device and Windows host check inside your own customer portal with one script tag, in your own colors and logo. Keys work only on the sites you register, and usage rolls up to your API allowance.

Embed the check
Web app

The BreachSpider app

Search any CVE free. On a plan, keep your inventory in environments, import spreadsheets, run reports, manage clients and train your team, all on the same matching engine.

Create a free account
What every result carries
Matching

Only what applies to the version you run

Matching and ranking are deterministic: the same device and version always give the same result. Each finding says how sure it is and why.

Explicit confidence

Each finding is confirmed for the installed version, a product-level match, or marked as needing review. Nothing uncertain is presented as confirmed.

Evidence on every finding

The affected version range and the advisory or record it came from, so a person or an agent can cite it instead of guessing.

An empty result says why

No data behind the product, too uncertain to call, or no recorded range for that version: the result names which.

Vendor version spellings

Letter suffixes and builds in brackets (1.10a, 5.0(3)) order correctly, and Yokogawa revisions match whether written R6.09.00 or 6.09.00.

384,000+ CVEs · 165,000+ products · 1.4M+ links
Prioritization

Fix first, with a reason

Results come in the order to act, grouped under the update that clears them, with known-exploited status and exploit signals alongside.

Fix-first rank

Every finding carries its rank and a plain-language reason a person can act on, with known-exploited CVEs first.

One action per group

Findings are grouped under the single update or firmware upgrade that clears them, with the vendor document behind it.

Fix plan per device

The version that clears every CVE with a published version fix, and how many it clears, so an upgrade can be planned once.

Exploit signals

Known-exploited status synced daily, EPSS probability and percentile, CVSS, and whether public exploit code is known.

Lifecycle

End of sale and end of support, from the vendor

Each device result says whether the product is past the vendor's end of sale or end of support, and links the publication that says so.

Vendor statements only

Dates and statuses come from vendor product pages, lifecycle notices, release histories and advisories, and every lifecycle fact links its source.

Never supported by default

A product reads as supported only when the vendor states a future end date or lists it as active. No notice found is never read as supported.

No known CVEs is not the same as supported

An unsupported product with no known vulnerabilities still says that future vulnerabilities will not be fixed.

Software release lines

Operating systems, databases and server software such as Debian, Red Hat Enterprise Linux, VMware ESXi and PostgreSQL, from endoflife.date, labeled as such and linked to the vendor page it cites.

18 vendors' own lifecycle publications read directly · 85+ vendors with lifecycle facts · 40,000+ part numbers and models
Firmware and software currency

How far behind the vendor's latest release

For vendors that publish their release history, each device says whether it is on the latest listed release, links the release notes, and quotes the security lines from the releases it is missing.

Current or behind

Compared within the right firmware line, hardware series and branch. When that cannot be told, the answer says why rather than guessing.

Security lines quoted

Security-relevant lines are quoted word for word from the notes of later releases, even when no CVE was ever assigned.

Software versions too

PostgreSQL, Debian, Red Hat, Oracle Java, Apache Tomcat, OpenSSL and Veeam compared with the latest release listed by endoflife.date, linking the vendor's own release notes.

Advice, not alarm

A device that is behind is told to review the release notes before planning an upgrade, and a device that is behind with no known CVEs still says it is behind.

firmware currency for 6 vendors · 1,300+ firmware lines · 8,000+ firmware releases
Windows

Windows hosts, decided per CVE

Engineering workstations, historians and HMI servers usually hold the most vulnerabilities. Send the OS build and installed updates, and every Microsoft CVE for that host is decided.

Open, patched or needs review

Each decision comes with the fixed build, the update to install and the Microsoft source it rests on. When evidence conflicts, the result says needs review.

The update that closes it

For current Windows versions, the latest cumulative update and how many open CVEs it closes, most urgent first.

No identifying data

The Windows check refuses hostnames, IP addresses and user names, so they cannot be sent by accident.

Checked independently

On 15 test hosts, a separate checker reading Microsoft's raw data with its own code found no differences across 40,000 per-CVE decisions.

206,000+ Microsoft fix records
What changed

Check, don't resubmit

Each device result carries a hash of its findings and of its status. A lightweight check call says whether anything changed since a saved result, so you only act when something new applies.

Findings changed

New and resolved CVEs, named device by device and host by host.

Status changed

A CVE newly known to be exploited, a change in vendor support, or a new firmware release, each named.

Nothing stored

The device API keeps no submitted asset data. The saved result on your side is the only record.

Isolated by default

Every customer is separated at the database level, and a dedicated node is available where data rules require it.

In the web app

Research any CVE, free

Search by CVE ID, vendor, product or keyword, filter by CVSS, EPSS, known-exploited, patch status, vendor and protocol, and read each CVE with its affected versions and sources.

Environments and import

Keep your inventory in environments. Import CSV or XLSX with assistant-suggested column mapping and name cleanup, then review findings by confidence.

CVE analysis and the assistant

The assistant (Claude, by Anthropic) writes an analysis of each CVE and answers questions from BreachSpider's data and your environments. Matching itself never uses a language model.

Reports

Weekly digest, patch gap, environment risk and executive summary reports, plus framework-aligned reports that support NERC CIP and IEC 62443 work.

MSSP console

Run many clients from one console with isolated data, per-client environments and white-label reporting.

Training

13 OT security courses in eight tracks with scored assessments and certificates anyone can check. Three courses are free on every plan.

See it against your own devices

Search any CVE free, connect your agent, or book an assessment scoped to your plant.