GitGuardian

GitGuardian is the code security platform. With automated secrets detection and remediation, GitGuardian platform enables Dev, Sec, and Ops to collaborate on a Secure Software Development Lifecycle. More information can be found at GitGuardian website.

Integration Method: API

Tables: Account Change (3001), Authentication (3002), Incident Finding (2005)

The integration supports the following events.

This integration supports the following versions.

Prerequisites

• The user should have access to a GitGuardian workspace with Admin privileges.

• The user should have access to DataBee console.

Configuration Overview

1. Generate an API token with the required scopes:

   1. audit_logs:read

   2. incidents:read

2. Add GitGuardian in the DataBee console with the below parameters.

   DataBee Parameter	GitGuardian Parameter
   Token	Personal Access Token

GitGuardian Configuration

1. Log on to GitGuardian Workspace using a user account with Admin privileges.
    

2. Navigate to Settings.

   
   

3. Click Personal access tokens.

    

4. Click + Create token button.
    

5. Give an appropriate token name and select Never from the dropdown for ‘Expires’. Make sure to select incidents:read under incidents section.
    

6. Select audit_logs:read and then click Create token.
    

7. Click the Copy icon and store the generated Personal access token somewhere safe as it will be required later.
   
   

DataBee Configuration

1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
    

2. Search for the GitGuardian and click it.
    

3. Click on the API Ingest option for collection method.
    

4. Enter feed contact information and click Next.

   

5. In the configuration page, confirm the following:

   • API Base URL: this is the base URL that DataBee will interact with.

   • Authorization Method: Bearer Token

   • Token: paste the Personal Access Token generated earlier in the GitLab console.

   • Event types: preselected for all the event types that integration pulls.
      

6. Click Submit.

Troubleshooting Tips

• Ensure the token is pasted correctly. Since you cannot view the token after the 1^st 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 GitGuardian scopes/permissions are correct.