Getting Started with PRO
Load the ADscan PRO Docker image and configure the launcher in under 10 minutes.
Prerequisites
- Linux x86_64 host
- Docker Engine installed and running (
docker versionto verify) - The
adscan-pro-latest.tar.gzfile you received - ADscan launcher installed:
pip install adscanorpipx install adscan
Verify Docker is running
docker versionIf you see Cannot connect to the Docker daemon, start it:
sudo systemctl start docker
# Add your user to the docker group to avoid sudo on every command:
sudo usermod -aG docker "$USER" && newgrp dockerLoad the PRO image
docker load < adscan-pro-v8.0.0.tar.gz # replace with the filename you receivedVerify both tags loaded:
docker images | grep adscan-pro
# adscan/adscan-pro v8.0.0 <id> <size>
# adscan/adscan-pro latest <id> same ID — both point to the same imagePoint the launcher to the PRO image
Two options — pick whichever fits your setup:
Option A — --image flag (recommended if you use both LITE and PRO)
Pass --image directly to any launcher command. Clean, no environment setup needed:
adscan start --image 'adscan/adscan-pro:latest'
adscan ci --image 'adscan/adscan-pro:latest' --generate-report --frameworks iso27001 ...Option B — environment variable (recommended if you always use PRO)
Set once in your shell profile and every adscan command uses PRO automatically:
# Add to ~/.zshrc or ~/.bashrc
export ADSCAN_DOCKER_IMAGE=adscan/adscan-pro:latestsource ~/.zshrc # reload
adscan ci --generate-report --frameworks iso27001 ... # PRO used automaticallyBoth methods work identically. --image takes precedence over the env var if both are set.
Install supporting tools
This sets up BloodHound CE and validates the runtime environment:
adscan installIf you already have LITE installed
adscan install will pull BloodHound CE and configure it.
It skips pulling the main ADscan image when ADSCAN_DOCKER_IMAGE points to an already-loaded local image.
Verify PRO is active
adscan startYou should see PRO in the version line of the startup banner:
ADscan 8.0.0 PRO
Automate the AD kill chain.If it says LITE, the ADSCAN_DOCKER_IMAGE variable is not set correctly. Exit ADscan (exit or Ctrl+D) — you're ready to run scans.
One-time setup complete
From this point, use adscan ci --generate-report for automated compliance scans. See Generate a Report for the full command reference.
Updating PRO
When you receive a new version:
docker load < adscan-pro-v8.1.0.tar.gzUse the new version explicitly in your command:
adscan ci --image 'adscan/adscan-pro:v8.1.0' --generate-report ...Previous versions remain available for rollback — they stay loaded until you explicitly remove them:
# Roll back to previous version instantly if needed:
adscan ci --image 'adscan/adscan-pro:v8.0.0' --generate-report ...
# Remove an old version when no longer needed:
docker rmi adscan/adscan-pro:v8.0.0