Documentation / Home

Quick Start

Quick Start

Get from zero to your first autonomous pentest in under 15 minutes. This guide walks you through the five tools you'll use most often in Prancer and points you to deeper docs for each.

Tip: if this is your very first time, start with the Autonomous Security Wizard — it discovers your environment and runs an end-to-end scan with almost no configuration.

Before you start

1. Autonomous Security Wizard

Discover assets and run pentests against your cloud or domains with one wizard.

What it does

  • Crawls your cloud or domains to find assets.
  • Runs CSPM checks against security best practices.
  • Identifies pentestable resources, generates a PAC config, and (optionally) runs the pentest.

Steps

1. Pick a cloud environment *(or just enter domains)*. 2. Choose Auto Discover or Auto Discover and Emulate Attacks. 3. Start the run — connectors, if any, are shown. 4. Review results in Collection Management (cloud) or Inventory Management (domains).

→ Full guide: Autonomous Security Wizard

2. PAC Configuration Wizard

Use this when you want fine-grained control over a specific application.

Five-step flow

1. Connect to your cloud. Use an existing connection or create one with tenant ID, service principal, and key. The SP needs read, pentest-resource-create, and key vault permissions. 2. Describe the application. Name, type, risk level, compliance requirements, and schedule. Decide whether the scanner should stop or be deleted after the run. 3. Set up the scanner. Reuse an existing one or spin up a new instance; pick External or Internal pentest and the relevant subscription/region. 4. Pick a target. Manual URL or auto-discovered endpoint, hosted internally or external. 5. Configure auth. Form-based, NTLM, JSON, Azure AD, or JWT. Cloud secrets live in the Vault. 6. Review and submit the PAC file — the pentest starts immediately.

Note: results land on the Pentest Findings page within minutes.

→ Full guide: PAC for Azure

3. Infra (CSPM) Wizard

Connect a cloud subscription for continuous compliance monitoring.

Steps

1. Pick a collection name and the wizard type for your cloud. 2. Enter connection details (tenant ID, service principal info). 3. Choose Monitor *(report only)* or Monitor and Remediate *(auto-fix)*. 4. Set a one-time or recurring schedule. 5. Load subscriptions, pick one, and finish.

Prancer creates the connector, snapshot, and compliance configs, runs the crawler, and evaluates policies. View results in Infra Findings and runtime details in Logs.

→ Full guides: Wizard – AWS · Wizard – Azure · Wizard – GCP

4. Custom Attacks

Bring your own business-logic or zero-day attacks into Prancer.

You'll need three things

  • A CVE entry in your PAC config that references the attack.
  • A Git Connector so Prancer can pull the attack from your repo.
  • A Vault entry for the Git access token.

Steps

1. Push the attack script and its metadata YAML to a Git repo. 2. Store the Git access token (read-only on the target repo) in the Vault. 3. Create and upload a Git Connector JSON file to the collection. 4. Generate a PAC config via the wizard. 5. Add the custom attack CVE block to the PAC config and save.

→ Full guide: Custom Attack

5. User Management

Invite teammates and control what they can see.

  • Roles — create roles with specific permissions.
  • Invites — invite by email; users set their own password.
  • Permissions — newly registered users have *no* access until you assign a role.

→ Full guide: User Management

Next steps