Skip to main content

3 posts tagged with "automation"

View All Tags

2025.7 - Required

Versioncalendar icon Release Date
2025.7.0July 25, 2025
2025.7.1August 8, 2025

System Requirements Update

Ensure your infrastructure meets the latest requirements for optimal performance and security:

ComponentMinimum VersionRecommended Version
KOTS1.117.3Latest
Kubernetes1.28 ⚠️1.32
PostgreSQL1516
Redis67
ggscout0.16.6Latest

Helm & Upgrade Considerations

To ensure compatibility, please review Helm values updates from the previous version. Air gap deployment? Find all the images and tag names in the air gap install page.

⚠️ Important: This is a required release and cannot be skipped.

Upgrading to 2025.7

Machine Learning engine is now enabled by default. Ensure your infrastructure meets the ML requirements.

If you're concerned about resource usage, you can lower the priority of ML pods to ensure other critical services are scheduled first.

Feature highlights

  • Jira and Confluence Data Center historical scanning — scan past content for secrets. Learn more
  • Auto-ignore invalid incidents playbook — automatically clear confirmed invalid secrets. Learn more

Secrets Detection Engine

  • v2.141 — 12 new detectors (Kubernetes User Certificate with Port, NVIDIA, Alchemy v2, OpenRouter, Duffel, Apify, Jina, Deno Account, Segment Workspace v2, Resend, VKontakte, Fireworks AI), 6 improved, 10 new checkers.
  • v2.142 — 2 new detectors (AI71, AMP), 9 improved (Kubernetes Docker, MySQL, Sourcegraph, GitHub, HashiCorp Vault, Confluent, GitHub Fine-Grained PAT, Slack, DigitalOcean Spaces), 2 new checkers.
  • v2.143 — 7 new detectors (GitLab Incoming Mail, Coze PAT, Tavus, Heroku Platform, SSH with port, Tableau Cloud PAT, Notion v2), 7 improved, 6 new checkers. All JWT detectors now only catch signed JWTs.

Enhancements

  • Custom tags API key/value filtering, auto-resolve revoked secrets playbook, custom remediation links. See SaaS release: Jun 19.
  • Jira DC leaker emails. See SaaS release: Jun 30.
  • Custom tags API documentation. See SaaS release: Jul 21.
  • GitLab multi-hook support. See SaaS release: Jul 23.

Fixes

  • Custom tags bulk assignment, Azure DevOps token handling. See SaaS release: Jun 19.
  • GitHub installation checks. See SaaS release: Jun 30.
  • Teams email notifications. See SaaS release: Jul 7.
  • SCIM case-insensitive emails. See SaaS release: Jul 21.
  • Deletion line scanning. See SaaS release: Jul 28.

Hotfixes

2025.7.1

calendar icon   Release Date: August 8, 2025

Fixes

  • Self-Hosted:
    • Embedded Cluster with Embedded Redis configuration to use bitnamilegacy/redis registry following Bitnami's registry changes.
    • ML Secret Engine updated to version 20250806 fixing critical CVE-2025-54381.
    • NHI Scout bumped to version 0.18.2.

2025.6

Versioncalendar icon Release Date
2025.6.0June 20, 2025

System Requirements Update

Ensure your infrastructure meets the latest requirements for optimal performance and security:

ComponentMinimum VersionRecommended Version
KOTS1.117.3Latest
Kubernetes1.28 ⚠️1.32
PostgreSQL1516
Redis67
ggscout0.16.6Latest

Helm & Upgrade Considerations

To ensure compatibility, please review Helm values updates from the previous version. Air gap deployment? Find all the images and tag names in the air gap install page.

Upgrading to 2025.6 Kubernetes Support

GitGuardian 2025.6 now requires Kubernetes 1.28 as the minimum supported version. However, Kubernetes 1.28 is no longer receiving active or maintenance support from the Kubernetes project (see end-of-life schedule).

We strongly recommend upgrading to Kubernetes 1.32 for optimal security and stability. See our system requirements for more details.

Feature highlights

  • Secure API access to secret values — retrieve secret values via API endpoint for automation workflows. Learn more
  • Microsoft Teams secret detection — scan Teams messages for hardcoded secrets with real-time and historical scanning. Learn more
  • Jira and Confluence Cloud historical scanning — detect secrets leaked in the past across Jira and Confluence Cloud. Learn more
  • Container Registries secret detection — detect hardcoded secrets in Azure, Google, JFrog, and DockerHub registries. Learn more
  • Self-Hosted: Export GitGuardian logs to Splunk, Loki, Elasticsearch, Kafka, and Datadog for centralized monitoring. Learn more

