Validity checks | GitLab Docs
/ Validity checks Tier : Ultimate Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated Introduced in GitLab 18.0 with a feature flag named validity_checks . Disabled by default. Additional access introduced in GitLab 18.2 with a flag named validity_checks_security_finding_status . Disabled by default. Enabled on GitLab.com in GitLab 18.5. Changed from experiment to beta in GitLab 18.5. Generally available in GitLab 18.7.
Feature flag validity_checks_security_finding_status removed. Generally available in GitLab 18.7. Feature flag validity_checks is enabled by default. Removed feature flag validity_checks in GitLab 18.8. The availability of this feature is controlled by a feature flag. For more information, see the history. GitLab validity checks determine whether a secret, like an access token, is active. A secret is active when: It is not expired.
It can be used for authentication. Because active secrets can be used to impersonate a legitimate user, they pose a greater security risk than inactive secrets. If several secrets are leaked at once, knowing which secrets are active is an important part of triage and remediation. Enable validity checks Prerequisites: You must have a project with pipeline security scanning enabled. Your instance must have outbound network access to partner validation APIs.
To enable validity checks for a project: In the top bar, select Search or go to and find your project. In the left sidebar, select Secure > Security configuration . Under Pipeline Secret Detection , turn on the Validity checks toggle. GitLab checks the status of detected secrets when the secret_detection CI/CD job is complete. To view a secret’s status, view the vulnerability details page. To update the status of a secret, for example after revoking it, re-run the secret_detection CI/CD job.
To turn on validity checks at the group level, as a user with the Security Manager, Maintainer, or Owner role, use a GraphQL API mutation : graphql mutation { setGroupValidityChecks ( input : { validityChecksEnabled : true , namespacePath : "my-group/my-subgroup" , projectsToExclude : [ 100 , 105 , 108 ] }) { clientMutationId validityChecksEnabled } } Coverage Introduced support for external service tokens in GitLab 18.7 with a feature flag named secret_detection_partner_token_verification .
Enabled by default. Generally available in GitLab 18.8. Expanded validity checks for external service tokens in GitLab 19.3. Feature flag secret_detection_partner_token_verification removed in GitLab 19.4. Expanded validity checks to more GitHub token types in GitLab 19.4. Expanded validity checks to more OpenAI token types in GitLab 19.5. Validity checks support the following secret types: GitLab tokens: GitLab personal access tokens Routable GitLab personal access tokens GitLab deploy tokens GitLab Runner authentication tokens Routable GitLab Runner authentication tokens GitLab Kubernetes agent tokens GitLab SCIM OAuth tokens GitLab CI/CD job tokens GitLab incoming email tokens GitLab feed tokens (v2) GitLab pipeline trigger tokens External service tokens: Adafruit IO keys Anthropic API keys Asana personal access tokens AWS IAM long-term access key IDs (beginning with AKIA ) Beamer API tokens Brevo API keys Contentful personal access tokens Datadog API keys DigitalOcean OAuth access tokens DigitalOcean personal access tokens Doppler personal tokens Doppler service tokens Dropbox app access tokens Dropbox short-lived access tokens EasyPost API tokens EasyPost test API tokens Fastly API tokens Flutterwave live secret keys Flutterwave test secret keys GC Notify API keys GitHub App installation tokens GitHub fine-grained personal access tokens GitHub OAuth access tokens GitHub personal access tokens (classic) GoCardless API tokens Google Cloud API keys Grafana Cloud access policy tokens HashiCorp Terraform user and organization API tokens Heroku API keys Highnote live secret keys Highnote test secret keys HubSpot private app access tokens and service keys Hugging Face user access tokens Intercom access tokens Ionic personal access tokens LangChain API keys Linear personal API keys Lob API keys Mailgun private API keys MessageBird access keys New Relic user API keys npm access tokens Onfido live API tokens OpenAI admin API keys OpenAI project API keys OpenAI service account keys OpenAI user API keys PostHog personal API keys Postman API tokens Pulumi access tokens RubyGems API keys Segment public API tokens SendGrid API tokens Shippo live API tokens Shippo test API tokens Slack app configuration tokens Slack app-level tokens Stripe live publishable keys Stripe live restricted keys Stripe live secret keys Stripe live short secret keys Stripe test publishable keys Stripe test restricted keys Stripe test secret keys Stripe test short secret keys Tailscale API access tokens Typeform personal access tokens Validity checks for AWS IAM access key IDs, Google Cloud API keys, and Postman API tokens work with any secret detection analyzer.
GitLab validates all other external service token types, including token types added in the future, only when GitLab Secret Scanning for Source Code detects the secret. Beamer API tokens are verified with requests that count against the key owner’s monthly Beamer API quota, which is 1,000 requests on free plans. When the quota is used up, Beamer rate limits the check and the token shows as possibly active until the quota resets.
HashiCorp Terraform tokens are verified against HCP Terraform only. A token that HCP Terraform rejects shows as possibly active, because it might belong to a self-hosted Terraform Enterprise instance. Mailgun private API keys are verified from GitLab IP addresses. If your Mailgun account restricts API access with an IP allowlist, a live key might show as inactive because Mailgun rejects the request. A Brevo API key on an account that restricts API access to authorized IP addresses shows as possibly active, because Brevo rejects requests from other addresses.
Configure outbound network access Validity checks are not supported in offline environments. This feature requires outbound network access to partner validation APIs to verify whether detected tokens are active. If your GitLab instance is behind a firewall but has internet access, allowlist the URLs for each partner’s validation API. The supported URLs are: https://api.anthropic.com/v1/models https://api.brevo.com/v3/account https://api.ca.onfido.com/v3.6/applicants https://api.contentful.com/users/me https://api.datadoghq.com/api/v1/validate https://api.digitalocean.com/v2/account https://api.doppler.com/v3/me https://api.dropboxapi.com/2/users/get_current_account https://api.easypost.com/v2/addresses https://api.eu.contentful.com/users/me https://api.eu.newrelic.com/v2/applications.json https://api.eu.onfido.com/v3.6/applicants https://api.fastly.com/tokens/self https://api.flutterwave.com/v3/balances https://api.getbeamer.com/v0/ping https://api.getpostman.com/me https://api.github.com/installation/repositories https://api.github.com/user https://api.gocardless.com/creditors https://api.goshippo.com/addresses/ https://api.heroku.com/account https://api.hubapi.com/account-info/v3/details https://api.intercom.io/me https://api.ionicjs.com/users/self https://api.linear.app/graphql https://api.lob.com/v1/addresses https://api.mailgun.net/v4/domains https://api.newrelic.com/v2/applications.json https://api.notification.canada.ca/v2/notifications https://api.openai.com/v1/models https://api.openai.com/v1/organization/admin_api_keys https://api.pulumi.com/api/user https://api.segmentapis.com/echo https://api.sendgrid.com/v3/scopes https://api.smith.langchain.com/api/v1/sessions https://api.stripe.com/v1/balance https://api.tailscale.com/api/v2/tailnet/-/devices https://api.typeform.com/me https://api.typeform.eu/me https://api.us.highnote.com/graphql https://api.us.onfido.com/v3.6/applicants https://api.us.test.highnote.com/graphql https://app.asana.com/api/1.0/users/
The rest of this page is on the live site.