Jane
Enter the war room
Deny-by-default · scope-verified · audit-logged

Send Jane to war on your attack surface.

Jane is an AI operator you send against your target — she reasons, probes, and breaches like a real adversary, then proves every kill with reproducible evidence. And she never crosses a line you didn't draw: every move is gated by the scope you authorize.

// no unscoped egress · no unproven kills

jane · engagement //mission-4f2a · exploitation
Jane's battle rhythm

Jane fights the engagement — she doesn't run a fixed scan

A bounded ReAct loop drives every mission: she reasons a move, picks one scope-gated weapon, observes what it hit, and presses the advantage — forming hypotheses, testing them under fire, and promoting only the proven ones to findings. A miss is kept as intel, never discarded.

01

Reason

Calls the shot — states a hypothesis and why the next strike is in-scope and safe.

02

Strike — gated

Fires one tool through the policy gate. Out-of-scope shots are refused, not sent.

03

Observe

Reads the captured exchange; the request/response is logged as evidence.

04

Hypothesize

Opens, confirms, or rules out a lead — dead-ends kept as intel.

05

Confirm the kill

Promotes a proven breach to a finding with a PoC, CVSS and counterevidence.

Kill-chain campaign

The offensive advances phase by phase — and only when the gate falls

Jane wages a real campaign, not a checklist. Each phase pulls its own framework playbooks and must breach a validation gate before the next front opens. Escalation into post-exploitation is authorized separately — a surface-only mission documents and holds the line.

Recon

Scout the ground

Enumerate endpoints, params and tech.

gate: breached
Discovery

Find the weak point

Probe authn/z, injection, IDOR, SSRF.

gate: breached
Exploitation

Take the ground

Confirm the breach with reproducible evidence.

gate: breached
Post-exploit

Press deeper — if authorized

Escalate within the granted depth.

policy: ESCALATE
Reporting

The after-action

Findings + kill-chain coverage.

gate: breached
The war room

Watch the assault unfold, in real time

Operators command missions from a board and follow Jane live on the front: her reasoning trace, the hypothesis timeline, kills as they’re confirmed, and a coverage map of every position taken.

Jane’s live trace agent_step · streaming
httpGET /rest/products/search?q=' — 500 differentialsuccess
hypoSQLi on search q — boolean + time-basedtesting
httpGET …q=')-- — union reflects 9 colssuccess
skillread playbook WSTG-INPV-05info
confirmSQLi confirmed — 2 exchanges citedcritical
Mission board operators drive the column
In progress
app.acme.io
exploitation · 61%
2 high
Review
api.acme.io
7 findings
1 critical
Done
staging.acme.io
reported
clean
Finding · SQL injection retest lineage
severity
Critical · CVSS 9.1
endpoint
/rest/products/search
att&ck
T1190 · Initial Access
owasp
A03:2021 — Injection
status
proposed → validated
evidence · replayable
exchange ex_7f21, ex_7f2a · poc.sh · counterevidence recorded
Coverage ATT&CK / OWASP
Initial AccessT1190
ExecutionT1059
A01 Access CtlIDOR
A10 SSRFWSTG-19
Jane's arsenal

A signed armory of expert playbooks, drawn for the phase and the target

Jane never fights from nothing. She draws the right playbook for the active phase and the target in front of her — from an armory built independently from public sources and Ed25519-signed, so a tampered pack never makes it to the field.

278
Signed framework packs in the armory
5
Kill-chain phases, each gated
15
MITRE ATT&CK tactics covered
Ed25519
Every pack verified before it loads
MITRE ATT&CK · enterprise techniques OWASP WSTG · web testing guide NIST · SP 800-53 / 800-115 CIS · benchmark references CWE · weakness mapping
Force multipliers

Jane plugs into the stack you already fight with

She doesn’t just report — she acts through your tools: reading your source for white-box analysis, shipping the fix, sounding the alarm, and commanding the scanners you already trust. Every integration stays inside the same scope and audit log as the rest of the engagement.

GitHub GitLab Bitbucket
GitHub · GitLab · Bitbucket

Reads the source, ships the fix

Connect a repo and Jane can pull the code to run white-box analysis alongside the live attack (optional) — then open an auto-fix pull or merge request for a confirmed finding, patch and evidence attached, scoped to the repos you install her on.

acme/api · pull request
● Open #482 opened by jane
fix: parameterize product search query (SQLi)
merge jane/fix-sqli-482 into main · 1 commit · +3 −2
app/api/search.py
- rows = db.execute(f"…WHERE q = '{q}'") + rows = db.execute("…WHERE q = %s", (q,))
✓ 4 checks passed · evidence attached
Slack
Slack

Sounds the alarm in Slack

Point Jane at a channel and every confirmed kill, mission milestone and escalation lands where your team already lives — with the evidence attached and a jump straight into the war room. No dashboard-watching required.

#sec-alerts
JaneApp9:41 AM
🔴 Critical finding confirmed on app.acme.io
SQL injection · /rest/products/search
SeverityCritical · CVSS 9.1
OWASPA03:2021 — Injection
Evidence2 exchanges · poc.sh
Statusproposed → validated
Open in the war room →
💬 2 replies · last from you
Burp Suite
Burp Suite

Commands Burp — not just scans

Connect over Burp's MCP server and Jane drives the whole toolkit — Intruder, Repeater, the Proxy history and the sitemap, not only the REST scanner. Works with Burp Pro on your machine (via a no-ports connector) or a cloud/Enterprise deployment. Every target-touching call is scope-gated, and she replays and re-proves each lead with her own reproducible evidence before it ever counts as a finding.

scanner · acme.io
TargetScannerProxyIntruderRepeater
SQL injection
Broken access (IDOR)
Reflected XSS
Missing CSP header
Verbose error
Request
GET /rest/products/search?q='+OR+1=1--
Host: app.acme.io
Response
HTTP/1.1 500 Internal Server Error
↳ differential confirms injection
MCP: Intruder · Repeater · Proxy driven · Jane replayed → 2 confirmed, 1 dropped
Rules of engagement

Built so an autonomous attacker can be trusted on a real target

A weapon this capable is only safe when it’s bounded and accountable. Jane is built around the scope you grant, the evidence she captures, and the identity of who gave the order.

Deny-by-default scope

Allowed hosts, ports, paths and methods are the front line. Every target-touching call is gated twice; an out-of-scope shot is refused before it leaves.

Proof of every kill

Findings carry replayable exchanges, a runnable PoC, a CVSS breakdown and counterevidence — cleared through a multi-gate validator before they confirm.

Chain of command

Authenticator MFA and passkeys, scoped API keys, and mission-scoped users — with an audit log of who gave the order, changed it, and read the results.

Ready when you are

Give the order

Set a scope, authorize the campaign, and watch Jane go to war on it — live, evidence-backed, and inside the lines you drew.