https://cybertoolchain.io/tools/gitguardian-saas New releases and features in GitGuardian SaaS, tracked by The Cyber Toolchain. en Fri, 30 Oct 2026 07:57:50 GMT https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 30 Oct 2026 07:57:50 GMT GitGuardian adds API endpoints to retrieve occurrence content in clear text, manage NHI policies, and trigger on-demand secret validity checks⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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 (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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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. • Retrieve a single NHI policy and its `incident_mode` and `is_incident_mode_fixed` fields via `GET /v1/nhi/policies/{policy_name}`. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Thu, 29 Oct 2026 07:55:04 GMT GitGuardian adds Docker Hub public monitoring, a `--background` scan mode, and a local machine dashboard with Codex and opencode redaction⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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. • 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. • 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. • Honeytoken planting is now supported on Windows endpoints. • Scans now skip additional folders of downloaded or generated files, including `pip-*`, `pytest-of-*`, and `_MEI*` temp leftovers, NuGet and Scoop package caches, and Electron app caches. Breaking changes: • Validity checks no longer read custom hosts from environment variables or local config files; custom hosts are now sourced exclusively from your GitGuardian workspace. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/10/29/changelog https://docs.gitguardian.com/releases/saas/2026/10/29/changelog Thu, 29 Oct 2026 00:00:00 GMT GitGuardian adds automatic GitHub team sync, multi-header custom webhooks, new Public API endpoints, and scoped Endpoint Protection auth⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Add a custom webhook integration that now accepts multiple custom headers (such as bearer tokens or routing headers) per webhook, configured from its settings page.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Unlink a ticket from an incident using a new Public API endpoint. • 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. • 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. • 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'. • 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. Breaking changes: • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/10/27/changelog https://docs.gitguardian.com/releases/saas/2026/10/27/changelog Tue, 27 Oct 2026 00:00:00 GMT GitGuardian Endpoint Protection gains background scanning, an Overview dashboard, Codex/opencode redaction, and validity checks for 501 secret types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `scan.resources.background.mode: auto` to `machine_scan.yaml` to make background-priority scanning the default for every scan. • 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. • Enables redaction of Codex and opencode history from the local dashboard, including their SQLite history databases. • Expands validity checks to 501 secret types (up from 432), adding coverage for Elastic, Datadog, Langfuse, Sumo Logic, Gitea, and Azure Container Registry. • Suppresses findings from VS Code, Cursor, VSCodium, Windsurf, and JetBrains IDE editor-history copies unless the secret in them is valid, reducing duplicate noise. • Expands folder exclusions to skip build leftovers (`pip-*`, `pytest-of-*`, `_MEI*`), Windows package caches (NuGet, Scoop), and Electron app caches, while still scanning credential-holding folders. Breaking changes: • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 23 Oct 2026 11:29:58 GMT GitGuardian adds NHI Identity and Source APIs plus ticket-unlinking endpoint for secrets and honeytokens.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `GET /v1/nhi/identities` to list non-human identities (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`. • Adds `GET /v1/nhi/identities/{identity_id}` to retrieve a single non-human identity with its permissions and a summary of its secrets. • 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. • 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`. • Adds `full_path` query parameter to NHI Sources endpoint for exact, case-sensitive source lookup, preferred over free-text search for single-source retrieval. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/10/21/changelog https://docs.gitguardian.com/releases/saas/2026/10/21/changelog Wed, 21 Oct 2026 00:00:00 GMT 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Routes Docker Hub incidents through existing notifications, integrations, and agents analysis, matching the workflow for GitHub incidents. • 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. • Extends Honeytoken planting support to Windows endpoints. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Tue, 20 Oct 2026 08:07:54 GMT GitGuardian adds API endpoints to list and skip GitHub Check Runs that block pull requests⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Tue, 20 Oct 2026 07:55:12 GMT 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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-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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Surfaces validity results in the NHI 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. • Adds a built-in `Valid` saved view to the Endpoint Protection discovered secrets page, listing all secrets currently checked as valid. • 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. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 16 Oct 2026 08:29:57 GMT GitGuardian adds NHI identity owner management endpoints for reading and updating ownership of non-human identities.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `GET /v1/nhi/identities/{identity_id}/owners` endpoint to list owners of a non-human identity.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `POST /v1/nhi/identities/{identity_id}/owners` endpoint to assign owners to a non-human identity. • Adds `POST /v1/nhi/identities/{identity_id}/owners/update` endpoint to update ownership records for a non-human identity. • Adds `GET /v1/nhi/identities/{identity_id}/owners/{owner_id}` endpoint to retrieve a specific owner of a non-human identity. • Adds `DELETE /v1/nhi/identities/{identity_id}/owners/{owner_id}` endpoint to remove a specific owner from a non-human identity. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/10/15/changelog https://docs.gitguardian.com/releases/saas/2026/10/15/changelog Thu, 15 Oct 2026 00:00:00 GMT ggscout 0.34.1 checks validity and permissions of vaulted secrets in-network, surfacing live verdicts in the NHI inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `[check] enabled = false` config key to opt out of in-network validity and permissions checks per ggscout deployment.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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 → Identities inventory. • Merges validity verdicts from vaulted or Kubernetes secrets with any matching secret incident, always keeping the most recent verdict. • Adds a built-in 'Valid' saved view on the Endpoint Protection discovered secrets page, available to all users. • Documents all API token permissions in the public API documentation, including eleven previously granted but undocumented permissions. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/10/09/changelog https://docs.gitguardian.com/releases/saas/2026/10/09/changelog Fri, 09 Oct 2026 00:00:00 GMT GitGuardian adds Harbor container registry scanning, bringing secrets detection to a seventh registry with full layer and metadata coverage.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds Harbor container registry as a new secrets-scanning source, covering all layers of tagged images (including multi-architecture platforms), Dockerfiles, and environment variables in image metadata.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Supports scanning Harbor instances not reachable from the internet via GitGuardian Bridge. • Uses a Harbor robot account with Repository (List, Pull) and Artifact (List, Read) permissions only — read-only, scoped, and revocable at any time. • Allows selecting specific Harbor repositories or monitoring the entire instance with automatic inclusion of new repositories. • Performs both historical scanning of existing images and incremental scanning of newly pushed images. • Flags unhealthy installations (expired robot accounts, lost permissions, or unreachable instances) and supports rotating the robot account secret without reinstalling. • Navigate to `Settings > Integrations > Sources` and click `Install` next to Harbor in the `Container registries` section to configure the integration. • Expands GitGuardian container registry coverage to seven registries, adding Harbor alongside Docker Hub, Amazon ECR, Azure Container Registry, Google Artifact Registry, JFrog Container Registry, and Red Hat Quay. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Mon, 05 Oct 2026 08:18:35 GMT GitGuardian SaaS: Introduces NHI Governance — NHI Identity Owners API group — enabling programmatic ownership management of non-human identities via scopes `nhi:ownership:read` and `nhi:ownership:write`. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Mon, 05 Oct 2026 07:56:28 GMT Breaking changes: • The `Health` filter on the perimeter sources table is replaced by `Has open incidents`; existing saved views are migrated automatically. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sun, 04 Oct 2026 14:00:18 GMT GitGuardian SaaS: Adds `POST /v1/secret-observability/identities/{identity_id}/owners` to add up to 5 owners (by email) to a non-human identity without removing existing ones. • Introduces NHI Governance / 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). Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Sun, 04 Oct 2026 07:49:53 GMT GitGuardian SaaS: Replaces the `Health` filter on the perimeter page with a `Has open incidents` filter; saved views are migrated. Breaking changes: • The `Health` filter on the perimeter sources table is replaced by the `Has open incidents` filter; saved views are migrated automatically. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sat, 03 Oct 2026 13:07:40 GMT GitGuardian API adds NHI identity owner management, presence-check endpoints, and source monitoring status filters for secret incidents.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `POST /v1/public-incidents/secrets/{incident_id}/check-presence` to trigger an asynchronous presence check on a public secret incident. • 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). • 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. • 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. • 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. • 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. • Adds `source_monitoring_status__nin` query parameter to exclude secret incidents where all sources fall within the specified monitoring status buckets (e.g. `archived`). • 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`). • Introduces NHI Governance and NHI Identity Owners as a new API surface area under `/v1/secret-observability/identities`, with `nhi:ownership:read` and `nhi:ownership:write` scopes. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Sat, 03 Oct 2026 12:54:17 GMT GitGuardian adds Wiz secret-findings integration, Coverage Hub, AI hook expansion to Kiro/Junie, and configurable API timeout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `api_timeout` config key and `GITGUARDIAN_API_TIMEOUT` environment variable to override the previously fixed 60-second API timeout for large scans.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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 hash of the secret — never the raw value. • 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. • 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. • 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. • 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`. • Adds a new Public Monitoring agents page showing how agents classified incidents as Related, Unclear, or Not related, with counts linking to matching incidents. • Extends the `secret value` and `validity` API endpoints to cover secrets found through Public Monitoring, not only Internal Monitoring. • Adds optional author attribution for leaks detected through custom sources (BYOS), allowing an author email to be provided and returned when leaks are found. • Introduces a per-account setting to keep team access to unmonitored sources and their existing incidents instead of removing them from team perimeters. • Introduces a per-account setting to automatically remove archived sources from team perimeters. • 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. • 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. Breaking changes: • The `Health` filter on the perimeter sources table is replaced by `Has open incidents`; saved views using the old filter are migrated automatically. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/09/30/changelog https://docs.gitguardian.com/releases/saas/2026/09/30/changelog Wed, 30 Sep 2026 00:00:00 GMT GitGuardian now pushes secret incidents to Wiz as native findings, with SHA-256-hashed context and auto-closing sync.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Transfers only a SHA-256 hash of the secret and its metadata to Wiz — the raw secret value never leaves GitGuardian. • Maps GitGuardian incident severity directly to the Wiz finding severity, so a critical secret appears as critical in both platforms. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Tue, 29 Sep 2026 14:36:39 GMT GitGuardian API gains occurrence content retrieval and scan list/poll endpoints for secrets and audit workflows.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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 with `read:incident` and `secrets:read` scopes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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. • 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) to efficiently poll only scans still running or updated since a given instant, sorted by `-gg_created_at` by default. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/09/28/changelog https://docs.gitguardian.com/releases/saas/2026/09/28/changelog Mon, 28 Sep 2026 00:00:00 GMT GitGuardian's new Coverage Hub surfaces unmonitored, unscanned, and unowned sources on the perimeter page with one-click remediation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds card actions that filter the sources table to sources needing action — unmonitored, unscanned, or unassigned — in one click. • 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. • Adds a `Teams` column to the perimeter sources table showing the teams assigned to each source. • Adds a `No team assigned` option to the Team filter to surface sources without an owner. • Replaces the `Health` filter with `Has open incidents` on the perimeter page, with saved views migrated automatically. • Sorts the perimeter sources table by open incidents by default, prioritising sources at risk. • 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. Breaking changes: • The `Health` filter on the perimeter page is replaced by `Has open incidents`; saved views using the old filter are migrated automatically. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sat, 26 Sep 2026 12:59:06 GMT 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 25 Sep 2026 13:25:50 GMT GitGuardian API adds detector custom hosts endpoint and live historical-scan progress polling⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • 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`. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 25 Sep 2026 08:03:53 GMT Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/09/25/changelog https://docs.gitguardian.com/releases/saas/2026/09/25/changelog Fri, 25 Sep 2026 00:00:00 GMT AI Hooks now withhold tool output from Claude Code, Codex, and Mistral Vibe, and extend coverage to Kiro and Junie CLI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `api_timeout` config key and `GITGUARDIAN_API_TIMEOUT` environment variable to override the previously fixed 60-second API timeout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `ggshield machine setup` subcommand to register AI Hooks for Kiro and Junie CLI in one step. • 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. • Extends AI Hooks and the AI agents/MCP inventory to cover Amazon Kiro (IDE and CLI) and Junie CLI, blocking secrets in commands and file reads. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Thu, 24 Sep 2026 13:20:35 GMT GitGuardian adds GET /v1/detector-custom-hosts to list workspace-level custom hosts grouped by secret detector.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `GET /v1/detector-custom-hosts` endpoint to list all custom hosts configured on the workspace, grouped by secret detector, including each detector's `checker_default_base_url` and `custom_hosts[].base_url` values — only detectors that support custom hosts are returned.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Wed, 23 Sep 2026 13:25:55 GMT Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Tue, 22 Sep 2026 13:07:40 GMT Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Mon, 21 Sep 2026 14:40:56 GMT GitGuardian API adds GET /v1/detector-custom-hosts to list workspace custom hosts grouped by secret detector.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `GET /v1/detector-custom-hosts` endpoint to list all custom hosts configured on a workspace, grouped by secret detector (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ `gitlab_token`), returning each detector's `checker_default_base_url` alongside any configured `custom_hosts` `base_url` entries. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Mon, 14 Sep 2026 07:51:17 GMT GitGuardian SaaS: Extends team read and write endpoints to accept `secrets:read` and `secrets:write` scoped API keys, supporting both personal access tokens and service account tokens. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sun, 13 Sep 2026 14:52:42 GMT GitGuardian API adds `external_provider_type` field with Okta support for team management endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `external_provider_type` field (supporting `"okta"` as a valid value) to team-related API responses and requests, enabling identity-provider-aware team management via the API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sat, 12 Sep 2026 13:33:31 GMT 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 associated with a team.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 11 Sep 2026 14:51:20 GMT 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Thu, 10 Sep 2026 14:51:40 GMT GitGuardian API adds `external_provider_type` field with Okta support for team management endpoints.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ • Adds `external_provider_type` field (with supported value `okta`) to team-related API endpoints, enabling teams to be associated with an external identity provider.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Tue, 08 Sep 2026 12:21:35 GMT GitGuardian adds AI agent/MCP secret blocking and vault secret classification via ggshield 1.54.0 and ggscout 0.32.0 • Adds AI Hooks to block secrets at prompt submission, pre-tool use, and post-tool use for Codex and Mistral Vibe, alongside existing Claude Code, Cursor, Copilot CLI, and VS Code coverage. • Runs the Secrets Detection Engine on every value ggscout collects, classifying vaulted secrets against 550+ detectors including multi-match detectors. • Adds `detector`, `detector type`, `secret family`, `secret category`, and `secret provider` filters and sort options to the NHI inventory. • Groups multi-match credentials (e.g. PostgreSQL username, password, host, and port) as a single inventory entry rather than separate fields. • Labels unmatched secrets as `Unknown` in the inventory so they remain visible and filterable without being dropped. • Adds per-team incident permission controls when promoting a user to Member, including bulk application and post-promotion editing of team rights. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/09/07/changelog https://docs.gitguardian.com/releases/saas/2026/09/07/changelog Mon, 07 Sep 2026 00:00:00 GMT GitGuardian adds AI agent/MCP inventory and `ggshield machine setup` to block secrets leaking through AI coding tools. • Adds `ggshield machine setup` command to configure AI Hooks and git hooks for every detected AI agent on a machine in a single step. • Adds `--history` flag to `ggshield ai discover` to parse MCP tool calls from agent transcripts for post-compromise investigation. • Adds AI Hooks coverage for Codex and Mistral Vibe, joining Claude Code, Cursor, Copilot CLI, and VS Code — scanning prompt submission, pre-tool use, and post-tool use, and blocking with a named secret and remediation hint. • 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. • Adds automatic removal of remotely-deleted sources from team perimeters via a new workspace setting, while keeping them accessible to workspace managers. • AWS access keys stored in a secret manager or Kubernetes now link to their IAM identity by `AccessKeyId`, showing permissions of the stored key in the NHI Governance exploration map. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/09/04/changelog https://docs.gitguardian.com/releases/saas/2026/09/04/changelog Fri, 04 Sep 2026 00:00:00 GMT GitGuardian runs its 550+ Secrets Detection Engine on vaulted secrets, with detector/family/category/provider filters in NHI Governance. • 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. • 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. • 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. • Labels unmatched secrets as 'Unknown' in the inventory so they remain visible and can be excluded without being dropped entirely. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Mon, 31 Aug 2026 07:40:55 GMT GitGuardian adds AI-agent verdicts on public leaks, AWS S3 bucket scanning, and auto-monitoring for Jira, Confluence, and Teams. • 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. • 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. • 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. • 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. • 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. • 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. • Adds SSO/SCIM sign-in support when the identity provider does not supply first and last name, deriving these values from the user's email address. Breaking changes: • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Fri, 28 Aug 2026 19:49:51 GMT 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). • 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 repositories). • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/08/25/changelog https://docs.gitguardian.com/releases/saas/2026/08/25/changelog Tue, 25 Aug 2026 00:00:00 GMT GitGuardian can now scan AWS S3 buckets for secrets, including inside archives, using OIDC role assumption with no long-lived keys. • 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. • Opens and scans inside archives (e.g. `tar.gz`) found in S3 objects, so secrets buried in compressed backups still surface as incidents. • Connects via OIDC — GitGuardian assumes a read-only IAM role you create and scope in your own AWS account, with no long-lived AWS keys required. • Lets you select individual buckets to monitor and assign them to teams, the same way any other source is managed in the integration settings. • 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. • Incidents found in S3 objects carry the same severity ratings, validity status, playbooks, and notifications as code-repository incidents. • Historical (on-demand) scans are available now; recurrent scanning of new and modified objects is coming soon. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Sun, 16 Aug 2026 09:31:25 GMT GitGuardian API adds three new endpoints: secret-location listing by incident or source, and live scan progress polling. • 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`. • 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. • 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`. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Sun, 16 Aug 2026 08:54:16 GMT GitGuardian adds custom secret validity via API, honeytoken endpoint protection, and programmatic PAT/SAT token creation. • New API endpoint lets teams push their own validity status (`valid` or `invalid`) for secrets on unreachable internal systems, using a personal access token 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. • 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. • New `Honeytoken protection` card in the Endpoints dashboard reports fleet coverage percentage and lists unprotected endpoints. • Adds ability to create Personal Access Tokens (PATs) and Service Account Tokens (SATs) programmatically via the API for automated token rotation workflows; tokens created via the API must have a finite TTL. • Scans triggered via a Personal Access Token now emit an audit log event. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/08/14/changelog https://docs.gitguardian.com/releases/saas/2026/08/14/changelog Fri, 14 Aug 2026 00:00:00 GMT 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 with the `secrets:write` scope. • 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. • The custom validity status applies to the secret itself, so every incident tied to that secret reflects the status. • Public API now supports setting the 'Only use detectors with validators' option when creating or updating custom sources, enabling fully automated source configuration. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Wed, 12 Aug 2026 10:30:25 GMT GitGuardian adds `use_only_detectors_with_validators` to custom source APIs, filtering scans to only secrets with validity checks. • Adds `use_only_detectors_with_validators` field to custom source create and update endpoints — when `true`, scans of that source retain only secrets whose detector supports validity checks; defaults to `false` on creation, omit to leave unchanged on update. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/08/10/changelog https://docs.gitguardian.com/releases/saas/2026/08/10/changelog Mon, 10 Aug 2026 00:00:00 GMT GitGuardian adds honeytoken-based endpoint intrusion detection via `ggshield honeytoken plant`, plus API-based PAT/SAT creation. • New `ggshield honeytoken plant` command plants a decoy AWS credential on developer endpoints to detect credential-stealing malware the moment it reads the file. • New 'Honeytoken protection' card in the Endpoints dashboard reports fleet-wide coverage percentage and lists endpoints not yet protected. • Adds Public API endpoints to create Personal Access Tokens (PATs) and Service Account Tokens (SATs) programmatically, enabling automated token rotation workflows; tokens created via the API must have a finite TTL. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://api.gitguardian.com/docs https://api.gitguardian.com/docs Wed, 05 Aug 2026 11:27:42 GMT GitGuardian API gains a token-creation endpoint that lets personal access tokens 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. • 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. • 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. • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Fri, 31 Jul 2026 16:20:25 GMT GitGuardian adds a dedicated GitHub Check Runs dashboard page, bulk perimeter actions, and Bitbucket source health management. • 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. • Fine-grained GitHub personal access tokens can now be used to monitor private members of a GitHub organization (previously only classic tokens were supported). • Customizable column display on the perimeter table lets users surface the source attributes most relevant to their workflow. • 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. • Historical scans now have a dedicated tab on the perimeter page for tracking past and in-progress scan statuses in one place. Breaking changes: • The 'Display as Tree' view has been removed from integration source pages; only the 'Display as List' view remains. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/07/28/changelog https://docs.gitguardian.com/releases/saas/2026/07/28/changelog Tue, 28 Jul 2026 00:00:00 GMT GitGuardian adds a dedicated GitHub Check Runs dashboard page with filtering, KPIs, re-run controls, and incident linking. • 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. • Filter and search check runs by repository, status, or date — including workspaces with hundreds of thousands of runs. • KPI strip at the top of the Check Runs page summarizes activity to surface failures and trends at a glance. • Re-run or skip a check run directly from the dashboard without switching to GitHub. • Navigate from a check run directly to linked incidents when secrets are detected, enabling faster remediation. • Fine-grained GitHub personal access tokens can now be used to monitor private members of a GitHub organization in the Public Perimeter (previously limited to classic tokens). • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas https://docs.gitguardian.com/releases/saas Thu, 23 Jul 2026 16:01:31 GMT • 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. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/07/20/changelog https://docs.gitguardian.com/releases/saas/2026/07/20/changelog Mon, 20 Jul 2026 00:00:00 GMT GitGuardian adds @mention notifications in incident notes, source health for new integrations, and oversized PR scanning on Business plan. • 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. • Extends source health management (auto-pause, auto-resume, and recovery guidance) to ServiceNow, JFrog Container Registry, JFrog Package Registry, and Microsoft OneDrive sources. • Introduces per-source status indicators (Monitored, Unmonitored, Unreachable, Archived, Deleted) on the perimeter page and incident list, with filterability and saveable views. • 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. • Adds opt-in 'use only detectors with validators' option for Custom Source (BYOS) installs, dropping unverifiable matches before validity checks to reduce noise. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas https://docs.gitguardian.com/releases/saas/2026/07/08/changelog https://docs.gitguardian.com/releases/saas/2026/07/08/changelog Tue, 07 Jul 2026 00:00:00 GMT GitGuardian extends Generic Password and High Entropy Secret detection to Confluence, Jira, Slack, and Teams — with AI false-positive filtering built in. • 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. • Extends the False Positive Remover (LLM-based model) to non-code source findings, automatically tagging 25–40% of generic findings as false positives before they surface in the dashboard. • Adds remediation guidance content and detector-specific links as assignable metadata fields in the Jira Notifier integration ticket description template. Full history on Cyber Toolchain: https://cybertoolchain.io/tools/gitguardian-saas