Docs / Run scans

Scanning

The five engines, the workflows that run them, and how to schedule a scan or chain several.

Scan engines

Engines are the scanners. Each is a standalone, open-source tool that runs as a local daemon, keeps its work in the toolchain database, and can run entirely on its own from the terminal. Enrol a host as a node and the platform supervises the same engines across your fleet, paces each scan to what the target can take, and streams every result into one shared asset graph. Install and manage them with the CLI (crossfyre extension install <name>); each runs a live terminal UI standalone and reports to your dashboard on the platform.

The five engines run as one pipeline from recon to vulnerabilities, and each also stands on its own:

  1. 1 voyage Subdomains
  2. 2 doorward Ports and services
  3. 3 ambulo Paths and pages
  4. 4 toolmark Tech and versions
  5. 5 plessor Vulnerabilities
voyageSubdomain enumeration. Passive intel sources plus active brute-force. Finds the hostnames.
doorwardNetwork and port scanning. Finds live hosts, open ports and the services on them.
ambuloContent discovery and crawling. Finds hidden paths and maps each web app's surface.
toolmarkService enumeration and fingerprinting. Identifies the tech, versions and CVE leads.
plessorVulnerability scanning. Runs detection templates and authorization tests, and confirms them.

The pipeline in one line: voyage finds subdomains, doorward finds open ports and services, ambulo discovers content and crawls each web service, toolmark fingerprints the tech and versions, and plessor checks the surface for vulnerabilities. Every engine is stateful and resumable: a scan you stop, or one interrupted by a dropped node, picks up exactly where it left off.

Full reference for each engine: flags, sources, tuning and what each one does not do.

Workflows

A workflow is a .cfx script (Python) that drives a scan: it picks targets, calls the engines, and reports results. Run one locally with crossfyre run content-discovery.cfx url:https://example.com, or launch it from the dashboard to run across your nodes.

Workflows are crash-safe: the platform reserves an estimated cost at launch and reconciles the actual work at completion (reserve-then-reconcile). A dropped node or a crash resumes where it left off, and you are never charged twice or for work that did not run. To run scans again on a schedule, use a mission.

What you can run

Ten workflow types ship today. Each has a create form in the dashboard under Operations, and each maps onto one or more engines:

subdomain-enumPassive and active subdomain discovery. Usually the first stage, because everything downstream works from its output.
port-scanLive hosts, open ports and the services behind them, spread across the fleet rather than run fast from one box.
content-discoveryHidden paths and files, rate-adapted per target so a wordlist does not get you blocked.
web-crawlMaps a web application by following it, producing the endpoint and parameter surface the testing stages need.
service-enumFingerprints technology and versions on what was found, and turns that into CVE leads.
vuln-scanDetection templates plus the injection oracle, with out-of-band confirmation where the class allows it.
api-testDrives an API from a spec or a capture, so endpoints get tested as endpoints rather than as URLs.
origin-discoveryFinds the real origin behind a CDN or WAF. Often the highest-value single result on a target, and the exposure is itself reportable.
web-tracerCaptures traffic from a browser or a phone and feeds the real request shapes into the graph. See Traffic capture.
customHalf builtYour own .cfx script, when the built-in shapes do not fit. Custom scripts run, but the create card in the dashboard is still locked.

Authenticated scanning, authorization testing and browser-fingerprint mode are capabilities that apply within these workflows rather than separate types. Which ones you can switch on depends on your plan.

RoutinesEvery plan

A routine is several scans in a row that you launch once. Pick a template, give it your domains, and the platform runs each stage on your fleet and starts the next when it finishes: subdomains first, then the hosts behind them, then the web applications on those hosts.

Each stage's findings become the next stage's targets, up to the cap you set for that stage, so new subdomains get their ports scanned and new endpoints get crawled without you starting each scan. A host one stage finds goes on to the next only when the workspace's authorised scope list admits it. Create and manage them from the Routines page.

Routines run on every plan, once each time you launch one. To have a chain run again on a schedule, use a mission.

MissionsReaper

A mission is a chain of scans that runs again on a schedule. Where a routine runs once when you launch it, a mission has its own schedule and a full run history you can go back through, so you can see what changed between runs. Its steps pass data as a routine's stages do: the hosts one step discovers become the targets of the next, when the authorised scope list admits them, and each step can be given its own nodes.

Use the Planner to compose one and to bulk-launch work across a set of targets rather than starting scans one at a time.

A mission can make a report each time a run finishes, final and compared with its last one, and tell everyone in the workspace it is there.

Missions are a Reaper capability, enforced server-side at launch, on schedule, and on re-run.

Scan defaults

Every workflow form starts pre-filled. Those values are yours to set, per user, from Operations then Settings: thread counts, target ceilings, timeouts, which pacing posture to use, and whether a stage runs at all.

Worth setting once early. The defaults are conservative on purpose, and if you find yourself changing the same three fields on every launch, that is the page to change instead.

A saved default that names a capability your plan does not include is ignored rather than failing the launch.

Reaching hard targets

An authorized scan is not much use if the edge drops it before it arrives. Two things get in the way: the target sits behind a WAF or CDN, and a scanner announces itself as a scanner.

Origin discovery

voyage can work out a target's real origin behind a CDN, which lets a scan reach the application directly. It is also worth reporting on its own: an origin that answers the public internet without the edge in front of it is an exposure.

Looking like a browser

Rather than presenting the fingerprint of a scanning library, Crossfyre can present a genuine browser handshake, so an authorized scan is not rejected purely on how the client looks. It will not solve an interactive challenge you have not been authorized to solve, and it is not a way to bypass access controls: what it does is stop a legitimate test being discarded at the edge.

Pacing

Throughput is adapted continuously to what the target is actually tolerating, rather than fixed at a number you guessed. That keeps a run fast without hammering any single host, and it is what lets a large distributed scan finish instead of collecting rate-limit errors.

The Browser-fingerprint mode switchReaper

Browser-fingerprint mode is a per-scan setting, so you can turn it off for a target that does not need it. It is a Reaper capability; adaptive pacing runs on every plan, at a level set by your tier.

These capabilities exist so an authorized scan reaches the application it was contracted to test. Use them only within a scope you have written permission for.

Agents (MCP)

crossfyre mcp is an MCP server built into the CLI. An AI agent's client starts it and talks to it over stdio. It serves the toolmark and plessor engines on that machine, held to a scope file you write, and a Crossfyre Workbench open beside it. With an MCP key from Settings, then Agent access, it also reaches one workspace here: its scans, findings, assets and nodes and, with a launch key, scans started on its nodes. Those launches are checked against the authorised scope list like any other, and a workspace can hold them until you approve them.

crossfyre mcp covers connecting a client, the tools it exposes, keys, approval, the limits on a key and how to revoke one.