Skip to content

Lifecycle

Where: Lifecycle in the Intelligence group, /app/lifecycle.

What it answers: which devices has the vendor stopped supporting, or will soon?

Support status for every checked device, as each vendor states it. Every date links to the vendor page it came from, with the day it was checked. Background: Lifecycle and firmware currency.

Statuses

Status Meaning
Past end of support The vendor's end of support date has passed
Support ending within 12 months The vendor states an end date within a year
Paid support program only Fixes continue only under a paid extended program
Supported The vendor states a future end date or lists the product as active
Unknown A source exists but gives no answer for this device, with the reason (for example "Lifecycle dates differ by edition")
No lifecycle source yet We hold no lifecycle source for this vendor. A link to check with the vendor is shown where one is known

"Supported" is never the default: no notice found is shown as unknown or no source, never as supported.

Each device shows

End of support date (with the vendor's own term, such as "discontinued" or "end of service"), end of sale, date confidence, named replacement, the vendor's status wording, the vendor source and when it was checked.

Filters partition the devices by status; sort by end of support date or device name; Export as CSV.

Use it elsewhere

The lifecycle block on each device result of Correlate CVEs, described in Lifecycle and firmware currency (API), is available to client plans and partner keys. A change in support status changes the device's status_hash.

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.