---
title: "Container registries"
description: "Scan every new image that your GitLab container registry receives."
url: https://whitespots.io/docs/appsec-portal/integrations/container-registries
slug: appsec-portal/integrations/container-registries
publish_date: 2026-10-30T19:42:15.000Z
last_modified: 2026-10-30T19:42:15.000Z
---

# Container registries

A container registry integration watches the images in a GitLab container registry. When an image
gets a new tag, Portal adds the image as a Docker image asset if it isn't one
yet and runs an [audit](https://whitespots.io/docs/appsec-portal/find-vulnerabilities/audits) of the new tag. Auditor
pulls the image with the integration's token, so you don't enter the registry credentials anywhere
else.

GitLab is the only registry supported now. GitHub and Docker Hub are shown as **Coming Soon**.

Container registry integrations need a paid license. See [License](https://whitespots.io/docs/appsec-portal/administration/license).

## Connect

Open the settings, then **Container Registries** under **Integrations**, and click
**Add Container Registry**.

1. Choose the registry.
2. Enter the GitLab URL and a personal access token with the `read_registry` and `read_api`
   scopes. The form links to the page where you create the token.
3. Enter the **Registry domain**, for example `registry.gitlab.com`.

After you connect, Portal reads the tags that are already in the registry. They
are listed on the integration's page, and only tags that appear after this are scanned.

## Choose when to scan

| Trigger | How it works |
| --- | --- |
| **On webhook events** | GitLab tells Portal when a CI job finishes, and the new tags of that project are scanned. Copy the **Webhook URL** from the integration's page and add it to the project or group webhooks in GitLab with job events turned on. |
| **On schedule** | The registry is checked for new tags on a cron schedule. Webhook events are ignored, so you don't need the webhook. |

## Choose what to run

**Job sequence** sets the [sequence](https://whitespots.io/docs/appsec-portal/find-vulnerabilities/audits/sequences) that the audits
of new tags run. Leave it empty to use each asset's own sequence.

New images go to the default product, **Unsorted**. Move them to their products on the
[Assets](https://whitespots.io/docs/appsec-portal/products-and-assets/assets) page; the next tags are scanned in the product you chose.

## Image tags

The integration's page lists the tags that Portal has seen. Delete a tag from
the list to scan it again the next time it is found.

---

## Navigation

- Location: [Docs](https://whitespots.io/docs) > [Application Security Portal](https://whitespots.io/docs/appsec-portal) > [Integrations](https://whitespots.io/docs/appsec-portal/integrations)
- Previous: [Version control](https://whitespots.io/docs/appsec-portal/integrations/version-control)
- Next: [Task trackers](https://whitespots.io/docs/appsec-portal/integrations/task-trackers)