GitGuardian
GitGuardian is a comprehensive secrets detection and security monitoring platform designed to protect organizations from exposed credentials, API keys, certificates, and other sensitive information in source code and digital environments. The platform specializes in identifying and preventing secrets sprawl across development workflows, code repositories, and collaboration tools.
| Category | Secrets management |
| Direction | Query source |
| Sign-in | Personal Access Token |
| Query languages | SQLite |
| Website | gitguardian.com |
Before you start
Huntbase signs in to GitGuardian with Personal Access Token. Create the credential in GitGuardian first, then keep it to hand for the Connect step.
- In the GitGuardian dashboard, go to the API section of your workspace, open Personal access tokens, and select Create token.
- Name the token after its use case and choose an expiry.
- Select the scopes
incidents:read,audit_logs:readandmembers:read. - Click Create token and copy it. It will not be visible again.
Permissions:
incidents:readaudit_logs:readmembers:read
- With a personal access token,
audit_logs:readis available only to Managers. - A personal access token only returns what its owner can see in the dashboard.
For the vendor's own instructions, see GitGuardian personal access token documentation.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect GitGuardian
- Go to Connections and click New connection, or click New connection on the GitGuardian product page.
- On Product, pick GitGuardian and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Credentials
The only Method is Personal Access Token. Enter a Credential label (for example Production), then fill in:
| Field | Required | Notes |
|---|---|---|
| Personal Access Token | Yes | Secret — not shown again after you save it. |
Query it
Once connected, GitGuardian can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| SQLite | SQL across this source and every other connected source. |
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog