Home / Goals

Mission goals

Write the mission. Get a verdict.

Tell Autopilot what to prove IDOR on /api/users, SQLi on login, OWASP on payments, or a named checkout flow. It compiles a MissionObjective, sends the right specialists first, and can stop when it is proved.

Prove a classScope a flowOWASP coverageOr run full Autopilot
mission_compiler.sh
live proved
$ guardial run --goal
"Prove IDOR / BOLA on /api/users and stop when confirmed"
recon
compile
run
verdict
compiled output
{
  type:          "vulnerability",
  targets:       "/api/users",
  classes:       "idor, bola",
  constraints:   "stop_on_prove, needs_session",
  success:       "Foreign User B reads User A object; control ID 404s"
}
01

Compile the mission

Scan intent → MissionObjective: statement, targets, attack classes, success criteria, and prerequisites (e.g. identity session).

type
vulnerability
targets
/api/users
classes
idor, bola
constraints
stop_on_prove, needs_session
02

Seed the Strategist

Only the specialists that match your goal run first. Budget is focused, not sprayed across the whole surface.

session_api_diffbola_probeoracle_confirm
03

Prove, then stop

Oracles confirm exploitability. When proved, Autopilot can stop early so wallet spend goes to evidence, not noise.

provedrefutedpartialblocked
success criteria

Foreign User B reads User A object; control ID 404s

vulnerability

Prove a class

IDOR, SQLi, XSS, and SSRF on the paths you care about, with a clear prove or refute verdict.

asset / flow

Assess a surface

Checkout, admin, or wallets. Focus Autopilot on a named API or user journey.

coverage

Checklist depth

OWASP-style coverage runs that still demand oracle confirmation, not grepped signatures.

outcome

Adversary goal

Frame the impact you care about (privilege, data access, forged credit) and hunt until blocked or proved.

hunt

Open-ended hunt

Budget-bound exploration when you know the risk area but not the exact vuln class.

autopilot

No goal needed

Empty mission = full Autopilot. Map the surface and run all permitted specialists within RoE.

Goal vs Autopilot

Focus the budget, or map everything

A named mission seeds the right specialists and can stop when proved. An empty goal is still full Autopilot inside your Rules of Engagement.

Mission goal
  • Named targets and attack classes
  • Specialists that match the objective run first
  • Stop on prove so wallet spend goes to evidence
Full Autopilot
  • Empty mission, whole permitted surface
  • All specialists allowed by RoE
  • Same oracle confirmation, broader coverage
FAQ

Questions teams ask

Ready when you are

Try Autopilot on your app

Create a free account, get ₹350 credit, and run a Quick scan with a mission goal or full Autopilot.

Keep reading

More guides