Overview¶
Where: breachspider.com/app, the first screen after sign-in.
What it answers: how exposed are we right now, what should we do first, and what changed?
Filters¶
At the top you choose a site, a vendor, an asset type and a time range (7, 30 or 90 days, 6 or 12 months). The line under the filters states exactly what you are looking at, for example "Showing 214 assets · North plant · All vendors · All asset types · 30 days of changes and history".
Counts are always the latest check of each asset; the time range sets only the history and the change window.
Start here¶
The first Fix first action for this scope: how many devices it covers and how many findings (and known-exploited CVEs) it clears. Review first action opens it in Fix first.
The headline numbers¶
| Tile | Counts |
|---|---|
| Assets | Devices in inventory in this scope |
| With confirmed findings | Devices with at least one CVE confirmed for the installed version |
| Needs review | Devices whose identity or version is uncertain |
| Fix First actions | Actions that each clear one or more findings |
| Known-exploited devices | Devices with a known-exploited CVE confirmed for the installed version |
| Vendor support ended | Devices past the vendor's end of support |
Each tile shows its change against the start of the range when daily history exists. Every number opens the device list behind it, computed with the same rule as the list it opens (this is tested).
Panels¶
- Fix First: the top three actions in Fix first order, each labelled Vendor-confirmed fix, Derived candidate target, Fix exists, version unknown or Manual review required. Why this order? explains the ranking. Fix first is grouped per site and vendor, so the asset type filter does not apply to it.
- Exposure trend: assets with confirmed findings, one point per recorded daily snapshot. Days without a snapshot are gaps, never estimated. Daily history is kept for the whole organization and per site, so no trend is drawn for a vendor or asset type filter.
- Important changes and Known-exploited changes: events in the time range. View all opens Changes.
- Vendor lifecycle: supported, end of sale announced, support ending within 12 months, support ended, not published or not held.
- Firmware currency: current, behind, unknown. Unknown means the vendor's release history is not held for that product, not that the firmware is current.
- Assets requiring attention: highest priority first (known-exploited findings, then public exploits, fix availability and confirmed findings), with identity confidence.
Ask about your environment¶
If the assistant is turned on for your organization, you can ask questions in plain language, such as "Which devices have known-exploited CVEs?" or "What changed in the last 7 days?". The assistant (Claude, by Anthropic) reads only your stored checks through the same views as these screens, links every sentence to the records it used, and never changes anything. An answer that does not pass the checks (every figure must come from your records) is not shown. See The assistant and its limits.
Before you have devices¶
A new organization sees the sample plant, fictional devices with real products and versions checked by the same engine, labelled Sample. A getting-started checklist tracks four steps: import devices, run the first check, invite your team, set owners.
Use it elsewhere¶
The overview is a web app screen. The same per-device results are available to your own systems through the API, the SDK and the MCP servers:
Sign in at breachspider.com/login. The web app is at breachspider.com/app. New here: Getting started.
curl -X POST https://breachspider.com/api/v1/assets/correlate-cves \
-H "Authorization: Bearer $BREACHSPIDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"assets": [{"asset_id": "SW-01", "vendor": "Moxa", "product": "EDS-518A", "version": "V3.5"}]}'
Keys: Integrations in the web app, or a free 14 day trial key at breachspider.com/developers. Reference: Correlate CVEs.
pip install breachspider
import os, breachspider
bs = breachspider.Client(os.environ["BREACHSPIDER_API_KEY"])
resp = bs.correlate.correlate([{"asset_id": "SW-01", "vendor": "Moxa", "product": "EDS-518A", "version": "V3.5"}])
print(resp.results[0].fix_plan)
Guide: Python SDK.
pipx install breachspider-mcp
claude mcp add breachspider -e BREACHSPIDER_API_KEY="$BREACHSPIDER_API_KEY" -- breachspider-mcp
Runs on your own machine; only vendor, product, version and a neutral asset id leave it. Guide: MCP server (local).
Connect an assistant that supports remote MCP servers to:
https://mcp.breachspider.com/mcp
You sign in with your BreachSpider email and approve the access. Connecting by URL is turned on per organization: the Integrations page shows whether it is open for yours. Guide: Hosted MCP.