Inside the Docker connector: registries and self-managed Docker hosts

What CloudMonitor reads from your container registries and from a Docker Engine API over mutual TLS, the findings it raises, and what it cannot reach.

The Docker connector has two halves, both read-only and both scanned on a schedule: exposure checks hourly, everything nightly. You can connect either or both.

Container registries

Connect Docker Hub with your namespace and a read-only personal access token, GitHub Container Registry with an owner and a token scoped to read:packages, or any self-hosted registry that speaks the Docker Registry v2 API — the open-source registry:2, Harbor, Nexus, Artifactory, GitLab or Quay — by its https URL, with read-only credentials or none.

Docker Hub, GHCR and plain Registry v2 publish no vulnerability results we can read, so each image says so plainly instead of reading as clean. ACR, ECR and GAR registries are supported by the same scanner and set up on request; ECR and GAR do return their own scan results.

Self-hosted registries and Docker hosts have been tested against a real registry:2 and a real Docker Engine; the Docker Hub and GHCR connections are in Beta, written to those services' documented APIs but not yet validated on a live customer account.

Docker hosts

For a host, CloudMonitor is a read-only client of the Docker Engine API over TCP with mutual TLS — Docker's own standard secured-remote-API setup. You paste the CA, a client certificate and its key; they are stored encrypted. There is no "trust any client" mode. Every call is a GET: container and image inventory, one stats snapshot per running container, and daemon version and info.

What it can't reach

The scanner runs on our infrastructure and only connects to public addresses: a host or registry on a private network, an internal-only name, or a daemon exposed only as a local Unix socket cannot be scanned. An agent for air-gapped hosts is not built yet. Registry URLs must be https.

What it doesn't do

Doesn't push, delete or pull image layers; doesn't create, start, stop or exec into containers; doesn't read mounted file contents; and doesn't run its own vulnerability scan of your images. Swarm services are not scanned today. Connection details are on the Connectors page.

← Back to all posts