Fissure control dashboard

Server

Enter the API token and press Connect.

Workspace overview

Connect to see the active project, scope, proxy and traffic.
Project-
Scope-
Proxy-
Traffic-
Jobs-
The same control session an agent drives over the MCP bridge: what it captured and configured is what every tab here shows.

Findings summary

-
Critical
-
High
-
Medium
-
Low
-
Info
-
Total

Findings

SeverityTitleHostSource

Start a scan

Scan options
Scans run in scope only. Active/aggressive require an authorized, in-scope target.

Repeater - send a request through the engine

Request headers (one per line: Name: value)
Request body
The response status, headers, and body appear here.

Intercepting proxy

Start the proxy, then point your browser's HTTP proxy at the shown host:port.

Interception - hold, edit, forward

Editing here goes through a text box: a head that loses its carriage returns is repaired, but for byte-exact work use the desktop raw editor.

Captured flows

#MethodURLStatusClientTLS
Click a flow to read its request and response below.

Flow detail

No flow selected.
Request
The selected flow's request is shown here.
Response
The selected flow's response is shown here.

Traffic - every request every tool sent

#ToolMethodURLStatusLengthms
Scans, Repeater, Intruder, discovery and the proxy all log here; the Proxy tab lists only flows captured through the intercepting proxy. Click a record to read its bytes below.

Record detail

No record selected.
Request
The selected record's request is shown here.
Response
The selected record's response is shown here.

Recon - feed tool output into the inventory and scope

Assets (recon diff)

HostLiveStatusTechEndpointsDiff

Protobuf / gRPC decode


Transform


Remediation lookup

The same fix guidance and references the report generator uses per finding.

Prettify


Scope

In-scope (one per line)
Out-of-scope (one per line)

Named scopes

NameIn scopeOut of scope
A project holds several named scopes and one active; the active one is what scans, requests, Intruder and discovery are held to.

Projects

ProjectState
The active project owns the per-project stores (scope, environments, parameter jar, team, Repeater tabs). Activating another one re-points them; findings and captured flows of the running session are not moved.

Request parameters carried by the crawl

NameValueCurrentOnQueryBodyTrackNoFuzzReq
#URL POSTed before the crawlExtra body

Shared cookie jar

The session every tool sends: the scanner, the Repeater and each manual request read this jar, so a session put here authenticates all of them.

NameDomainPathValueSecure

Paste a session from your browser

Paste what the browser gives you: document.cookie, the Cookie: request header from the network tab, or a whole Copy as cURL command. Only its cookie option is read, so the URL and the other headers do not become cookies.

Log in through a browser

For a login no script can perform: a nonce the page computes, a captcha or key you answer yourself, an SSO hand-off across origins. It drives a real headless browser, then puts the session it establishes into the jar above.

Report

Generate a report from the findings store in the chosen format.

Targeted probes

SeverityTitleLocationConfidence
Pick a probe, enter an in-scope target, and Run. The verdict and any findings appear here.

Start a background check job

Jobs

IDKindNameTargetStatusElapsed

Event log

TimeLevelSourceMessage

Purple team

Record what every probe puts on the wire, then reconcile it against the telemetry the target's own logging and alerting produced. This measures the defenders instead of evading them: each probe carries an X-Fissure-Probe header so a line in their logs names one exact request.

Import the defenders' telemetry

Detection coverage by technique

TechniqueSentLoggedAlertedBlockedCoverageBaseline

Add a recurring scan schedule

Schedules

IDNameURLProfileEveryEnabledLast

Attack surface

The endpoint inventory summary (counts by source, method, and status) appears here.

Query language (HTTPQL)

Matching rows appear here (capped). Invalid queries report the compile error.

Saved queries

NameQuery

Workflow templates

The template description appears here.

Run a workflow

The per-node trace and findings count appear here.

Import a check (nuclei / BCheck / Jaeles)

The compiled check JS + any skipped features appear here.

Run a check (jscheck)

SeverityTitleLocationConfidence

AI-assisted shadow repeater

The baseline, the variations, and any findings appear here.

OAST out-of-band collector

Start the listener, mint a canary, plant it in a payload, then poll for the hit.

Poll / history

TokenMethodPathSourceChannel

API console - every control route

Pick a route. A GET reads state (extensions, plugins, tags, scan profiles, Repeater tabs, relay history and the rest); a POST runs the documented action.
The JSON response is shown here; a list in it is also drawn as a table above.
This is the same API an agent drives through the MCP bridge. Routes that send traffic are held to the scope and the aggressive toggle exactly as they are there.

Engine configuration

Settings an agent can change over the API that decide what the engine sends: the User-Agent, environments, transform tags, resource budgets, host routes, scan profiles and the auto-repeater ruleset. Each card loads what is in force now.

Extensions

Installed extension bundles and the offline marketplace, plus the context actions, session actions and message editors each enabled extension contributes.

OSS-tool plugins

The bundled external-tool plugins, their installed state, and a form to run an installed one against a target.

Saved requests and attacks

The Repeater tab workspace, the organizer queue and the saved Intruder attack configs. Send any saved request to the Repeater tab.

Raw TCP/UDP relay

The non-HTTP interception relay: start it, watch the captured chunks, and hold or forward a chunk. The status and chunk cards load what is running now.