Assets and the device panel¶
Where: Assets in the Inventory group, /app/assets.
What it answers: what do we have, and what is the state of each device?
The asset list¶
Every device you keep in BreachSpider, with its last check. Results come from the same engine as the API.
- Search by name, vendor, model or version.
- Views filter the list: All assets, Known-exploited, Fix available, Needs review, Support ended, Support ending within 12 months, Firmware behind, Firmware unknown, Firmware current, Not checked, Check failed, Confirmed findings, and the lifecycle buckets.
- Columns: asset, vendor and model, version, confirmed findings, known-exploited, fix group, lifecycle, firmware, match confidence, last checked. Click a column to sort.
- Check all assets now queues a check of every device and shows progress. You can cancel it.
- Import devices opens Import. Add a device adds one device by vendor, product and version and checks it at once.
- When some devices need attention, a link opens Data quality.
Bulk actions¶
Select devices (or every device matching the filters) and choose an action: move to a site, set area, zone, owner, criticality, role or maintenance window, add or remove a tag, or record an action.
- Preview the change shows how many devices are in scope and how many will change. Nothing changes yet.
- Apply changes exactly the previewed devices. If any of them changed since the preview, nothing is applied and you are asked to preview again.
- Undo (for 24 hours) restores only devices still holding the value the action set.
Owner, tags, criticality, role and maintenance window are your organization's notes. They never change a result or its order. Every bulk action and export is recorded in the audit history.
The device panel¶
Click a device to open its panel without leaving the list.
- Notes: owner, tags, criticality, role and maintenance window.
- Record an action: updated or patched (enter the version now installed; the device is checked again and findings clear only if the check shows the new version is past the fixed one), mitigation applied, replaced, decommissioned, investigated, scheduled, or a note. Each entry keeps who, when and an optional work order.
- Edit device: name, vendor, product, version, firmware, part number, type. Changing what identifies the device checks it again. Remove device takes it out of counts and checks; its history is kept and Undo brings it back.
- Match: which catalog product the device matched and with what confidence, and when it was last checked.
Tabs:
| Tab | Shows |
|---|---|
| Fix plan | The target version, what it clears, and the fix groups. Says plainly when no CVE has a published version fix |
| Findings | Each CVE, most urgent first, with the affected range, the sources (vendor advisory, public ICS advisory, CVE record) and acknowledgement controls |
| Lifecycle | End of support and end of sale with the vendor source, named replacement, or a link to check with the vendor |
| Firmware | Latest listed release, release notes and the security lines from later releases |
| History | Changes and acknowledgements for the last year. A first check sets the baseline |
When asset operations are turned on, the panel also has the device's asset identity (tag, record status, identifiers), QR label, maintenance records and documents vault. See QR and identifiers, Maintenance and Backups & integrity.
Acknowledging a finding¶
An acknowledgement records a decision about one finding: Risk accepted, Compensating control in place, Does not apply to how the device is used, Fix planned or Other, with a written reason of at least 10 characters and an expiry of up to a year.
An acknowledgement only labels. It never removes the finding from counts, from Fix first or from reports. It ends at its expiry, and it asks for review again when the finding changes (for example the CVE becomes known-exploited or a fix is named). It can be revoked with its own reason. Acknowledgements are never edited or deleted.
The CVE record¶
Click a CVE anywhere to open its record:
- Evidence: every fact links to the source that states it, with what its date means (read, as of, retrieved, published, modified). Sections: known-exploited listing (listing date, catalog due date, ransomware use), public exploit code (repositories as of the index commit; contents not reviewed), severity and exploit probability, affected and fixed versions with their stating document, fixes and mitigations, advisories, description.
- Your devices with this CVE and their fix group.
- Download the evidence (JSON).
- Open the full CVE page on the public site.
- Explain this finding: when the assistant is turned on, a plain-language explanation for an operator or a manager, from this record's evidence only (see The assistant and its limits).
Use it elsewhere¶
POST /api/v1/assets/correlate-cves returns the same per-device result for devices you keep in your own system:
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.