Launching a New Mission

The New Mission view is where you define an engagement and hand it to the agent. Fill in the brief, choose your cases and mode, confirm authorization, and launch.

The mission brief

Field	What to enter
Client name	Who the engagement is for. (Required.)
Engagement title	A label for the mission (e.g. Penetration Test & Security Assessment).
Target IP / host	The IP address or host to test.
Target URL / site	The web address to test.
VHost	An optional virtual host to send with requests.
Network CIDR	An optional range for LAN discovery from this workstation (e.g. 192.168.1.0/24).
Additional scope	Extra in-scope targets or notes.
Operator information	Credentials to try, VPN context, known accounts, prior findings, business constraints.

At least one target

You must provide an IP, a URL, or enable LAN discovery with a CIDR. The launch button stays disabled until the brief is valid.

Choose a mode

Pick Auditor (proportionate, compliance-oriented) or Attacker (maximum-depth adversary simulation). See Engagement modes.

Attacker mode is Pro

Launching in Attacker mode requires an active Pro subscription. On the free trial you can run Auditor missions.

Select engagement cases

Choose which engagement cases to cover — web, network, identity, cloud, endpoint, and more. Each mode pre-selects a sensible default set, which you can adjust. You must keep at least one case selected.

Confirm authorization

Before a mission can start you must confirm that penetration testing is authorized for this target. This written-mandate confirmation is enforced by the app — without it, the mission will not launch.

Launch and watch

Click Launch. The mission starts and the New Mission nav item shows a live badge. From here you can watch:

• the workflow phases light up (recon → enumeration → exploitation → privilege escalation → credentials → report),
• the Activity stream of exact tools and commands,
• new vulnerabilities appear as they're confirmed,
• the cartography map fill in,
• and finally a PDF report when the engagement is done.

Reusing what it learned

If you've tested a target before, AgentRidge reuses prior context — known endpoints, suspected flaws, credential hints — to prioritize, then re-verifies everything live in the new run. This is why later engagements against the same target tend to go deeper. See the mission lifecycle.

Next: interactive Chat →