Turn a finding into a change ticket¶
Take an action from Fix First (or a device's fix plan) and turn it into a change ticket your team can file, send or plan as maintenance work.
Role: owner, admin or editor. The assistant must be turned on for your organization; if it is not, the draft says "The assistant is not turned on for this organization."
1. Pick the action¶
- Open Fix First. Each row is one action, for example "Fortinet FortiOS, upgrade to 8.0.0", with the devices it covers and the findings it addresses.
- Click the row to open it. It has three tabs: Overview, Devices and Take action. Overview shows the impact, the target version, how the fix is classified (for example Vendor-verified fix) and where it comes from.
- Open Take action. It has Record the fix, Plan maintenance and Draft a change ticket.
Recording a fix logs the work; it does not clear anything by itself. Findings clear only when the next check confirms the new version on the device.
2. Draft the ticket¶
Press Draft a change ticket. The draft uses this action's devices and findings and takes a little while. It shows:
- The label "Drafted by the assistant (Claude, by Anthropic). Every line restates a vendor or government statement shown below. Review before use."
- Summary, for example "Upgrade Fortinet FortiOS on 5 devices to version 8.0.0."
- Steps, Rollback and Verification. Each step points to the statement it restates, for example "(statement 1)". Where the vendor gives nothing, the draft says "None given in the vendor's statements."
- Scope (from your inventory, not drafted): a table of the devices with Device, Site, Version, Owner and Maintenance window, taken from your inventory.
- Vendor and government statements used, with links to each source.
Review it before use. If the draft fails, it says "The assistant could not draft this ticket. Try again later."
3. Send it on¶
Under the draft:
- Copy ticket text copies the whole ticket as plain text, with the statements and their links, to paste into your ticketing system. The page says "Copied."
- Email to team members lists the members of your organization under Send to. Tick the ones to send it to and press Send. BreachSpider sends the ticket as plain text, with your address to reply to.
- Open in your email app opens a new email in your own email app with the subject "Change ticket: ..." and the ticket as its text. Use it for anyone outside the organization, such as a ticketing system inbox. A long ticket is shortened to fit; the email then says to paste the full copy from BreachSpider.
- Close draft closes it.
4. Plan it as maintenance¶
On Take action, press Plan maintenance. Maintenance opens with New work already filled in:
- The note "From Fix first: Fortinet FortiOS, upgrade to 8.0.0. A planned change is not a fix until the device check confirms it."
- "One work record per device", with the number of devices.
- Maintenance type Firmware update, Title the action (for example "upgrade to 8.0.0") and Start as Planned.
Add the due date, priority, technician and window, then press Save. Carry out and close the work as described in Plan and record maintenance.
5. From a single device¶
Open the device (from Assets, a QR scan or a search) and its Fix plan tab. Draft a change ticket next to the target version drafts the same ticket for this one device.
Export every action¶
On Fix First, Export change tickets (CSV) downloads one row per action (for example change-tickets-20261109-1135.csv) with the title, vendor, product, action, target version, devices, sites, owners, maintenance windows, findings cleared, known-exploited cleared, past catalog due date, earliest due date and fix source. Nothing in it is drafted by the assistant. Export as CSV downloads the Fix First list itself.