Skip to main content

GitGuardian

GitGuardian is a secrets detection platform that integrates with your development workflow to detect and remediate leaked secrets across code repositories. You can bring code repository, secret incident, and incident definition data from GitGuardian into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with GitGuardian and how to obtain that information from GitGuardian. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select GitGuardian from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate GitGuardian with Brinqa:

  • API URL: The GitGuardian API URL. The default URL is https://api.gitguardian.com.

  • API key: The API key associated with your GitGuardian account.

Generate GitGuardian API keys

For the GitGuardian connector to access the GitGuardian API, you must provide an API key. GitGuardian supports two types of API keys: service accounts and personal access tokens. To use the connector, you need to create a personal access token. To do so, follow these steps:

  1. Log in to your GitGuardian workspace.

  2. Navigate to API > Personal access tokens and click Create token.

  3. Name your token and optionally set an expiry date.

  4. Under Scope, select the permissions required for the connector to read incidents, sources, and detectors.

  5. Click Create token and copy the generated API key. Store it in a secure location, as it cannot be viewed again.

note

If you do not have the permissions to create API keys, contact your GitGuardian administrator. For additional information, see GitGuardian documentation.

Additional settings

The GitGuardian connector contains additional options for specific configuration:

  • Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
  • Maximum retries: The maximum number of times that the integration attempts to connect to the GitGuardian API before giving up and reporting a failure. The default setting is 10.

Types of data to retrieve

The GitGuardian connector can retrieve the following types of data from the GitGuardian API:

Table 1: Data retrieved from GitGuardian

Connector ObjectRequiredMaps to Data Model
Secret IncidentYesIncident
Secret Incident DefinitionNoIncident Definition
SourceNoCode Repository
info

The GitGuardian connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from GitGuardian in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

Secret Incident

Table 2: Secret Incident attribute mappings

Source Field NameSDM Attribute
CustomTagResource.keyCUSTOM_TAG_KEYS
CustomTagResource.valueCUSTOM_TAG_VALUES
DestinationTicketResource.idDESTINATION_TICKET_IDS
DestinationTicketResource.linkDESTINATION_TICKET_LINKS
DestinationTicketResource.typeDESTINATION_TICKET_TYPES
FeedbackResource.emailFEEDBACK_EMAILS
IncidentResource.assigneeEmailASSIGNEE_EMAIL
IncidentResource.assigneeIdASSIGNEE_ID
IncidentResource.dateSOURCE_CREATED_DATE
IncidentResource.detector.detectorGroupNameTYPE
IncidentResource.gitguardianUrlGITGUARDIAN_URL
IncidentResource.gitguardianUrlURL
IncidentResource.hmslHashHMSL_HASH
IncidentResource.idINCIDENT_ID
IncidentResource.ignoreReasonIGNORE_REASON
IncidentResource.ignoredAtIGNORED_AT
IncidentResource.ignorerApiTokenIdIGNORER_API_TOKEN_ID
IncidentResource.ignorerIdIGNORER_ID
IncidentResource.incidentNameINCIDENT_NAME
IncidentResource.isVaultedIS_VAULTED
IncidentResource.occurrencesCountOCCURRENCES_COUNT
IncidentResource.regressionREGRESSION
IncidentResource.resolvedAtLAST_FIXED
IncidentResource.resolvedAtRESOLVED_AT
IncidentResource.resolverApiTokenIdRESOLVER_API_TOKEN_ID
IncidentResource.resolverIdRESOLVER_ID
IncidentResource.secretHashSECRET_HASH
IncidentResource.secretIdSECRET_ID
IncidentResource.secretRevokedSECRET_REVOKED
IncidentResource.shareUrlSHARE_URL
IncidentResource.statusPROVIDER_STATUS
IncidentResource.statusSOURCE_STATUS
IncidentResource.statusSTATUS
IncidentResource.statusSTATUS_CATEGORY
IncidentResource.tagsTAGS
IncidentResource.triggeredAtFIRST_FOUND
IncidentResource.triggeredAtTRIGGERED_AT
IncidentResource.validityVALIDITY
MatchResource.nameMATCH_NAMES
OccurrenceResource.authorInfoAUTHOR_INFO
OccurrenceResource.authorNameAUTHOR_NAME
OccurrenceResource.changeTypeCHANGE_TYPE
OccurrenceResource.filepathFILEPATH
OccurrenceResource.idUID
OccurrenceResource.kindKIND
OccurrenceResource.presencePRESENCE
OccurrenceResource.shaSHA
OccurrenceResource.source.fullNameSOURCE_NAME
OccurrenceResource.source.fullNameTARGETS
OccurrenceResource.urlOCCURRENCE_URL
PublicExposureResource.leakedOutsidePerimeterLEAKED_OUTSIDE_PERIMETER
PublicExposureResource.publicIncidentLinkedPUBLIC_INCIDENT_LINKED
PublicExposureResource.sourcePubliclyVisibleSOURCE_PUBLICLY_VISIBLE
SecretPresenceResource.filesFixedFILES_FIXED
SecretPresenceResource.filesPendingMergeFILES_PENDING_MERGE
SecretPresenceResource.filesRequiringCodeFixFILES_REQUIRING_CODE_FIX
SecretPresenceResource.inVcsIN_VCS
SecretPresenceResource.outsideVcsOUTSIDE_VCS
SecretPresenceResource.removedInVcsREMOVED_IN_VCS
SecretPresenceResource.removedOutsideVcsREMOVED_OUTSIDE_VCS
Secret Incident Definition