Secrets Detection Engine

  • v2.139 — 1 new detector (GitLab Feature Flags Client Token), 6 improved (AMQP, Confluent, Generic High Entropy, Artifactory, Azure Storage), 1 engine enhancement.
  • v2.140 — 12 new detectors (Laravel, GitLab tokens, Kubernetes JWT, Brave Search, Dify, Firecrawl, Ubidots, Vapi, Llama Cloud), 4 improved, 7 new checkers, 2 engine enhancements.

Enhancements

  • Teams API endpoint optimization. See SaaS release: Jun 19.
  • Self-Hosted:
    • Improved ML Secret Engine Docker image permissions to support running with custom user and group IDs for better Kubernetes security contexts.
    • Improved Docker image permissions to support running with custom user and group IDs for better Kubernetes security contexts.
    • Improved handling of failed index creation migrations to allow safe re-execution of database updates.
    • Added capability to specify constraint of only one worker per node in Kubernetes deployments to optimize resource allocation. Learn more about scaling.

Fixes

  • Email alerts to inactive members, custom tags pagination, GitLab parent group permissions, secret analyzer validity checking. See SaaS release: Jun 19.
  • Self-Hosted:
    • Corrected an issue preventing Self-Hosted customers from adding or editing custom severity rule sets.
    • Fixed an issue with ACL limitations on GCP and Azure cloud platforms where Redis deployments disable the ACL command, causing pre-deployment checks for the FLUSHDB command to fail. The system now gracefully handles scenarios where ACL commands are unavailable.

2025.5

Versioncalendar icon Release Date
2025.5.0May 22, 2025

System Requirements Update

Ensure your infrastructure meets the latest requirements for optimal performance and security:

ComponentMinimum VersionRecommended Version
KOTS1.117.3Latest
Kubernetes1.251.32
PostgreSQL1516
Redis67
ggscout0.16.6Latest

Helm & Upgrade Considerations

To ensure compatibility, please review Helm values updates from the previous version.

Upgrading to 2025.5 Air gap deployments

Air gap deployment? We've renamed images in this release. Follow the upgrade instructions to update your tooling for downloading and uploading GitGuardian images to your private registry.

FIPS: This release uses Chainguard images without FIPS-approved cryptographic modules. If you would like to use Chainguard images with FIPS, please contact our support team.

Feature highlights

  • ServiceNow secret scanning — detect secrets and honeytokens in ServiceNow for automated incident tracking. Learn more
  • Customizable incidents view — create custom views with specific properties for better context exploration and prioritization. Learn more
  • SCIM user provisioning — automate user onboarding and offboarding with Okta and Microsoft Entra ID integration. Learn more
  • NHI Policies improvements — enhanced policy breach visibility with filtering, analytics, and Secret Reuse policy support.

Secrets Detection Engine

  • v2.136 + v2.137 — 5 new detectors (Perplexity AI, Azure SignalR, Azure Event Grid, Anthropic Admin, GitGuardian Magic Link), 7 improved (LDAP, JWT, Cloudinary, Auth0, Claude, Riot Games, LINE Notify), 2 new checkers.
  • v2.138 — 6 new detectors (Azure Entra ID, Azure Communication Services, Azure DevOps PAT, Laravel, Azure App Configuration, X AI), 5 improved (Azure Storage, ODBC, Jira, SMB, Octopus).

Enhancements

  • Weekly digest and historical scan email subject lines, Jira DC ticket creation permissions. See SaaS release: May 21.
  • Self-Hosted:
    • Ensured that the Redis FLUSHDB command is available for use before installing or upgrading GitGuardian. Learn more.
    • Added support for configuring proxy username and password using Kubernetes secrets. Learn more.
    • GitGuardian Chainguard images are now used by default and include a shell for troubleshooting and maintenance.
    • Implemented a Content Security Policy in response headers to better control which resources can be loaded, strengthening overall security.

Fixes

  • GitLab read-only token errors, dashboard toast messages, empty GitHub repo scans, deleted sources API display. See SaaS release: May 21.
  • Self-Hosted:
    • Resolved an issue where deployment failed when using Kustomize.
    • Increased the readiness probe timeout for public-api to enhance stability and prevent failures.