Skip to main content

Access the Invicti registries

This document explains how to authenticate with and pull images from the Invicti Docker registries and Docker Hub, which host the Invicti Scan command-line tool Docker image for use in CI/CD integrations.

1. Invicti private registries

Invicti provides two private registries depending on your deployment type:

1.1 On-demand registry

Registry URL: platform.invicti.com

Use case: For Invicti Platform on-demand deployments

Authentication credentials:

  • username: Your Invicti Platform login email address
  • password: Your active Invicti license key
Important

You need these credentials to pull Docker images. Use your CI/CD tool's secret management features to store them securely.

Docker login command:

docker login platform.invicti.com \
-u <your-email@example.com> \
-p <your-license-key>

Pulling the image:

docker pull platform.invicti.com/invicti-platform/invicti-scan-cli

1.2 On-premises registry

Registry URL: platform-registry.invicti.com

Use case: For Invicti Platform on-premises deployments

Authentication credentials:

  • username: Your Invicti Platform login email address
  • password: Your active on-premises license key
Important

This registry requires an on-premises license key. The on-demand license key won't work for this registry.

Docker login command:

docker login platform-registry.invicti.com \
-u <your-email@example.com> \
-p <your-on-premises-license-key>

Pulling the image:

docker pull platform-registry.invicti.com/invicti-platform/invicti-scan-cli

2. Docker Hub (public registry)

If you prefer not to authenticate or need access to a public version, you can use the official image from Docker Hub.

Docker Hub Image URL: docker.io/invicti/scan-cli

Pulling the image:

docker pull invicti/scan-cli
Important

This public image may have fewer features or a delayed release cycle compared to the private registries. Always verify version compatibility.

Best practices

  • CI/CD security: Store credentials in environment variables or secret managers
  • Least privilege: Use automation-scoped credentials where possible
  • Logout after use (for local testing):
# For on-demand registry
docker logout platform.invicti.com

# For on-premises registry
docker logout platform-registry.invicti.com

Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center

Was this page useful?