Integrate with GitLab Self-Managed


Integrating Bridgecrew with GitLab Self-Managed makes it possible for Bridgecrew to scan your Infrastructure-as-code files (Terraform and CloudFormation) and monitor configuration issues in development.


For details on integrating Bridgecrew with, see Integrate with GitLab.

Getting Ready

IP-based Network Access
If your organization requires IP-based access to its network, add all three IP addresses below to your ingress access configuration.

For Prisma cloud console integration - discover relevant IP addresses here

For Bridgecrew platform - Bridgecrew performs load balancing across these addresses.

How to Integrate

Part 1 - In Bridgecrew

  1. From Integrations Catalogue, under Code Integrations, select GitLab Self-Managed .
  1. Enter your GitLab Self-Managed domain, for example,, then select Register. A new tab opens for registering a new OAUTH app in GitLab Self-Managed.
  1. Copy Application Name and Redirect URI from the Register OAUTH app step.

Part 2 - In GitLab Self-Managed

  1. Paste the copied values for Name and Redirect URI from the previous step in Bridgecrew.
  1. Check API.
  2. Select Save Application. An Application Summary page opens in GitLab Self-Managed.



The Confidential setting shown in the image above, is checked by default in GitLab Self-Managed, however, it is not required for Bridgecrew Cloud.

  1. Copy the Application ID and Secret values.

Part 3 - In Bridgecrew

  1. Paste the copied values in the Application ID and Secret fields, then select Authorize.

Part 4 - In GitLab Self-Managed.

Select Authorize.
You are then redirected back to Bridgecrew on the same tab.


Part 5 - In Bridgecrew

  1. Select one of the following options then select Next:
  • Permit all existing repositories
  • Permit all existing and future repositories
  • Choose from the repository list.
    If choosing from the repository list, select the relevant repositories.
  1. When the message "New account successfully configured" appears, select Done.
    Note: after the next GitLab Self-Managed scan, the scanned repository will appear in the Integrations grid; for further details, see here.


The image below shows an example of a Bridgecrew comment on a license compliance error.