--- title: "GitLab Security" slug: "gitlab-security" updated: 2026-10-26T14:42:28Z published: 2026-10-26T14:42:28Z canonical: "docs.databee.buzz/gitlab-security" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt > Use this file to discover all available pages before exploring further. # GitLab Security GitLab integrates a wide array of security tools directly into the development workflow including SAST, DAST, container scanning, SCA, secret detection, and fuzz testing. This enables developers to identify and address security vulnerabilities. More information can be found at [GitLab's Website](https://about.gitlab.com/platform/). **Integration Method:** API **Tables:** Vulnerability Findings (2002), Detection Findings (2004) This integration supports the following events. | **Event** | **Description** | | --- | --- | | Vulnerabilities | Get vulnerability information for the queried project folder. | This integration was tested against the following versions | | | | --- | --- | | GitLab Version Tested | GitLab Enterprise Edition 17.9.0-pre | | GitLab API version | v4.0 | ## Prerequisites - The user should have GitLab Administratorprivileges to create API tokens. - The user should have DataBeeconsole access. > **Test Connection** > > The GitLab Security integration supports the **Test Connection** button in the DataBee feed configuration. Use this to validate that DataBee can successfully reach the GitLab Security API with the credentials you have provided before saving the feed configuration. ## Configuration Overview 1. Generate an [API token](/docs/gitlab-security#personallaccesstoken) on the GitLab console with the required scopes. 2. Add the [GitLab data feed integration](/user-manual/docs/gitlab-security#databee-configuration) in the DataBee console with the required API token. | **DataBee Parameter** | **GitLab Parameter** | | --- | --- | | Token | [Personal Access Token](/docs/gitlab-security#personallaccesstoken) | ## GitLab Configuration Start by creating an API Token for the integration. 1. Login to your [**GitLab account**](https://gitlab.com/users/sign_in/)which has Administrator privileges. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-cxn0tlj5.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 2. In the upper-left corner, select the **Avatar**, then click **Preferences**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-9qae5ikk.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 3. Select the **Access tokens** from the side bar. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-ac6vrmlu.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 4. Click **Add new token** button under **Personal access tokens.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-9smbh9vv.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 5. Fill in a ‘Token name’, ‘Tokendescription’ and ‘Expirationdate’. Choose a 12-month expiration. Longer expiration times can minimize disruption. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-j87qzcq7.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 6. Select the following scopes and click **Create personal access token.** 1. read_api 2. read_user 3. read_repository ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-ev0jczfw.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 7. Copy and save the generated **Personal access token**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-2gfzgb84.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) > Note: > > Copy and save the personal access token. The personal access token cannot be shown again. The credentials will expire in 12 months, you will have to generate them again and update them in DataBee as well. ## DataBee Configuration 1. Login to the DataBee console, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-oqwlvn1b.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 2. Search for the GitLab Security option using the search bar in the **Add New Data Feed** page. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-xifwqbuk.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-hmj5n19b.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-zu6vv8v7.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 5. In the configuration page, confirm the following: - Authorization Method: Bearer Token - API Base URL: this is the base URL that DataBee will interact with. - Token: paste the [Personal Access Token](/docs/gitlab-security#personallaccesstoken) generated earlier in the GitLab console. - Event types: Preselected for all the event types that integration pulls. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-security-mar2025-image-y6bawn9y.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A23%3A30Z&se=2026-10-30T12%3A23%3A30Z&sr=c&sp=r&sig=j%2FdzmX3Km2fykDecfQuGsfpdsJ7pIqW5iqLyT99pPag%3D) 6. Click **Submit.** ## Troubleshooting Tips - Ensure the token is pasted correctly. Since you cannot view the token after the 1st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed. - Ensure the GitLab scope/permissions is correct.