Connecting GitLab Issues to Drata allows for the automated checks and evidence collection to prove to auditors that your company follows its vulnerability management policy and procedures. For a more streamlined process, you can now connect through the GitLab Issues self-managed connection.
BEFORE DIVING IN
Make sure you have admin access to your company's GitLab Issues account.
Connect GitLab Issues self-managed to Drata
Select Connections on the side navigation menu.
Select the Available connections tab and then search for
GitLab Issues self-managedto select the connect button for the GitLab Issues self-managed connection.Within the connection drawer, enter the required information.
Account Alias: Enter a unique identifier or alias for your connection.
Hostname: Enter the URL where your GitLab self-managed instance is hosted (for example,
https://gitlab.example.com).Personal Access Token: You can use a Personal Access Token (PAT) to connect. Generate a PAT in your GitLab instance with the appropriate permissions and enter the PAT:
read_apiread_user
Security Label: Enter the label you use to categorize tickets as security issues within GitLab Issues.
Critical, High, Medium, and Low Severity Level: Enter the corresponding severity level labels you use for your tickets in GitLab Issues for each severity level field within the connection drawer.
Write Access: Toggle on if you would like to create tickets in GitLab Issues. Toggle off if you do not want to create tickets.
