GitKraken
Connect GitKraken to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your GitKraken connection as version control evidence. Automated collection is not available for this provider yet.
| Category | Version Control |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In GitKraken:
- Go to your account on gitkraken.dev (https://gitkraken.dev/account).
- Open the Security settings tab.
- Under API keys, click Create API key.
- Give the key a name, choose the organization it applies to, and set an expiration.
- Click Create API key, then copy the key (it looks like gk_tkn_...). GitKraken shows it only once.
Where to find the other values:
- Base URL (optional): GitKraken documents the API base URL as https://api.gitkraken.dev.
- Account / Org / Workspace (optional): The organization you choose when creating the API key on gitkraken.dev.
GitKraken shows the secret only once, so copy it before you leave the page.
Source is GitKraken's Insights API help page (plan: GitKraken Insights; role: an account that can create API keys for your organization). The page does not document read-only scopes for API keys, so no least-privilege option could be sourced. If a key is exposed, delete it in the Security tab and create a replacement.
Source: help.gitkraken.com, checked 2026-10-07.
-
On Compliance › Connectors, open GitKraken, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
GitKraken publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Version Control connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks