Docs / Results and account

Results

Where scan output lands: the asset graph, findings, reports, imports and alerts.

Asset graph

Every engine writes into one shared asset graph rather than its own silo. A domain leads to hosts, hosts to ports and services, services to endpoints, and endpoints to the operations (a method against a path) and the parameters each one takes. So toolmark knows what ambulo found, and plessor knows what both of them found.

Views

  • Assets: browse and filter everything discovered, and open any asset for its full context and history.
  • Attack surface: the same graph as a map, for seeing shape and reach rather than rows.
  • Overview: the same graph reduced to counts, a feed of what changed, and a ranked list of what to look at next.

What changed

Assets are content-hashed at ingest, so a re-run does not just add rows: it produces a typed diff. New hosts, endpoints that disappeared, a service whose version moved, a response shape that changed. The change feed is usually the fastest way to see what a target did since you last looked.

Traffic capture feeds the same graph (see Traffic capture), so a surface you browsed and a surface you scanned are one picture.

Findings

Results land in the Findings explorer: filter by severity, by active or passive discovery, and by host; search, paginate, and export the set to CSV, JSON or Markdown for your report or pipeline.

PDF on a finding's page gives that one finding as a page of its own: what was seen, what it allows, how to fix it and its status history. Bounty write-up gives the same finding as Markdown in the order a bug bounty form asks for it: summary, steps to reproduce, what was observed, impact and a suggested fix. Read it and put it in your own words before you send it. It names no tool, and whether a program takes findings from automated testing is in that program's rules. Both are on every plan.

Each finding's page says what the finding allows and how to fix it, with its CWE and OWASP references where there is a standard one. From the same page you set its status: Open, Confirmed, Fixed, Accepted risk or False positive. Accepted risk and False positive ask for a reason, because a report prints it. Every change is kept with who made it and when. A finding marked Fixed goes back to Open by itself if a later scan finds it again.

Export on the Findings page gives every finding in the workspace as one file: CSV for a spreadsheet, JSON for a script, or SARIF for a code scanning dashboard. A finding closed as accepted or a false positive is in the SARIF file as suppressed, with its reason.

Reports

A report is a dated account of what Crossfyre found, as a page and a PDF. Intel → Reports → New report makes one. It is read from the workspace once and kept, so it says the same thing whenever it is opened, whatever has happened to the findings since.

  • What it covers: one scan, on every plan, or the whole workspace over a period, on Pro and above.
  • What is in it: a summary and what to fix first; the scope list with who authorised each entry; every scan with the node and address it was sent from; what is exposed and what changed; each open finding with what Crossfyre saw, what it allows and how to fix it; and what was closed in the period, by whom and why.
  • Draft: a new report is a draft. You can reword its title, who it is for and its summary. The findings, the scope and the scans are what was read, and stay.
  • Final: making a report final fixes it. It gets a fingerprint for its data and one for its PDF, the PDF is kept as it was set, and it can no longer be edited. To say something different, make a new report.
  • Script: the PDF is set in Latin script. Text from a target in another script prints as empty boxes.

On Reaper and above, a workspace report compares itself with the last final one: what is new, what is still open, what was fixed and what a scan reopened. A report is an automated assessment. It does not replace a manual penetration test where a contract or a standard asks for one, and the report says so.

Your name and logo

On Pro and above, Reports → Branding puts your own name and logo on the cover in place of Crossfyre's. It is set once for whoever owns the workspace, a person or a team, and every report made afterwards carries it. A report already made keeps what it was made with. The logo is a PNG or a JPEG up to 512 KB; Crossfyre keeps its own copy of the picture, not your file. Crossfyre stays credited in the footer.

On Syndicate and Enterprise you can leave Crossfyre's name off altogether: the cover, the footer, the wording and the file's own metadata then name only you, and the page a share link opens does the same. A report made this way does not point at crossfyre.io/verify, though its file still checks there.

Reports from a mission

A mission can make a report each time a run of it finishes: open the mission, then Schedule → Make a report when a run finishes. With the mission on a weekly schedule that is a weekly report with nobody pressing anything. Missions are on Reaper and above.

  • The report covers the workspace from where the mission's last report stopped, and compares itself with that one, so a report somebody made by hand in between does not move the comparison.
  • It is made final at once, because nobody is there to read a draft.
  • Everyone in the workspace is told, in the inbox and by email, with the counts and a link. The email does not carry the PDF or name a finding. Turn it off under Notifications, Report ready.
  • A mission that runs more than once a day reports once a day, and a run whose scans never started makes no report.

Checking a report

Anybody holding a final report's PDF can check it at crossfyre.io/verify, without an account. They choose the file, their browser works out its fingerprint, and only the fingerprint is sent. The page answers with the report's number and the day it was made final, or says no such file is on record. A file that was opened and saved again, or printed to a new PDF, no longer matches. A deleted report answers as withdrawn.

Share links

On Syndicate and Enterprise, Share on a final report makes a link for somebody with no account. It opens the summary and the PDF until it ends (1, 7, 30 or 90 days) or you revoke it. The link is shown once, when it is made: Crossfyre keeps only a hash of it, so it cannot be shown again or recovered from our side. The report's page lists each link, who it was for, and how often it was opened. Deleting the report ends all of them.

Import

Most engagements do not start from zero. Import brings an existing list of hosts, endpoints or an API specification into a workspace so the asset graph starts populated and the first scan has something to work from.

Imported assets carry their provenance. An endpoint you supplied from a spec is marked as coming from a spec, not as something observed, and the distinction survives into findings: a parameter the platform saw in real traffic is stronger evidence than one a document claimed exists.

Notifications

Get alerted the moment a scan finishes or a finding lands, on the channel you already use:

  • Discord / Slack: add the Crossfyre bot, run /login <email> and confirm with the code we email you (/verify). Subscribe a channel and alerts post there.
  • Email: enable email alerts in Settings → Notifications.

Manage channels and what triggers an alert from the Notifications page in your dashboard.

Valkyrie triageSwitched off

Valkyrie is switched off on crossfyre.io while it moves to bring-your-own-key, so that every model call runs on an API key under API terms. Nothing below runs until it is back, and no plan sells AI credits in the meantime.

A scanner's output is a queue, and the work is deciding which twenty of two hundred findings are worth an afternoon. Valkyrie reads the findings in a workspace and ranks them, with the reasoning attached rather than a bare score.

It is metered separately from scanning. Scanning within your plan limits is unlimited and costs no credits; triage consumes AI credits, which your plan grants each term and which you can top up. That split is deliberate, so an expensive feature cannot make an ordinary scan expensive.

Before a request leaves our server for the model, every message in it is redacted: a value under a key that names a credential, a token in a known format, a private key or a password hash is replaced with a placeholder, so the model can still tell that a credential was there. The Security page lists what is sent, what is taken out and what redaction misses.

Triage reads findings that already exist. It does not send traffic at a target and it cannot turn an unconfirmed finding into a confirmed one.