Skip to main content

​
Overview

GitGuardian finds hardcoded secrets across your repositories, git history and CI pipelines. Tierity imports GitGuardian’s secret incidents so leaked credentials sit in the same queue, with the same deadlines, as everything else.

​
Prerequisites

  • A GitGuardian workspace and permission to create API tokens
  • Manage access (or higher) in Tierity

​
Credentials required

​
Setup

1

Create a token

In GitGuardian, go to API → Personal access tokens (or Service accounts) and create a token with the incidents:read scope. Copy it.
2

Connect in Tierity

Go to Config → Integrations → GitGuardian, enter the token (and base URL if you need one), and click Test connection.

​
What gets synced

Secret incidents with the detector that found them, severity, status, validity (whether the secret still works) and where it was found.

​
Disconnecting

Go to Config → Integrations → GitGuardian and click Disconnect, then revoke the token in GitGuardian.