Table 3: Secret Incident Definition attribute mappings

Source Field NameSDM Attribute
DetectorResource.detectorGroupDisplayNameDETECTOR_GROUP_DISPLAY_NAME
DetectorResource.detectorGroupNameDETECTOR_GROUP_NAME
DetectorResource.familyDETECTOR_FAMILY
DetectorResource.natureDETECTOR_NATURE
IncidentResource.severitySEVERITY
IncidentResource.severitySEVERITY_SCORE
IncidentResource.severitySOURCE_SEVERITY
IncidentResource.tagsTAGS
SecretDetectorResource.categoryCATEGORIES
SecretDetectorResource.checkableCHECKABLE
SecretDetectorResource.displayNameDESCRIPTION
SecretDetectorResource.displayNameDETECTOR_DISPLAY_NAME
SecretDetectorResource.displayNameNAME
SecretDetectorResource.frequencyFREQUENCY
SecretDetectorResource.ignoredIncidentsCountIGNORED_INCIDENTS_COUNT
SecretDetectorResource.isActiveIS_ACTIVE
SecretDetectorResource.isRecommendedForBusinessIS_RECOMMENDED_FOR_BUSINESS
SecretDetectorResource.nameDETECTOR_NAME
SecretDetectorResource.nameUID
SecretDetectorResource.openIncidentsCountOPEN_INCIDENTS_COUNT
SecretDetectorResource.removedAtREMOVED_AT
SecretDetectorResource.resolvedIncidentsCountRESOLVED_INCIDENTS_COUNT
SecretDetectorResource.scansCodeOnlySCANS_CODE_ONLY
SecretDetectorResource.typeDETECTOR_TYPE
Source

Table 4: Source attribute mappings

Source Field NameSDM Attribute
Always "Code Repository"CATEGORIES
Always "active"STATUS
LastScanResource.branchesScannedLAST_SCAN_BRANCHES_SCANNED
LastScanResource.commitsScannedLAST_SCAN_COMMITS_SCANNED
LastScanResource.dateLAST_SCAN_DATE
LastScanResource.durationLAST_SCAN_DURATION
LastScanResource.failingReasonLAST_SCAN_FAILING_REASON
LastScanResource.progressLAST_SCAN_PROGRESS
LastScanResource.statusLAST_SCAN_STATUS
SourceResource.closedIncidentsCountCLOSED_INCIDENTS_COUNT
SourceResource.defaultBranchDEFAULT_BRANCH
SourceResource.defaultBranchHeadDEFAULT_BRANCH_HEAD
SourceResource.deletedDELETED
SourceResource.externalIdEXTERNAL_ID
SourceResource.fullNameNAME
SourceResource.healthHEALTH
SourceResource.idUID
SourceResource.monitoredMONITORED
SourceResource.openIncidentsCountOPEN_INCIDENTS_COUNT
SourceResource.sourceCriticalitySOURCE_CRITICALITY
SourceResource.typeSOURCE_TYPE
SourceResource.urlURL
SourceResource.visibilityVISIBILITY

APIs

The GitGuardian connector uses the GitGuardian REST API (v1). Specifically, it uses the following endpoints:

Table 5: GitGuardian API endpoints

Connector ObjectAPI Endpoint
Secret IncidentGET /v1/incidents/secrets
GET /v1/occurrences/secrets
Secret Incident DefinitionGET /v1/secret_detectors
GET /v1/incidents/secrets
SourceGET /v1/sources

Changelog

The GitGuardian connector has undergone the following changes:

Table 6: GitGuardian connector changelog

VersionDescriptionDate Published
3.0.0Initial Integration+ release.March 10th, 2026