Skip to content

Fix first

Where: Fix first at the top of the menu, /app/fix-first.

What it answers: which actions, in which order, reduce our verified exposure the most?

Actions, not CVEs

A device with 40 CVEs usually needs one or two updates, not 40 tasks. Fix first groups findings by action: one row is one fix (for example "upgrade to security patch 3.11.2") on one product, across every device it applies to, with how many findings and known-exploited CVEs it clears.

The order

  1. Actions that clear a known-exploited CVE past its catalog due date come first.
  2. Then actions clearing more known-exploited CVEs.
  3. Then by the highest severity score, and the number of findings cleared.

The order uses only the engine's evidence and the catalog's own dates. Your owners, tags and criticality never move an action. Sorting by most devices, most findings or most known-exploited is possible; the screen then says that this is not the Fix first order.

Catalog due dates

The known-exploited catalog's due date is the date set for US federal agencies, not a deadline set for your organization. It is used here as an urgency signal.

What each action tells you

Item Meaning
Classification Vendor-verified fix (the vendor states this version as the fix), Derived candidate version (computed from the end of the published affected ranges: confirm it in the vendor advisory), Version not recorded (the vendor marks a fix available but no version is held), Partial coverage (some CVEs still apply at the target)
Devices Unique devices; a device in several groups counts once in the totals
Findings addressed, known-exploited addressed What the action clears
Past the catalog due date Known-exploited CVEs whose catalog due date has passed
Fixed-version source, data freshness Where the target comes from and when the catalog was read

Open an action for its Overview, its Devices (current version, target, what it clears per device, owner and maintenance window) and Take action.

Taking action

  • Record the fix records the update on every device of the action, with the target version filled in and its known-exploited CVEs attached. Recording logs the work; it clears nothing by itself. Findings clear only when the next check confirms the new version on the device.
  • Plan maintenance (with asset operations) creates a work record per device in Maintenance.
  • Draft a change ticket: a change ticket draft from the vendor's and government's statements about this action. When the assistant is turned on, it writes the summary, steps, rollback and verification, and every line cites a numbered statement; where no statement gives a step, the draft says so rather than inventing one. The scope (devices, sites, versions, owners, windows) comes from your inventory, never from the assistant.
  • Export as CSV: every action with its devices, sites, owners, maintenance windows and what it clears. Cells that could be read as spreadsheet formulas are neutralized.

Known-exploited CVEs with no known fix are counted separately; they stay on each device's findings.

Use it elsewhere

The API returns the same grouping per call as fix_groups, fix_plan and data.fix_summary (see Correlate CVEs), and the MCP tool get_fix_plan returns it for one device:

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.