What BreachSpider does¶
In plain language¶
An industrial site runs controllers (PLCs), operator panels (HMIs), protection relays, gateways, network switches, engineering workstations and Windows servers from many vendors. Many of them run firmware that is years old, because a controller that runs a process cannot simply be restarted to install an update.
Every week new vulnerabilities are published as CVE records. Each record says which products are affected, and usually which versions. The hard part is not finding the records. The hard part is answering three questions for each device you actually own:
- Which CVEs affect this device at the version it runs? Not the product in general, the exact version.
- What is the one update that clears the most of them, starting with the ones attackers are known to use?
- Is the device still supported by its vendor? If not, the answer is a replacement plan, not a patch.
BreachSpider answers those three questions for every device you give it, and shows you the document behind every answer: the CVE record, the vendor advisory, the government advisory, the vendor's lifecycle page. When it cannot answer, it says so and tells you why.
A worked example¶
Your inventory lists a network switch: vendor Moxa, product EDS-518A, firmware V3.5.
BreachSpider:
- Identifies the product. It finds the catalog product "EDS-518A" from Moxa with high confidence. You did not need to know the product's CPE name (the formal naming scheme CVE data uses).
- Compares the version with every affected range. Three CVE records say firmware 1.0 up to and including 3.11 is affected. 3.5 is inside that range, so all three are confirmed for this device.
- Finds the fix. Moxa's advisory MPSA-241156 names security patch 3.11.2. That one update clears all three.
- Checks status. None of the three is on the known-exploited catalog today. Lifecycle and firmware currency are reported where Moxa publishes them.
- Gives you a fingerprint. A
result_hash(for the findings) and astatus_hash(for known-exploited, lifecycle and firmware facts). Ask again tomorrow with the same input and you get the same hashes, unless something in the data changed. That is how you know a result moved.
What makes it different¶
Exact versions, not product names. A tool that matches by product name alone lists every CVE ever published for that product. Most do not apply to the version you run. BreachSpider compares your version with each record's affected range in the vendor's own numbering scheme, and labels every CVE as confirmed for your version, possibly affected (the record gives no version limit, or the model is not known), or likely not affected (the vendor's stated fix is at or below your version).
Deterministic. Matching and ranking use fixed rules and stored data. No language model takes part in deciding which CVEs apply or in which order to fix them. The same input gives the same answer and the same hash, whether you ask through the web app, the API, the Python SDK, the partner widget or an assistant over MCP.
Every fact is cited. Each affected range, fix and lifecycle date links to the document that states it, with the date it was read. See Sources and evidence.
Honest about what it does not know. Unknown products, missing versions, product families without a model and vendors that publish no version data are all reported as such. See Zero CVEs is not the same as no risk.
What you can use¶
| Way in | For | Install or open |
|---|---|---|
| Web app | Teams who keep their inventory in BreachSpider: overview, fix order, progress, reports, operations | breachspider.com/app |
| API | Checking an inventory you keep in your own system | API overview |
| Python SDK | The API from Python, with paging and retries handled | pip install breachspider |
| MCP server (local) | Assistants such as Claude Code, Claude Desktop or Cursor on your machine | pipx install breachspider-mcp |
| Hosted MCP | Assistants that connect to a URL and sign you in | https://mcp.breachspider.com/mcp |
| Partner widget | A device check embedded on a partner's own website | Partner widget |
What BreachSpider is not¶
- It is not a network scanner. It does not probe your network or connect to your devices. It works from the vendor, product and version you give it.
- It does not test whether a vulnerability can be exploited in your plant. It tells you which published vulnerabilities apply to the versions you run, so your engineers can decide what to do.
- It is not an audit or a certification. Reports can carry a framework label (for example NERC CIP-007 R2) to show what the evidence relates to; that label is never a certification or an audit opinion.
Next¶
- How matching works: the engine, step by step.
- Getting started: set up your organization.