No entries match these filters. Clear filters
Invalid secrets no longer block your developers and AI coding agents (2026-11-20)
Nov 20, 2026
·
issue 146
GitGuardian adds automatic filtering of invalid secrets from scan results, so hooks and AI agents no longer block on credentials the provider has confirmed dead︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Verify that your CI pipeline now passes when only invalid secrets are detected — no code change or ggshield upgrade needed, since the filter runs server-side on the /v1/scan endpoint.
copy
$ curl -s -X POST https://api.gitguardian.com/v1/scan \
-H 'Authorization: Token <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"document": "<content-with-known-invalid-secret>", "filename": "config.yaml"}'
GitGuardian's scan API now drops confirmed-invalid secrets from results for pre-commitpre-commit An open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. , pre-push, ggshield secret scan ci, and direct calls to the /v1/scan and /v1/multiscan endpoints, so hooks and AI agents only block on valid or unverifiable secrets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Paste a full repository URL — including sub-page URLs for files or branches — into the Perimeter search or Source filter to locate the matching source. Not checked yet
GitGuardian's scan API now drops confirmed-invalid secrets from results for pre-commitpre-commit An open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. , pre-push, ggshield secret scan ci, and direct calls to the /v1/scan and /v1/multiscan endpoints, so hooks and AI agents only block on valid or unverifiable secrets.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
api-docs-5f43d1220789
Nov 18, 2026
·
issue 143
GitGuardian adds a 'Get the validity and analysis of a secret' API endpoint that returns stored analyzer status, active scopes, metadata, and last analysis date︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
GitGuardian adds an automated, asynchronous revoker for the Azure Container Registry Key detector, driven by a service principal with the Contributor role.
New detection Revoke leaked Azure Container Registry credentials automatically using tenant_id, client_id, client_secret, and container_registry_resource_id — the revoker authenticates via POST /{tenant_id}/oauth2/v2.0/token and operates asynchronously. Not checked yet The revoker calls GET and POST endpoints under /subscriptions/{subscription_id}/resourceGroups/{resource_group}/providers/Microsoft.ContainerRegistry/registries/{registry_name}/ to list, regenerate, and rotate registry tokens and admin credentials. Not checked yet
2 details in Everything
GitGuardian adds async automatic revocation for AWS SES AWS SES Amazon's cloud email-sending service, used by cyber tools to deliver alerts, reports, or notifications without running their own mail infrastructure. keys, driven by admin_client_id and admin_client_secret IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. credentials in the revoker config.
Configure automatic AWS SES key revocation by setting admin_client_id (IAM principal Access key ID with iam:GetAccessKeyLastUsed and iam:DeleteAccessKey permissions) and admin_client_secret (matching Secret access key) in the revoker auth credentials. Not checked yet AWS SES key revocation now runs asynchronously. Not checked yet
2 details in Everything
GitGuardian adds an asynchronous revoker for Azure Active Directory Active Directory Microsoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. API keys, configured via admin_client_id and admin_client_secret.
New detection Revoke leaked Azure Active Directory API keys automatically using admin_client_id and admin_client_secret config credentials — requires the Application.ReadWrite.All Microsoft Graph Microsoft Graph Microsoft's unified REST API for accessing data and services across Microsoft 365, Azure AD, and related cloud products, giving cyber tools a single authenticated endpoint to query users, emails, files, and sign-in logs. application permission on an app in the same tenant. Not checked yet Revoker calls GET /v1.0/applications(appId='{client_id}') , POST /v1.0/applications(appId='{client_id}')/removePassword, and POST /{tenant_id}/oauth2/v2.0/token to remove the compromised credential. Not checked yet Revocation runs asynchronously. Not checked yet
3 details in Everything
GitGuardian adds an asynchronous revoker for Microsoft Azure Storage Account Keys, using a service principal with the Storage Account Key Operator Service Role.
Revoke leaked Azure Storage Account Keys automatically by configuring tenant_id, client_id, client_secret, and storage_account_resource_id credentials for a service principal holding the Storage Account Key Operator Service Role. Not checked yet New detection The revoker calls POST /subscriptions/{subscription_id}/resourceGroups/{resource_group}/providers/Microsoft.Storage/storageAccounts/{account_name}/regenerateKey to rotate the exposed key, preceded by a listKeys call and an OAuth2 OAuth2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. token request to POST /{tenant_id}/oauth2/v2.0/token. Not checked yet Revocation for Azure Storage Account Keys runs asynchronously. Not checked yet
3 details in Everything
GitGuardian adds automated asynchronous revocation for Azure Entra App Secrets, requiring an admin app credential with Microsoft Graph Microsoft Graph Microsoft's unified REST API for accessing data and services across Microsoft 365, Azure AD, and related cloud products, giving cyber tools a single authenticated endpoint to query users, emails, files, and sign-in logs. Application.ReadWrite.All permission.
New detection Revoke detected Azure Entra App Secrets automatically by supplying admin_client_id (a Client ID with Microsoft Graph application permission Application.ReadWrite.All) and admin_client_secret in the revoker configuration. Not checked yet Revoker performs asynchronous revocation via GET /v1.0/applications(appId='{client_id}') , POST /v1.0/applications(appId='{client_id}')/removePassword, and POST /{tenant_id}/oauth2/v2.0/token. Not checked yet
2 details in Everything
GitGuardian adds 13 new secret detectors and 23+ new analyzers across Google, AWS, HashiCorp, and SaaS platforms, plus SSH key validation against custom hosts.
Updated detection HashiCorp Vault token, AppRole, and unseal key detectors now also report the host of the Vault instance when it appears next to the credentials. Not checked yet Updated detection The private_key_rsa, base64_private_key_rsa, private_key_elliptic, base64_private_key_elliptic, private_key_openssh, base64_private_key_openssh, private_key_generic, and base64_private_key_generic checkers can now validate SSH keys against a custom host such as a self-hosted GitLab or GitHub Enterprise instance. Not checked yet New detection The Google Cloud Express API Key detector is renamed to Google Gemini API Key , and the former Google Gemini API Key detector is renamed to Google Bard Session Cookie . Not checked yet The linear_api_key checker now returns INVALID instead of FAILED_TO_CHECK for revoked or invalid keys. Not checked yet New detection New analyzer for DeepSeek API keys, reporting account balance with currency, availability status, and usable models. Not checked yet
+2 more
show less
New analyzer for Groq API keys, reporting the models the key can use. Not checked yet New analyzer for Telegram bot tokens, reporting the bot username and name. Not checked yet
7 details in Everything
GitGuardian adds private key checkers that now validate SSH keys against a custom host, and renames two Google detectors (Google Cloud Express API Key to Google Gemini API Key; Google Gemini API Key to Google Bard Session Cookie).
Updated detection Private key checkers private_key_rsa, base64_private_key_rsa, private_key_elliptic, base64_private_key_elliptic, private_key_openssh, base64_private_key_openssh, private_key_generic, and base64_private_key_generic now validate SSH keys against a custom host, such as a self-hosted GitLab or GitHub Enterprise instance. Not checked yet The linear_api_key checker now returns INVALID instead of FAILED_TO_CHECK for revoked or invalid keys. Not checked yet New detection The Google Cloud Express API Key detector is renamed to Google Gemini API Key, and the former Google Gemini API Key detector is renamed to Google Bard Session Cookie. Not checked yet
3 details in Everything
New detection base64_googlecloud_access_token detector New detection googlecloud_storage_hmac_key detector New detection base64_googleaiza detector New detection AWS AppSync API Key detector New detection AWS CodeArtifact Authorization Token detector Updated detection HashiCorp Vault detectors host reporting Updated detection AWS Bedrock long-term API key detection improvement New detection Jamf OAuth Credentials detector New detection Pydantic Logfire Token detector New detection Supabase Personal Access Token detector New detection Food Safety Korea API Key detector New detection Grafana service account token analyzer New detection Cloudinary API key analyzer Updated detection Google API key analyzer base64 support New detection 23 new analyzers for DeepSeek, Groq, Telegram, GitLab, New Relic, Amp, Sourcegraph, Gemfury, Mercado Pago, Cloudflare, Facebook, LlamaCloud, Azure Entra
└──▷ BREAKING ON UPGRADE
! The Google Cloud Express API Key detector is renamed to Google Gemini API Key , and the former Google Gemini API Key detector is renamed to Google Bard Session Cookie — any rules, filters, or integrations referencing those detector names by their old labels must be updated.
GitGuardian adds AWS key honeytoken support to self-hosted installations︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Self-hosted installations now support AWS key honeytokens (previously a SaaS-only capability); kubeconfig honeytokens remain SaaS-only.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
GitGuardian adds endpoint honeytoken deployment to ~/.aws and ~/.kube to catch credential-harvesting malware on developer machines︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Deploy an AWS honeytoken into the local credential file so any credential-harvesting malware on a developer machine triggers a named-machine alert in GitGuardian.
📍 Place the honeytoken AWS key pair into an AWS profile under ~/.aws/credentials on the developer machine, then confirm reconciliation in the GitGuardian dashboard.
Plant honeytokens directly on developer machines in ~/.aws AWS profiles or ~/.kube kubeconfig contexts, reconciled with GitGuardian, so credential-harvesting malware triggers an alert naming the compromised machine.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Create kubeconfig honeytokens — only possible via the endpoint deployment method — to monitor Kubernetes credential files on developer machines. Not checked yet
2 details in Everything
GitGuardian GGScout adds a fetch-only mode that writes a local JSON audit report before any data leaves your environment︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
GitGuardian adds ClickHouse as an analytics backend for Endpoint Protection, AI agent inventory, and honeytoken fleet coverage︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
GitGuardian now uses ClickHouse, a column-oriented database, to store and serve machine scan results and findings for every endpoint, plus analytics shown in the Endpoints dashboard︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet AI agent and MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. inventory — MCP tool calls reported by AI Hooks and complete AI agent sessions — now requires ClickHouse on the instance Not checked yet Honeytoken protection on endpoints now stores honeytoken coverage across the fleet in ClickHouse; without ClickHouse this feature is unavailable Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! Machine scans with secrets findings, AI agent and MCP inventory, and honeytoken protection on endpoints are unavailable on an instance without ClickHouse deployed
GitGuardian adds kubeconfig honeytoken support, planting decoy bearer-token contexts in ~/.kube/config alongside existing AWS key honeytokens︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Plant a kubeconfig honeytoken on a Kubernetes developer's machine so that any credential harvester touching ~/.kube/config triggers an alert with the kubectl user agent and API path.
copy
$ ggshield honeytoken plant --type kubeconfig
Plant a kubeconfig honeytoken on a developer machine — a decoy cluster, user, and context written to ~/.kube/config — using ggshield honeytoken plant --type kubeconfig; a trigger records the kubectl user agent and API path requested.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Alert cards for kubeconfig honeytoken events now name the on-disk file the decoy was written to and record the kubectl user agent and API path that was requested at trigger time. Not checked yet
Plant a kubeconfig honeytoken on a developer machine — a decoy cluster, user, and context written to ~/.kube/config — using ggshield honeytoken plant --type kubeconfig; a trigger records the kubectl user agent and API path requested.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
GitGuardian adds IBM Cloud Secrets Manager integration, ML risk scoring for self-hosted, and per-role secret obfuscation︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds an IBM Cloud Secrets Manager integration to inventory vaulted secrets, cross-reference them with leaked secrets, and support rotation workflows, alongside HashiCorp Vault, AWS, Azure, GCP, CyberArk, Akeyless, and Delinea.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Brings ML-powered risk scoring to self-hosted deployments so teams can prioritize incidents by predicted severity without SaaS cloud connectivity. Not checked yet Adds per-role secret obfuscation controls — partial secret display with a visible prefix/suffix and persona-based obfuscation rules — extending the existing workspace-wide privacy mode. Not checked yet Monitors multiple Red Hat Quay organizations from a single integration instead of connecting them one at a time. Not checked yet
Adds an IBM Cloud Secrets Manager integration to inventory vaulted secrets, cross-reference them with leaked secrets, and support rotation workflows, alongside HashiCorp Vault, AWS, Azure, GCP, CyberArk, Akeyless, and Delinea.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Brings ML-powered risk scoring to self-hosted deployments so teams can prioritize incidents by predicted severity without SaaS cloud connectivity. Not checked yet
2 more in Everything
GitGuardian SaaS: The azure_subscription_key detector gains improved recall.
└──▷ BREAKING ON UPGRADE
! The Google Cloud Express API Key detector is renamed to Google Gemini API Key ; the former Google Gemini API Key detector is renamed to Google Bard Session Cookie — any rules or alerts referencing these names by their old labels will need to be updated.
GitGuardian adds Kubeconfig honeytoken type for planting decoy kubeconfigs on developer machines via ggshield︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Plant decoy kubeconfig honeytokens on developer machines using ggshield to detect credential theft alongside existing AWS key honeytokens.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
GitGuardian adds a secret revocation API, richer public incident fields, new audit log events for login lockout, and expanded perimeter bulk-selection controls.
Revoke a secret via the new POST /v1/secrets/{secret_id}/revoke endpoint, passing provider credentials in the credentials body field to override workspace defaults. Not checked yet Filter public incidents and check runs by commit_sha, pull_request_number, or source_id in addition to existing filters; each check run now also returns its repository's full name and source ID. Not checked yet Public incident responses now include company_related_verdict (values: related, unclear, unrelated) and agents_stage in list, detail, and CSV export, and both fields are filterable. Not checked yet Filter the Teams page by Synced from provider when Team Sync is enabled, to distinguish synced teams from manually created ones. Not checked yet Filter public incidents by Source owner — the GitHub organization or user, or Docker Hub namespace, that published the source. Not checked yet
+2 more
show less
Lock out password logins for six minutes after ten failed attempts for the same email and IP address; the login endpoint responds with a Retry-After header and logs a password_login_locked_out entry in the audit log with the IP address and attempt count. Not checked yet Select all sources matching current filters at the root level of an integration's perimeter to monitor or unmonitor them in one action. Not checked yet
7 details in Everything
└──▷ BREAKING ON UPGRADE
!
SharePoint Online and OneDrive integrations no longer require the `Organization.Read.All` permission on your Entra application; installations without it are now named after their tenant ID rather than the organization name.
Our best guess
api-docs-b9ecd19de385
Nov 13, 2026
·
issue 138
GitGuardian adds collaborator management endpoints for secret incidents and an agents-stage filter for public incidents︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Assign remediation owners to a secret incident by adding specific workspace members as collaborators.
copy
$ curl -s -X PATCH 'https://api.gitguardian.com/v1/incidents/secrets/42/collaborators' \
-H 'Authorization: Token <your_api_key>' \
-H 'Content-Type: application/json' \
-d '{"member_ids_to_add": [101, 202, 303], "member_ids_to_remove": []}'
Find public incidents that the AI pipeline has fully confirmed as valid secrets, to prioritise remediation.
copy
$ curl -s 'https://api.gitguardian.com/v1/public-incidents/secrets?agents_stage=deep_analysis_confirmed' \
-H 'Authorization: Token <your_api_key>'
Scope NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. identity queries to a specific team's cloud resources using tag-based filtering.
copy
$ curl -s 'https://api.gitguardian.com/v1/identities?tag__in=team=payments,aws:cloudformation:stack-name=billing' \
-H 'Authorization: Token <your_api_key>'
List workspace members collaborating on a secret incident via GET /v1/incidents/secrets/{incident_id}/collaborators, returning member_ids.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Add or remove up to 1,000 collaborators on a secret incident in one call via PATCH /v1/incidents/secrets/{incident_id}/collaborators, using member_ids_to_add and member_ids_to_remove; requires an API key with the incidents:write scope and edit access on the incident. Not checked yet List workspace members collaborating on a public secret incident via GET /v1/public-incidents/secrets/{incident_id}/collaborators, returning member_ids. Not checked yet Add or remove up to 1,000 collaborators on a public secret incident in one call via PATCH /v1/public-incidents/secrets/{incident_id}/collaborators, using member_ids_to_add and member_ids_to_remove; requires an API key with the incidents:write scope. Not checked yet Filter public secret incidents by AI pipeline stage using the agents_stage query parameter, accepting values triage_rejected, triage_inconclusive, deep_analysis_rejected, deep_analysis_inconclusive, and deep_analysis_confirmed. Not checked yet
+1 more
show less
Filter NHI identity locations by resource tags using the tag__in query parameter, expressed as key=value pairs (e.g. tag__in=team=payments,aws:cloudformation:stack-name=billing). Not checked yet
6 details in Everything
Catch secret theft on your developers' machines with a Kubeconfig honeytoken (2026-11-12)
Nov 12, 2026
·
issue 138
GitGuardian adds a Kubeconfig honeytoken that alerts on secret theft from developer machines, plus new Public API filters and a secret-revoke endpoint︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Add a Kubeconfig honeytoken to a developer machine's fleet job alongside an existing AWS key decoy, so any credential-stealing malware triggers a named-machine alert.
copy
$ ggshield honeytoken plant --type kubeconfig
Revoke a compromised secret found by GitGuardian, supplying provider credentials so the revocation uses them instead of workspace defaults.
copy
$ curl -X POST https://api.gitguardian.com/v1/secrets/secret_123/revoke \
-H 'Authorization: Token <api_key>' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"api_key": "<provider_api_key>"}}'
Find all check-runs for a specific pull request even when its findings have no incident yet, to audit CI scan results in a pipeline.
copy
$ curl 'https://api.gitguardian.com/v1/check-runs?pull_request_number=42&source_id=789' \
-H 'Authorization: Token <api_key>'
Plant a Kubeconfig honeytoken on developer endpoints with ggshield honeytoken plant --type kubeconfig, writing a decoy into ~/.kube/config that fires an alert with IP, country, user agent, and machine name on first use — requires ggshield 1.56+ and the honeytokens:write scope.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Revoke a detected secret via the new POST /v1/secrets/{secret_id}/revoke endpoint, passing provider credentials in the credentials body field to override workspace defaults; requires the secrets:write scope. Not checked yet Filter GET /v1/check-runs by commit_sha, pull_request_number, or source_id in addition to incident_id; each check-run response now also includes the repository's full name and source ID. Not checked yet Public incident list, detail, and CSV export now carry agents analysis fields company_related_verdict (values: related, unclear, unrelated) and agents_stage, both filterable, so a SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. or ticketing tool can reproduce dashboard views. Not checked yet Filter public incidents by source owner (GitHub organization or user, or Docker Hub namespace) in Public Monitoring. Not checked yet
+3 more
show less
Team Sync gains a Synced from filter on the Teams page to distinguish provider-synced teams from manually created ones. Not checked yet Password login now locks out for six minutes after ten failed attempts for the same email and IP; the login endpoint returns HTTP 429 with a Retry-After header and writes a password_login_locked_out entry to the audit log. Not checked yet JFrog Container Registry integration now scans federated Docker repositories alongside local ones. Not checked yet
Plant a Kubeconfig honeytoken on developer endpoints with ggshield honeytoken plant --type kubeconfig, writing a decoy into ~/.kube/config that fires an alert with IP, country, user agent, and machine name on first use — requires ggshield 1.56+ and the honeytokens:write scope.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Revoke a detected secret via the new POST /v1/secrets/{secret_id}/revoke endpoint, passing provider credentials in the credentials body field to override workspace defaults; requires the secrets:write scope. Not checked yet
6 more in Everything
GitGuardian SaaS adds a tokenscanner plugin installable via ggshield plugin install, with optional version pinning via --version.
GitGuardian adds AI agent honeytoken management, K8s K8s Shorthand for Kubernetes, the open-source container orchestration system originally from Google; cyber tools use it to deploy, scale, and manage containerized workloads across clusters. runtime deception injection, configurable honeytoken rotation policies, and bidirectional Jira status sync.
Manage Honeytokens at scale through AI agents — disseminate, reset, rotate, and test them across your entire tech stack using Agent Skills. Not checked yet New supported platform Auto-inject ephemeral honeytokens into Kubernetes pods and process memory for runtime deception via a new K8s Operator and Advanced Runtime Protection feature. Not checked yet Configure rotation policies for honeytoken lifecycle, including short-lived CI/CD tokens, scheduled rotation, and stale token detection via Token and Accounts Auto-Rotation. Not checked yet New integration Keep GitGuardian incident status and linked Jira issue status in sync in both directions with two-way status sync, replacing the previous one-way auto-resolve and comment-only updates. Not checked yet
4 details in Everything
GitGuardian adds a Wiz integration to sync open secret incidents from version control into Wiz as native secret findings once a day︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Connect GitGuardian to Wiz so your cloud security team sees leaked secrets alongside cloud risk without leaving their tool.
📍 In Wiz, open the GitGuardian integration page and copy the Client ID, Client secret, Authentication URL, and API endpoint URL. In GitGuardian, go to Settings › Integrations › Wiz, click Configure, paste the four values, choose how to map Info and Unknown severities to Wiz severities, and click Add integration. Findings appear in Wiz within 24 hours.
Configure the Wiz integration in GitGuardian at Settings > Integrations > Wiz by pasting the Client ID, Client secret, Authentication URL, and API endpoint URL that Wiz provides, then map Info and Unknown severities to Wiz equivalents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet GitGuardian now syncs open secret incidents daily from GitHub, GitLab, Bitbucket, and Azure DevOps into Wiz as native secret findings, each carrying repository, file path, commit, detector, validity status, severity, and a link back to the GitGuardian incident. Not checked yet Secret values never leave GitGuardian — Wiz receives only a SHA-256 SHA-256 A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. hash of the value plus metadata. Not checked yet Validity context is included in each Wiz finding so that live, still-working keys are surfaced ahead of inactive ones. Not checked yet Pausing or resuming the daily sync is available from the same Settings > Integrations > Wiz settings page at any time. Not checked yet
5 details in Everything
api-docs-dbcff7cc4c0f
Oct 30, 2026
·
issue 125
GitGuardian adds API endpoints to retrieve occurrence content in clear text, manage NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. policies, and trigger on-demand secret validity checks︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Pull the exact diff content of a triaged occurrence — including where the secret sits — so you can pipe it into a remediation script without opening the dashboard.
copy
$ curl -H 'Authorization: Token <PAT>' \
https://api.gitguardian.com/v1/occurrences/secrets/<occurrence_id>/content
Switch an NHI policy from tagging-only to full incident creation so breaches start appearing in your incident queue once NHI promotion is active.
copy
$ curl -X PATCH \
-H 'Authorization: Token <PAT>' \
-H 'Content-Type: application/json' \
-d '{"incident_mode": "creates_incidents"}' \
https://api.gitguardian.com/v1/nhi/policies/<policy_name>
Retrieve the clear-text content of a private secret occurrence, including secret match positions, via GET /v1/occurrences/secrets/{occurrence_id}/content — requires a PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. (service account tokens are refused) and the workspace setting 'Enable API endpoints to retrieve detected secrets and occurrence content in clear text' plus IP allowlist on SaaS.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet List all NHI policies and their current incident_mode values (hidden, tag_only, or creates_incidents) via GET /v1/nhi/policies — requires full NHI governance activation. Not checked yet Retrieve a single NHI policy and its incident_mode and is_incident_mode_fixed fields via GET /v1/nhi/policies/{policy_name}. Not checked yet Trigger an on-demand secret validity check via POST /v1/secrets/{secret_id}/validity/check; poll last_checked_at afterward to confirm the refreshed result — checks are rate-limited to one per secret per 5 minutes and skipped for secrets with a validity override or that GitGuardian cannot check. Not checked yet
4 details in Everything
GitGuardian adds Docker Hub public monitoring, a --background scan mode, and a local machine dashboard with Codex and opencode redaction︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Add to a scheduled MDM MDM Mobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. scan command so the scan runs at low priority without slowing developer machines.
copy
$ ggshield machine report --background
Make low-priority background mode the default for all machine scans fleet-wide, so no per-command flag is needed.
machine_scan.yaml
copy
scan:
resources:
background:
mode: auto
Open the local dashboard overview to start triaging and redacting secrets by AI agent or repository.
copy
$ ggshield machine dashboard
Open a cleanup overview with ggshield machine dashboard, which now lands on an Overview page grouping findings by AI agents, repositories, and history and logs. Not checked yet Docker Hub incidents now carry publishing account, image, repository, and layer context, and flow through the same notifications, integrations, and agents analysis as GitHub incidents. Not checked yet Findings pushed to Wiz now include GitGuardian incident, occurrence, and source IDs in the finding's originalObject field for use in Wiz workflows and the Wiz API. Not checked yet Honeytoken planting is now supported on Windows endpoints. Not checked yet Scans now skip additional folders of downloaded or generated files, including pip-*, pytest-of-*, and _MEI* temp leftovers, NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. and Scoop package caches, and Electron app caches. Not checked yet
Docker Hub incidents now carry publishing account, image, repository, and layer context, and flow through the same notifications, integrations, and agents analysis as GitHub incidents. Not checked yet
4 more in Everything
└──▷ BREAKING ON UPGRADE
!
Validity checks no longer read custom hosts from environment variables or local config files; custom hosts are now sourced exclusively from your GitGuardian workspace.
Our best guess
Sync your GitHub teams, members, and perimeters automatically (2026-10-29)
Oct 29, 2026
·
issue 125
GitGuardian adds automatic GitHub team sync, multi-header custom webhooks, new Public API endpoints, and scoped Endpoint Protection auth︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Trigger or review GitHub team sync after enabling it, to immediately mirror your GitHub org's teams and members without waiting for the 24-hour cycle.
📍 Open your GitHub integration settings, scroll to Team synchronization , click Add organization , select the organization to mirror, then click Sync now to run an immediate sync and view results in the synchronization history.
Add a custom webhook integration that now accepts multiple custom headers (such as bearer tokens bearer tokens A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. or routing headers) per webhook, configured from its settings page.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Unlink a ticket from an incident using a new Public API endpoint. Not checked yet Retrieve the stored content of an occurrence of an internal or public incident in clear text via new Public API endpoints, subject to the same requirements as secret access. Not checked yet Scope Endpoint Protection permissions more narrowly: the ggshield auth login authorization page now groups Endpoint Protection scopes in a single opt-in card, no longer granted by default. Not checked yet GitGuardian adds GitHub team sync: enable team synchronization on your GitHub integration and GitGuardian mirrors your GitHub organization's teams, members, and repository ownership into your workspace, running every 24 hours or on demand via Sync now . Not checked yet
+1 more
show less
GitGuardian Bridge now routes validity checks and secret analysis for detectors where the host is read from the secret itself (such as database connection strings), whenever that host is mapped to a bridge — previously limited to detectors with a custom host configured. Not checked yet
Add a custom webhook integration that now accepts multiple custom headers (such as bearer tokens bearer tokens A credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else. or routing headers) per webhook, configured from its settings page.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Unlink a ticket from an incident using a new Public API endpoint. Not checked yet Retrieve the stored content of an occurrence of an internal or public incident in clear text via new Public API endpoints, subject to the same requirements as secret access. Not checked yet GitGuardian adds GitHub team sync: enable team synchronization on your GitHub integration and GitGuardian mirrors your GitHub organization's teams, members, and repository ownership into your workspace, running every 24 hours or on demand via Sync now . Not checked yet
2 more in Everything
└──▷ BREAKING ON UPGRADE
!
Endpoint Protection scopes are no longer granted by default during `ggshield auth login` — users must explicitly opt in via the new single card, so existing automation that relied on those scopes being pre-selected will need to re-authenticate.
Our best guess
Scan developer machines with less noise, and clean up what you find (2026-10-27)
Oct 27, 2026
·
issue 123
GitGuardian Endpoint Protection gains background scanning, an Overview dashboard, Codex/opencode redaction, and validity checks for 501 secret types.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Run a scheduled daily inventory scan at low priority so developer machines stay responsive during the MDM MDM Mobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. job.
copy
$ ggshield machine report --background
Make background-priority scanning the permanent default so every scan — however triggered — leaves the machine responsive.
machine_scan.yaml
copy
scan:
resources:
background:
mode: auto
Open the local remediation dashboard to see the Overview and start cleaning up findings grouped by AI agent or repository.
copy
$ ggshield machine dashboard
Adds --background flag to ggshield machine scan and ggshield machine report to run scans at low priority using 2–4 threads and one-tenth of normal memory (minimum 512 MB), suited for scheduled MDM jobs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds scan.resources.background.mode: auto to machine_scan.yaml to make background-priority scanning the default for every scan. Not checked yet Adds an Overview page to ggshield machine dashboard that lists one row per cleanup area (AI agents, repositories, history and logs) and guides remediation order: overprivileged secrets first, then history leaks, then secrets in daily use. Not checked yet Enables redaction of Codex and opencode history from the local dashboard, including their SQLite history databases. Not checked yet Expands validity checks to 501 secret types (up from 432), adding coverage for Elastic, Datadog, Langfuse, Sumo Logic, Gitea, and Azure Container Registry. Not checked yet
+2 more
show less
Suppresses findings from VS Code, Cursor, VSCodium, Windsurf, and JetBrains IDE editor-history copies unless the secret in them is valid, reducing duplicate noise. Not checked yet Expands folder exclusions to skip build leftovers (pip-*, pytest-of-*, _MEI*), Windows package caches (NuGet NuGet Microsoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. , Scoop), and Electron app caches, while still scanning credential-holding folders. Not checked yet
Adds --background flag to ggshield machine scan and ggshield machine report to run scans at low priority using 2–4 threads and one-tenth of normal memory (minimum 512 MB), suited for scheduled MDM jobs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds scan.resources.background.mode: auto to machine_scan.yaml to make background-priority scanning the default for every scan. Not checked yet Adds an Overview page to ggshield machine dashboard that lists one row per cleanup area (AI agents, repositories, history and logs) and guides remediation order: overprivileged secrets first, then history leaks, then secrets in daily use. Not checked yet Enables redaction of Codex and opencode history from the local dashboard, including their SQLite history databases. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
!
Validity checks now take custom hosts only from your GitGuardian workspace; environment variables and local config files that previously set custom hosts are no longer read.
Our best guess
api-docs-cce17ae86794
Oct 23, 2026
·
issue 118
GitGuardian adds NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. Identity and Source APIs plus ticket-unlinking endpoint for secrets and honeytokens.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Unlink a stale Jira ticket from a secret incident after it was closed on the Jira side, without touching the Jira ticket itself.
copy
$ curl -X DELETE 'https://api.gitguardian.com/v1/incidents/secrets/8821/destination-tickets/PROJ-42?resource_type=secret-incidents' \
-H 'Authorization: Token <your_api_token>'
List all NHIs NHIs A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. in production that breach the long_lived_secret policy and carry critical risk, to prioritise remediation.
copy
$ curl -G 'https://api.gitguardian.com/v1/nhi/identities' \
-H 'Authorization: Token <your_api_token>' \
--data-urlencode 'env__in=production' \
--data-urlencode 'policy__in=long_lived_secret' \
--data-urlencode 'risk_criticality__in=critical'
Retrieve all locations where a specific NHI holds a secret — useful for tracing blast radius before rotating credentials.
copy
$ curl 'https://api.gitguardian.com/v1/nhi/identities/arn%3Aaws%3Aiam%3A%3A123456789012%3Auser%2Fci-deployer/locations' \
-H 'Authorization: Token <your_api_token>'
Adds DELETE /v1/incidents/secrets/{resource_id}/destination-tickets/{ticket_id} to unlink a Jira or ServiceNow ticket from a secret incident, public secret incident, or honeytoken without deleting the ticket on the external platform; uses resource_type query parameter to select the resource kind.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds GET /v1/nhi/identities to list non-human identities non-human identities A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. (NHIs) in the workspace, with filters including source__in, env__in, policy__in, risk_criticality__in, validity__in, principal_type__in, owner_id__in, vault_source_id__in, consumer_source_id__in, endpoint_source_id__in, provider_source_id__in, detector_group_name__in, detector_type__in, secret_family__in, secret_category__in, secret_provider__in, has_owner, has_detector, is_admin, and hmsl_hash. Not checked yet Adds GET /v1/nhi/identities/{identity_id} to retrieve a single non-human identity non-human identity A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. with its permissions and a summary of its secrets. Not checked yet Adds GET /v1/nhi/identities/{identity_id}/locations to list all locations holding a secret of a non-human identity — secrets manager paths, consumer resources (Kubernetes, CI), endpoints, and provider accounts; requires full NHI governance on the workspace. Not checked yet Adds GET /v1/nhi/sources to list sources sending NHI data to GitGuardian (secrets managers, Kubernetes clusters, CI systems, cloud providers, endpoints), filterable by type, is_vault, and full_path. Not checked yet
+1 more
show less
Adds full_path query parameter to NHI Sources endpoint for exact, case-sensitive source lookup, preferred over free-text search for single-source retrieval. Not checked yet
6 details in Everything
GitGuardian SaaS: Adds GET /v1/check-runs to list check runs by incident and retrieve their IDs.
└──▷ TRY IT
Skip a blocking GitHub check run from CI/CD or an incident-response script when the skip buttons are disabled in the UI.
copy
$ curl -X POST https://api.gitguardian.com/v1/check-runs/{check_run_id}/skip \
-H 'Authorization: Token <your_api_token>' \
-H 'Content-Type: application/json' \
-d '{"reason": "<skip_reason>"}'
Retrieve all check runs for a specific incident to get the IDs needed for programmatic skip operations.
copy
$ curl -X GET 'https://api.gitguardian.com/v1/check-runs?incident_id=<incident_id>' \
-H 'Authorization: Token <your_api_token>'
Adds Docker Hub monitoring to GitGuardian Public Monitoring, checking newly published public images daily against your perimeter and surfacing leaked secrets as incidents with publishing account, image repository, and layer context. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The line_notify_token detector has been removed.! The ftp_credentials_assignment detector now only captures FTP FTP A decades-old TCP-based protocol for transferring files between a client and server, using separate control and data connections; cyber tools target or support it because it often transmits credentials in plaintext. secrets, not SFTP SFTP SSH File Transfer Protocol, a file transfer standard built on top of SSH that provides encrypted upload, download, and remote file management; cyber tools use it to move files or exfiltrate data over an authenticated, encrypted channel. — existing SFTP detections move to sftp_credentials_assignment.! The postgres_assignment_attached_port and postgres_assignment_no_port detectors are merged into postgres_assignment; any references to the old detector names will no longer match.! The azure_event_grid_access_key_with_host detector is merged into azure_event_grid_access_key; references to the old name will no longer match.! The grafana_service_account_token_with_host detector is merged into grafana_service_account_token; references to the old name will no longer match.! The kubernetes_jwt_with_host detector is merged into kubernetes_jwt; references to the old name will no longer match.! The planetscale_database_password_with_host_and_username detector is merged into planetscale_database_password; references to the old name will no longer match.
Catch secrets leaked in public Docker Hub images (2026-10-21)
Oct 21, 2026
·
issue 116
GitGuardian Public Monitoring now scans newly published Docker Hub images daily, matching secrets to your perimeter.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Surfaces Docker Hub-specific context on every incident — publishing account, image and repository name, and the layer the secret was found in — instead of commit and author.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Routes Docker Hub incidents through existing notifications, integrations, and agents analysis, matching the workflow for GitHub incidents. Not checked yet Enriches findings pushed to Wiz with GitGuardian incident, occurrence, and source IDs in the finding's originalObject field, enabling use in Wiz workflows and via the Wiz API. Not checked yet Extends Honeytoken planting support to Windows endpoints. Not checked yet
Surfaces Docker Hub-specific context on every incident — publishing account, image and repository name, and the layer the secret was found in — instead of commit and author.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
3 more in Everything
api-docs-6756f12bc87c
Oct 20, 2026
·
issue 114
GitGuardian adds API endpoints to list and skip GitHub Check Runs that block pull requests︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Find all blocking check runs tied to a known secret incident so you can review before unblocking a PR.
copy
$ curl -s -H 'Authorization: Token <manager-token>' 'https://api.gitguardian.com/v1/check-runs?incident_id=3759'
Programmatically skip a blocking check run marked as a false positive, so the PR can merge even when workspace Skip buttons are disabled.
copy
$ curl -s -X POST -H 'Authorization: Token <manager-token>' -H 'Content-Type: application/json' -d '{"reason": "false_positive"}' 'https://api.gitguardian.com/v1/check-runs/42/skip'
Adds GET /v1/check-runs endpoint to list GitHub check runs GitGuardian ran on pull requests, filterable by incident_id to surface runs that reported a specific secret incident.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds POST /v1/check-runs/{check_run_id}/skip endpoint to programmatically skip a blocking GitHub check run, tagging its incidents and occurrences with CHECK_RUN_SKIP_* and logging activity — even when the Skip buttons are disabled in workspace settings. Not checked yet Exposes check run response fields including repository_full_name, commit_sha, pull_requests, github_status, github_conclusion, head_branch, and base_branch for rich filtering and automation. Not checked yet
3 details in Everything
ggscout 0.34.1 adds in-network validity checks and permissions analysis for vaulted secrets, plus a new POST /v1/check-runs/{check_run_id}/skip API endpoint.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Opt out of validity and permissions checks on a specific ggscout deployment where outbound provider calls are not permitted.
ini
copy
[check]
enabled = false
Adds in-network validity checks and permissions analysis to ggscout (requires v0.34.1 or later), running after classification and before hashing so internal vaults, VPN VPN A virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. -gated databases, and provider-restricted endpoints are reachable without allowlisting GitGuardian IPs, with a new [check] enabled = false config key to opt out of these checks per deployment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Surfaces validity results in the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory as a Validity column and filter with Valid and Invalid values, exposes token permission scopes (e.g. repo, admin:org on GitHub; api on GitLab) per credential in the NHI identity detail, adds owner account, expiry date, and provider metadata to NHI identity detail via ggscout, and merges validity verdicts from vaulted or Kubernetes secrets with any matching secret incident, keeping the most recent verdict across both surfaces. Not checked yet Adds a built-in Valid saved view to the Endpoint Protection discovered secrets page, listing all secrets currently checked as valid. Not checked yet On-demand Jira Cloud scans launched from the dashboard or the public API now queue ahead of recurrent and system scans; public API launches using a service account token on AWS S3 and version control sources now count as on-demand scans. Not checked yet GitGuardian plans are renamed to Free (Starter), Growth, and Enterprise, and the Plan and usage page now compares features per plan grouped as on the pricing page. Not checked yet
Adds in-network validity checks and permissions analysis to ggscout (requires v0.34.1 or later), running after classification and before hashing so internal vaults, VPN VPN A virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. -gated databases, and provider-restricted endpoints are reachable without allowlisting GitGuardian IPs, with a new [check] enabled = false config key to opt out of these checks per deployment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Surfaces validity results in the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory as a Validity column and filter with Valid and Invalid values, exposes token permission scopes (e.g. repo, admin:org on GitHub; api on GitLab) per credential in the NHI identity detail, adds owner account, expiry date, and provider metadata to NHI identity detail via ggscout, and merges validity verdicts from vaulted or Kubernetes secrets with any matching secret incident, keeping the most recent verdict across both surfaces. Not checked yet Adds a built-in Valid saved view to the Endpoint Protection discovered secrets page, listing all secrets currently checked as valid. Not checked yet
2 more in Everything
api-docs-5b2c2350cba5
Oct 16, 2026
·
issue 110
GitGuardian adds NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. identity owner management endpoints for reading and updating ownership of non-human identities non-human identities A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
List all owners of a non-human identity non-human identity A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. to audit accountability for a service account or API key.
copy
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/nhi/identities/{identity_id}/owners'
Assign an owner to a non-human identity so the responsible team member is tracked for remediation workflows.
copy
$ curl -s -X POST -H 'Authorization: Token <api_key>' -H 'Content-Type: application/json' -d '{"owner_id": "<owner_id>"}' 'https://api.gitguardian.com/v1/nhi/identities/{identity_id}/owners'
Remove a former owner from a non-human identity when team membership changes.
copy
$ curl -s -X DELETE -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/nhi/identities/{identity_id}/owners/{owner_id}'
Adds GET /v1/nhi/identities/{identity_id}/owners endpoint to list owners of a non-human identity.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds POST /v1/nhi/identities/{identity_id}/owners endpoint to assign owners to a non-human identity. Not checked yet Adds POST /v1/nhi/identities/{identity_id}/owners/update endpoint to update ownership records for a non-human identity. Not checked yet Adds GET /v1/nhi/identities/{identity_id}/owners/{owner_id} endpoint to retrieve a specific owner of a non-human identity. Not checked yet Adds DELETE /v1/nhi/identities/{identity_id}/owners/{owner_id} endpoint to remove a specific owner from a non-human identity. Not checked yet
5 details in Everything
Check validity and permissions of your vaulted secrets, from inside your network (2026-10-15)
Oct 15, 2026
·
issue 110
ggscout 0.34.1 checks validity and permissions of vaulted secrets in-network, surfacing live verdicts in the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Disable in-network validity checks for a specific ggscout deployment that cannot reach external providers.
ini
copy
[check]
enabled = false
After upgrading to ggscout 0.34.1, run a fetch-and-send to populate validity verdicts, then filter the NHI inventory to immediately see all invalid credentials still sitting in vaults or Kubernetes clusters.
📍 In NHI Governance → Identities, open the Validity filter and select Invalid to list revoked credentials across vaults, CI variables, and Kubernetes clusters.
Adds [check] enabled = false config key to opt out of in-network validity and permissions checks per ggscout deployment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds a Validity column and filter (Valid, Invalid, Unknown) for all secrets collected by ggscout, surfaces token permission scopes (e.g. repo, admin:org on GitHub; api on GitLab) alongside each identity, and reports credential owner, expiry date, and provider metadata in the identity detail view, sourced directly from the provider during each ggscout run, in the NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. → Identities inventory. Not checked yet Merges validity verdicts from vaulted or Kubernetes secrets with any matching secret incident, always keeping the most recent verdict. Not checked yet Adds a built-in Valid saved view on the Endpoint Protection discovered secrets page, available to all users. Not checked yet Documents all API token permissions in the public API documentation, including eleven previously granted but undocumented permissions. Not checked yet
+1 more
show less
Adds on-demand priority queuing for Jira Cloud historical scans launched from the dashboard or public API so they start ahead of recurrent and system scans, and counts public API historical scan launches made with a service account token as on-demand on AWS S3 and version control sources. Not checked yet
Adds [check] enabled = false config key to opt out of in-network validity and permissions checks per ggscout deployment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds a Validity column and filter (Valid, Invalid, Unknown) for all secrets collected by ggscout, surfaces token permission scopes (e.g. repo, admin:org on GitHub; api on GitLab) alongside each identity, and reports credential owner, expiry date, and provider metadata in the identity detail view, sourced directly from the provider during each ggscout run, in the NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. → Identities inventory. Not checked yet Merges validity verdicts from vaulted or Kubernetes secrets with any matching secret incident, always keeping the most recent verdict. Not checked yet Adds a built-in Valid saved view on the Endpoint Protection discovered secrets page, available to all users. Not checked yet
2 more in Everything
GitGuardian adds Harbor registry scanning, per-secret environment classification, PR comment notes, and a new presence-check API endpoint︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Trigger an on-demand presence check for a specific secret incident without waiting for the next scheduled scan.
copy
$ curl -X POST 'https://api.gitguardian.com/v1/incidents/secrets/42/check-presence' \
-H 'Authorization: Token <your-api-token>'
Filter the incidents API to only surface incidents where ALL sources are deleted or archived, reducing noise from partially-removed code.
copy
$ curl -G 'https://api.gitguardian.com/v1/incidents' \
-H 'Authorization: Token <your-api-token>' \
--data-urlencode 'source_monitoring_status__all=deleted,archived'
Set up Harbor integration via the GitGuardian dashboard to begin scanning all image layers in a self-hosted registry for secrets.
📍 1. In Harbor, create a system-level robot account with Repository (List, Pull) and Artifact (List, Read) permissions.
2. In GitGuardian, go to Integrations › Harbor.
3. Enter your Harbor URL and the robot account name (including its robot$ prefix) and secret.
4. Choose your monitored perimeter: select specific Harbor repositories or monitor the entire instance.
Adds POST /v1/incidents/secrets/{id}/check-presence and POST /v1/public-incidents/secrets/{id}/check-presence endpoints to trigger an asynchronous presence check on a secret incident.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds source_monitoring_status__all operator to the public API, exposing the new is all of filter so you can isolate incidents whose sources are ALL deleted or archived. Not checked yet Adds per-secret environment classification in NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. , reading environment from secret paths, tags, and labels (recognising prod, prd, stg, qa, uat, dev, and more) before falling back to the source-level env setting. Not checked yet Enables developers to reply to a GitGuardian check run by commenting @gitguardian on a pull request, adding the comment as a note on every incident the check run found, visible in the dashboard and through the incident notes API. Not checked yet Adds is all of operator to the source status filter in the UI, letting you isolate incidents whose sources are all deleted or archived. Not checked yet
+3 more
show less
Supports connecting GitGuardian to Google Cloud keyless via Workload Identity Federation, removing the need to store or rotate a service account key, with project, folder, or organization-level scopes. Not checked yet Confluence incident notifications now carry the stable Confluence user key for new occurrences, enabling mapping of incident authors to users even when the instance does not expose emails. Not checked yet GitLab System Hooks integrations with a non-admin token now monitor projects in personal namespaces and in groups the service account reaches only through a project. Not checked yet
Adds POST /v1/incidents/secrets/{id}/check-presence and POST /v1/public-incidents/secrets/{id}/check-presence endpoints to trigger an asynchronous presence check on a secret incident.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Enables developers to reply to a GitGuardian check run by commenting @gitguardian on a pull request, adding the comment as a note on every incident the check run found, visible in the dashboard and through the incident notes API. Not checked yet Supports connecting GitGuardian to Google Cloud keyless via Workload Identity Federation, removing the need to store or rotate a service account key, with project, folder, or organization-level scopes. Not checked yet
5 more in Everything
GitGuardian adds incident playbook multi-user assignment and GitHub team auto-creation for direct-access members︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds playbook auto-assign to multiple users for incident routing, enabling a single playbook to assign incidents to more than one user simultaneously.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds opt-in GitHub team sync option to auto-create GitGuardian teams for GitHub users who belong to no GitHub team, grouped by the repositories they access directly, enabling 100% team coverage. Not checked yet
Adds playbook auto-assign to multiple users for incident routing, enabling a single playbook to assign incidents to more than one user simultaneously.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Scan your Harbor container registry for secrets (2026-10-09)
Oct 9, 2026
·
issue 099
Harbor integration uses a read-only robot account, supports air-gapped instances via GitGuardian Bridge, flags unhealthy installs, and enables secret rotation without reinstall.
Uses a Harbor robot account with Repository (List, Pull) and Artifact (List, Read) permissions only — read-only, scoped, and revocable at any time. Not checked yet Supports scanning Harbor instances not reachable from the internet via GitGuardian Bridge. Not checked yet Allows selecting specific Harbor repositories or monitoring the entire instance with automatic inclusion of new repositories. Not checked yet Performs both historical scanning of existing images and incremental scanning of newly pushed images. Not checked yet Flags unhealthy installations (expired robot accounts, lost permissions, or unreachable instances) and supports rotating the robot account secret without reinstalling. Not checked yet
+1 more
show less
New integration Navigate to Settings > Integrations > Sources and click Install next to Harbor in the Container registries section to configure the integration. Not checked yet
6 details in Everything
api-docs-41a58f79d912
Oct 5, 2026
·
issue 095
GitGuardian SaaS: Introduces NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. — NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. Identity Owners API group — enabling programmatic ownership management of non-human identities non-human identities A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. via scopes nhi:ownership:read and nhi:ownership:write.
└──▷ TRY IT
Trigger a fresh presence check on a private secret incident to confirm whether its occurrences still exist in source repositories.
copy
$ curl -s -X POST 'https://api.gitguardian.com/v1/incidents/secrets/42/check-presence' \
-H 'Authorization: Token <your_api_token>'
Assign ownership of an NHI to two team members by email so they receive governance alerts for that identity.
copy
$ curl -s -X POST 'https://api.gitguardian.com/v1/secret-observability/identities/1234/owners' \
-H 'Authorization: Token <your_api_token>' \
-H 'Content-Type: application/json' \
-d '{"owners": [{"email": "alice@example.com"}, {"email": "bob@example.com"}]}'
List only secret incidents that have at least one source still actively monitored but archived, to triage stale exposure.
copy
$ curl -s 'https://api.gitguardian.com/v1/incidents/secrets?source_monitoring_status__in=archived,unreachable' \
-H 'Authorization: Token <your_api_token>'
└──▷ USE IT
Set a persistent API timeout in ggshield config so every scan in the environment respects the higher limit.
~/.gitguardian.yaml
copy
api_timeout: 120
└──▷ BREAKING ON UPGRADE
! The Health filter on the perimeter sources table is replaced by Has open incidents ; existing saved views are migrated automatically.
api-docs-41a58f79d912
Oct 4, 2026
·
issue 094
GitGuardian SaaS: Adds POST /v1/secret-observability/identities/{identity_id}/owners to add up to 5 owners (by email) to a non-human identity non-human identity A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. without removing existing ones.
└──▷ TRY IT
Trigger a live presence re-check on a private secret incident to confirm whether the leaked credential is still present in its source repos.
copy
$ curl -X POST 'https://api.gitguardian.com/v1/incidents/secrets/42/check-presence' \
-H 'Authorization: Token <your_api_token>'
Assign an owner to an NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. identity so the responsible team member is accountable for rotating or revoking the credential.
copy
$ curl -X POST 'https://api.gitguardian.com/v1/secret-observability/identities/1234/owners' \
-H 'Authorization: Token <your_api_token>' \
-H 'Content-Type: application/json' \
-d '{"owners": [{"email": "alice@example.com"}]}'
Filter the incident list to surface only incidents whose sources are fully gone (archived or deleted on remote), helping triage what no longer needs active remediation.
copy
$ curl -G 'https://api.gitguardian.com/v1/incidents/secrets' \
-H 'Authorization: Token <your_api_token>' \
--data-urlencode 'source_monitoring_status__all=archived,deleted_on_remote'
Introduces NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. / NHI Identity Owners as a new API surface area, requiring nhi:ownership:read or nhi:ownership:write scopes and Manager access level or above (or a service account token). Not checked yet
1 detail in Everything
GitGuardian SaaS: Replaces the Health filter on the perimeter page with a Has open incidents filter; saved views are migrated.
└──▷ USE IT
Raise the API timeout when large scans fail with a read timeout error.
yaml
copy
api_timeout: 120
Set the API timeout via environment variable in a CI pipeline where config files are not practical.
📍 GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
└──▷ BREAKING ON UPGRADE
! The Health filter on the perimeter sources table is replaced by the Has open incidents filter; saved views are migrated automatically.
api-docs-41a58f79d912
Oct 3, 2026
·
issue 093
GitGuardian API adds NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. identity owner management, presence-check endpoints, and source monitoring status filters for secret incidents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Re-verify whether a leaked secret is still live on its source before closing or escalating an incident.
copy
$ curl -s -X POST https://api.gitguardian.com/v1/incidents/secrets/42/check-presence \
-H 'Authorization: Token <your_api_token>'
Assign an owner to an NHI identity programmatically so your team can track who is responsible for a non-human credential.
copy
$ curl -s -X POST https://api.gitguardian.com/v1/secret-observability/identities/99/owners \
-H 'Authorization: Token <manager_api_token>' \
-H 'Content-Type: application/json' \
-d '{"owners": [{"email": "alice@example.com"}]}'
Narrow an incident triage pipeline to secrets still reachable in real time by excluding those whose sources are entirely archived or deleted.
copy
$ curl -s 'https://api.gitguardian.com/v1/incidents/secrets?source_monitoring_status__nin=archived,deleted_on_remote' \
-H 'Authorization: Token <your_api_token>'
Adds POST /v1/incidents/secrets/{incident_id}/check-presence to trigger an asynchronous presence check on a private secret incident, confirming whether occurrences still exist on their sources.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds POST /v1/public-incidents/secrets/{incident_id}/check-presence to trigger an asynchronous presence check on a public secret incident. Not checked yet Adds GET /v1/secret-observability/identities/{identity_id}/owners to list active NHI identity owners, including both GitGuardian-suggested and manually added owners (requires Manager access level or service account token). Not checked yet Adds POST /v1/secret-observability/identities/{identity_id}/owners to add owners to an NHI identity by email address, up to a maximum of 5 owners per identity. Not checked yet Adds POST /v1/secret-observability/identities/{identity_id}/owners/update to replace all owners of an NHI identity atomically; an empty list removes all owners. Not checked yet
+5 more
show less
Adds DELETE /v1/secret-observability/identities/{identity_id}/owners/{owner_id} to remove a specific owner from an NHI identity and suppress future suggestions for that owner. Not checked yet Adds source_monitoring_status__in query parameter to secret incident list endpoints to keep only incidents with at least one source in the given comma-separated monitoring status buckets (e.g. archived,unreachable); requires the monitoring-status feature on the workspace. Not checked yet Adds source_monitoring_status__nin query parameter to exclude secret incidents where all sources fall within the specified monitoring status buckets (e.g. archived). Not checked yet Adds source_monitoring_status__all query parameter to keep only secret incidents whose every source is in the given monitoring status buckets (e.g. archived,deleted_on_remote). Not checked yet Introduces NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. and NHI Identity Owners as a new API surface area under /v1/secret-observability/identities, with nhi:ownership:read and nhi:ownership:write scopes. Not checked yet
10 details in Everything
GitGuardian adds Wiz secret-findings integration, Coverage Hub, AI hook expansion to Kiro/Junie, and configurable API timeout.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Persist a higher API timeout in ggshield config so every scan in the environment picks it up without an env-var prefix.
~/.gitguardian.yaml
copy
api_timeout: 120
Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout for large scans.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds native Wiz integration that syncs active GitGuardian secret incidents to Wiz as secret findings daily, carrying repository, file path, commit, detector, validity, severity, and a SHA-256 SHA-256 A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. hash of the secret — never the raw value. Not checked yet Extends AI Hooks and ggshield 1.55.0+ to cover Amazon Kiro (IDE and CLI) and Junie CLI, blocking secrets in commands and file reads. Not checked yet Adds tool-output withholding on Claude Code, Codex, and Mistral Vibe: ggshield intercepts tool output containing secrets and replaces it with a safe message so the secret never reaches the model or session transcript. Not checked yet Introduces the Coverage Hub on the perimeter page: four cards showing installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team — each card action filters the sources table to the gap. Not checked yet
+8 more
show less
Adds a Team column to the sources table and a No team assigned filter option to surface unowned sources; replaces the Health filter with Has open incidents . Not checked yet Adds a new Public Monitoring agents page showing how agents classified incidents as Related, Unclear, or Not related, with counts linking to matching incidents. Not checked yet Extends the secret value and validity API endpoints to cover secrets found through Public Monitoring, not only Internal Monitoring. Not checked yet Adds optional author attribution for leaks detected through custom sources (BYOS), allowing an author email to be provided and returned when leaks are found. Not checked yet Introduces a per-account setting to keep team access to unmonitored sources and their existing incidents instead of removing them from team perimeters. Not checked yet Introduces a per-account setting to automatically remove archived sources from team perimeters. Not checked yet Perimeter bulk actions now gray out inapplicable actions with a tooltip explanation, and show a confirmation listing skipped sources when monitoring, unmonitoring, or scanning more than 30 sources. Not checked yet System hooks integrations with a non-admin token now monitor projects in personal namespaces and in groups the service account reaches only through a project. Not checked yet
Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout for large scans.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds native Wiz integration that syncs active GitGuardian secret incidents to Wiz as secret findings daily, carrying repository, file path, commit, detector, validity, severity, and a SHA-256 SHA-256 A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. hash of the secret — never the raw value. Not checked yet Adds tool-output withholding on Claude Code, Codex, and Mistral Vibe: ggshield intercepts tool output containing secrets and replaces it with a safe message so the secret never reaches the model or session transcript. Not checked yet Introduces the Coverage Hub on the perimeter page: four cards showing installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team — each card action filters the sources table to the gap. Not checked yet Adds a new Public Monitoring agents page showing how agents classified incidents as Related, Unclear, or Not related, with counts linking to matching incidents. Not checked yet
+2 more
show less
Introduces a per-account setting to keep team access to unmonitored sources and their existing incidents instead of removing them from team perimeters. Not checked yet Introduces a per-account setting to automatically remove archived sources from team perimeters. Not checked yet
6 more in Everything
└──▷ BREAKING ON UPGRADE
! The Health filter on the perimeter sources table is replaced by Has open incidents ; saved views using the old filter are migrated automatically.
GitGuardian adds Agents Analysis to Public Monitoring: automatic company-relevance verdicts, an Analysis tab with reasoning, and analyst feedback controls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
When triaging a flood of public exposure alerts, open the Company-related saved view first to see only incidents Agents Analysis has confirmed as belonging to your org, then drill into the Analysis tab on any incident to review the reasoning and Investigation details before deciding on remediation.
📍 In Public Monitoring, select the Company-related saved view › open an incident › click the Analysis tab to review the verdict (Related / Uncertain / Unrelated), the reasoning, and the Investigation details section.
After reviewing an incident where Agents Analysis reached the wrong company-attribution conclusion, submit a thumbs-down with a comment so GitGuardian can improve attribution accuracy for your organization over time.
📍 In Public Monitoring, open an incident › click the Analysis tab › click the thumbs-down icon › optionally type a comment explaining the misattribution › submit.
Adds an Analysis tab on public incidents showing the company-relevance verdict (Related, Uncertain, or Unrelated), the reasoning behind it, and an Investigation details section tracing how the incident moved through triage.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds thumbs-up/thumbs-down feedback controls with optional comments on the Analysis tab, letting analysts signal when company attribution is correct or incorrect. Not checked yet Introduces Agents Analysis, which automatically labels every analyzed public incident with a Company-related verdict and is enabled automatically for all customers using Public Monitoring. Not checked yet Reorganizes the Public Monitoring incident list with three new saved views — Company-related , Unclear if company-related , and Not company-related — alongside the existing All and Open views. Not checked yet Adds Company-related and Risk score columns to the Public Monitoring incident list by default. Not checked yet
+1 more
show less
Updates agent-generated risk scoring so that company-relevance (not just the secret's own characteristics) drives incident score, with Unrelated incidents receiving a score of zero and unanalyzed incidents carrying no score. Not checked yet
Adds an Analysis tab on public incidents showing the company-relevance verdict (Related, Uncertain, or Unrelated), the reasoning behind it, and an Investigation details section tracing how the incident moved through triage.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds thumbs-up/thumbs-down feedback controls with optional comments on the Analysis tab, letting analysts signal when company attribution is correct or incorrect. Not checked yet Introduces Agents Analysis, which automatically labels every analyzed public incident with a Company-related verdict and is enabled automatically for all customers using Public Monitoring. Not checked yet
3 more in Everything
Wiz integration syncs active secret incidents as native Wiz findings daily; a new Public Monitoring agents page tracks incident classification and triage counts.
New integration Integrates with Wiz to push active secret incidents from version control sources as native Wiz secret findings on a daily sync, carrying repository, file path, commit, detector, validity, severity, and a link back to the GitGuardian incident. Not checked yet Severity of the GitGuardian incident is mapped to the severity of the corresponding Wiz finding, keeping critical secrets marked critical in both platforms. Not checked yet Sends only a SHA-256 SHA-256 A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. hash of the secret and its metadata to Wiz — the raw secret value is never transmitted. Not checked yet Automatically closes Wiz findings when the corresponding GitGuardian incident is resolved or ignored, with no manual reconciliation required. Not checked yet Adds a Public Monitoring agents page showing how agents classified all public incidents (Related , Unclear , Not related ) and how they moved through triage and deep analysis, with counts linking to matching incidents. Not checked yet
5 details in Everything
Push your secret incidents to Wiz (2026-09-30)
Sep 30, 2026
·
issue 090
GitGuardian adds a Wiz integration that syncs active secret incidents as native Wiz findings and a new agents page for public incident classification.
New integration Adds a Wiz integration that daily syncs active secret incidents from version control sources into Wiz as native secret findings, carrying repository, file path, commit, detector, validity, severity, and a link back to the GitGuardian incident. Not checked yet Transfers only a SHA-256 SHA-256 A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. hash of the secret and its metadata to Wiz — the raw secret value never leaves GitGuardian. Not checked yet Maps GitGuardian incident severity directly to the Wiz finding severity, so a critical secret appears as critical in both platforms. Not checked yet Auto-closes Wiz findings when the corresponding GitGuardian incident is resolved or ignored — each sync uploads the full active-incident list and Wiz removes findings that drop off. Not checked yet Adds a GitGuardian agents page showing how agents classified public incidents (Related, Unclear, Not related) and their progression through triage and deep analysis, with each count linking to matching incidents. Not checked yet
5 details in Everything
api-docs-93f0b74f7cdd
Sep 29, 2026
·
issue 089
GitGuardian API gains occurrence content retrieval and scan list/poll endpoints for secrets and audit workflows.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Fetch the exact file content and secret match positions for a known private occurrence — what a reviewer sees in the dashboard — via the API for automated triage pipelines.
copy
$ curl -H 'Authorization: Token <your-pat>' \
'https://api.gitguardian.com/v1/occurrences/secrets/42/content'
Poll for all scans that are still running or whose payload changed since a checkpoint timestamp, so a CI integration never misses a scan that finished or gained an audit summary between two polls.
copy
$ curl -H 'Authorization: Token <your-pat>' \
'https://api.gitguardian.com/v1/scans?active_or_updated_since=2025-09-22T10:00:00Z'
Retrieve a single scan's byte and element counters plus its audit summary to drive a poll-until-complete loop that waits for the audit report, not just scan completion.
copy
$ curl -H 'Authorization: Token <your-pat>' \
'https://api.gitguardian.com/v1/scans/<scan_id>'
Adds GET /v1/occurrences/secrets/{occurrence_id}/content to retrieve the file content and secret match positions GitGuardian stored for a private occurrence, requiring a PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. with read:incident and secrets:read scopes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds GET /v1/public-incidents/secrets/{incident_id}/occurrences/{occurrence_id}/content to retrieve the same stored content for occurrences of public incidents, with the same PAT and scope requirements. Not checked yet Adds GET /v1/scans to list historical scans in bulk — the same payload as the scan detail endpoint — supporting the active_or_updated_since query parameter (ISO 8601 ISO 8601 An international standard for representing dates and times as text, using formats like 2025-04-23T14:00:00Z. Tools adopt it to ensure timestamps are unambiguous and sortable across systems and locales. ) to efficiently poll only scans still running or updated since a given instant, sorted by -gg_created_at by default. Not checked yet Adds GET /v1/scans/{scan_id} to retrieve a single scan's progress: element and byte counters plus the audit summary once available, enabling poll-until-complete workflows that distinguish scan completion from audit summary readiness. Not checked yet
4 details in Everything
GitGuardian adds automatic source-removal rules for team perimeters based on deleted, archived, or unmonitored status.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Automatically remove unmonitored sources from a team perimeter so stale sources do not clutter a team's incident view — while keeping manager access intact.
📍 In the GitGuardian console, go to Workspace Settings › Team perimeter and enable the Unmonitored sources setting so that sources which are no longer monitored are automatically removed from all team perimeters.
GitGuardian's Monitored Perimeter page gains a Coverage Hub, saved views, bulk actions, and team-ownership tracking.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Kick off historical scans for every source that has never been scanned, confirming the batch when GitGuardian prompts on selections over 30 sources.
📍 In the Monitored Perimeter page, click See unscanned sources in the Historical scans card, use 'Select all N sources that match filters', choose the Launch historical scan bulk action, and confirm the dialog.
Adds the Coverage Hub — four summary cards (Integrations, Real time monitoring, Historical scans, Team ownership) above the perimeter table that quantify coverage gaps and link directly to filtered source lists.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds saved views to the perimeter page, including non-editable built-in views: Monitored , Critical sources , With open secret incidents , Scanning issues , and Without honeytoken . Not checked yet Adds Columns control to show, hide, or reorder perimeter table columns. Not checked yet Adds bulk actions bar for acting on many sources at once, including Monitor , Unmonitor , and Launch historical scan ; confirmations are required when selecting more than 30 sources or when some sources will be skipped. Not checked yet Adds Teams column (shown by default in the Monitored view) and a No team assigned filter value to identify unowned sources. Not checked yet
+2 more
show less
Adds Last scan column with a Skipped badge and hover explanation for scans that did not run. Not checked yet Adds team perimeter setting for unmonitored sources, letting managers keep or remove unmonitored and archived/deleted sources from team perimeters. Not checked yet
7 details in Everything
GitGuardian SaaS: Adds optional author attribution for leaks detected through custom sources (BYOS), allowing an author email to be provided and returned when leaks are found.
└──▷ USE IT
Raise the API timeout so that large repository scans no longer fail with a read timeout error.
.gitguardian.yaml
copy
api_timeout: 120
Adds support for monitoring GitLab projects under personal namespaces even when the service account lacks namespace-level access. Not checked yet Introduces a per-account setting to keep team access to unmonitored sources and their existing incidents instead of removing them from team perimeters. Not checked yet Extends secret value and validity API endpoints to cover secrets found via Public Monitoring, not only Internal Monitoring. Not checked yet
Introduces a per-account setting to keep team access to unmonitored sources and their existing incidents instead of removing them from team perimeters. Not checked yet
2 more in Everything
└──▷ BREAKING ON UPGRADE
! The Health filter on the sources table is replaced by Has open incidents ; saved views using Health are migrated automatically.
Spot your uncovered assets. Close your blindspot in one click! (2026-09-28)
Sep 28, 2026
·
issue 089
GitGuardian's new Coverage Hub surfaces unmonitored, unscanned, and unowned sources on the perimeter page with one-click remediation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Identify all sources not yet assigned to a team and bulk-assign them to close ownership gaps.
📍 In the perimeter page, click the Owned by a team card action to filter the sources table to unassigned sources, select all, then choose a bulk action to assign them. Alternatively, use the Team filter and select No team assigned to reach the same view.
Surface integrations with unreachable sources so you can restore monitoring coverage before secrets go undetected.
📍 In the perimeter page, look for the red badge on the Coverage Hub, then click Show more details to see which integrations have unreachable sources and click the card action to filter the table to those sources.
Adds the Coverage Hub to the perimeter page: four cards show installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds card actions that filter the sources table to sources needing action — unmonitored, unscanned, or unassigned — in one click. Not checked yet Adds a red badge on the Coverage Hub to count sources GitGuardian cannot reach, with a Show more details view listing integrations and flagging unreachable ones. Not checked yet Adds a Teams column to the perimeter sources table showing the teams assigned to each source. Not checked yet Adds a No team assigned option to the Team filter to surface sources without an owner. Not checked yet
+3 more
show less
Replaces the Health filter with Has open incidents on the perimeter page, with saved views migrated automatically. Not checked yet Sorts the perimeter sources table by open incidents by default, prioritising sources at risk. Not checked yet Improves bulk actions on perimeter sources: grays out inapplicable actions with explanatory tooltips, and lists skipped sources with reasons when monitoring, unmonitoring, or scanning more than 30 sources. Not checked yet
Adds the Coverage Hub to the perimeter page: four cards show installed integrations, share of sources monitored in real time, share scanned successfully, and share owned by a team.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds card actions that filter the sources table to sources needing action — unmonitored, unscanned, or unassigned — in one click. Not checked yet Adds a red badge on the Coverage Hub to count sources GitGuardian cannot reach, with a Show more details view listing integrations and flagging unreachable ones. Not checked yet Adds a Teams column to the perimeter sources table showing the teams assigned to each source. Not checked yet
4 more in Everything
└──▷ BREAKING ON UPGRADE
! The Health filter on the perimeter page is replaced by Has open incidents ; saved views using the old filter are migrated automatically.
└──▷ HOW TO FIND IT
Prevent large-repo scans from failing with a read timeout by raising the API timeout above the old 60-second hard limit.
📍 GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
Set a persistent API timeout in the ggshield config file so every scan honours the higher limit without needing an environment variable.
~/.gitguardian/.gitguardian.yaml
copy
api_timeout: 120
api-docs-401357175309
Sep 26, 2026
·
issue 086
GitGuardian SaaS: Adds report_status field to historical scan progress responses, signalling done (with final duration_seconds, pending_seconds, and outcome_by_reason) or unavailable independently of scan_status, so callers know when the audit summary is ready rather than just when the scan has finished.
└──▷ TRY IT
Verify which custom GitLab (or other service) hosts your workspace has registered, so you can confirm a self-hosted instance is being checked for leaked tokens.
copy
$ curl -s -H 'Authorization: Token <your_api_key>' https://api.gitguardian.com/v1/detector-custom-hosts | jq '.[] | {detector: .detector_name, default: .checker_default_base_url, custom: [.custom_hosts[].base_url]}'
Poll a historical scan until the audit summary is ready — stop on report_status of done or unavailable rather than on scan_status alone.
copy
$ while true; do
resp=$(curl -s -H 'Authorization: Token <your_api_key>' "https://api.gitguardian.com/v1/historical-scans/<scan_id>/progress")
report_status=$(echo "$resp" | jq -r '.report_status')
echo "report_status: $report_status"
if [ "$report_status" = "done" ] || [ "$report_status" = "unavailable" ]; then
echo "$resp" | jq '{duration_seconds, pending_seconds, outcome_by_reason}'
break
fi
sleep 5
done
GitGuardian SaaS: Adds an opt-in Public Monitoring playbook that auto-ignores incidents agents rule Unrelated with reason Credential not related to the company , closed by GitGuardian Bot.
api-docs-401357175309
Sep 25, 2026
·
issue 085
GitGuardian API adds detector custom hosts endpoint and live historical-scan progress polling︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Verify which custom GitLab (or other self-hosted) base URLs your workspace has registered for secret detection, to confirm coverage before scanning an internal repo.
copy
$ curl -s -H 'Authorization: Token <your_api_token>' https://api.gitguardian.com/v1/detector-custom-hosts
Adds live progress polling for historical scans, exposing report_status (values: running, watching, done, unavailable) alongside scan_status, with terminal fields duration_seconds, pending_seconds, and outcome_by_reason (reasons: skipped, binary_file, too_large, failed, file_not_downloadable, empty_content) available once report_status reaches done. Not checked yet
1 detail in Everything
api-docs-e88e8519d038
Sep 25, 2026
·
issue 085
└──▷ TRY IT
Audit which custom host URLs (e.g. self-hosted GitLab instances) are registered for each secret detector in your workspace.
copy
$ curl -s -H 'Authorization: Token <your_api_key>' https://api.gitguardian.com/v1/detector-custom-hosts | jq '.'
AI Hooks keep leaked tool output away from the model (2026-09-25)
Sep 25, 2026
·
issue 087
AI Hooks now withhold tool output from Claude Code, Codex, and Mistral Vibe, and extend coverage to Kiro and Junie CLI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Raise the API timeout when large scans are failing with read timeouts in CI or on slow networks.
yaml
copy
api_timeout: 120
Register AI Hooks for Kiro and Junie CLI on a developer workstation after upgrading to ggshield 1.55.0.
copy
$ ggshield machine setup
Override the API timeout via environment variable in a CI pipeline where the config file is not available.
📍 GITGUARDIAN_API_TIMEOUT=120 ggshield secret scan repo .
Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds ggshield machine setup subcommand to register AI Hooks for Kiro and Junie CLI in one step. Not checked yet AI Hooks now withhold shell-command output containing secrets from the model context on Claude Code, Codex, and Mistral Vibe — the assistant receives only the ggshield message, keeping the secret out of the model session transcript. Not checked yet Extends AI Hooks and the AI agents/MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. inventory to cover Amazon Kiro (IDE and CLI) and Junie CLI, blocking secrets in commands and file reads. Not checked yet
Adds api_timeout config key and GITGUARDIAN_API_TIMEOUT environment variable to override the previously fixed 60-second API timeout.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds ggshield machine setup subcommand to register AI Hooks for Kiro and Junie CLI in one step. Not checked yet
2 more in Everything
GitGuardian publishes a Docker Sandbox Mixin Kit that auto-installs ggshield AI hooks for Claude Code, Codex, Cursor, and GitHub Copilot agents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Store your GitGuardian API key securely outside the sandbox before launching, so the credential never lands inside the agent microVM.
copy
$ sbx secret set gitguardian
Adds sbx secret set gitguardian to supply a GitGuardian API key through Docker's host-side credential proxy, keeping the real token outside the sandbox microVM.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Publishes a Docker Sandbox Mixin Kit on Docker Hub and GitHub that automatically installs ggshield and configures agentic AI hooks when a sandbox starts, requiring no manual setup. Not checked yet Adds a prompt-submission hook via ggshield that scans a developer's prompt for secrets and blocks it before it reaches the AI model. Not checked yet Adds a pre-tool-use hook via ggshield that scans file reads, shell commands, and MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. calls before execution and blocks the action when a secret is detected. Not checked yet Adds a post-tool-use hook via ggshield that scans tool output and sends a desktop notification when a secret appears in the result. Not checked yet
+2 more
show less
Supports stacking the GitGuardian mixin with other kits by passing additional --kits <targeted mixin> arguments to sbx. Not checked yet Covers Claude Code, Codex, Cursor, and VS Code with GitHub Copilot as supported coding assistants in the mixin kit. Not checked yet
7 details in Everything
api-docs-9a01e0949b3e
Sep 24, 2026
·
issue 084
GitGuardian adds GET /v1/detector-custom-hosts to list workspace-level custom hosts grouped by secret detector.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Audit which custom GitLab (or other service) hosts your workspace has registered for secret detection, to verify self-hosted instances are being scanned.
copy
$ curl -s -H 'Authorization: Token <your_api_token>' https://api.gitguardian.com/v1/detector-custom-hosts
GitGuardian adds permissions sync from Bitbucket, Azure DevOps, Jira, Confluence, and JFrog Artifactory, plus Platform API notifier management︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds Platform API support to create, update, and delete Slack, Microsoft Teams, webhook, and email notifiers, enabling scripted and version-controlled notification setup for large workspaces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds team and permissions sync from Bitbucket, automatically mirroring Bitbucket groups, projects, and repository access into GitGuardian teams and perimeters. Not checked yet Adds team and permissions sync from Azure DevOps, automatically mirroring Azure DevOps projects, teams, and repository access into GitGuardian teams and perimeters. Not checked yet Adds team and permissions sync from Jira and Confluence, mirroring Jira project and Confluence space access into GitGuardian teams and perimeters. Not checked yet Adds team and permissions sync from JFrog Artifactory, mirroring Artifactory users, groups, and repository permissions into GitGuardian teams and perimeters. Not checked yet
5 details in Everything
GitGuardian adds 10 new detectors, 8 secret analyzers, and new validators for Splunk, Artifactory, Salesforce, and Databricks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds a new detector for Brightcove OAuth credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds a new detector for Infor ION API Gateway OAuth client credentials, capturing the authorization host and token endpoint when present. Not checked yet Adds a new detector for generic Sanctum tokens. Not checked yet Adds a new detector for Telnyx API keys with the KEY prefix. Not checked yet Adds a new detector for Bifrost virtual keys, matched alone or together with the URL of the Bifrost deployment. Not checked yet
+19 more
show less
Adds a new detector for Bitbucket HTTP access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. with the BBDC- prefix. Not checked yet Adds a new detector for Jira Data Center personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. . Not checked yet Adds a new detector for MetaApi cloud tokens. Not checked yet Adds a new detector for Appwrite instance encryption keys. Not checked yet Adds a new detector for APIclub API keys. Not checked yet Adds a new secret analyzer for AWS Cognito OAuth credentials with host. Not checked yet Adds a new secret analyzer for Alibaba Cloud IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. . Not checked yet Adds a new secret analyzer for Databricks access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. with hostname. Not checked yet Adds a secret analyzer for PyPI API tokens. Not checked yet Adds a secret analyzer for Contentful Content Management API keys. Not checked yet Adds a new secret analyzer for DigitalOcean personal access tokens v1. Not checked yet Adds a new secret analyzer for DigitalOcean tokens. Not checked yet Adds a new secret analyzer for DigitalOcean OAuth application tokens v1. Not checked yet Extends the Scaleway Token detector to catch SCW_SECRET_KEY and SCALEWAY_SECRET_KEY assignments, including when the word scaleway is absent from the document. Not checked yet Extends the Username Password detector to also match Spanish, Portuguese, French, and Turkish username/password assignment keywords. Not checked yet Extends the Salesforce OAuth2 OAuth2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. Keys detector to also capture the Salesforce instance host, and switches the checker to validate against that instance's OAuth token endpoint (production or sandbox) instead of the token introspection endpoint; returns failed_to_check when no host is found. Not checked yet Extends the Splunk Authentication Token detector to also match an optional Splunk host alongside the token, and adds a new checker that validates the token against it with custom host support. Not checked yet Adds a checker for Artifactory reference tokens with custom host support. Not checked yet Switches the Databricks Authentication Token With Hostname checker to a more reliable endpoint. Not checked yet
Adds a new detector for Brightcove OAuth credentials.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds a new detector for Infor ION API Gateway OAuth client credentials, capturing the authorization host and token endpoint when present. Not checked yet Adds a new detector for generic Sanctum tokens. Not checked yet Adds a new detector for Telnyx API keys with the KEY prefix. Not checked yet Adds a new detector for Bifrost virtual keys, matched alone or together with the URL of the Bifrost deployment. Not checked yet
+14 more
show less
Adds a new detector for Bitbucket HTTP access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. with the BBDC- prefix. Not checked yet Adds a new detector for Jira Data Center personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. . Not checked yet Adds a new detector for MetaApi cloud tokens. Not checked yet Adds a new detector for Appwrite instance encryption keys. Not checked yet Adds a new detector for APIclub API keys. Not checked yet Adds a new secret analyzer for AWS Cognito OAuth credentials with host. Not checked yet Adds a new secret analyzer for Alibaba Cloud IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. . Not checked yet Adds a new secret analyzer for Databricks access token access token A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. with hostname. Not checked yet Adds a secret analyzer for PyPI API tokens. Not checked yet Adds a secret analyzer for Contentful Content Management API keys. Not checked yet Adds a new secret analyzer for DigitalOcean personal access tokens v1. Not checked yet Adds a new secret analyzer for DigitalOcean tokens. Not checked yet Adds a new secret analyzer for DigitalOcean OAuth application tokens v1. Not checked yet Adds a checker for Artifactory reference tokens with custom host support. Not checked yet
5 more in Everything
api-docs-9a01e0949b3e
Sep 23, 2026
·
issue 083
└──▷ TRY IT
Audit which custom GitLab (or other service) base URLs are registered in your workspace so secrets are checked against self-hosted instances.
copy
$ curl -s -H 'Authorization: Token <your_api_key>' https://api.gitguardian.com/v1/detector-custom-hosts
api-docs-9a01e0949b3e
Sep 22, 2026
·
issue 082
└──▷ TRY IT
Audit which non-default GitLab (or other service) base URLs GitGuardian is scanning secrets against, to verify custom host coverage before a workspace change.
copy
$ curl -s -H 'Authorization: Token <your_api_token>' https://api.gitguardian.com/v1/detector-custom-hosts | jq '.[] | {detector: .detector_name, default: .checker_default_base_url, custom: [.custom_hosts[].base_url]}'
api-docs-9a01e0949b3e
Sep 21, 2026
·
issue 081
GitGuardian API adds GET /v1/detector-custom-hosts to list workspace custom hosts grouped by secret detector.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ TRY IT
Audit which custom host URLs (e.g. self-hosted GitLab instances) are registered for each secret detector in your workspace.
copy
$ curl -H 'Authorization: Token <your_api_token>' https://api.gitguardian.com/v1/detector-custom-hosts
GitGuardian roadmap adds integrations and protections including ServiceNow VR, Azure DevOps Boards, Linear, Mattermost, Google Chronicle SOAR SOAR Security orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions. , Docker Hub presence checks, and GitHub/GitLab issue integrations.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds ServiceNow Vulnerability Response (VR/AVR) integration to push GitGuardian secret incidents into ServiceNow with risk scoring, bi-directional status sync, and ServiceNow RBAC RBAC Role-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. /ABAC ABAC Attribute-based access control, where rules evaluate facts about the user, resource and request. Access can depend on conditions such as department, data sensitivity or device status. controls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds Azure DevOps Boards integration to automatically create and sync Azure DevOps work items from GitGuardian incidents. Not checked yet Adds Google Chronicle SOAR integration to send GitGuardian secret incidents natively, enabling playbook triggering and SOC SOC A security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. -driven remediation orchestration. Not checked yet Adds Linear integration to automatically create and sync Linear issues from GitGuardian incidents alongside engineering backlogs. Not checked yet Adds Mattermost integration for incident alerting, delivering GitGuardian notifications to Mattermost channels with the same options as Slack and Teams. Not checked yet
+6 more
show less
Adds GitHub Issues integration to automatically create issues on affected repositories when secrets are detected, reaching developers in their existing workflow. Not checked yet Adds GitLab Issues integration to automatically create and track GitLab issues from GitGuardian incidents, enabling remediation without a GitGuardian account. Not checked yet Adds a Docker Hub presence check to show whether a secret leaked in a public Docker Hub image is still exposed or whether the image has since been deleted or made private. Not checked yet Adds custom email sender support for notification emails, allowing customers to send from their own domain so recipients recognize the sender as internal. Not checked yet Adds a GitGuardian Power for Amazon Kiro with secret-detection skill guidelines, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. configuration, and hooks to secure AI-assisted development. Not checked yet Adds Public Monitoring support on self-hosted GitGuardian instances, bringing public secret leak detection to on-premises deployments. Not checked yet
11 details in Everything
GitGuardian now links AWS access keys stored in secrets managers, Vault, or Kubernetes to their AWS IAM AWS IAM AWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. identity in the identity map.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-b91fddb85ba2
Sep 14, 2026
·
issue 074
GitGuardian SaaS: Extends team read and write endpoints to accept secrets:read and secrets:write scoped API keys, supporting both personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. and service account tokens.
api-docs-b91fddb85ba2
Sep 13, 2026
·
issue 073
GitGuardian API adds external_provider_type field with Okta support for team management endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-b91fddb85ba2
Sep 12, 2026
·
issue 072
GitGuardian SaaS: Adds external_provider_type field (supporting "okta" as a valid value) to team-related API endpoints, enabling callers to read and write the external identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. associated with a team.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-b91fddb85ba2
Sep 11, 2026
·
issue 071
GitGuardian SaaS: Adds external_provider_type field to team API objects, with "okta" as a supported value, enabling identification of Okta-managed teams via the API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-b91fddb85ba2
Sep 10, 2026
·
issue 070
GitGuardian API adds external_provider_type field with Okta support for team management endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
GitGuardian adds AI agent/MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. secret blocking and vault secret classification via ggshield 1.54.0 and ggscout 0.32.0
└──▷ TRY IT
Bootstrap AI agent secret blocking across an entire developer machine — covers every detected agent (Codex, Cursor, Claude Code, etc.) plus git hooks in one step.
copy
$ ggshield machine setup
After a credential compromise, reconstruct which MCP tool calls an agent made by replaying its transcripts — useful for blast-radius analysis.
copy
$ ggshield ai discover --history
Adds AI Hooks to block secrets at prompt submission, pre-tool use tool use A model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions. , and post-tool use for Codex and Mistral Vibe, alongside existing Claude Code, Cursor, Copilot CLI, and VS Code coverage. Not checked yet Runs the Secrets Detection Engine on every value ggscout collects, classifying vaulted secrets against 550+ detectors including multi-match detectors. Not checked yet Adds detector, detector type, secret family, secret category, and secret provider filters and sort options to the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory. Not checked yet Groups multi-match credentials (e.g. PostgreSQL username, password, host, and port) as a single inventory entry rather than separate fields. Not checked yet Labels unmatched secrets as Unknown in the inventory so they remain visible and filterable without being dropped. Not checked yet
+1 more
show less
Adds per-team incident permission controls when promoting a user to Member, including bulk application and post-promotion editing of team rights. Not checked yet
Runs the Secrets Detection Engine on every value ggscout collects, classifying vaulted secrets against 550+ detectors including multi-match detectors. Not checked yet Adds detector, detector type, secret family, secret category, and secret provider filters and sort options to the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory. Not checked yet Groups multi-match credentials (e.g. PostgreSQL username, password, host, and port) as a single inventory entry rather than separate fields. Not checked yet Labels unmatched secrets as Unknown in the inventory so they remain visible and filterable without being dropped. Not checked yet
2 more in Everything
GitGuardian adds Docker Hub monitoring, intelligent perimeter-free attribution, unified exclusion rules, and a new agents overview page for public incidents.
└──▷ HOW TO FIND IT
Review how many of your public incidents the agents have analysed and drill into company-attribution verdicts.
📍 In the GitGuardian console, go to Public Monitoring › GitGuardian agents to see the breakdown of agent-analysed incidents and their company-attribution verdicts, then click through to the matching incidents.
Consolidate all your monitoring exclusions — sources, file paths, and patterns — into one place to reduce management overhead.
📍 In the GitGuardian console, go to Settings › Monitoring › Exclusion Rules to add or migrate source exclusions, file-path exclusions, and pattern exclusions into the Unified Exclusion Rules experience.
Adds a GitGuardian agents overview page under Public Monitoring showing how many public incidents the agents analysed and how company-attribution verdicts break down, with one-click filtering to matching incidents. Not checked yet Adds continuous Docker Hub monitoring, scanning public images daily and attributing exposures to your company as they appear after the initial historical scan. Not checked yet Adds intelligent attribution beyond your monitored perimeter for new GitHub commits, attributing public leaks to your company even when no perimeter rule matches. Not checked yet Adds intelligent attribution beyond your monitored perimeter for GitHub commit history, surfacing past leaks that no perimeter rule ever attributed to your company. Not checked yet Adds intelligent attribution beyond your monitored perimeter for Docker Hub images, attributing leaks found in public Docker Hub images even when no perimeter rule matches. Not checked yet
+6 more
show less
Adds Unified Exclusion Rules for Monitoring, consolidating source exclusions, file-path exclusions, and pattern exclusions into a single unified experience. Not checked yet Adds immediate agent analysis on new public incidents, making company-attribution verdicts and risk scores available as soon as an incident is created. Not checked yet Adds full agent analysis coverage on public incidents, ensuring company attribution and risk scores are present on every incident including those previously skipped. Not checked yet Adds decoded JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. and Base64 payload exposure in incident views. Not checked yet Enables assigning multiple users to incidents and automatically assigns the leaker as assignee. Not checked yet Scopes historical scans to each developer's time in perimeter, excluding activity from before they joined, with support for recurring scan schedules that apply new detectors to past commits. Not checked yet
Adds a GitGuardian agents overview page under Public Monitoring showing how many public incidents the agents analysed and how company-attribution verdicts break down, with one-click filtering to matching incidents. Not checked yet Adds continuous Docker Hub monitoring, scanning public images daily and attributing exposures to your company as they appear after the initial historical scan. Not checked yet Adds intelligent attribution beyond your monitored perimeter for new GitHub commits, attributing public leaks to your company even when no perimeter rule matches. Not checked yet Adds intelligent attribution beyond your monitored perimeter for GitHub commit history, surfacing past leaks that no perimeter rule ever attributed to your company. Not checked yet Adds intelligent attribution beyond your monitored perimeter for Docker Hub images, attributing leaks found in public Docker Hub images even when no perimeter rule matches. Not checked yet
+1 more
show less
Adds decoded JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. and Base64 payload exposure in incident views. Not checked yet
5 more in Everything
GitGuardian adds AI Hooks and agent/MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. inventory to Developer Endpoint Protection, plus IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. identity linking for stored AWS keys
└──▷ TRY IT
Bootstrap AI Hook and git hook coverage across every AI agent detected on a developer machine in one step.
copy
$ ggshield machine setup
After a credential compromise, reconstruct which MCP tool calls were made by parsing the agent's saved transcripts.
copy
$ ggshield ai discover --history
Adds AI Hooks to Developer Endpoint Protection, scanning prompt submission, pre-tool use tool use A model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions. , and post-tool use for secrets across Claude Code, Cursor, Copilot CLI, VS Code, Codex, and Mistral Vibe — a block names the secret and how to remove it so the developer or agent can fix and retry. Not checked yet Adds ggshield machine setup to configure hooks for every detected AI agent on a machine alongside git hooks, replacing per-agent manual setup. Not checked yet Adds a workspace setting to automatically remove sources deleted on the remote from team perimeters, while keeping them accessible to workspace managers. Not checked yet
3 details in Everything
GitGuardian adds six new detectors (Firebase, Coze, Keycloak, Fish Audio, Azure Custom Vision) plus an Apify analyzer and Docker Hub PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. detection.
Adds docker login --username / -u detection to the Docker Credentials detector, catching Docker Hub personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. used in that login pattern. Not checked yet Adds new Firebase ID Token detector for Firebase ID tokens. Not checked yet Adds new Coze Access Token detector for Coze access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. . Not checked yet Adds new Keycloak Access Token detector for Keycloak access tokens. Not checked yet Adds new Keycloak Refresh Token detector for Keycloak refresh and offline tokens. Not checked yet
+6 more
show less
Adds new Fish Audio API Key detector for Fish Audio API keys. Not checked yet Adds new Azure Custom Vision Training Key detector for Azure Custom Vision Training keys. Not checked yet Adds new Apify API tokens analyzer. Not checked yet Extends New Relic Key and New Relic Insights Insert Key checkers to identify revoked keys via an empty POST request. Not checked yet Improves scaleway_token precision by rejecting node UUIDs UUIDs A universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide. from proxy-subscription configs. Not checked yet Improves fastly_personal_token precision by rejecting proxy-subscription node passwords and 32-char prefixes of longer base64url values. Not checked yet
Adds new Firebase ID Token detector for Firebase ID tokens. Not checked yet Adds new Coze Access Token detector for Coze access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. . Not checked yet Adds new Keycloak Access Token detector for Keycloak access tokens. Not checked yet Adds new Keycloak Refresh Token detector for Keycloak refresh and offline tokens. Not checked yet Adds new Fish Audio API Key detector for Fish Audio API keys. Not checked yet
+2 more
show less
Adds new Azure Custom Vision Training Key detector for Azure Custom Vision Training keys. Not checked yet Adds new Apify API tokens analyzer. Not checked yet
4 more in Everything
GitGuardian adds ggshield machine setup and ggshield machine doctor to protect endpoints with AI Hooks, git hooks, and honeytokens.
└──▷ TRY IT
Set up all three endpoint protections (AI Hooks, git hooks, honeytoken) on a developer machine in one step, including the extra scope needed to plant the decoy credential.
copy
$ ggshield auth logout
ggshield auth login --scopes honeytokens:write
ggshield machine setup
Deploy endpoint protections across a fleet without planting honeytokens, using only the default install-script scopes.
copy
$ ggshield machine setup --no-honeytokens
Verify that AI Hooks, git hooks, and token scopes are all correctly configured after running machine setup.
copy
$ ggshield machine doctor
Adds ggshield machine setup command (requires ggshield 1.53.0+) to configure all three endpoint protections in one idempotent run: AI Hooks for every AI coding agent found, pre-commit pre-commit An open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. /pre-push git hooks in the global git configuration, and a honeytoken decoy AWS credential profile. Not checked yet Adds --no-honeytokens, --no-ai-hooks, and --no-git-hooks flags to ggshield machine setup to selectively skip individual protections. Not checked yet Adds ggshield machine doctor command (requires ggshield 1.53.0+) to report per-AI-agent hook installation status, git hook status, and token scope validity. Not checked yet Adds honeytokens:write scope requirement to ggshield auth login for planting honeytoken decoy credentials, gated behind the workspace Manager role. Not checked yet Adds honeytokens:check, endpoints:send, and ai-discover:send default authentication scopes provisioned by the install script to cover scanning, AI Hooks, and git hooks. Not checked yet
5 details in Everything
GitGuardian adds AI Hooks to block secrets in AI coding tool prompts and MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tool calls, with ClickHouse-backed agent session scanning.
Adds AI Hooks to block secrets in prompts and tool calls in AI coding tools before they leak via developer AI agents. Not checked yet Requires ClickHouse on self-hosted instances to support machine scans with secrets findings, MCP tool calls, and complete AI agent session recording. Not checked yet
2 details in Everything
GitGuardian Public Secrets Monitoring adds dual AI agents delivering company-related verdicts, risk scores, and visible reasoning for every public incident.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Review the AI-generated reasoning for a public incident before deciding whether to escalate a credential rotation to your engineering team.
📍 In the Public Secrets Monitoring incident list, open an incident, then select the Analysis tab to see the triage agent reasoning, the deep analysis verdict (Related / Uncertain / Unrelated), and the agent-computed risk score.
Adds an Analysis tab to the incident investigation details view, showing triage reasoning, deep-analysis findings, and the timeline of both AI agent passes so reviewers can inspect the logic behind each verdict.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds a triage AI agent and a deep analysis AI agent that run over every public GitHub and Docker Hub incident, returning a company-related verdict (Related , Uncertain , or Unrelated ) and an agent-computed risk score. Not checked yet Ships three pre-configured saved views covering company-related, unclear if company-related, and not company-related incidents, so teams open a pre-triaged queue instead of a flat incident list. Not checked yet Enables Agents Analysis by default for new Public Secrets Monitoring workspaces, with gradual rollout to existing workspaces; customers can request early access through their Customer Success Manager. Not checked yet
4 details in Everything
See all your AI agents across the fleet. Stop them leaking your secrets. (2026-09-07)
Sep 7, 2026
·
issue 068
GitGuardian adds AI agent/MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. inventory and ggshield machine setup to block secrets leaking through AI coding tools.
└──▷ TRY IT
Bootstrap AI Hook and git hook protection across all detected AI agents on a developer machine in one shot.
copy
$ ggshield machine setup
After a suspected compromise, reconstruct which MCP tools an agent called by replaying its transcript history.
copy
$ ggshield ai discover --history
Adds ggshield machine setup command to configure AI Hooks and git hooks for every detected AI agent on a machine in a single step. Not checked yet Adds --history flag to ggshield ai discover to parse MCP tool calls from agent transcripts for post-compromise investigation. Not checked yet Adds AI Hooks coverage for Codex and Mistral Vibe, joining Claude Code, Cursor, Copilot CLI, and VS Code — scanning prompt submission, pre-tool use tool use A model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions. , and post-tool use, and blocking with a named secret and remediation hint. Not checked yet Adds AI agents and MCP inventory to Developer Endpoint Protection, reporting agents and MCP servers per endpoint, hook coverage, and whether an agent subscription is personal or company-owned. Not checked yet Adds automatic removal of remotely-deleted sources from team perimeters via a new workspace setting, while keeping them accessible to workspace managers. Not checked yet
+1 more
show less
AWS access keys stored in a secret manager or Kubernetes now link to their IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. identity by AccessKeyId, showing permissions of the stored key in the NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. exploration map. Not checked yet
Adds ggshield machine setup command to configure AI Hooks and git hooks for every detected AI agent on a machine in a single step. Not checked yet Adds --history flag to ggshield ai discover to parse MCP tool calls from agent transcripts for post-compromise investigation. Not checked yet Adds AI agents and MCP inventory to Developer Endpoint Protection, reporting agents and MCP servers per endpoint, hook coverage, and whether an agent subscription is personal or company-owned. Not checked yet
3 more in Everything
GitGuardian ggscout 0.32.0 brings Secrets Detection Engine classification to vaulted secrets, with 550+ detectors and multi-match grouping
└──▷ HOW TO FIND IT
Filter your NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory down to real credentials by detector type and secret provider, excluding noise and unknowns.
📍 In the NHI inventory, open the Detector column filter and select the desired detector type , secret family , secret category , or secret provider to isolate real credentials from placeholders and feature flags.
Requires ggscout version 0.32.0 or later to enable Secrets Detection Engine classification on vault, CI, and Kubernetes secrets. Not checked yet Runs the Secrets Detection Engine — the same 550+ detectors used for code scanning, including multi-match detectors — against every value ggscout collects, classifying vaulted secrets as real credentials, noise, or Unknown . Not checked yet Adds Detector column and filter controls to the NHI inventory, letting you filter and sort by detector, detector type, secret family, secret category, and secret provider. Not checked yet Retains unmatched secrets in the inventory labeled Unknown so they remain visible and filterable without being silently dropped. Not checked yet Adds per-team incident permission controls when promoting a user to Member, including bulk-apply and post-promotion editing of team rights. Not checked yet
Requires ggscout version 0.32.0 or later to enable Secrets Detection Engine classification on vault, CI, and Kubernetes secrets. Not checked yet Runs the Secrets Detection Engine — the same 550+ detectors used for code scanning, including multi-match detectors — against every value ggscout collects, classifying vaulted secrets as real credentials, noise, or Unknown . Not checked yet Retains unmatched secrets in the inventory labeled Unknown so they remain visible and filterable without being silently dropped. Not checked yet
2 more in Everything
Vaulted Secrets Now Classified by Value (2026-09-04)
Sep 4, 2026
·
issue 065
GitGuardian runs its 550+ Secrets Detection Engine on vaulted secrets, with detector/family/category/provider filters in NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. .
└──▷ HOW TO FIND IT
Review classified vault secrets filtered to a specific provider in the NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. inventory after ggscout has run.
📍 In the GitGuardian console, go to NHI Governance → Identities, click the Detector column header to sort, then open the filter panel and select a value under Secret provider to scope the inventory to credentials from that provider.
Adds Detector column to the NHI Governance → Identities inventory, filterable by detector, detector type, secret family, secret category, and secret provider — the same filter set used for code-scanning incidents. Not checked yet Runs the Secrets Detection Engine (550+ detectors, including multi-match detectors) on every value ggscout collects from vaults, CI systems, and Kubernetes clusters, classifying each secret by its actual value rather than its name or path. Not checked yet Groups sibling fields that form a single credential (e.g. PostgreSQL username, password, host, and port) into one inventory entry instead of four separate items. Not checked yet Labels unmatched secrets as Unknown in the inventory so they remain visible and can be excluded without being dropped entirely. Not checked yet Teams Management now allows setting per-team incident permissions when promoting a user to Member, applying one permission in bulk, and editing team rights afterward. Not checked yet
Adds Detector column to the NHI Governance → Identities inventory, filterable by detector, detector type, secret family, secret category, and secret provider — the same filter set used for code-scanning incidents. Not checked yet Runs the Secrets Detection Engine (550+ detectors, including multi-match detectors) on every value ggscout collects from vaults, CI systems, and Kubernetes clusters, classifying each secret by its actual value rather than its name or path. Not checked yet Groups sibling fields that form a single credential (e.g. PostgreSQL username, password, host, and port) into one inventory entry instead of four separate items. Not checked yet Labels unmatched secrets as Unknown in the inventory so they remain visible and can be excluded without being dropped entirely. Not checked yet
1 more in Everything
GitGuardian adds AI agents for public secret attribution, source health management for GitHub, and automatic monitoring toggles for Jira, Confluence, and Teams.
└──▷ HOW TO FIND IT
Triage only the public leaks the AI agents flagged as related to your company, ignoring noise from unrelated repositories.
📍 In the Public Monitoring incidents view, open the Company-related filter and select Related , then sort by risk score descending to prioritize the highest-risk leaks the agents attributed to your company.
└──▷ BREAKING ON UPGRADE
! On public incidents, the agents' risk score replaces the ML risk score, and the Context related to company tag is superseded by the Company-related verdict. Risk score filtering is no longer available for notifications on public incidents.
GitGuardian now scans AWS S3 buckets, including ZIP and tar.gz archives, for exposed secrets routed into existing incident workflows.
└──▷ HOW TO FIND IT
When onboarding S3 to your monitored perimeter to surface years of credential debt in backup, CI/CD, and infrastructure buckets.
📍 In GitGuardian, go to Perimeter › Sources › AWS S3, select the buckets you want monitored, and trigger a historical scan to analyze existing objects for exposed credentials.
Adds AWS S3 bucket scanning to GitGuardian's monitored perimeter, performing historical scans of accumulated objects — including backups, CI/CD logs, and Terraform state files — to surface exposed credentials as incidents. Not checked yet Extends S3 secret scanning secret scanning Checking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. into supported ZIP and tar.gz archives, surfacing credentials stored inside compressed objects that are not directly visible in the S3 console. Not checked yet Routes S3 findings into existing GitGuardian incident workflows, enabling triage, ownership assignment, and remediation alongside secrets found in other sources. Not checked yet
3 details in Everything
GitGuardian adds AI-agent verdicts on public leaks, AWS S3 bucket scanning, and auto-monitoring for Jira, Confluence, and Teams.
└──▷ HOW TO FIND IT
Triage public leaks by company relevance — filter to only incidents the AI agents flagged as Related to your company so your team works the leaks most likely to be yours first.
📍 In the GitGuardian dashboard, open Public Monitoring › Incidents, then use the Company-related filter and select Related . Alternatively, open one of the three ready-made saved views (Related , Uncertain , Unrelated ) from the saved views menu.
Connect an AWS S3 bucket for secret scanning secret scanning Checking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. without handing over long-lived keys — set up the OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. provider and scoped IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role, then register the account in GitGuardian.
📍 In the GitGuardian dashboard, go to Integrations › AWS S3 and follow the three-step setup: (1) create the OIDC provider in AWS, (2) create a read-only IAM role scoped to the buckets you want monitored, (3) enter your AWS account ID and role name in the integration settings. Then select individual buckets, assign them to teams, and trigger a historical scan.
Adds AI-agent analysis of public secret incidents, producing a Company-related verdict (Related , Uncertain , or Unrelated ) available as a column, a filter, and three ready-made saved views — replacing the ML risk score on public incidents. Not checked yet Adds a new Analysis tab on public incidents showing the company the agents identified, their reasoning, the risk score with its rationale, and which agent concluded. Not checked yet New AWS S3 bucket scanning integration: connects via OIDC-assumed read-only IAM role (no long-lived keys), lets you select individual buckets and assign them to teams, scans objects and contents of archives (e.g. tar.gz), and surfaces findings as regular incidents with existing severity, validity, playbooks, and notifications. Not checked yet AWS S3 scanning defaults to the integration's region and S3 Standard storage class; cross-region scanning and other storage classes are opt-in to control retrieval and transfer costs. Not checked yet Adds automatic monitoring and automatic scan toggles for Jira Cloud, Jira Data Center, Confluence Cloud, Confluence Data Center, and Microsoft Teams — new spaces, projects, and channels are picked up without manual addition. Not checked yet
+2 more
show less
Sources health management for GitHub now pauses real-time ingestion and historical scans on unreachable GitHub sources, auto-resumes on recovery, and surfaces an actionable recovery step. Not checked yet Adds SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. /SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. sign-in support when the identity provider identity provider A service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. does not supply first and last name, deriving these values from the user's email address. Not checked yet
7 details in Everything
└──▷ BREAKING ON UPGRADE
! When AI-agent analysis is enabled, the agents' risk score replaces the ML risk score on public incidents, and the Context related to company tag is superseded by the Company-related verdict; risk score filtering is no longer available for notifications on public incidents.
api-docs-6d60f7883285
Aug 28, 2026
·
issue 058
GitGuardian API adds risk score range filters for incidents and new scan byte counters.
Adds risk_score minimum and maximum filter parameters to incident list endpoints, allowing queries that bound results by risk score range (incidents with a null risk score are excluded from filtered results). Not checked yet Adds data_downloaded_bytes and data_scanned_bytes counters to scan progress reporting, tracking byte-level scan telemetry alongside existing element counters (reported as null for sources that do not measure bytes, such as VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. repositories). Not checked yet Extends user name component handling so that omitting name fields on a member update preserves the existing stored name rather than blanking it, with given/family name derived by splitting the email local part on the first dot. Not checked yet
3 details in Everything
GitGuardian agents tell you which Public Monitoring incidents are actually yours (2026-08-27)
Aug 27, 2026
· release notes
GitGuardian introduces AI agents for public monitoring incidents, adding Company-related verdicts and agent risk scores.
Adds a Company-related verdict (Related, Uncertain, Unrelated) to public secret incidents, available as a column, filter, and saved views. Not checked yet Introduces an Analysis tab showing the identified company, verdict reasoning, score rationale, and the specific agent that concluded. Not checked yet Adds source health management for GitHub, pausing ingestion/scans on unreachable sources and auto-resuming upon recovery. Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! The Context related to company tag is superseded by the Company-related verdict.! Risk score filtering is no longer available for notifications on public incidents because agent analysis arrives asynchronously.
GitGuardian now scans AWS S3 buckets — including objects inside archives — using the same detection engine and incident workflow as repositories.
└──▷ HOW TO FIND IT
Set up the AWS S3 integration in GitGuardian by creating the OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. provider and read-only IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role, then registering your account.
📍 In the GitGuardian console, go to Integrations › AWS S3 and follow the three-step setup: create the OIDC provider in AWS, create the read-only IAM role scoped to the buckets you want monitored, then enter your AWS account ID and role name in the integration settings.
Adds AWS S3 bucket scanning via a read-only OIDC-assumed IAM role in your own account — no long-lived AWS keys required — surfacing secrets in CI logs, Terraform state, .env files, support exports, and other objects that code scanners never reach. Not checked yet Scans inside archives (e.g. tar.gz) nested within S3 objects, so credentials buried in compressed backups still surface as incidents with severity, validity, playbooks, and notifications. Not checked yet Lets you select individual buckets to monitor and assign them to teams like any other source, starting with high-risk buckets such as backup and log archives. Not checked yet
3 details in Everything
Scan your AWS S3 buckets for secrets (2026-08-25)
Aug 25, 2026
·
issue 056
GitGuardian can now scan AWS S3 buckets for secrets, including inside archives, using OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. role assumption with no long-lived keys.
└──▷ HOW TO FIND IT
Connect an AWS account so GitGuardian can scan S3 buckets without handing over long-lived keys.
📍 In GitGuardian, go to Integrations › AWS S3, then follow the three-step setup: create the OIDC provider in AWS, create a read-only IAM role scoped to the buckets you want monitored, and register your AWS account ID and role name in the integration settings.
Kick off a historical scan on high-risk buckets (backup archives, log stores) to surface secrets that have never been visible to code scanners.
📍 In GitGuardian, go to Integrations › AWS S3 › your connected account, select the individual buckets to scan (e.g. your backup and log-archive buckets), assign them to the relevant team, and click Trigger historical scan .
Adds AWS S3 bucket scanning powered by the same detection engine and incident workflow used for repositories, surfacing secrets in objects across CI logs, Terraform state, database dumps, .env files, and support exports. Not checked yet Opens and scans inside archives (e.g. tar.gz) found in S3 objects, so secrets buried in compressed backups still surface as incidents. Not checked yet Connects via OIDC — GitGuardian assumes a read-only IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role you create and scope in your own AWS account, with no long-lived AWS keys required. Not checked yet Lets you select individual buckets to monitor and assign them to teams, the same way any other source is managed in the integration settings. Not checked yet Scans are scoped to the integration's configured region and S3 Standard storage class by default; cross-region scanning and other storage classes are opt-in to keep retrieval and transfer costs under control. Not checked yet
+2 more
show less
Incidents found in S3 objects carry the same severity ratings, validity status, playbooks, and notifications as code-repository incidents. Not checked yet Historical (on-demand) scans are available now; recurrent scanning of new and modified objects is coming soon. Not checked yet
7 details in Everything
GitGuardian adds Cloudsmith container registry support for Secret Scanning
api-docs-983de2edf972
Aug 16, 2026
·
issue 047
GitGuardian API adds three new endpoints: secret-location listing by incident or source, and live scan progress polling.
└──▷ TRY IT
Find every file still exposing the secret for a given incident, scoped to actively monitored sources with more than one mention, to prioritize remediation.
copy
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/incidents/secrets/42/locations?monitored=true&number_of_mentions_min=2&ordering=-number_of_mentions'
Poll a running historical scan for live progress counters and stop when completed is returned, then fetch the audit summary from audit_url.
copy
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/scans/<scan_id>/live-progress'
List all secret locations in a specific source that match a filepath pattern, to hand off an exact file list to the owning team.
copy
$ curl -s -H 'Authorization: Token <api_key>' 'https://api.gitguardian.com/v1/sources/5523/locations?search=settings.py&code_fix_request_status=created'
New GET /v1/incidents/secrets/{incident_id}/locations endpoint lists every file on a source's default branch that still holds a secret, with exact line positions, filterable by source, number_of_mentions_min, number_of_mentions_max, code_fix_request_status (processing, created, error), and search (filepath substring), sortable by last_updated_at, number_of_mentions, or source. Not checked yet New GET /v1/sources/{source_id}/locations endpoint lists all files in a single source that still hold any secret on the default branch, carrying the same per-match line positions, filters (number_of_mentions_min, number_of_mentions_max, code_fix_request_status, search), and sort options as the incident-level endpoint. Not checked yet New beta GET /v1/scans/{scan_id}/live-progress endpoint returns the live status (queued, in_progress, completed) and real-time counters (elements_scanned, elements_total, elements_skipped, elements_failed, data_downloaded_bytes, data_scanned_bytes) for a running historical scan, and includes an audit_url field once the scan reaches completed. Not checked yet
3 details in Everything
GitGuardian adds custom secret validity via API, honeytoken endpoint protection, and programmatic PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. /SAT token creation.
└──▷ TRY IT
Plant a honeytoken on a developer machine to detect credential-harvesting malware the moment it reads the credential file.
copy
$ ggshield honeytoken plant
New API endpoint lets teams push their own validity status (valid or invalid) for secrets on unreachable internal systems, using a personal access token personal access token A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. with the secrets:write scope; the status propagates to all incidents for that secret, appears as Custom validity with a datestamp, and is recorded in the incident activity log and audit log. Not checked yet New ggshield honeytoken plant command (existing agent binary) plants a decoy AWS credential on developer endpoints; any use of the decoy triggers an alert naming the compromised machine, its IP address, user agent, and timestamp — no new agent required. Not checked yet New Honeytoken protection card in the Endpoints dashboard reports fleet coverage percentage and lists unprotected endpoints. Not checked yet Adds ability to create Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. (PATs PATs A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. ) and Service Account Tokens (SATs) programmatically via the API for automated token rotation workflows; tokens created via the API must have a finite TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. . Not checked yet Scans triggered via a Personal Access Token now emit an audit log event. Not checked yet
5 details in Everything
GitGuardian adds an API to let customers override the validity status of a detected secret.
GitGuardian adds custom validity reporting via API, Azure DevOps pipeline decorator, and API-driven detector filtering for custom sources.
New API endpoint lets practitioners set a custom validity status (valid or invalid) on secrets from internal or private systems — requires a personal access token personal access token A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. with the secrets:write scope — so GitGuardian can surface that status in filters, severity, and all downstream incident workflows. Not checked yet Custom validity status is displayed as Custom validity with the date it was set on every incident for that secret, and setting or removing it is recorded in both the incident activity log and the audit log. Not checked yet Adds the Only use detectors with validators option to the public API when creating or updating custom sources, enabling fully automated and consistent source configuration. Not checked yet Launches an Azure DevOps extension that lets admins add a ggshield secret scan job to every pipeline in their organization with a single pipeline decorator via Azure Pipelines. Not checked yet
4 details in Everything
Set your own validity status on a secret (2026-08-14)
Aug 14, 2026
·
issue 046
GitGuardian lets you set custom validity status on secrets via API, plus new source configuration options in the public API.
New API capability to set your own validity status (valid or invalid) on secrets that GitGuardian cannot reach — requires a personal access token personal access token A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. with the secrets:write scope. Not checked yet Incidents display Custom validity with the date it was set, distinguishing user-provided status from GitGuardian-checked status, recorded in both the incident activity log and the audit log. Not checked yet The custom validity status applies to the secret itself, so every incident tied to that secret reflects the status. Not checked yet Public API now supports setting the Only use detectors with validators option when creating or updating custom sources, enabling fully automated source configuration. Not checked yet
4 details in Everything
api-docs-1c2e4c9efcfd
Aug 12, 2026
·
issue 043
GitGuardian adds use_only_detectors_with_validators to custom source APIs, filtering scans to only secrets with validity checks.
└──▷ TRY IT
When creating or updating a custom source, restrict its scan results to secrets that can be actively validated — cutting noise from detectors that cannot confirm whether a secret is live.
copy
$ curl -X PATCH https://api.gitguardian.com/v1/sources/custom/<source_id> \
-H 'Authorization: Token <api_key>' \
-H 'Content-Type: application/json' \
-d '{"use_only_detectors_with_validators": true}'
GitGuardian adds honeytoken-based endpoint intrusion detection, programmatic PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. /SAT creation via API, and expanded VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. source health management.
└──▷ TRY IT
Plant a honeytoken on a developer workstation to detect credential-stealing malware the moment it reads the credential file.
copy
$ ggshield honeytoken plant
Adds ggshield honeytoken plant command to plant a decoy AWS credential on developer endpoints — any access to the decoy triggers an alert naming the compromised machine, its IP address, user agent, and timestamp. Not checked yet New Honeytoken protection card in the Endpoints dashboard reports the share of the fleet with active honeytoken coverage and lists unprotected endpoints. Not checked yet Adds API endpoints to create Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. (PATs PATs A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. ) and Service Account Tokens (SATs) programmatically, enabling automated token rotation workflows; tokens created via the API must have a finite TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. . Not checked yet Scans triggered via a Personal Access Token now emit an audit log event. Not checked yet Extends source health management to Bitbucket Cloud, Bitbucket Data Center, GitLab, and Azure DevOps: GitGuardian now pauses real-time ingestion and historical scans on unreachable sources, auto-resumes on recovery, and surfaces an actionable recovery step. Not checked yet
5 details in Everything
GitGuardian adds 10 new detectors/checkers for Lovable, Slack, n8n, Atlassian, AWS Cognito, OpenAI, Vercel, OpenCode, and Supabase.
Adds Lovable Access Token detector for Lovable project access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. . Not checked yet Adds Lovable Git Token detector for Lovable git tokens. Not checked yet Adds Slack Webhook Trigger URL detector for Slack Workflow Builder webhook trigger URLs. Not checked yet Adds n8n API Key detector for n8n API keys. Not checked yet Adds Atlassian Auth Key detector for Atlassian OAuth 2.0 OAuth 2.0 An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. access tokens issued by auth.atlassian.com. Not checked yet
+9 more
show less
Adds AWS Cognito Access Token detector for AWS Cognito User Pool access tokens. Not checked yet Adds OpenAI Access Token detector for OpenAI platform access tokens. Not checked yet Adds Vercel OIDC Token detector for Vercel workload-identity tokens. Not checked yet Adds OpenCode API Key detector for OpenCode API keys. Not checked yet Adds Supabase Service Role JWT checker for Supabase service_role JWTs JWTs JSON Web Tokens — an open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object. Cyber tools use them for stateless authentication without server-side session storage. . Not checked yet Improves precision for github_oauth_token, generic_password, base64_generic_high_entropy_secret, and generic_high_entropy_secret detectors: values that fail format validation are no longer reported. Not checked yet Expands generic_password detector to ignore passwords in public proxy-subscription configs (shadowsocks/vmess/vless/trojan/hysteria URIs, Telegram MTProto links, clash/mihomo node lists). Not checked yet Expands generic_encryption_key detector to ignore Talend encrypted passwords (enc:system|routine.encryption.key.vN:...). Not checked yet Improves recall for PostgreSQL credential detectors: usernames containing dashes (e.g. workflow-prod-user) are now matched, and the username length bound is raised from 20 to 30 characters. Not checked yet
14 details in Everything
└──▷ BREAKING ON UPGRADE
! The Amadeus OAuth credentials detector and checker have been disabled as the Amadeus self-service API has been discontinued.
Catch credential stealers on your endpoint fleet (2026-08-10)
Aug 10, 2026
·
issue 042
GitGuardian adds honeytoken-based endpoint intrusion detection via ggshield honeytoken plant, plus API-based PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. /SAT creation.
└──▷ TRY IT
Plant a honeytoken decoy credential on a developer machine — run once per endpoint via MDM MDM Mobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies. job or manually to activate tripwire detection.
copy
$ ggshield honeytoken plant
New ggshield honeytoken plant command plants a decoy AWS credential on developer endpoints to detect credential-stealing malware the moment it reads the file. Not checked yet New Honeytoken protection card in the Endpoints dashboard reports fleet-wide coverage percentage and lists endpoints not yet protected. Not checked yet Adds Public API endpoints to create Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. (PATs PATs A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. ) and Service Account Tokens (SATs) programmatically, enabling automated token rotation workflows; tokens created via the API must have a finite TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. . Not checked yet
3 details in Everything
api-docs-7c9d3e1aa9a9
Aug 5, 2026
·
issue 036
GitGuardian API gains a token-creation endpoint that lets personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. and service account tokens mint new tokens programmatically.
Adds a Create API Token endpoint that mints a new personal_access_token or service_account token programmatically; the clear-text token value is returned only in the creation response and cannot be retrieved again via list or retrieve endpoints. Not checked yet Enforces scope delegation on token creation: the scopes granted to the new token must be a subset of the calling token's scopes, and some scopes implicitly include others, so the returned token may carry more scopes than explicitly requested. Not checked yet Rejects creation when the name is already used by an active token of the same type, when the workspace has reached its active-token limit, or when the requested lifetime exceeds the workspace policy maximum. Not checked yet Requires no particular scope on the calling token — any valid token can call this endpoint, making it self-service for both members and service accounts. Not checked yet
4 details in Everything
GitGuardian adds 4 new detectors, 2 new validity checkers, and expands HTML/Markdown scanning to npm, GitHub, and Slack tokens
New Azure Immersive Reader Key detector added. Not checked yet New DashScope Coding Plan API Key detector added for Alibaba Cloud Model Studio (Qwen / DashScope) Coding Plan API keys. Not checked yet New DashScope Token Plan API Key detector added for Alibaba Cloud Model Studio (Qwen / DashScope) Token Plan API keys. Not checked yet New Prefect Cloud API Key detector added. Not checked yet New validity checker for Alibaba Cloud Keys (IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. ) — requires username and host to be present. Not checked yet
+7 more
show less
New validity checker for GitLab Deploy Tokens — requires username and host to be present. Not checked yet HTML and Markdown file scanning extended to npm, GitHub Personal Access Token, GitHub OAuth Token, GitHub App, and Slack Application Credentials tokens. Not checked yet Generic High Entropy Secret detector broadened to detect more credential key names: access, app, vault, sign, dev, prod, and staging key prefixes; encryption keys are now handled by generic_encryption_key. Not checked yet Okta host matching updated to cover regional and preview host domains, raising precision from ~0% to ~100% on a manually reviewed subset. Not checked yet auth0_keys detector now requires a JSON response to mark secrets valid, preventing non-Auth0 domains from being reported as valid. Not checked yet microsoft_power_apps_webhook detector now treats WorkflowNotFound responses from deleted flows as invalid. Not checked yet bearer_token detector now drops expired JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. tokens, reducing false positives. Not checked yet
12 details in Everything
GitGuardian adds ggshield machine report command to scan and submit results in a single step for scheduled jobs.
GitGuardian adds a dedicated GitHub Check Runs dashboard page, bulk perimeter actions, and Bitbucket source health management.
└──▷ HOW TO FIND IT
Bulk-unmonitor a set of deprecated sources and remove them from all team assignments in one operation.
📍 On the perimeter page, select the sources you want to remove from monitoring, then choose Unmonitor from the bulk actions menu. Confirm the popup that appears when more than 30 sources are selected.
New dedicated GitHub Check Runs page in the dashboard lets security teams browse all check run statuses, filter by repository/status/date, view KPI metrics, re-run or skip checks, and jump directly to linked incidents — without leaving GitGuardian. Not checked yet Fine-grained GitHub personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. can now be used to monitor private members of a GitHub organization (previously only classic tokens were supported). Not checked yet Customizable column display on the perimeter table lets users surface the source attributes most relevant to their workflow. Not checked yet Bulk actions on perimeter sources now support Monitor, Unmonitor, and Assign Team operations on multiple sources at once, with a confirmation popup when more than 30 sources are selected. Not checked yet Historical scans now have a dedicated tab on the perimeter page for tracking past and in-progress scan statuses in one place. Not checked yet
5 details in Everything
└──▷ BREAKING ON UPGRADE
! The Display as Tree view has been removed from integration source pages; only the Display as List view remains.
GitGuardian roadmap adds Honeytoken multi-cloud/CI/CD/vault support, Slack App with interactive actions, Teams DMs, and an Amazon Kiro integration.
Adds Endpoint Breach Detection view, shifting endpoint UX toward asset protection and attack detection. Not checked yet Surfaces Non-Human Identity policy breaches (overprivilege, stale identities, cross-environment usage) as actionable incidents with lifecycle tracking. Not checked yet Replaces the Slack webhook notifier with a native Slack App that threads incident events under a single parent message per incident. Not checked yet Adds interactive Slack Block Kit buttons (Resolve / Ignore) so developers can act on incidents directly from the Slack notification card. Not checked yet Delivers incident notifications as Slack direct messages to the responsible developer, with configurable Thread / DM / Both delivery mode and a fallback user. Not checked yet
+8 more
show less
Delivers incident notifications as Microsoft Teams direct messages to the responsible developer, with configurable Channel / DM / Both delivery mode and a fallback user. Not checked yet Adds a GitGuardian Power for Amazon Kiro with secret-detection skill guidelines, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. configuration, and hooks for AI-assisted development. Not checked yet Expands Honeytoken support beyond AWS to GCP service account JSON keys and Azure AD client secrets. Not checked yet Adds new Honeytoken deception primitives: fake service endpoints, database credentials, and SaaS API keys. Not checked yet Enables Honeytoken injection into CI/CD runners to detect supply-chain attacks that exfiltrate environment variables. Not checked yet Enables planting Honeytokens inside HashiCorp Vault, AWS Secrets Manager, and Azure Key Vault as a second dissemination surface. Not checked yet Adds a unified protection coverage dashboard across all asset types: endpoints, vaults, CI/CD, cloud accounts, and repos. Not checked yet Introduces an Attack Detection incident type that surfaces Honeytoken triggers as high-priority alerts with attacker forensics. Not checked yet
13 details in Everything
GitGuardian roadmap adds Honeytoken multi-cloud/CI/CD/vault support, Slack App with interactive actions, Teams DMs, and an Amazon Kiro integration.
Adds Endpoint Breach Detection view, shifting endpoint UX toward asset protection and attack detection. Not checked yet Surfaces Non-Human Identity policy breaches (overprivilege, stale identities, cross-environment usage) as actionable incidents with lifecycle tracking. Not checked yet Replaces the Slack webhook notifier with a native Slack App that threads incident events under a single parent message per incident. Not checked yet Adds interactive Slack Block Kit buttons (Resolve / Ignore) so developers can act on incidents directly from the Slack notification card. Not checked yet Delivers incident notifications as Slack direct messages to the responsible developer, with configurable Thread / DM / Both delivery mode and a fallback user. Not checked yet
+8 more
show less
Delivers incident notifications as Microsoft Teams direct messages to the responsible developer, with configurable Channel / DM / Both delivery mode and a fallback user. Not checked yet Adds a GitGuardian Power for Amazon Kiro with secret-detection skill guidelines, MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. configuration, and hooks for AI-assisted development. Not checked yet Expands Honeytoken support beyond AWS to GCP service account JSON keys and Azure AD client secrets. Not checked yet Adds new Honeytoken deception primitives: fake service endpoints, database credentials, and SaaS API keys. Not checked yet Enables Honeytoken injection into CI/CD runners to detect supply-chain attacks that exfiltrate environment variables. Not checked yet Enables planting Honeytokens inside HashiCorp Vault, AWS Secrets Manager, and Azure Key Vault as a second dissemination surface. Not checked yet Adds a unified protection coverage dashboard across all asset types: endpoints, vaults, CI/CD, cloud accounts, and repos. Not checked yet Introduces an Attack Detection incident type that surfaces Honeytoken triggers as high-priority alerts with attacker forensics. Not checked yet
13 details in Everything
GitGuardian Self-Hosted 2026.7.0 adds Public Monitoring, native Gerrit scanning, Smart Notifiers, 9 new detectors, and an MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server deployment.
└──▷ USE IT
Enable Public Monitoring on a self-hosted instance to process public perimeter scanning queues.
yaml
copy
celeryWorkers:
public-monitoring:
enabled: true
Deploy the GitGuardian MCP server in your cluster Beta via Helm values.
yaml
copy
mcpServer:
enabled: true
Adds Public Monitoring to self-hosted instances (license-gated): monitor public perimeter for secret leaks and route incidents through custom webhooks, Slack, Microsoft Teams, ServiceNow ticketing, and severity-filtered email alerts via the new celeryWorkers.public-monitoring worker. Not checked yet Adds native Gerrit VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. source with full historical scanning, real-time detection via webhook plugin, and read-replica support for cloning. Not checked yet Adds Smart Notifiers: define per-channel filtering rules so alerts, tickets, or emails are only created for incidents matching severity, validity, secret type, or GitGuardian tag — across internal and public monitoring. Not checked yet GitHub check runs now scan oversized pull requests by cloning the repository branch instead of calling the GitHub API commit-by-commit, and can skip merge commits; thresholds and rate-limit behavior are configurable from the admin area GitHub preferences. Not checked yet Adds Gateway API routing: route external traffic through the Kubernetes Gateway API instead of the legacy Ingress resource, with HPA or KEDA autoscaling for webapps. Not checked yet
+6 more
show less
Adds 9 new detectors (Amadeus OAuth Credentials, Kinde OAuth Credentials, TomTom API Key, Datadog Personal Access Token, Azure Maps, Azure Mixed Reality, Azure Service Bus, Azure Quantum, Azure Bot Direct Line) and 2 new checkers (Gemfury Deploy/Push Token, Gemfury Full Access Token). Not checked yet Jira Notifier now exposes remediation guidance and detector-specific links as assignable fields in the ticket description template. Not checked yet Custom Sources (BYOS) now support a scan-with-validated-detectors-only option. Not checked yet Daily analytics job can now write Spark scratch data to a dedicated ephemeral volume, preventing failures from node ephemeral-storage limits on large workspaces. Not checked yet Adds opt-in mcpServer Helm deployment to run the GitGuardian MCP server in-cluster (currently in beta). Not checked yet Incident assignment now auto-grants access to the assignee. Not checked yet
11 details in Everything
└──▷ BREAKING ON UPGRADE
! logCollector.collectMigrationLogs is enabled by default and requires Kubernetes 1.29 or later; on older clusters, set logCollector.collectMigrationLogs: false before upgrading.! Developer Endpoint Protection is not functional on self-hosted instances in 2026.7.0; instances relying on Endpoint Protection should hold off on upgrading.
GitGuardian Self-Hosted 2026.7.0 adds Public Monitoring, native Gerrit scanning, Smart Notifiers, 9 new detectors, and an MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server deployment.
└──▷ USE IT
Enable Public Monitoring on a self-hosted instance to process public perimeter scanning queues.
yaml
copy
celeryWorkers:
public-monitoring:
enabled: true
Deploy the GitGuardian MCP server in your cluster Beta via Helm values.
yaml
copy
mcpServer:
enabled: true
Adds Public Monitoring to self-hosted instances (license-gated): monitor public perimeter for secret leaks and route incidents through custom webhooks, Slack, Microsoft Teams, ServiceNow ticketing, and severity-filtered email alerts via the new celeryWorkers.public-monitoring worker. Not checked yet Adds native Gerrit VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. source with full historical scanning, real-time detection via webhook plugin, and read-replica support for cloning. Not checked yet Adds Smart Notifiers: define per-channel filtering rules so alerts, tickets, or emails are only created for incidents matching severity, validity, secret type, or GitGuardian tag — across internal and public monitoring. Not checked yet GitHub check runs now scan oversized pull requests by cloning the repository branch instead of calling the GitHub API commit-by-commit, and can skip merge commits; thresholds and rate-limit behavior are configurable from the admin area GitHub preferences. Not checked yet Adds Gateway API routing: route external traffic through the Kubernetes Gateway API instead of the legacy Ingress resource, with HPA or KEDA autoscaling for webapps. Not checked yet
+6 more
show less
Adds 9 new detectors (Amadeus OAuth Credentials, Kinde OAuth Credentials, TomTom API Key, Datadog Personal Access Token, Azure Maps, Azure Mixed Reality, Azure Service Bus, Azure Quantum, Azure Bot Direct Line) and 2 new checkers (Gemfury Deploy/Push Token, Gemfury Full Access Token). Not checked yet Jira Notifier now exposes remediation guidance and detector-specific links as assignable fields in the ticket description template. Not checked yet Custom Sources (BYOS) now support a scan-with-validated-detectors-only option. Not checked yet Daily analytics job can now write Spark scratch data to a dedicated ephemeral volume, preventing failures from node ephemeral-storage limits on large workspaces. Not checked yet Adds opt-in mcpServer Helm deployment to run the GitGuardian MCP server in-cluster (currently in beta). Not checked yet Incident assignment now auto-grants access to the assignee. Not checked yet
11 details in Everything
└──▷ BREAKING ON UPGRADE
! logCollector.collectMigrationLogs is enabled by default and requires Kubernetes 1.29 or later; on older clusters, set logCollector.collectMigrationLogs: false before upgrading.! Developer Endpoint Protection is not functional on self-hosted instances in 2026.7.0; instances relying on Endpoint Protection should hold off on upgrading.
GitGuardian adds a dedicated Check Runs dashboard page, Bitbucket source health management, perimeter column customization, and bulk source actions.
└──▷ HOW TO FIND IT
Audit scan coverage and unblock a stalled pull request without leaving GitGuardian — find the failed check run, diagnose it, and re-run it from the dashboard.
📍 In the GitGuardian dashboard, open the Check Runs tab (under the relevant section). Filter by repository and status Failed , locate the check run tied to the blocked PR, then click Re-run to trigger a new scan directly from the list.
Apply team assignment or monitoring status to a large batch of sources in one operation instead of editing each source individually.
📍 In the GitGuardian dashboard, navigate to the Perimeter page, select the sources you want to update (up to or exceeding 30 — a confirmation popup will appear for larger selections), then choose Monitor, Unmonitor, or Assign Team from the bulk actions menu.
New dedicated Check Runs page in the dashboard lets security teams browse all GitHub check run results (status, repo, commit SHA, PR, timing), filter by repository/status/date, re-run or skip checks, and jump directly to linked incidents — without switching to GitHub. Not checked yet Fine-grained GitHub personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. can now be used to monitor private members of a GitHub organization (previously only classic tokens were supported) in the Public Perimeter view. Not checked yet Perimeter table now supports column customization, letting users choose which source attributes are displayed to tailor the view to their workflow. Not checked yet Bulk actions on perimeter sources now support Monitor, Unmonitor, and Assign Team operations on selected sources, with a confirmation popup when selecting more than 30 sources. Not checked yet Historical scans now have their own dedicated tab on the perimeter page for tracking past and in-progress scans and their statuses. Not checked yet
5 details in Everything
GitGuardian adds a dedicated Check Runs dashboard page, Bitbucket source health management, perimeter column customization, and bulk source actions.
└──▷ HOW TO FIND IT
Audit scan coverage and unblock a stalled pull request without leaving GitGuardian — find the failed check run, diagnose it, and re-run it from the dashboard.
📍 In the GitGuardian dashboard, open the Check Runs tab (under the relevant section). Filter by repository and status Failed , locate the check run tied to the blocked PR, then click Re-run to trigger a new scan directly from the list.
Apply team assignment or monitoring status to a large batch of sources in one operation instead of editing each source individually.
📍 In the GitGuardian dashboard, navigate to the Perimeter page, select the sources you want to update (up to or exceeding 30 — a confirmation popup will appear for larger selections), then choose Monitor, Unmonitor, or Assign Team from the bulk actions menu.
New dedicated Check Runs page in the dashboard lets security teams browse all GitHub check run results (status, repo, commit SHA, PR, timing), filter by repository/status/date, re-run or skip checks, and jump directly to linked incidents — without switching to GitHub. Not checked yet Fine-grained GitHub personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. can now be used to monitor private members of a GitHub organization (previously only classic tokens were supported) in the Public Perimeter view. Not checked yet Perimeter table now supports column customization, letting users choose which source attributes are displayed to tailor the view to their workflow. Not checked yet Bulk actions on perimeter sources now support Monitor, Unmonitor, and Assign Team operations on selected sources, with a confirmation popup when selecting more than 30 sources. Not checked yet Historical scans now have their own dedicated tab on the perimeter page for tracking past and in-progress scans and their statuses. Not checked yet
5 details in Everything
GitGuardian v2.167.0 adds 11 new secret detectors across Azure, AI/LLM LLM A large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. , and dev tooling, plus new validity checkers for LiteLLM, Llama Cloud, New Relic, and npm.
Adds detector for LiteLLM API Key (without host capture). Not checked yet Adds detector for Azure SQL Credentials (Assignment). Not checked yet Adds detector for Azure Machine Learning keys. Not checked yet Adds detector for Azure Video Indexer Key. Not checked yet Adds detector for Azure Health Insights Key. Not checked yet
+10 more
show less
Adds detector for Azure Fluid Relay Key. Not checked yet Adds detector for Apify Proxy Token. Not checked yet Adds detector for DashScope API Key (signed/workspace Alibaba Cloud Model Studio / Qwen keys). Not checked yet Adds detector for Authress Service Client Access Key. Not checked yet Adds detectors for Gemfury Deploy Or Push Token Without Username and Gemfury Full Access Token Without Username. Not checked yet Improves recall for Datadog API Key and Snyk Key detectors. Not checked yet Adds validity checker for LiteLLM API Key Without Host with custom host support. Not checked yet Adds validity checker for Llama Cloud API key. Not checked yet Adds validity checker for New Relic APM APM Application Performance Monitoring — a category of software that collects metrics, traces, and logs from running applications so developers can detect slowdowns and diagnose their root cause. License Key. Not checked yet Adds validity checkers for npm token and npm token (prefixed variant). Not checked yet
15 details in Everything
GitGuardian v2.167.0 adds 11 new secret detectors across Azure, AI/LLM LLM A large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. , and dev tooling, plus new validity checkers for LiteLLM, Llama Cloud, New Relic, and npm.
Adds detector for LiteLLM API Key (without host capture). Not checked yet Adds detector for Azure SQL Credentials (Assignment). Not checked yet Adds detector for Azure Machine Learning keys. Not checked yet Adds detector for Azure Video Indexer Key. Not checked yet Adds detector for Azure Health Insights Key. Not checked yet
+10 more
show less
Adds detector for Azure Fluid Relay Key. Not checked yet Adds detector for Apify Proxy Token. Not checked yet Adds detector for DashScope API Key (signed/workspace Alibaba Cloud Model Studio / Qwen keys). Not checked yet Adds detector for Authress Service Client Access Key. Not checked yet Adds detectors for Gemfury Deploy Or Push Token Without Username and Gemfury Full Access Token Without Username. Not checked yet Improves recall for Datadog API Key and Snyk Key detectors. Not checked yet Adds validity checker for LiteLLM API Key Without Host with custom host support. Not checked yet Adds validity checker for Llama Cloud API key. Not checked yet Adds validity checker for New Relic APM APM Application Performance Monitoring — a category of software that collects metrics, traces, and logs from running applications so developers can detect slowdowns and diagnose their root cause. License Key. Not checked yet Adds validity checkers for npm token and npm token (prefixed variant). Not checked yet
15 details in Everything
Track your GitHub check runs from the dashboard (2026-07-28)
Jul 28, 2026
·
issue 028
GitGuardian adds a dedicated GitHub Check Runs dashboard page with filtering, KPIs, re-run controls, and incident linking.
└──▷ HOW TO FIND IT
Audit scan coverage and unblock a stuck pull request by finding and re-running a failed check run without leaving GitGuardian.
📍 In the dashboard, go to Perimeter › GitHub check runs. Filter by repository and set Status to Failed , locate the run for the relevant commit SHA, then click Re-run.
Jump straight to remediation when a check run catches a secret, without switching to GitHub.
📍 In the dashboard, go to Perimeter › GitHub check runs. Find the check run with detected secrets, then click the linked incident to open the incident details and begin remediation.
New GitHub Check Runs page in the Perimeter section surfaces every check run with status, repository, commit SHA, pull request, and timing in one place. Not checked yet Filter and search check runs by repository, status, or date — including workspaces with hundreds of thousands of runs. Not checked yet KPI strip at the top of the Check Runs page summarizes activity to surface failures and trends at a glance. Not checked yet Re-run or skip a check run directly from the dashboard without switching to GitHub. Not checked yet Navigate from a check run directly to linked incidents when secrets are detected, enabling faster remediation. Not checked yet
+2 more
show less
Fine-grained GitHub personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. can now be used to monitor private members of a GitHub organization in the Public Perimeter (previously limited to classic tokens). Not checked yet Sources health management extended to Bitbucket Cloud and Bitbucket Data Center: GitGuardian now auto-pauses ingestion on unreachable sources, auto-resumes on recovery, and surfaces actionable recovery steps. Not checked yet
7 details in Everything
└──▷ HOW TO FIND IT
Loop in a teammate or team directly on an incident without leaving GitGuardian — they receive an email linking straight to the incident.
📍 In any incident, open the Notes or Feedback panel, type @ and select a member (@name) or a team (@team-name) from the searchable list, then submit.
Filter the incident list to set aside noise from archived or deleted sources, then save it as a persistent view.
📍 On the Perimeter page or Incident list, open the source status filter and select Archived or Deleted , then save as a view.
Reduce false positives on a Custom Source install by restricting scans to detectors that can actually verify secret validity.
📍 In the Custom Source install settings, enable the 'use only detectors with validators' option for the target source.
Adds @mention support in incident notes and feedback — type @name or @team-name to notify individual members or entire teams via email, linked directly to the incident. Not checked yet
└──▷ HOW TO FIND IT
Loop in a teammate or team directly on an incident without leaving GitGuardian — they receive an email linking straight to the incident.
📍 In any incident, open the Notes or Feedback panel, type @ and select a member (@name) or a team (@team-name) from the searchable list, then submit.
Filter the incident list to set aside noise from archived or deleted sources, then save it as a persistent view.
📍 On the Perimeter page or Incident list, open the source status filter and select Archived or Deleted , then save as a view.
Reduce false positives on a Custom Source install by restricting scans to detectors that can actually verify secret validity.
📍 In the Custom Source install settings, enable the 'use only detectors with validators' option for the target source.
Adds @mention support in incident notes and feedback — type @name or @team-name to notify individual members or entire teams via email, linked directly to the incident. Not checked yet
GitGuardian roadmap adds incident routing, Sonatype Nexus scanning, and full encoded-secret insights
New incident routing (phase 1) automatically assigns a Lead (accountable) and Participants (doing the work) to every incident at creation. Not checked yet Supports scanning Sonatype Nexus Repository package and container image registries for hardcoded secrets. Not checked yet Displays full encoded insights — persists and surfaces analyzer feedback including decoded base64 and JWT JWT An open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store. detector results. Not checked yet
3 details in Everything
GitGuardian adds @mentions in incident notes, perimeter source status filtering, and oversized PR scanning for Business plans.
└──▷ HOW TO FIND IT
Loop in a teammate or team on a live incident without leaving the platform — replaces the need to ping via Slack or email.
📍 In the console, open any incident, add a note or feedback, type @ and select a member (@name) or team (@team-name) from the searchable list. They receive an email linking directly to the incident. Manage mention email preferences under notification settings.
Filter the incident list to ignore noise from archived or deleted sources by saving a perimeter view filtered by source status.
📍 In the console, go to the Perimeter page or Incident list, filter by source status (e.g. Archived or Deleted), then save the filtered view for ongoing use.
Cut false-positive noise on a Custom Source install by restricting scans to only secrets whose detector supports validity verification.
📍 In the console, go to your Custom Source (BYOS) install settings and enable the 'use only detectors with validators' option for the desired install.
Adds @mentions in incident notes and feedback — type @name or @team-name to notify individuals or entire teams via email, linking directly to the incident; works on both Internal and Public Monitoring incidents. Not checked yet Extends source health management (auto-pause, auto-resume, and actionable recovery steps) to ServiceNow, JFrog Container Registry, JFrog Package Registry, and Microsoft OneDrive. Not checked yet Introduces perimeter source status indicators (Monitored, Unmonitored, Unreachable, Archived, Deleted) filterable from the perimeter page and incident list, with saveable views. Not checked yet Enables scanning of oversized pull requests (>200 commits, >60,000 files, or >300,000 lines changed) on the Business plan via repository branch cloning, bypassing GitHub API rate limits. Not checked yet Adds opt-in 'use only detectors with validators' option for Custom Source (BYOS) installs, filtering out unverifiable matches before validity checks run to reduce noise. Not checked yet
+1 more
show less
Logs monitoring setting changes (e.g. toggling automatic monitoring on/off) in the audit trail. Not checked yet
6 details in Everything
Mention members and teams in incident notes (2026-07-20)
Jul 20, 2026
·
issue 021
GitGuardian adds @mention notifications in incident notes, source health for new integrations, and oversized PR scanning on Business plan.
└──▷ HOW TO FIND IT
Loop in a teammate or an entire team on a critical incident without leaving GitGuardian.
📍 In the console, open any incident › add a note or feedback › type @ and select a member (@name) or team (@team-name) from the searchable list. The mentioned users receive an email linking directly to the incident.
Filter the incident list to only incidents from active sources, setting aside noise from archived or deleted ones.
📍 In the console, go to the Perimeter page or Incident list › open the source status filter › select Monitored (or exclude Archived / Deleted) › save as a view for reuse.
Reduce false positives on a Custom Source install by limiting scans to detectors that can verify secret validity.
📍 In the console, go to the Custom Source install settings › enable 'use only detectors with validators' › save. Subsequent scans on that source will drop matches whose detector has no validator before the validity check runs.
Adds @mention support in incident notes and feedback — type @ to tag a member by @name or an entire team by @team-name, triggering email notifications that link directly to the incident. Not checked yet Extends source health management (auto-pause, auto-resume, and recovery guidance) to ServiceNow, JFrog Container Registry, JFrog Package Registry, and Microsoft OneDrive sources. Not checked yet Introduces per-source status indicators (Monitored, Unmonitored, Unreachable, Archived, Deleted) on the perimeter page and incident list, with filterability and saveable views. Not checked yet Enables scanning of oversized pull requests (>200 commits, >60,000 files, or >300,000 lines changed) via repository cloning on the Business plan, bypassing GitHub API rate limits. Not checked yet Adds opt-in 'use only detectors with validators' option for Custom Source (BYOS) installs, dropping unverifiable matches before validity checks to reduce noise. Not checked yet
5 details in Everything
Generic Detectors landing on your non-VCS sources, powered by the False Positive Remover (2026-07-07)
Jul 7, 2026
·
issue 014
GitGuardian extends Generic Password and High Entropy Secret detection to Confluence, Jira, Slack, and Teams — with AI false-positive filtering built in.
└──▷ HOW TO FIND IT
Review or toggle AI-powered false-positive filtering for non-code sources after it is enabled by default on Business accounts.
📍 In the GitGuardian console, go to Settings › AI settings and confirm that AI features (including the False Positive Remover) are enabled for your non-code source integrations.
Adds Generic Password and Generic High Entropy Secret detection to non-code sources including Confluence, Jira, Slack, Microsoft Teams, and others — matching the coverage already available for VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. . Not checked yet Extends the False Positive Remover (LLM LLM A large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. -based model) to non-code source findings, automatically tagging 25–40% of generic findings as false positives before they surface in the dashboard. Not checked yet Adds remediation guidance content and detector-specific links as assignable metadata fields in the Jira Notifier integration ticket description template. Not checked yet
3 details in Everything
ServiceNow Integration: Event Group Selection, Public Monitoring & Honeytoken Support (2026-06-30)
Jun 30, 2026
·
issue 014
GitGuardian's ServiceNow integration gains Public Monitoring, Honeytoken support, and granular event subscription filters.
└──▷ TRY IT
Retrieve the activity log for a specific secret incident via the Public API to feed into an automation or SIEM SIEM Security information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. workflow.
copy
$ curl -s -H 'Authorization: Token <your_api_token>' 'https://api.gitguardian.com/v1/incidents/<incident_id>/activity' | jq .
Enable Honeytoken and Public Monitoring event routing in a new ServiceNow integration so decoy and perimeter alerts land in the same ticketing workflow as internal incidents.
📍 In the GitGuardian dashboard, go to Integrations › ServiceNow › Configure, then under Event Groups enable Public monitoring and Honeytoken events . In the Notify when section, select the additional events (e.g. Incident ignored, Incident resolved) to be posted as comments on the ticket.
Adds Event Group Selection to the ServiceNow integration: choose to route Internal Monitoring, Public Monitoring, or Honeytoken incidents into ServiceNow tickets. Not checked yet Supports Public Monitoring in ServiceNow, so secrets exposed on public sources flow into the same remediation workflow as internal incidents. Not checked yet Supports Honeytoken events in ServiceNow, bringing decoy-token alerts into the ticketing and remediation workflow. Not checked yet New Notify when section enables granular event subscription: the New incident detected event creates the ticket, while additional selected events are posted as comments, keeping full incident history in one place. Not checked yet Adds severity and risk score information to incident notifications in Slack and Microsoft Teams. Not checked yet
+3 more
show less
Adds source health management for Confluence Cloud, Slack, Gerrit, and Microsoft SharePoint Online: GitGuardian pauses ingestion on unreachable sources and auto-resumes once health is restored, surfacing an actionable recovery step. Not checked yet Adds a new Public API endpoint to retrieve the activity log of a secret incident, enabling automation and monitoring workflows. Not checked yet Adds support for a second AWS Marketplace seller account (GitGuardian Inc., US entity) so US customers can transact through the US listing. Not checked yet
8 details in Everything
Smart Notifiers - filter alerts, tickets, and emails by incident criteria (2026-06-19)
Jun 19, 2026
·
issue 014
Smart Notifiers lets GitGuardian alert only on incidents that match severity, ML risk, validity, or secret type — no middleware needed.
└──▷ HOW TO FIND IT
Route only high-severity, valid secrets to a Slack channel — eliminating noise from informational or unverified incidents.
📍 In the console, go to Alerting & Notifications › Slack notifier settings, then add a filter rule: set Severity to High or Critical and Validity to Valid . Save the rule to apply it to that channel.
Prevent false-positive check run failures caused by secrets merged in from the target branch during large PRs.
📍 In the console, go to Integrations › GitHub › Check Runs settings and enable Skip merge commits to restrict flagging to secrets introduced on the PR branch only.
Unlink a runaway or mistakenly created Jira ticket from an incident without deleting the external ticket.
📍 In the console, open the incident detail page, locate the linked Jira ticket section, and click Dissociate ticket to remove the association while keeping the Jira issue intact.
Adds Smart Notifiers: per-channel filtering rules for webhooks, Slack, and Microsoft Teams alerts based on severity, ML risk score, validity, secret type, or GitGuardian tag across internal and public monitoring. Not checked yet Enables email alerting to filter public monitoring incidents by severity. Not checked yet Adds sources health management for Confluence Data Center and Microsoft Teams: auto-pauses ingestion on unreachable sources and auto-resumes when health is restored. Not checked yet Expands Overview analytics to include Non-Human Identity (NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. ) and Public Monitoring data. Not checked yet New GitHub check run setting to skip merge commits in pull request scans, flagging only secrets introduced on the PR branch. Not checked yet
+6 more
show less
GitHub check runs now skip scans on pull requests exceeding a configured size limit to protect the shared GitHub API rate limit. Not checked yet Enables dissociation of a Jira or ServiceNow ticket from an incident directly on the incident detail page without deleting the external ticket. Not checked yet Adds support for the Feedback Received event in ServiceNow event-based notifications. Not checked yet Adds ability to filter incidents by closure reason. Not checked yet Increases character limit for secret value search on the incidents page to support longer secrets such as large JWTs JWTs JSON Web Tokens — an open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object. Cyber tools use them for stateless authentication without server-side session storage. . Not checked yet Supports read-only tokens for GitLab group hook installations, with manual webhook creation instructions surfaced when needed. Not checked yet
11 details in Everything
Smart Notifiers - filter alerts, tickets, and emails by incident criteria (2026-06-19)
Jun 19, 2026
· release notes
Smart Notifiers lets you filter alerts by criteria; improved scan coverage and ticketing controls
config rules for Smart Notifiers allow filtering notifications by severity, ML risk score, validity, secret type, or GitGuardian tag for custom webhook, Slack, Microsoft Teams, and email channels. Not checked yet Incidents page now filters by closure reason via the UI filter options. Not checked yet GitHub check runs gain a new setting to skip merge commits in pull request checks. Not checked yet Large GitHub pull requests can now be skipped based on a configured size limit to protect API rate limits. Not checked yet
4 details in Everything
Open-source agent skills - teach AI coding assistants to use ggshield (2026-05-21)
May 21, 2026
· release notes
GitGuardian SaaS adds agent skills for Claude Code and Cursor to invoke ggshield scanning and remediation natively within AI coding assistants.
└──▷ TRY IT
Install the agent skill so Claude Code can scan secrets when requested by the developer.
copy
$ /plugin install ggshield
Enable automatic scanning of all AI agent interactions by installing the ggshield hook for Claude Code.
copy
$ ggshield install -t claude-code
Configure Cursor rules to expose the ggshield workflow for on-demand agent use.
📍 Drop the provided skills into your .cursor/ directory
Adds gitguardian/agent-skills repository providing Claude Code plugin and Cursor rules to teach AI assistants how to use ggshield Not checked yet Enables optional ggshield install -t claude-code hook to automatically scan every prompt, tool call, and output inside the agent Not checked yet Jira Cloud integration now uses scheduled recurrent scans instead of inbound webhooks for monitoring Not checked yet
3 details in Everything
A smarter search bar - find incidents by value, author, file path, or in plain English (2026-05-20)
May 20, 2026
· release notes
GitGuardian SaaS adds value/author/path/NL search and Teams regression notifications to the UI
└──▷ HOW TO FIND IT
Find incidents involving a specific developer fragment like @contractor.com
📍 Type @contractor.com into the main incident search bar.
Use AI to filter for unassigned critical cloud incidents via natural language
📍 Ensure AI Filters are enabled in workspace settings, then type "Open critical unassigned incidents related to cloud providers" into the search bar.
Adds natural language search (AI Filters) to the incident search bar, allowing full-sentence queries that compose with structured filters. Not checked yet Adds search by secret value, commit author, file path, and source name directly in the main incident search bar. Not checked yet
2 details in Everything
Enhanced Microsoft Teams Notifications - Public Monitoring, Internal Monitoring & Honeytoken Alerts (2026-04-29)
Apr 29, 2026
· release notes
Enhanced Microsoft Teams notifications for all incident events, public monitoring, and honeytokens; new API health checks and archived source filters
Microsoft Teams config supports granular subscription to specific event types (resolution, assignment, status changes, comments, access control, sharing) per channel Not checked yet Microsoft Teams notifications now include Public Monitoring incidents alongside internal monitoring alerts Not checked yet Microsoft Teams notifications now support Honeytoken Alerting events, previously only available via custom webhooks and email Not checked yet GET /rest/sources returns provider_metadata.archived field for GitHub sources and accepts provider_metadata_archived=true filter Not checked yet GET /rest/incidents accepts only_on_provider_archived_sources=true filter to focus on incidents from archived sources Not checked yet
5 details in Everything
Attachment scanning now covers all Jira and Confluence variants! (2026-04-27)
Apr 27, 2026
· release notes
Attachment scanning adds support for Jira and Confluence Cloud and Data Center sources.
└──▷ HOW TO FIND IT
Reinstall Jira or Confluence integrations to grant new read:attachment:jira or readonly:content.attachment:confluence scopes required for attachment scanning.
📍 Go to Settings › Integrations › Sources and click Reinstall for each affected Jira/Confluence source.
Removes deprecated Honeytoken Labels API endpoints, requiring migration to the Custom Tags API. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The Honeytoken Labels API endpoint is removed; use the Custom Tags API instead.
GitGuardian now listed on the Slack Marketplace, packed with new capabilities! (2026-04-23)
Apr 23, 2026
· release notes
GitGuardian Slack app now on Marketplace with channel selection, attachment scanning, and Jira dynamic variables.
└──▷ HOW TO FIND IT
Install GitGuardian in the US region via the app directory.
📍 Open https://slack.com/apps? Referring to the GitGuardian (US) listing in the Slack Marketplace.
Use dynamic variables to create a Jira ticket that includes the secret type and source name.
📍 When configuring the Jira Integration in Settings › Integrations, use {secretType} and {sourceName} in Labels or Summary fields.
Monitor specific public channels instead of all of them during Slack setup.
📍 During the Slack app installation flow, use Channel selection at setup time to choose which public channels to monitor.
Slack app is officially listed on the Slack Marketplace in both US and EU regions. Not checked yet Channel selection at setup time allows users to choose which public channels to monitor during installation instead of the app automatically joining every public channel. Not checked yet File attachment scanning detects secrets hiding in file attachments dropped in channels and messages alongside text-based messages. Not checked yet Interactive messages Beta posts a threaded response directly in the original conversation with details about the finding and quick actions, including the ability to ignore low-risk incidents without leaving Slack. Not checked yet Enhanced privacy controls redact private channel names for users who don't have access to those channels in Slack and display a privacy information banner during setup. Not checked yet
+1 more
show less
Jira Integration now supports dynamic variables (e.g., {secretType}, {sourceName}, {sourceType}) across all Jira fields — including Labels, Summary, Priority, and custom fields — not just the description. Not checked yet
6 details in Everything
└──▷ BREAKING ON UPGRADE
! If you previously covered your Slack Perimeter with GitGuardian, you will need to reinstall your Slack App using the same procedure.
Monitor your Gerrit repositories (2026-04-20)
Apr 20, 2026
· release notes
GitGuardian adds native Gerrit VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. integration with read replica support
Adds native Gerrit VCS source integration for secrets detection in enterprise code review workflows. Not checked yet Enables read replica configuration to point GitGuardian to a secondary server for cloning operations, reducing load on the primary Gerrit instance. Not checked yet Introduces support for the webhook plugin to enable real-time secret detection as commits are pushed to Gerrit repositories. Not checked yet
3 details in Everything
Flag admin and overprivileged NHIs across AWS, Entra, and Okta
Apr 16, 2026
· release notes
New NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. admin/overprivilege detection, policy, badge, severity bump, and privacy mode scope
Identity level: Admin badge marks NHIs NHIs A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. with admin permissions (AWS AdministratorAccess, Entra Global Administrator, Okta Super Admin) in inventory and detail views Not checked yet New Overprivileged Identity policy flags NHIs granted broader permissions than used Not checked yet Admin NHI policy breaches automatically bumped one severity level higher (capped at critical) Not checked yet Workspace-level Privacy Mode restricts plaintext secret visibility to managers or owners only Not checked yet Public API now exposes the list of captured audit log event types Not checked yet
5 details in Everything
Control team access to any Internal Monitoring source type
Apr 13, 2026
· release notes
Team perimeter access control now extends to all non-VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. integrations and BYOS sources.
team perimeter configuration now scopes internal incident access for container registries, messaging (Slack, Microsoft Teams), documentation/file storage (Confluence, SharePoint Online, OneDrive), ticketing (Jira, ServiceNow), package registries, and Bring Your Own Sources Not checked yet Managers can add specific sources to a team's perimeter via Settings > User management > Teams using the Add sources option in the perimeter section Not checked yet
2 details in Everything
ggshield 1.49.0 adds real-time secret scanning secret scanning Checking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. hooks for Cursor, Claude Code, and GitHub Copilot
New ggshield install -t <tool> -m global command to configure real-time AI coding assistant hooks Not checked yet Added GET /v1/severity-rules endpoint to list severity rules programmatically Not checked yet Public API now supports privacy mode to control secret content visibility in retrieved secrets Not checked yet
3 details in Everything
Email Verification for Sensitive Actions (MFA)
Mar 24, 2026
· release notes
GitGuardian adds email MFA MFA Multi-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. for login/sensitive actions and new API/location fields
Adds POST /v1/scan/create-incidents endpoint support for optional location.url field to link scanned documents back to their origin Not checked yet Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. (PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. ) and Service Account Tokens (SAT) now use an improved v2 format with gg_pat_ and gg_sat_ prefixes Not checked yet
2 details in Everything
Publicly leaked tag and exposure detail in internal incidents
Mar 10, 2026
· release notes
GitGuardian SaaS introduces consolidated Publicly leaked tag and new Public exposure property for internal monitoring incidents.
Adds new Public exposure property with categories: Source is publicly visible, Has linked public incident, Found outside perimeter Not checked yet Introduces default saved view Public exposure and dedicated column for filtering and viewing exposure details Not checked yet
2 details in Everything
GitGuardian Is Now on the Okta Integration Network
Mar 6, 2026
· release notes
GitGuardian adds Okta Integration Network support for SAML SSO SAML SSO An authentication protocol that lets a user log in once with an identity provider and access multiple services without re-entering credentials, by passing signed XML assertions between parties. and SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. provisioning
Adds Okta-verified app integration on the Okta Integration Network for streamlined identity management. Not checked yet Enables One-click SAML SAML A standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. SSO SSO Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. configuration via the Okta app catalog without custom SAML apps. Not checked yet Supports automatic user lifecycle management through built-in SCIM provisioning (create, update, deactivate). Not checked yet Adds Group Push capability to sync Okta groups and memberships directly into GitGuardian teams. Not checked yet Supports both SP-initiated SP-initiated A SAML or OAuth/OIDC login flow where the Service Provider redirects the user to an Identity Provider to authenticate, rather than the IdP pushing an assertion unprompted; tools use it to trigger SSO from their own login page. and IdP-initiated SSO IdP-initiated SSO A single sign-on flow where the identity provider redirects an already-authenticated user directly to a service provider without the service provider first requesting authentication, removing the need for a separate login prompt. flows from the GitGuardian dashboard or Okta portal. Not checked yet
+1 more
show less
Introduces Just-in-Time provisioning for new users on first login, independent of SCIM status. Not checked yet
6 details in Everything
Red Hat Quay Integration: Your Enterprise Images, Under Watch
Mar 5, 2026
· release notes
GitGuardian SaaS adds Red Hat Quay integration and a public API for egress IPs
Adds Red Hat Quay container registry integration to Settings > Integrations > Sources for scanning image layers in both quay.io and self-hosted instances Not checked yet Adds public API endpoint to retrieve GitGuardian's egress IP addresses in CIDR CIDR A notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network. notation Not checked yet Enables OAuth2 OAuth2 An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. authentication for the Red Hat Quay integration with read-only access Not checked yet
3 details in Everything
JFrog Artifactory Package Registries: Secrets Hide in Your Packages Too
Mar 3, 2026
· release notes
GitGuardian adds JFrog Artifactory package registry integration for secrets detection in build artifacts.
Adds JFrog Package Registries integration to the Package registries section under Settings > Integrations > Sources Not checked yet Adds PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. scope restriction setting in Security Settings, allowing workspace managers to limit members to specific scopes like Scan only Not checked yet Adds customizable session duration setting in Authentication Settings for automatic dashboard logout Not checked yet Adds filename and line number template options in Jira ticketing templates Not checked yet Adds System theme mode option in Dashboard that matches OS light/dark preference Not checked yet
+1 more
show less
Adds feedback content (remarks) to Slack and Webhook alert payloads for monitoring incidents Not checked yet
6 details in Everything
Ownership - Assign Accountability for Non-Human Identities
Feb 11, 2026
· release notes
GitGuardian adds Ownership for Non-Human Identities with owner assignment, suggested owners, and Owner column/filter in NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. .
Adds Ownership capability in NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. Governance to assign and track responsibility for each Non-Human Identity. Not checked yet Adds automatic suggested owners based on integrated source data and secret incidents. Not checked yet Adds an Owner column in the NHI inventory view showing responsible identities. Not checked yet Adds ability to add, edit, or remove owners at any time from an NHI's detail view for workspace members and external users identified by email. Not checked yet Adds filtering capability by owner (e.g., "identities with no owner" or "owned by my team") in the NHI inventory. Not checked yet
5 details in Everything
Night Owl Mode: Improved UI + Dark Theme
Feb 2, 2026
· release notes
GitGuardian adds Dark Mode UI and incident API external ticket fields
Account → Interface → Theme dropdown allows per-user selection of Light or Dark theme to reduce eye strain during late-night incident response. Not checked yet Incidents API responses now include external ticket information for Jira and ServiceNow integrations. Not checked yet Analytics period selector expanded to include Last 30/60/90 days and Previous month/quarter/year ranges. Not checked yet
3 details in Everything
Unified Identity Governance for Entra & AWS IAM
Jan 22, 2026
· release notes
GitGuardian expands NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. to Microsoft Entra ID Entra ID Microsoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. and AWS IAM AWS IAM AWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. with unified identity mapping, risk scoring, and OIDC OIDC OpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. authentication.
Expands NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. Governance integrations for Microsoft Entra ID and AWS IAM IAM Identity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. with an enriched graph of identities, policies, and secrets. Not checked yet Introduces automatic risk criticality scoring to surface high-impact threats like leaked credentials and orphaned accounts Not checked yet Enables credential-free, short-lived token-based access via OIDC for the new identity integrations Not checked yet
3 details in Everything
More NHI Integrations - Datadog, Snowflake, Okta, and Auth0
Dec 31, 2025
· release notes
Release expands non-human identity non-human identity A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. (NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. ) governance capabilities by enabling enumeration of service accounts and API keys across four critical infrastructure platforms: Datadog, Snowflake, Okta, and Auth0.
Analytics Overview - Executive Bird's-Eye View of Security Posture
Dec 19, 2025
· release notes
New Analytics Overview dashboard for executives with unified KPIs and trend visualizations
Adds Analytics > Overview page providing a unified KPI strip for Protect, Detect, Remediate, and Govern metrics including repository coverage, incident volume, remediation speed, and identity safeguards. Not checked yet Enables visualization of monitored perimeter trends showing how repository count evolves week over week. Not checked yet Introduces Top Risky Data Sources view to identify repositories generating the most critical and high-severity incidents. Not checked yet Adds Critical Incident Trajectories chart to track incident volume changes over time. Not checked yet Displays Most Common Secret Types breakdown to understand frequently appearing secret categories in the perimeter. Not checked yet
+2 more
show less
Provides Closure Progress metrics monitoring auto-closures and manual resolutions for remediation performance. Not checked yet Surfaces Governance Signals view showing vaulted secrets and breached policies for NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. governance insights. Not checked yet
7 details in Everything
Risk score - ML-powered incident prioritization
Dec 17, 2025
· release notes
GitGuardian adds ML-powered risk score (0-100) to incidents for Business workspaces with filtering, sorting, and updated Critical view.
Adds a 0–100 risk score to incidents based on secret type, validity, detection context, and exposure patterns. Not checked yet Enables filtering by risk score range and sorting by priority in the incidents table Not checked yet Updates the Critical saved view to show incidents with risk score above 80 Not checked yet Introduces a Recommended for business filter in detector settings to help re-enable detectors previously flagged as non-business Not checked yet
4 details in Everything
Secret Enricher - From Generic to Actionable
Dec 17, 2025
· release notes
Secret Enricher v2 provides enriched secret types in UI and API responses for Business/Enterprise plans.
Incident UI now displays ML-enriched secret identities (e.g., Redis Identifiers , AWS Access Key ) instead of generic detector names like Generic High Entropy Secret . Not checked yet Incident API responses include enriched secret names for programmatic access. Not checked yet CSV and JSON export reports now include both the original detector name and enriched secret name. Not checked yet
3 details in Everything
New NHI Integrations - Airbyte, Anthropic, N8n, OpenAI, CyberArk Self Hosted, an
Dec 12, 2025
· release notes
GitGuardian SaaS adds NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. discovery for Airbyte, Anthropic, and more; incidents API date filtering
└──▷ HOW TO FIND IT
Connect a new Airbyte workspace to expand NHI discovery coverage.
📍 Navigate to Settings › Integrations › Sources › NHI Governance and connect your Airbyte, Anthropic, N8n, OpenAI, CyberArk Secrets Manager Self Hosted, or Slack workspace.
Adds Identity Discovery for Airbyte, Anthropic, N8n, OpenAI, CyberArk Secrets Manager Self Hosted, and Slack via Settings > Integrations > Sources > NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. Not checked yet Adds support for filtering incidents by triggered date in the public Incidents API endpoint Not checked yet Adds Valid saved view to the Incidents Dashboard available for all accounts Not checked yet
3 details in Everything
SCIM Team provisioning now available
Nov 17, 2025
· release notes
GitGuardian SaaS adds SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. team provisioning for Okta and Entra ID Entra ID Microsoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments.
Adds SCIM team provisioning capability for Okta and Microsoft Entra IdPs Not checked yet Requires teams:write and members:write service account token scopes Not checked yet
2 details in Everything
Playbooks extended to Public Monitoring
Nov 7, 2025
· release notes
GitGuardian Playbooks now support Public Monitoring to automate secret remediation workflows.
Adds Playbooks support for public secret incidents in Public Monitoring Not checked yet Exposes the change_type field for secret occurrences via the API Not checked yet
2 details in Everything
Graph Enhancement and HasMySecretLeaked Integration
Oct 28, 2025
· release notes
Enhanced identity graph unifies public leak detection and displays large occurrence patches in incident views
Displays severity levels, source information, and occurrence data directly within the unified identity graph interface for both internal and public monitoring incidents Not checked yet Adds three distinct types of public exposure categorization to the HasMySecretLeaked integration: secrets in monitored public sources, incidents in your public perimeter, and external GitHub locations Not checked yet Unifies previously scattered exposure indicators under a new Publicly Leaked tag across Internal Monitoring, Public Monitoring, and NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. modules Not checked yet
3 details in Everything
Enhanced Slack Notifications - Public Monitoring, Internal Monitoring & Honeytok
Oct 25, 2025
· release notes
Enhanced Slack notifications now cover incident lifecycle events, public monitoring, and honeytoken alerts with granular per-channel configuration.
Slack notifications now include incident resolution, assignment, status changes, comments, access control, and sharing events in addition to new detections and regressions Not checked yet Public monitoring incidents can be sent to Slack channels alongside internal monitoring alerts for perimeter security visibility Not checked yet Honeytoken alerting is now supported in Slack notifications, previously limited to custom webhooks and email Not checked yet Slack webhook configuration supports subscribing to specific event types per channel for granular notification control Not checked yet Custom Monitored Perimeter can now be edited via the Public API for all sources except custom sources Not checked yet
5 details in Everything
ggshield - Show vault information for vaulted secrets
Oct 17, 2025
· release notes
ggshield now exposes vault names and paths for secrets in integrated managers
GitGuardian Bridge - Secure Access to All Your Self-Hosted Services
Oct 9, 2025
· release notes
GitGuardian Bridge expands to all self-hosted services; adds Generic Secret Enricher v2 and False Positive Remover v2.5
GitGuardian Bridge now supports comprehensive integration with any self-hosted service in private networks, including GitHub Enterprise, GitLab, Jira Data Center, Confluence, Container registry, and custom sources, using flexible domain mapping. Not checked yet Generic Secret Enricher v2 introduces 50 new providers and enhances enrichment by 75% for public data and 50% for internal data. Not checked yet False Positive Remover v2.5 improves detection of false positives in secret identifiers, file paths, variable names, and plugin versions; the vendor reports twice as many identified, varying by customer. Not checked yet Added automatic Jira ticket assignment to incident authors via email matching for both Jira Cloud and Data Center. Not checked yet
4 details in Everything
MS Teams attachment scanning is here!
Sep 30, 2025
· release notes
GitGuardian SaaS now scans Microsoft Teams file attachments for secrets with no extra setup or cost.
Adds automatic scanning of file attachments shared within Microsoft Teams to detect hidden secrets Not checked yet Enables manual historical scanning of past Teams messages via the perimeter interface to cover previously unscanned attachment debt Not checked yet
2 details in Everything
“Explore” and find more company-related secrets!
Sep 26, 2025
· release notes
New Explore feature in Public Monitoring enables proactive discovery of organizational secrets in public repos.
Adds Explore UI section under Public Monitoring for company-focused secret discovery Not checked yet Enables targeted queries against domains, service names, and internal system references in public GitHub repositories Not checked yet Supports CSV export of the developer list from the Public Monitoring perimeter view Not checked yet
3 details in Everything
Seal the Leak - Instantly Revoke Secrets with GitGuardian!
Sep 23, 2025
· release notes
GitGuardian SaaS adds in-platform Secret Revocation for GitHub, GitLab, and OpenAI via a new Revocable by GitGuardian tag.
Adds the Revocable by GitGuardian tag to incidents containing secrets that can be immediately revoked from the platform, accelerating incident response workflows Not checked yet Enables in-platform secret revocation for supported providers (GitHub, GitLab, OpenAI) via a call-to-action in the incident detail view, which automatically resolves valid revocations and logs them in the incident timeline Not checked yet Adds Container Registries endpoints to the public API documentation. Not checked yet
3 details in Everything
Introducing AI Filters - It's time to have a conversation with your data!
Sep 17, 2025
· release notes
GitGuardian SaaS introduces AI Filters for natural language querying and GitHub Check Runs with public share links
Adds AI Filters in Incidents, Perimeter, and Audit Logs to query data using natural language queries Not checked yet Adds the ability to save AI-generated filters as views for team sharing Not checked yet Adds option in GitHub Check Runs to include public share links for incident details Not checked yet
3 details in Everything
Context Preview for non-VCS Secret Leaks!
Aug 20, 2025
· release notes
Context Previews now available by default for non-VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. Secret Leaks incidents to accelerate investigation.
Adds automatic Context Preview visibility for Secret Leaks in non-VCS sources (SharePoint, OneDrive, Slack, Confluence) directly within GitGuardian incidents. Not checked yet
1 detail in Everything
Public Monitoring API endpoints now available
Aug 1, 2025
· release notes
GitGuardian adds Public Monitoring API endpoints to manage public incidents and list public-perimeter developer information.
Extend your security coverage with Public Monitoring
Jul 25, 2025
· release notes
New unified module extends secrets scanning to public GitHub with correlated incident management.
New Analytics - Gain Deeper Insights into Your Security Posture
Jul 23, 2025
· release notes
New Internal Monitoring analytics dashboards and multi-hook GitLab integration support
Adds new Internal Monitoring analytics dashboards tracking Protect, Detect, Remediate, and Prevent dimensions via Count of sources , Most detected secrets , Top teams by incident count , Top sources by incident count , Median time to remediate , Total count of incidents avoided by GGShield , and GGShield scans over time charts and tables Not checked yet Supports simultaneous configuration of multiple GitLab integrations using both system hooks and group hooks Not checked yet
2 details in Everything
Historical Scanning now available for Confluence Data Center
Jun 30, 2025
· release notes
GitGuardian SaaS adds historical secret scanning secret scanning Checking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. for Confluence Data Center
Enables historical secret scanning for Confluence Data Center, surfacing secrets leaked in past content rather than only real-time detections. Not checked yet Enhances Jira Data Center integration to include leaker email addresses in incident creation for historical comment occurrences. Not checked yet
2 details in Everything
GitGuardian MCP Server - Security in Your AI IDE
Jun 19, 2025
· release notes
GitGuardian MCP Server MCP Server A process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. releases for AI IDEs; Custom Tags API adds key/value filtering.
Releases the GitGuardian MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Server on GitHub to bring security scanning and incident management into Cursor, Windsurf, and other Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. -compatible IDEs Not checked yet Enhances the custom tags filter in the public API to support filtering by key/value pairs in addition to IDs Not checked yet
2 details in Everything
Securely Access Secret Values via API with GitGuardian's New “Secrets” Endpoint
May 23, 2025
· release notes
GitGuardian adds /v1/secrets/{secret_id} to retrieve secret values and detector information through the API.
Adds the /v1/secrets/{secret_id} API endpoint that returns the secret value alongside detector information in a single response Not checked yet
1 detail in Everything
Automate User Onboarding & Offboarding with SCIM
May 21, 2025
· release notes
GitGuardian SaaS adds SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. -based automated user provisioning and deprovisioning for Okta and Entra ID Entra ID Microsoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. .
Adds automatic user provisioning and deprovisioning via SCIM integration Not checked yet Requires Workspace Settings > Authentication to enable SCIM Not checked yet
2 details in Everything
New Secrets Detection in Microsoft Teams adds real-time and historical scanning capabilities for Teams messages.
Adds hardcoded secret detection for Microsoft Teams, scanning both new activity and historical content. Not checked yet Updates weekly digest and historical scan emails to include the number of incidents in the subject line. Not checked yet
2 details in Everything
Customize Your Incidents View for Enhanced Context Exploration
May 2, 2025
· release notes
GitGuardian adds fully customizable views for the Incidents page to filter, sort, and prioritize security data.
Adds ability to create fully customized Incident views displaying specific properties and exploring security data. Not checked yet
1 detail in Everything
Historical Scanning now available for Jira and Confluence Cloud sources.
Apr 29, 2025
· release notes
GitGuardian adds a Public API GET endpoint for retrieving invitation details.
Secure your Non-Human Identities with NHI Governance
Apr 23, 2025
· release notes
Introduces NHI Governance NHI Governance The policies, controls, and lifecycle management applied to Non-Human Identities — service accounts, API keys, tokens, and certificates — to enforce least-privilege access and reduce credential sprawl across systems. for non-human identity non-human identity A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. management and adds GET /v1/invitations/{invitation_id} API endpoint
Adds NHI NHI A non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls. Governance solution for comprehensive observability and lifecycle management of Non-Human Identities across environments like CI/CD pipelines and Kubernetes Clusters. Not checked yet
1 detail in Everything
Prioritize faster with Secrets Analyzer
Apr 14, 2025
· release notes
Secrets Analyzer adds scope/permission context; Custom Tags and webhook payload enhancements in SaaS
Adds Secrets Analyzer which automatically gathers scopes, permissions, ownership, and perimeter information for detected secrets to aid prioritization Not checked yet Enables creating Custom Tags directly from search queries in the dashboard Not checked yet Adds team name and webhook name fields to the custom webhook payload for incidents and occurrences Not checked yet
3 details in Everything
Improve incident remediation with custom tags
Mar 24, 2025
· release notes
Custom tags for incident categorization and filtering, plus email notification options
Adds support for custom tags to categorize, filter, and search incidents in the GitGuardian platform Not checked yet Adds All incidents (default) or Only incidents involving yourself options for email notifications Not checked yet
2 details in Everything
Detect hardcoded secrets in your Container Registries
Mar 19, 2025
· release notes
GitGuardian SaaS adds hardcoded secret detection for Azure ACR, Amazon ECR ECR Amazon Elastic Container Registry, AWS's managed service for storing and distributing Docker and OCI container images, giving cyber tools a private, IAM-gated registry without self-hosting infrastructure. , Google Artifact Registry, JFrog, and DockerHub container images.
Leverage insights from your Secrets Managers
Feb 28, 2025
· release notes
GitGuardian SaaS adds ggscout integration with AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, Google Secret Manager, Delinea, and Akeyless to sync secret incidents.
GitGuardian SaaS adds ServiceNow secret and honeytoken detection for automated incident tracking
Adds ServiceNow as a supported integration for automated tracking of security incidents via secret and honeytoken detection. Not checked yet Enhances Jira Data Center integration to support User Picker (single user) custom fields in templates. Not checked yet
2 details in Everything
Bitbucket Cloud scanning, Microsoft Teams alerts & Jira issue tracking
Jan 13, 2025
· release notes
GitGuardian adds Bitbucket Cloud scanning, Microsoft Teams alerts, and Jira Data Center auto-tracking in Jan 2025 release.
Enables secrets detection and real-time monitoring for Bitbucket Cloud repositories Not checked yet Delivers real-time GitGuardian security incident notifications directly to Microsoft Teams channels with direct investigation links Not checked yet Integrates Jira Data Center to auto-create issues on new incidents, sync custom fields, and auto-resolve incidents when linked Jira issues close Not checked yet
3 details in Everything
ML-Powered Similar Incident Grouping - Combat Incident Fatigue!
Jan 8, 2025
· release notes
Adds ML-powered similar incident grouping to sidebar for bulk remediation on Business & Enterprise plans
Introduces ML-Powered Similar Incident Grouping that automatically groups related security incidents (e.g., rotating tokens, QA credentials) based on context beyond just detector types. Not checked yet Adds a Similar Incidents section to the sidebar of any incident detail page to view grouped items and execute bulk actions for efficient remediation. Not checked yet Improved token refresh reliability for Slack and Atlassian Cloud integrations with automatic retry on transient failures. Not checked yet
3 details in Everything
GitGuardian adds GitLab OAuth Application Token detector in Dec 23, 2024 release
Added GitLab OAuth Application Token to the secrets detection engine (v2.129) Not checked yet
1 detail in Everything
GitGuardian SaaS updates detection engine v2.128 with four new detectors and allows disabling auto repo monitoring via GitHub integration
Adds Jenkins API token , chpasswd Username Password, Nessus Agent Key , and Statsig Server Secret Key detectors in secrets detection engine v2.128 Not checked yet Allows Workspace Managers to disable automatic repository monitoring during VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. integration setup Not checked yet
2 details in Everything
GitGuardian SaaS adds SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. user provisioning, secret pattern exclusions, GitHub forked repo checks, and Jira template selection.
Adds steps for SCIM integration enabling automatic user deprovisioning in GitGuardian based on Identity Provider changes Not checked yet Adds steps to define secret pattern exclusion rules to hide secrets matching defined patterns from all or specific repositories Not checked yet Adds steps to enable GitGuardian check runs on GitHub forked repositories for Business workspaces Not checked yet Adds steps for a template selection dropdown when manually creating Jira Cloud issues via the integration Not checked yet
4 details in Everything
GitGuardian SaaS adds send_email param to invite API, instance-level GitLab integration via admin token, and v2.126 secrets detection with 4 new detectors.
Adds send_email: true|false parameter to Platform API endpoints that trigger email notifications (e.g., invitation creation) to control whether an email is sent Not checked yet Upgrades secrets detection engine to version 2.126, adding support for X-API Key Secret, Azure Functions App Key Header, and Azure Functions App Key Query Parameter detections Not checked yet
2 details in Everything
SaaS release adds secrets detection engines v2.125, scopes for All Sources API, and new Settings sections.
Secrets detection engine upgraded to version 2.125 Not checked yet Added sources:read scope for GET endpoints in the All Sources API Not checked yet Added sources:write scope for PATCH endpoint in the All Sources API Not checked yet New Integrations section under Settings Not checked yet
4 details in Everything
Adds ServiceNow Issue Tracking integration for automated incident management
Adds ServiceNow issue tracking integration to create issues from GitGuardian incidents Not checked yet Enables auto-resolve setting to mark GitGuardian incidents as resolved when the linked ServiceNow issue closes Not checked yet
2 details in Everything
GitGuardian adds GitHub custom properties override for check runs and bulk historical scan management with instance filtering.
Adds gh_custom_properties support to leverage GitHub's custom properties for overriding GitGuardian global configuration of check runs at repository and organization levels Not checked yet Introduces Bulk Historical Scans Management page with a new filter for instances (e.g., production/staging) to track and filter historical scans Not checked yet
2 details in Everything
GitGuardian SaaS allows secrets detection filepath exclusions to be scoped to specific repositories.
Adds repository-scoped filepath exclusions for secrets detection incidents. Not checked yet
1 detail in Everything
GitGuardian adds ggshield VS Code extension and secrets engine v2.122
Adds GitGuardian CLI (ggshield) as a VS Code extension with automatic file scanning on save and in-IDE remediation guidance Not checked yet Upgrades secrets detection engine to version 2.122, adding Atlassian Access Token, Bitbucket Access Token, and Mistral AI API Key detectors Not checked yet
2 details in Everything
Jira Data Center integration for secret/honeytoken detection and Honeytoken saved views added in GitGuardian SaaS.
Adds Jira Data Center integration to support real-time secret detection and honeytoken detection Not checked yet Adds the ability to create Saved views in Honeytoken Not checked yet
2 details in Everything
GitGuardian adds Confluence Data Center integration, Slack history scanning, IP allowlisting, and Historical Scan filters.
Confluence Data Center integration enables real-time secret detection and honeytoken detection for Confluence Data Center instances Not checked yet Platform IP allowlist allows managers to restrict access to the dashboard and API by specified IP addresses or ranges (Business accounts only) Not checked yet Historical Scan UI adds new filters for failure reasons and last scan date Not checked yet
3 details in Everything
GitGuardian SaaS upgrades secrets detection engine to v2.120 with two new detectors and fixes Jira Cloud pagination.
Adds Generic Password YAML detector for identifying passwords in YAML files Not checked yet Adds Buildkite API Token V2 detector for identifying Buildkite tokens Not checked yet Enhances recall for existing detectors including Generic Database , Base64 , and High Entropy Secret Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! reCAPTCHA Key detector now skips validity checks for reCaptcha keys, potentially increasing noise as validity can no longer be ensured due to Google API changes
GitGuardian August 14 2024 adds saved views, custom remediation messages, and a new team leader API field
Adds is_team_leader boolean in the /v1/teams/{team_id}/team_memberships and /v1/teams/{team_id}/team_invitations API endpoints to replace the deprecated team_permissions field for designating team owners. Not checked yet Adds Saved Views feature allowing admins to save frequently used filters as named views for quicker access in the dashboard. Not checked yet Adds custom remediation message support in ggshield for pre-commit pre-commit An open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. , pre-push, or pre-receive stages to provide developers with internal guidance. Not checked yet Adds Health Check capability in the GitGuardian dashboard letting managers manually start checks for failed items immediately. Not checked yet
4 details in Everything
└──▷ BREAKING ON UPGRADE
! The team_permissions field is deprecated and replaced by the is_team_leader field in the /v1/teams/{team_id}/team_memberships and /v1/teams/{team_id}/team_invitations API endpoints.
GitGuardian SaaS adds ML-based false positive reduction and GitLab CE integration with optional historical scan skipping.
Deploying an in-house machine learning model that halves secrets detection false positives for all Business and Enterprise accounts Not checked yet Adding GitLab Community Edition integration support with the ability to skip historical scans upon installation Not checked yet
2 details in Everything
GitGuardian SaaS adds Microsoft Teams integration, .NET SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. support, scan skip for unchanged repos, and API fields.
Adds Microsoft Teams integration for real-time secret and honeytoken detection notifications Not checked yet Enables .NET SCA scanning for C#, F#, and Visual Basic dependencies Not checked yet Introduces a new scan skip mechanism for repositories that have not changed since the last scan Not checked yet Adds pending_timeout status to the API to distinguish queued scans from timed-out ones Not checked yet Exposes secret incident user feedback via the feedback_list field in the API payload Not checked yet
+2 more
show less
Displays the workspace data storage region in the workspace settings UI Not checked yet Adds an optional Skip action for check runs on forked repositories with detected secrets Not checked yet
7 details in Everything
Adds per page selector to secrets detection occurrences table; API deprecates role in favor of access_level.
Adds a per page selector to the secrets detection incident details occurrences table to control pagination density. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! The role field is deprecated and replaced by the access_level field in the API for endpoints /v1/members and /v1/invitations.
GitGuardian SaaS adds detection for Sentry and Slack secret types in engine v2.115
Secrets Detection engine upgraded to version 2.115 with expanded secret coverage Not checked yet Adds detection for Sentry Org Auth Token secrets Not checked yet Adds detection for Sentry User Auth Token v2 secrets Not checked yet Adds detection for Slack Configuration Refresh Token secrets Not checked yet Adds detection for Slack Configuration Token secrets Not checked yet
5 details in Everything
GitGuardian adds 9 new secret detectors, GitLab webhook auto-reactivation, Malicious Package detection, and health check email alerts.
Adds 9 new secret detectors: ASP.NET Decryption Key, ASP.NET Validation Key, Langchain API Key, OpenAI Project API Key, OpenAI Service Account, Sourcegraph Enterprise Subscription Token, Sourcegraph License Key Token, Sourcegraph User Gateway Access Token, and WakaTime API Key. Not checked yet Updates detection for 4 existing detectors: Sentry Token, Generic Database assignment, Generic FTP FTP A decades-old TCP-based protocol for transferring files between a client and server, using separate control and data connections; cyber tools target or support it because it often transmits credentials in plaintext. Assignment, and Generic Username Password. Not checked yet Enables periodic secret validity checks for ignored incidents to ensure they remain valid over time. Not checked yet Shows the count of new secret incidents that will be hidden by a new filepath exclusion rule during rule creation. Not checked yet Automatically reactivates disabled GitLab webhooks by sending a test payload before triggering an error message. Not checked yet
+1 more
show less
Sends email notifications when an integration health check fails, configurable via email preferences settings. Not checked yet
6 details in Everything
New API endpoint for querying secret incidents and improved incident details with GitHub merge commit author attribution.
Adds a new API endpoint to query the secret incidents of a specific source Not checked yet Merges commit authors from GitHub into Secrets Detection Incidents details Not checked yet
2 details in Everything
GitGuardian adds Nylas, Sourcegraph v3, Vercel and other new secret detectors plus platform health check tracking
Adds detection for Nylas API Key secrets Not checked yet Adds detection for Sourcegraph Access Token v3 secrets Not checked yet Adds detection for Duplo Cloud API Key secrets Not checked yet Adds detection for Fernet Key secrets Not checked yet Adds detection for Vercel Blob Token secrets Not checked yet
+1 more
show less
Introduces Platform Health Check tracking for last execution and last successful execution times with hourly periodic checks Not checked yet
6 details in Everything
Platform API tokens now include workspace_id; improved historical scan status visibility.
Adds workspace_id to the payload of API tokens in the Platform API Not checked yet Improves historical scan status overview on the perimeter page sidebar Not checked yet
2 details in Everything
GitGuardian SaaS adds Grafana Cloud API Key, Groq API Key, and Nx Cloud Token detectors in v2.111; allows deletion of AI query history.
Secrets detection engine upgraded to version 2.111 with three new detector types: Grafana Cloud API Key, Groq API Key, and Nx Cloud Token Not checked yet
1 detail in Everything
GitGuardian SaaS extends its secret management capabilities by integrating with CyberArk's Platform Vault.
April 15 release adds Generic CLI/DB detectors, SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. mod date filter, and updates detection engine v2.110
Generic CLI Secret and Generic Database Assignment detectors are now supported and active by default for data sources other than VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. . Not checked yet SCA incidents now include the last modification date of dependency files, along with a dedicated filter to view them. Not checked yet Secrets detection engine upgraded to version 2.110, adding support for Dropbox Key, Midtrans API Key, Sanity Token, and Zuplo API Key detectors. Not checked yet
3 details in Everything
GitGuardian SaaS introduces a new Jira Cloud integration with auto-create, custom fields, and auto-resolve for incident tracking
Adds automatic creation of a Jira issue upon new incident trigger via the Jira Cloud integration Not checked yet
1 detail in Everything
GitGuardian SaaS adds dynamic-only honeytonedeployment and a secret identity card to incident pages.
Honeytoken Context creation strategies now support selecting only dynamic contexts for deployment jobs Not checked yet Secret Incident detail pages now display a secret identity card Not checked yet Privacy mode can obfuscate secrets and other sensitive information in the GitGuardian UI Not checked yet
3 details in Everything
GitGuardian SaaS adds PHP dependency support and EPSS EPSS Exploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. scores to SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. incidents
Adds Support for PHP dependencies in the Software Composition Analysis (SCA) scanner Not checked yet Includes the EPSS score in SCA incident details along with a dedicated filter Not checked yet
2 details in Everything
GitGuardian SaaS adds filtering on Occurrences count and severity breakdown to API payload
└──▷ HOW TO FIND IT
Filter incidents by frequency to focus on high-volume issues.
📍 In the Incidents view, use the filter dropdown to select Occurrences count and enter your threshold.
Adds Occurrences count filter to Incidents view Not checked yet Includes secret incident severity breakdown in the API response payload Not checked yet
2 details in Everything
GitGuardian SaaS adds PHP dependency support to its SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. engine
Adds PHP dependencies to the Software Composition Analysis (SCA) engine for scanning third-party library vulnerabilities. Not checked yet
1 detail in Everything
GitGuardian SaaS adds Honeytoken deployment permissions UI and exposes Incident tags in CSV export.
Adds GitHub/GitHub Enterprise Server integration settings with actions to configure write permissions for Honeytoken deployment jobs Not checked yet Exposes incident tags in the All occurrences CSV report Not checked yet
2 details in Everything
Jira Cloud integration for secrets detection adds First detected date to incidents
Adds Jira Cloud integration support for real-time secret and honeytoken detection. Not checked yet Adds the First detected date field to incident details and the associated filter in the Secret incident dashboard. Not checked yet
2 details in Everything
GitGuardian SaaS enhances secrets detection capabilities with updated detectors and introduces automated honeytoken deployment jobs.
Secrets detection engine upgrade to version 2.106 Not checked yet Improvements to Generic Password, Generic High Entropy Secret, and Base64 Generic High Entropy Secret detectors Not checked yet Automated honeytoken deployment jobs for GitLab, GitHub, and GitHub Enterprise Server Not checked yet
3 details in Everything
Adds IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. shifting left metrics to analytics and improves Platform Check runs timeout transparency.
GitGuardian SaaS adds Square Token detector and configurable CSV export separators.
Adds Square Token detection engine (v2.105) Not checked yet Exporting CSV secret incidents now supports configurable separator (comma or tab) Not checked yet
2 details in Everything
GitGuardian SaaS adds Bunny.net and Hugging Face detectors; updates secrets engine to v2.104
└──▷ HOW TO FIND IT
Ensure Azure repository monitoring works correctly by updating the Personal Access Token scope.
📍 In your Azure DevOps organization settings, update the Personal Access Token used by GitGuardian to include the Graph:Read scope.
secrets detection engine upgrades to version 2.104, introducing new detection for Bunny.net API Key and Hugging Face user access token Not checked yet Platform SSO Platform SSO A macOS framework from Apple that lets identity providers hook into the operating system login flow, enabling enterprise single sign-on at the platform level rather than per-app. with Force SSO now enforces single sign-on single sign-on Single sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. for workspace owners as well as members Not checked yet Azure repos integration requires the Graph:Read scope in Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. for proper billing metrics functionality Not checked yet
3 details in Everything
GitGuardian SaaS upgrades secrets detection engine to v2.103 adding four new detectors.
Upgrades secrets detection engine to version 2.103 Not checked yet Adds detection for CircleCI Project Token Not checked yet Adds detection for Claude API Key Not checked yet Adds detection for Grafana Service Account Token With Host Not checked yet Adds detection for Klaviyo API Key Not checked yet
5 details in Everything
GitGuardian adds hsml_hash to API payloads, CSV columns for secret incidents, and Ignores IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. tag.
Adds hsml_hash field to the secret incident payload for Has My Secret Leaked integration Not checked yet Adds element_url and author_name columns to the secret occurrence CSV report Not checked yet Adds Ignored tag in IaC Security for ggshield-ignored incidents Not checked yet
3 details in Everything
GitGuardian adds Azure Repos integration for IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. misconfiguration monitoring and upgrades secrets detection engine.
Adds Azure Repos integration to the IaC Security feature for monitoring infrastructure-as-code misconfigurations Not checked yet Upgrades secrets detection engine to version 2.102, introducing 8 new detectors: Base64 AWS IAM AWS IAM AWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. Keys, Base64 AWS SES AWS SES Amazon's cloud email-sending service, used by cyber tools to deliver alerts, reports, or notifications without running their own mail infrastructure. Keys, Readme API Key, Tailscale API key, Tailscale oauth key, Tailscale pre-auth key, Tailscale SCIM SCIM A standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. key, and Tailscale webhook key Not checked yet
2 details in Everything
GitGuardian adds Azure Repos real-time monitoring, source-level criticality parameters, and Jira issue creation without assignees
Introduces a new parameter at the source level to prioritize Secret, SCA SCA Software composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. , and IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. incidents via source_criticality. Not checked yet Allows granting Members access to specific SCA and IaC incidents. Not checked yet Enables IP allow-listing for Honeytoken events to prevent triggering from specified IP ranges. Not checked yet Updates the Secrets detection engine (v2.101) adding the Airtable API Key v2 detector. Not checked yet
4 details in Everything
GitGuardian SaaS November 15 release adds Sourcegraph and Cohere detectors and CSV filter preservation.
└──▷ HOW TO FIND IT
Export incident reports filtered by a specific project or time range without manually re-filtering after download.
📍 In the Incidents view, apply your desired filters and click Export to CSV .
Detect Sourcegraph tokens in your codebase during CI checks now that detection is supported.
📍 Run your standard GitGuardian scan; the engine automatically applies new Sourcegraph Token and Cohere API Key detectors.
Upgrade secrets detection engine to version 2.100, adding support for Sourcegraph Token and Cohere API Key secret types. Not checked yet CSV export for incidents now preserves applied filters instead of exporting all results. Not checked yet GitHub integration checkruns updated to support the GitHub Merge Queue feature. Not checked yet
3 details in Everything
GitGuardian adds Source Criticality filtering for IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. and team-based filtering for incidents and perimeters
Adds a new Source Criticality field and filter to the IaC security incident view (IaC beta) Not checked yet
1 detail in Everything
New API for team secret incidents, restricted git patch visibility, and IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. remediation analytics in GitGuardian SaaS.
GET /api/team/{team_id}/incidents endpoint to retrieve secret incidents for a specific team Not checked yet New remediation analytics for IaC security (beta feature for testers) Not checked yet
2 details in Everything
GitGuardian SaaS v2.98 adds 4 new secret detectors and historical scan tooltip details.
Adds Aiven , Infracost API Key , Rollbar API Access Token , and Vercel to the secrets detection engine (v2.98) Not checked yet Displays scan duration, commit/branch counts, and failure reasons in historical scan status tooltips Not checked yet
2 details in Everything
Adds Publicly leaked tag to secret incidents exposed on public GitHub.
GitGuardian SaaS September 2023 release adds team-level alerting and incident occurrence limits
Imposes a limit of 1000 occurrences per incident in the Secrets detection engine to manage incident volume. Not checked yet Adds navigation links to the Get Started page within email notifications upon completion of the first scan. Not checked yet
2 details in Everything
GitGuardian SaaS introduces IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. Security monitoring, remediation, and new ggshield subcommands.
Adds ggshield pre-commit pre-commit An open-source framework for managing and running git hooks, maintained by the pre-commit project, that lets cyber tools enforce checks automatically on every commit before code reaches a repository. , pre-push, pre-receive, and ci subcommands for IaC security scanning Not checked yet Enables IaC monitoring and remediation features on the GitGuardian platform Not checked yet Upgrades secrets detection engine to version 2.96, adding Generic Terraform Variable Secret and CARTO API Access Token detectors Not checked yet
3 details in Everything
Workspace-level public sharing for incidents and new secret detectors via Databricks/Vault support
Secrets detection engine v2.95 adds Databricks Authentication Token With Hostname detector for secret identification. Not checked yet Secrets detection engine v2.95 adds Hashicorp Vault Token detector for secret identification. Not checked yet
2 details in Everything
GitGuardian SaaS adds four new secret detectors (Azure AD, Docusign, Pinecone) and renames the share modal.
Adds support for detecting Azure Active Directory Active Directory Microsoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. API Keys, Docusign API Key, and two variants of Pinecone API Key in the secrets detection engine. Not checked yet Moves the public sharing toggle to a renamed Share modal (previously Grant access ) for incident details. Not checked yet Adds an explanation tooltip to the Default branch tag in the Incidents view. Not checked yet
3 details in Everything
GitGuardian adds IP tagging rules for honeytokens and honeytoken label management API endpoints
Adds custom IP tagging rules for honeytoken events to assign tags based on source IP address Not checked yet Adds new API endpoints to manage labels for honeytokens Not checked yet Shows country flag next to the IP address in the honeytoken events table Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! Custom webhook v1 has been replaced by event-based custom webhooks
GitGuardian adds Default branch tag to secrets incidents, enforces PAT PAT A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. lifetime via API, and upgrades secret detection engine.
Adds the Default branch tag to secret incidents that occurred on the default git branch of a repository Not checked yet API endpoint enables managers of workspaces under the Business plan to enforce a maximum lifetime for personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. generated on their workspace Not checked yet Upgrades secrets detection engine to version 2.92 with two new detectors ( AWS SES AWS SES Amazon's cloud email-sending service, used by cyber tools to deliver alerts, reports, or notifications without running their own mail infrastructure. Keys , Forest Admin API Admin API A dedicated HTTP interface that exposes management and configuration operations separately from the data plane, letting cyber tools automate provisioning, policy changes, or monitoring without touching the main user-facing service. Key ) and improved coverage for six existing detectors Not checked yet
3 details in Everything
GitGuardian adds incident feedback forms, honeytoken management and new secret detectors
Incidents page now includes a standardized form for submitting remediation feedback. Not checked yet Adds publicly shared filter to the Incidents list. Not checked yet Business-only: Team owners with Member role can invite new users to the workspace when adding teammates. Not checked yet Business-only: Users with Full access incident permissions can invite new users to the workspace when granting access to an incident. Not checked yet Honeytoken settings page now supports managing labels directly. Not checked yet
+2 more
show less
Honeyton events can now be filtered by tags (AWS internal, GitGuardian Public Monitoring IP). Not checked yet Secrets detection engine upgraded to v2.91 with Tableau Personal Access Token and Yelp API key detectors. Not checked yet
7 details in Everything
May 30, 2023 release adds custom severity recomputation, new secret detectors, honeytoken search/notifications, and labels on honeytoken endpoints.
Custom severity rules option to recompute severity scoring manually Not checked yet ggshield now supports Palantir JWT and Figma Personal Access Token detection via Secrets detection engine v2.90 upgrade Not checked yet ggshield improves LDAP credentials detection via Secrets detection engine v2.90 upgrade Not checked yet Honeytoken list adds Created at column with sorting support Not checked yet Honeytokens can now be searched by ID Not checked yet
+2 more
show less
Email notification sent when a honeytoken is publicly exposed Not checked yet labels field added to honeytoken API endpoints Not checked yet
7 details in Everything
Customizable automated severity rules enabled by default on Free plan
automated severity scoring is now customizable via custom severity ruleset to maximize incident coverage. Not checked yet Automated severity scoring is activated by default for all workspaces under the Free plan. Not checked yet
2 details in Everything
GitGuardian SaaS adds five new secret detectors and exposes them via API in May 2023 release
Upgrades secrets detection engine to version 2.89 with five new detector types Not checked yet Exposes secret detection results in the API Not checked yet Activates automated severity scoring by default for new workspaces Not checked yet
3 details in Everything
Filepath search in secret incidents and Cloudinary/MongoDB detectors added
Adds filepath search to the free-text search field of the secret incidents table Not checked yet Upgrades secrets detection engine to v2.88 with new detectors for Cloudinary API keys and MongoDB Atlas Keys Not checked yet
2 details in Everything
GitGuardian SaaS April 3, 2023: Customizable remediation workflows, Keycloak detector, and new API endpoints.
remediation workflow is now 100% customizable with the removal of the final static step Not checked yet Keycloak Api Keys added as a new detection rule in secrets detection engine v2.87 Not checked yet New API endpoints for personal access tokenspersonal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. and service accounts management are available Not checked yet Secret incident payload now includes resolver_id and ignorer_id fields Not checked yet
4 details in Everything
Adds Jira integration and improved API error messages for missing scopes.
Introduces the new Jira alerting integration for sending findings to Jira projects Not checked yet Improves API token validation by specifying missing scopes in the error message when a token lacks required permissions Not checked yet
2 details in Everything
Adds a beta analytics page for monitoring IaC IaC Infrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. scanning usage and improves the display of historical scan status.
Adds event-based custom webhook integration and team description fields in GitGuardian SaaS
Adds a description field for teams, visible in the members table alongside the all-incidents team Not checked yet
1 detail in Everything
GitGuardian SaaS Nov 2022 adds external_id to sources API and increases historical scan size limit to 12GB.
Adds external_id field to the API source payload to represent the VCS VCS Version control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. id of a source Not checked yet Increases the maximum size of the historical scan from 1GB to 12GB for Business workspaces Not checked yet
2 details in Everything
GitGuardian SaaS adds Azure Repos beta integration and enhances analytics and webhooks.
Adds Azure Repos integration in beta upon request Not checked yet Updates the action field for custom webhooks with user-friendly messages Not checked yet Displays all ggshield modes in the Analytics section Not checked yet
3 details in Everything
GitGuardian SaaS adds team management with granular incident permissions and Auto-resolution playbooks
Introduces team management within a workspace for business workspaces with granular incident permissions: can view, can edit, and full access. Not checked yet Adds the Auto-resolution playbook to automatically close incidents that have once been valid and that become invalid. Not checked yet
2 details in Everything
GitGuardian SaaS adds new Member payload for webhooks and notifications on workspace removal
Custom webhook now includes a new Member payload for Grant/Remove access actions to track member lifecycle events Not checked yet Users who are removed from a Workspace now receive a notification Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! The resolve_reason field has been removed from all custom webhook payloads, potentially breaking integrations that rely on its presence
Members API adds retrieve and delete endpoints to enrich the Members section.
GitGuardian SaaS adds API filters for member search and role, plus invitations handling on access endpoints.
/members API endpoint now supports filtering by role and searching by name or email Not checked yet Features API handles invitations on grant/revoke access endpoints Not checked yet
2 details in Everything
Adds GDPR GDPR EU regulation enacted in 2018 that governs how organizations collect, store, and process personal data of EU residents, giving cyber tools legal obligations around data handling and breach notification. banner auto-reject with 6-month storage, unaffected counts in bulk actions, and audit log API filters
└──▷ TRY IT
Filter audit logs to only show events from a specific user or date range using the new query parameters.
copy
$ GET /audit-log?user_id=<USER_ID>&date_from=<DATE>&date_to=<DATE>
Closing the GDPR consent banner now automatically rejects consent and stores that decision for 6 months Not checked yet Incidents bulk actions now include the count of unaffected items Not checked yet API: The /audit-log list endpoint accepts new filter parameters Not checked yet
3 details in Everything
Adds audit_logs:read API scope and exposes tags on incidents for programmatic workflows.
Adds the audit_logs endpoint to the Features API, requiring the audit_logs:read scope for access Not checked yet Exposes tags in the incidents endpoint of the API, enabling filterable queries via tag Not checked yet Includes tags in CSV reports for secrets incidents for external analysis Not checked yet Makes repository names clickable links to filtered incident lists on the Perimeter page Not checked yet
4 details in Everything
└──▷ BREAKING ON UPGRADE
! The issue_id parameter is deprecated in favor of incident_id on incident note management endpoints
GitGuardian SaaS adds event-based custom webhook alerting and author filtering on the occurrences API endpoint
Custom webhook alerts are now event-based instead of static triggers Not checked yet The /occurrences API endpoint accepts author_name and author_info filter parameters Not checked yet
2 details in Everything
New API endpoints for invitation management and secret incident severity configuration.
Adds members:write scope to API keys for managing member invitations via new endpoints Not checked yet
1 detail in Everything
GitGuardian SaaS adds ggshield auth login, incident/role email notifications, CSV export enhancements, and deprecates old scan commands.
└──▷ USE IT
Authenticate the ggshield CLI for a new machine or environment reset.
shell
copy
ggshield auth login
Adds ggshield auth login command to simplify credential configuration for the CLI tool. Not checked yet Sends an email notification to Restricted users when they are granted access to an incident. Not checked yet Sends an email notification to members when their role is updated. Not checked yet Adds status, ignore_reason, and status_revoked columns to the CSV export of secret incidents. Not checked yet Adds occurrence_id column to the CSV export of occurrences. Not checked yet
+1 more
show less
Returns dates in ISO ISO A widely adopted international standards body that publishes technical specifications; cyber tools cite ISO standards to signal compliance with recognized benchmarks for quality, security, or interoperability. format in all CSV exports. Not checked yet
6 details in Everything
└──▷ BREAKING ON UPGRADE
! The ggshield scan command is deprecated; use ggshield secret scan instead.! The ggshield ignore command is deprecated; use ggshield secret ignore instead.
Exposes base/head branch data for GitHub pull requests and marks rewrite git history as optional.
Allows users to mark the rewrite git history remediation step as optional Not checked yet
1 detail in Everything
GitGuardian April 4, 2022 release adds repository state to incidents and Personal Access Token monitoring for Managers.
Display repository state (unmonitored or deleted) on incidents list and incident detail pages Not checked yet Adapt API to be compatible with personal access tokens personal access tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. Not checked yet Managers can monitor the Personal access tokens access tokens A credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. created on the workspace in the API section Not checked yet
3 details in Everything
GitGuardian adds PATs PATs A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. , service account audit logs, incident member API, new API pages, and check run limits.
Introduces Personal Access Tokens Personal Access Tokens A personal access token, a credential used by scripts and integrations instead of a user's password. Its permissions and expiry depend on the service issuing it. as a new type of API key for the Features API. Not checked yet Adds an Audit Log for Service Account actions. Not checked yet Adds a new endpoint to list workspace members having access to an incident. Not checked yet Makes Quota, Service Account, and Secrets detection playground pages available in the API section. Not checked yet
4 details in Everything
Adds automatic scanning for Bitbucket repositories upon integration
New workspace members API endpoint, enhanced Source payload fields with filtering, and incident-based user invitation.
Adds GET /api/v1/workspaces/{id}/members endpoint to list workspace members Not checked yet Extends the Source payload with health, last_scan, open_incidents_count, and closed_incidents_count fields Not checked yet Adds health and last_scan query parameters to filter sources in the API Not checked yet Allows inviting new Restricted users directly from an incident UI Not checked yet
4 details in Everything
GitGuardian adds last scan status filtering, detector incident counts, custom detector questions, and GitHub check run linking.
Perimeter UI gains filtering by last scan status Not checked yet Detector table now shows the number of secret incidents for each detector Not checked yet Custom detectors allow adding questions in the Additional notes placeholder Not checked yet Business plan users can extend the secrets detection engine with organization-specific secrets via Custom detectors Not checked yet GitGuardian incidents are now linked to GitHub check runs Not checked yet
5 details in Everything
Adds filtering/sorting to members table, bulk actions for Restricted users on incidents, and detector type display.
Adds filtering and sorting controls to the Members and Invitations tables Not checked yet Displays the detector type (generic/specific) in the Detectors table Not checked yet
2 details in Everything
Integrations list sorted alphabetically by default; incident detail sidebar scrolling improved.
Sorts Integrations sources alphabetically by default in the UI Not checked yet Improves the right sidebar scrolling behavior in Incident detail Not checked yet
2 details in Everything
Adds Regression setting for incident handling and fixes analytics display.
Add the Regression setting in Features Settings to control whether reoccurrences reopen resolved incidents Not checked yet Display deleted sources in the Top 5 sources Analytics panel Not checked yet
2 details in Everything
Secret validity in Features API and new grant/revoke access endpoints
Adds secret validity information to the Features API response payload for each detected secret. Not checked yet Introduces new API endpoints /incidents/{id}/grant-access and /incidents/{id}/revoke-access for managing incident permissions. Not checked yet Updates custom webhook payloads to include validity and severity fields for incidents. Not checked yet
3 details in Everything
New audit log search by incident ID, bulk scan cancellation, and GitHub check run comments.
Audit log now supports filtering by incident_id and event_name to locate specific security events Not checked yet Adds bulk secret scanning secret scanning Checking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. cancellation endpoint allowing administrators to abort multiple ongoing historical scans simultaneously Not checked yet GitHub integration posts secret detection results as comments directly on the pull request timeline via check runs Not checked yet GitLab group hook integration now supports the token_edition parameter for token management Not checked yet
4 details in Everything
GitGuardian adds Restricted role, auto-access playbook, incident sharing API, audit log for check runs, and GitLab multi-group support.
Adds the Restricted role to the RBAC RBAC Role-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. model for tighter access control Not checked yet Introduces an Auto-access granting playbook to automate permission assignments Not checked yet Adds a new API endpoint for sharing and unsharing incidents programmatically Not checked yet Adds an audit log for check runs settings to track configuration changes Not checked yet Enables GitLab.com integration with support for multiple GitLab groups Not checked yet
5 details in Everything
GitGuardian SaaS adds secret validity checks for incidents and presence data to CSV reports and API payloads.
Introduction of validity checks for secret incidents Not checked yet Manual triggering of validity checks for secret incidents Not checked yet Adds presence information to incidents in the CSV report and the API occurrence payload Not checked yet
3 details in Everything
GitGuardian SaaS adds manual secret presence checks and new API search/filtering capabilities.
Adds manual triggering of secret presence checks to verify if a secret still appears in the repository. Not checked yet
1 detail in Everything
GitHub Checkrun customization, multi-GitHub Enterprise support, dedicated historical scan queue, and Bitbucket search filter coverage
GitHub Checkruns now allow customization of the message and final status (fail or neutral). Not checked yet Integrations can now connect several GitHub Enterprise Server instances. Not checked yet Business workspaces have a dedicated queue for historical scanning. Not checked yet Incidents search filters now support Bitbucket repositories. Not checked yet
4 details in Everything
GitGuardian SaaS July 27, 2021 adds Docker integration and TTL TTL Time to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. support for shared incident links.
Adds docker integration to the platform. Not checked yet Adds TTL (Time To Live) expiration to share incident links. Not checked yet
2 details in Everything
New API data management scopes, GitHub dangling installation linking, and onboarding todo list.
Adds data_management scopes to the API key configuration for finer-grained access control Not checked yet Enables linking a dangling GitHub App installation to a workspace via the UI or direct app install Not checked yet Introduces an onboarding todo list to guide new users through initial setup steps Not checked yet
3 details in Everything
Adds analytics panel for shift-left visualization and ggshield configuration instructions; enforces 20MB API limit.
Add Features Analytics panel to visualize shift left efforts. Not checked yet Add instruction page on how to configure ggshield with each CI/CD tool. Not checked yet API now respects the 20MB limit. Not checked yet
3 details in Everything
GitGuardian introduces incident severity and new workspace incidents API endpoints.
Adds severity field to incidents for easier triaging Not checked yet Implements GET /workspaces/{workspace_id}/incidents endpoint Not checked yet Implements GET /workspaces/{workspace_id}/sources endpoint Not checked yet
3 details in Everything
GitGuardian SaaS adds filepath exclusions, workspace email settings, incident assignee filtering, bulk notes, CI/CD for Drone/Azure, and closed perimeter links
Adds the ability to configure and test a filepath exclusion list to stop monitoring specific paths Not checked yet Allows users to customize email notifications for each individual workspace via settings Not checked yet Adds assignee visibility and filtering in the incidents table for closed incidents Not checked yet Introduces quick action buttons (resolve/ignore/reopen/assign) directly in the incident table row Not checked yet Adds a bulk action add note for selecting multiple incidents at once Not checked yet
+3 more
show less
Updates the how to remediate section with detailed indications and blog links Not checked yet Adds a link to the incidents page for closed incidents within the Perimeter view Not checked yet Extends CI/CD support to include Drone.io and Azure Pipelines Not checked yet
8 details in Everything
GitGuardian adds Auto-healing playbook for secret incidents with developer share links and feedback filters.
Introduces Auto-healing playbook to automatically send incident share links to developers involved in a secret incident Not checked yet Adds developer feedback filter to the incidents table along with icons indicating feedback status Not checked yet Enables resolve/ignore actions directly on the share page for incident shares Not checked yet Updates CSV reports for secret incidents to respect current table filters and search results Not checked yet
4 details in Everything
GitGuardian SaaS adds Pagerduty/Discord/Splunk alerting, GGShield integration page, and cancelable historical scans
Add Pagerduty , Discord , and Splunk integrations to the alerting configuration for immediate notification of secrets findings Not checked yet Display ggshield (git hook, CI/CD) integrations on the central integrations page for unified management of developer tooling Not checked yet Add ability to cancel a running historical scan from the UI to reclaim compute resources Not checked yet
3 details in Everything
GitGuardian introduces Analytics section and incident sharing capabilities
Adds Analytics section for workspace metrics monitoring Not checked yet
1 detail in Everything
GitGuardian SaaS adds Bitbucket Data Center integration, Workspace Audit Log, Incident bulk actions, and Viewer role.
Adds Bitbucket Data Center support for secrets detection monitoring Not checked yet Introduces an Audit log section in settings for centralized user activity tracking Not checked yet Enables bulk actions (resolve, ignore, assign) on Incidents Not checked yet Adds a Viewer role with read-only access to all incidents Not checked yet
4 details in Everything