Documentation / Application Security

On Premise Wizard

On-Premise Discovery & Pentest

Run discovery and PAC pentests against on-premise targets using the Prancer PAC CLI. The CLI is installed on a machine inside your network, given an API token, and pointed at a collection in the Prancer portal.

Before you start

  • An API token — see Create a token.
  • A Linux host with Docker installed and outbound HTTPS access to:
  • portal.prancer.io
  • <customer-id>.core.windows.net (or *.core.windows.net)
  • The on-premise IP ranges you want to scan (include and exclude).

Step 1 — Create an API token

Generate an API token in the Prancer portal. See Token for the full procedure.

Step 2 — Install Prancer PAC

1. Download the latest CLI:

``bash curl -LO https://pacshare001.blob.core.windows.net/cli/prancer-pac-latest.tar.gz ``

2. Extract and install:

``bash tar -xvf prancer-pac-latest.tar.gz cd prancer-pac-latest/ sudo chmod 0777 install.sh sudo ./install.sh ``

3. Verify:

```bash prancer-pac version

The version of prancer pac is 1.4.4 linux/amd64

```

Step 3 — Run the Autonomous Discovery Wizard

1. In the Prancer portal, open the Autonomous Discovery Wizard. 2. Select On Premise and enter your IP address ranges. 3. Submit. The portal returns a one-line CLI command:

``bash prancer-pac discovery -i <tenant> -t <token> -c <collectionId> ``

4. Run the command on your on-premise host to start discovery.

Step 4 — Verify inventory

Open Inventory Management in the portal — every host discovered by the CLI appears in the list with its generated PAC manifest.

Step 5 — Run the pentest

1. Open the relevant PAC manifest in Inventory Management and copy the configuration ID at the top of the file. 2. Launch the pentest from the on-premise host:

``bash prancer-pac pentest \ --config CONFIGURATION_ID \ -d prod \ --customer abccustomer \ --token APITOKEN ``

3. Stream logs while the scan runs:

``bash docker logs prancer-scanner -f ``

Step 6 — Review results

Findings appear in the portal under Application Findings when the run completes. See Pentest Findings.

Warning: On-premise scans can be heavy. Always confirm your scope and rate limits with the asset owner before running attacks.

Troubleshooting

  • Discovery returns no hosts — confirm the host running the CLI can reach the target IP range and that the firewall allows the outbound calls listed in *Before you start*.
  • prancer-pac not found — re-run sudo ./install.sh and check which prancer-pac.
  • Pentest never reports back — check docker logs prancer-scanner -f for connectivity errors to *.core.windows.net.

Next steps