Changes¶
Where: Changes in the Inventory group, /app/changes.
What it answers: what changed on our devices between checks?
Every device is checked every night and whenever you run a check. A first check sets the baseline; changes start from the next one. Each change keeps the value before and after.
Three views¶
Digest¶
Repeated events are grouped so a busy week reads in a minute, and nothing is deleted: open a group to see every event in it.
- Each CVE newly listed as known-exploited is shown on its own and always first. These are never grouped with other changes.
- Other changes are grouped by product and by before and after value (new findings per product; status, lifecycle, firmware and version moves; checks that did not complete, per site).
- Each group shows its devices, events, repeats, CVEs and the first and last time.
Write a summary: when the assistant is turned on, it writes a short summary of the groups. It reads only the groups (products, counts, CVEs, before and after values), never device or site names, and each sentence lists the groups it describes.
Every event¶
Every change, newest first, filterable by type and window (last 7, 30, 90 or 365 days):
| Type | Meaning |
|---|---|
| Newly known-exploited | A CVE on the device was added to the known-exploited catalog |
| New findings | CVEs that now apply |
| Findings that no longer apply | CVEs that left the device's result |
| No longer known-exploited | A CVE left the catalog |
| Support status changed, Lifecycle dates changed | The vendor's lifecycle answer moved |
| Firmware status changed, New firmware release listed, Firmware answer changed | Firmware currency moved |
| Version changed | The device's recorded version changed |
| Same CVEs, evidence or match changed | The CVEs are the same, but their evidence or match level changed |
| Check did not complete | The last check failed; the earlier result stays until a check succeeds |
You can acknowledge a change event the same way as a finding (see Assets).
Actions taken¶
Every action people recorded on devices (updated, mitigated, replaced, decommissioned, investigated, scheduled, notes), newest first, with who and when, and Recent edits: device edits and removals, site changes and deleted reports, each of which can be undone for 30 days unless the item changed again since.
Use it elsewhere¶
For devices you keep in your own system, keep each device's result_hash and status_hash and ask the change check which devices changed: POST /api/v1/assets/correlate-cves/check (API), bs.correlate.check() (SDK) or the MCP tool check_changes. It costs a tenth of a full device check.
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.