Integrate GitLab with BoostSecurity¶
BoostSecurity lets you connect your GitLab instance to scan repositories, provision security scanners onto the repositories, and merge commits for security issues.
Prerequisites¶
To integrate GitLab into BoostSecurity, you will need the following:
- 
Create a GitLab access token with the apiscope selected. This access token can be:In all cases, the token must have the apiscope enabled.- 
It is advised that a protected, non-human GitLab account (such as a service account or bot user) be used to generate the token. Using a token tied to an individual's personal account increases the risk of the integration breaking if that user is offboarded or removed due to internal changes. 
- 
The entity associated with the token (whether personal, group, or service account) must have Ownerpermissions for the repositories within the GitLab groups being ingested into Boost.
 
- 
- 
Create a boostrepository within your organization's SCM, which should contain aREADME.mdfile. To do this, go to your GitLab organization where you installed BoostSecurity and create a newboostproject that contains a Readme file.- Ensure that at least boostrepository owners can define pipeline variables. That is in GitLab Settings --> CI/CD --> Variables set the minimal role to use pipeline variables to the owner role.
 
- Ensure that at least 
1. Connect GitLab to BoostSecurity¶
To install the BoostSecurity integration for GitLab:
- 
Navigate to the Integrations page.
- 
Select the GitLab integration from the Availablesection and select the Install button.
- 
A window directs to providing the Access Token to GitLab. Provide the Access Token with the apiscope selected and select Next.
- 
Select the Group in GitLab: Once the Access Token is provided, the GitLab Group, which enables the integration, needs to be selected from the menu. 
- 
Select Complete. 
Once the installation is completed, the BoostSecurity GitLab card is added to the Settings > Integrations > Installed section. At this point, BoostSecurity integration is enabled for your GitLab group. Note that the steps can be repeated to allow integration with additional GitLab groups.
2. Zero Touch Provisioning for GitLab¶
- 
Go to the Integrations page, select your GitLab integration and click on the configuration tab. 
- 
On the ZTP column, you will notice that the status is set to Not Set. Click on the menu next to the status and select Enable. 
- 
The ZTP wizard configures your GitLab organization's boostrepository, where the GitLab pipeline definition (.gitlab-ci.yml) is located.
- 
Select the boostrepository on your organization from the dropdown as shown above and click the Next button.
- 
Authorize the BoostSecurity.io CI provisioning on all organizations. Click on the Authorize button at the bottom of the page. 
- 
The pipeline configuration is complete following a successful CI pipeline setup! Note By clicking the Enable Boost Recommended Scanners button, Boost will provision multiple scanners for every repository it has access to. These scanners will then request new scans to be conducted for each of those repositories. Please note that this process would have a financial impact on your services, so ensure that this is the correct course of action before proceeding. If you are connecting to a large collection of repos, you may want to enable scanning in a more targeted manner. 
Zero Touch Provisioning is now enabled!!!
3. Default Scanner Protection¶
After successfully integrating into your GitLab organization, enabling the BoostSecurity scanner is recommended.
To do this,
- 
Navigate to the Scanner Coverage page and select the Default Scanner Protection column for your GitLab integration. 
- 
Toggle SBOM, SAST, SCA, or Secrets to enable the BoostSecurity Scanner default protection on your GitLab resource.. 
Edit an installed BoostSecurity GitLab Integration¶
In the event an adjustment needs to be made to an installed GitLab Integration, the following instructions are provided:
- 
Navigate to the Integrations page.
- 
Click on the GitLab Integration Card underneath the Installedsection.
- 
Click the Configurationtab.
- 
Click the pencil icon associated with the GitLab Integration you wish to edit. 
- 
Provide an Access Token that has the apiscope and clickUpdate.












