API Scanner - Self-Hosted Deployment

API Scanner is an automated API security testing tool that scans REST and SOAP APIs for vulnerabilities using OpenAPI/Swagger specifications and WSDL files.

Prerequisites

• Docker Engine 20.10+
• Docker Compose v2
• Python 3.6+ (for setup script)
• 8 GB RAM minimum (16 GB recommended)
• 20 GB disk space

Quick Start

1. Clone this repository

git clone https://github.com/CSPF-Founder/api-scanner-docker.git
cd api-scanner-docker

2. Run setup

python3 setup.py

The script will:

• Generate secure random passwords for all services
• Auto-detect your timezone
• Generate a self-signed TLS certificate (or use your own if already in ./certs/)
• Write the .env configuration file
• Offer to start the Docker Compose stack

3. Access the panel

Open https://localhost:4455 in your browser.

If using a self-signed certificate, your browser will show a security warning - proceed to accept it.

Manual Setup

If you prefer to configure manually instead of using the setup script:

1. Copy the example environment file:

cp .env.example .env

2. Edit .env and update:

   • All change_me_* passwords with strong random values
   • CSRF_KEY with a random 32+ character string
   • ZAP_API_KEY with a random string
   • TRUSTED_ORIGINS with your domain (e.g., https://scanner.yourcompany.com)
   • Ensure passwords in DATABASE_URI and MONGO_DATABASE_URI match the individual password variables

3. Start the stack:

docker compose up -d

Architecture

Configuration

All configuration is done through the .env file. See .env.example for all available options.

Key Settings

Data Persistence

All data is stored in Docker named volumes:

• mariadb_data - User accounts, roles, sessions
• mongodb_data - Scan records, results, reports
• scanner_data - Work files, uploaded specs, generated reports

Updating

docker compose pull
docker compose up -d

Stopping

docker compose down

To remove all data (destructive):

docker compose down -v

Troubleshooting

Check logs:

docker compose logs api-scanner
docker compose logs zap

Check service health:

docker compose ps

ZAP not starting: Ensure at least 4 GB of free RAM. ZAP requires ~3 GB.

Panel not accessible: Verify TLS certificates are in ./certs/ and TRUSTED_ORIGINS matches your URL including the port (e.g., https://localhost:4455).

Database connection errors: Wait 30-60 seconds after first start for databases to initialize.

Documentation

Full user manual: https://cspf-founder.github.io/api-scanner-docker/