Integrate your GitLab Enterprise with CloudDefense to harness advanced security capabilities directly within your enterprise's development workflow.
Pre-requisites:
You should be signed in with CloudDefense.ai. If not, please refer to our guide on creating a CloudDefense.ai account.
Access to a GitLub Enterprises account and permissions.
Step 1: Get GitLab Enterprise Link and Generate Access Token
Enterprise Token
Confirm that you have a GitLab Enterprise account. You can view your enterprise details by navigating to GitLab Group Settings.<https://gitlab.com/dashboard/groups>
If you lack an enterprise account, you can set one up here.<https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com>
Generate Access Token
To generate an access token essential for integration go from profile dropdown Preference > Access token to create a new token. You can directly go here.<https://gitlab.com/-/profile/personal_access_tokens>
After creating the token, ensure to copy it for integration use.
Step 2: Configure Your Integration
Enter Details for Integration:
Once your account is prepared for integration, proceed to the GitLab Enterprise tab, where you will see options to:
Enterprise Link: Input the link to your GitLab Enterprise environment.
Enterprise Access Token: Enter the access token you previously generated and copied
Once you've provided the required information, click the green Configure button on the left bottom of the screen to finalize the integration.
By following these instructions, you'll successfully integrate GitLab Enterprise with CloudDefense, enabling sophisticated security measures and streamlined workflow integration.
With your GitLab Enterprise integration complete, you are ready to scan your repositories. For step-by-step guidance on starting scans and analyzing results, please see our Scan Repos Documentation. This resource will assist you in effectively managing and securing your repositories.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article