Connecting GitLab

Connect Seal to a GitLab instance using a personal access token.

Connecting GitLab gives the Seal Platform read access to the GitLab projects you choose, so they can run in source code mode. The GitLab integration covers discovery; remediation runs through the Seal CLI in your CI/CD pipeline (or one of the other deployment methods).

Before you start

• You have the Admin or Sealer role in Seal.

• You have the URL of your GitLab instance (for example, https://gitlab.com/your-organization/ for GitLab.com, or your self-hosted URL).

• You have a GitLab personal access token with the api scope, generated by a user with Developer, Maintainer, or Owner role on the projects you want to import.

Steps

1. Open the Projects page in the Seal UI.

2. Click Import projects and select GitLab from the dropdown.

3. If GitLab is not yet connected, the modal opens at the LOGIN step. Fill in:

   • GitLab URL (the URL of your GitLab instance).

   • Personal Access Token (with the api scope).

4. If GitLab is already connected, the modal opens directly at the IMPORT step.

5. In the IMPORT step, select the GitLab projects you want to import as Seal Projects, then confirm.

Connecting to GitLab

Verify

Each imported project becomes a Seal Project in source code mode. The first scan starts in the background; results appear on the Protection page's Vulnerable packages tab as the scan completes.

Related

• Source code mode: what Seal sees once GitLab is connected.

• Managing source control connections: viewing or disconnecting the GitLab installation.