Version	Release Date
2025.8.0	August 18, 2025

System Requirements Update​

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

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.

Detect hardcoded secrets in your AWS ECR Container Registry​

We are excited to introduce Secret detection for Amazon Elastic Container Registry (ECR).

Secrets often end up in container images due to common mistakes during development and image creation, mainly:

• Hardcoding Secrets in Code: Developers may directly embed sensitive credentials, such as API keys or passwords, into application code, which gets packaged into container images.
• Misconfigured Dockerfiles: Commands like ENV or RUN in Dockerfiles can inadvertently expose sensitive data during the build process.

By identifying and addressing hardcoded credentials in your AWS ECR repositories early in the development pipeline, this feature significantly minimizes the risk of security breaches, helping you prevent the unintended exposure of sensitive information before it even reaches production.

Check out our Blog Post to learn more and our Amazon ECR documentation to enable the feature now!

Support Valkey (forked version Redis 7.2)​

We're excited to announce support for Valkey, a Redis-compatible database that is a fork of Redis 7.2. This provides users with an additional option for Redis while maintaining full compatibility with GitGuardian Self-Hosted.

Learn more about Redis configuration

Secrets Detection Engine (v2.144)​

New Detectors

• Weights & Biases API Key – Detects API keys for Weights & Biases services.
• Bitbucket App Password – New detector for Bitbucket app passwords to improve recall.
• Mercado Pago Access Token – Detects access tokens for Mercado Pago payment services.

New Checkers These checkers are implemented to verify the detected secrets, adding another layer of security and ensuring their validity and correct application:

• Mercado Pago Access Token

Detector Improvements

• Azure Subscription Key – Improved precision of Azure subscription key detector.
• X AI API Key – Properly report disabled API keys as invalid.
• Bitbucket Access Token – Restricted the detector to detect only Bitbucket repositories access tokens.
• CodeClimate Key – Deprecated CodeClimate key checker.

Enhancements​

• Custom webhooks: Enhanced webhook configuration with more granular event selection. See the updated documentation.
• VCS Integrations: Provided the capability to disable Automatic Repository Monitoring upon VCS Integration. Toggles controlling this capability was also moved on top of the discovered sources for more visibility
• Bitbucket Cloud Integration: Updated authentication to support API tokens as Atlassian discontinues app passwords, ensuring continued integration functionality.

Fixes​

• Incident permissions: Fixed an issue where assignees with "can view" permissions would be hidden from the incident's UI.
• Slack integration: Fixed an issue where duplicate secret occurrences were created when thread replies were posted to channels in Slack.
• JFrog Container Registry integration:
  • Fixed an error in repository last update date retrieval during recurrent scans.
  • Improved error handling and diagnostics for health check connectivity issues.
• Email Notifications: Fixed an issue where integration health check emails were sent without respecting user email notification preferences.
• Confluence Data Center Integration: Fixed an issue where private spaces were not being retrieved during integration setup.

Version	Release Date
2025.7.0	July 25, 2025
2025.7.1	August 8, 2025

System Requirements Update​

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

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.

Historical Scanning now available for Jira and Confluence Data Center​

We’re excited to announce a significant enhancement to our secret detection capabilities for both Jira and Confluence Data Center: historical scanning is now available!

What's new?

Previously, our integrations would surface hardcoded secrets in real-time, alerting you to newly introduced risks as soon as they appeared. With this update, we’re extending our detection to include secrets that were leaked in the past—not just those introduced going forward.

Why does this matter?

Once a secret is leaked, it should always be considered compromised, regardless of when the leak occurred. By surfacing historical secrets, you can now:

• Identify and remediate old, forgotten leaks that may still pose a security risk.
• Reach a comprehensive security posture by ensuring that no secrets—past or present—slip through the cracks.
• Take proactive action to rotate or revoke secrets that may have been exposed long ago.

Check out our documentation to enable historical scanning now:

• Confluence Data Center
• Jira Data Center

Automatically Ignore Invalid Incidents with New Playbook​

We’re excited to announce a powerful enhancement to your incident management experience, designed to help you focus on what matters: we are introducing a new playbook: Automatically Ignore Invalid Incidents.

What's new?

This new playbook will automatically ignore incidents where the detected secret has been confirmed invalid and revoked, even for those that have never been valid. With this new capability, your team can immediately focus on genuine, actionable threats without being distracted by unnecessary noise from already-resolved issues.

Why This Matters?

By automatically clearing these known invalid incidents, you'll save valuable time, reduce alert fatigue, and maintain a clear focus on critical security issues that require your attention.

Important Note

This playbook is designed for incidents from standard detectors and will not impact those related to detectors with a custom host.

You Stay in Control

The playbook will be enabled by default, but you can opt out at any time if it doesn’t fit your needs. All incidents will remain accessible in your workspace for review.

Documentation

Secrets Detection Engine (v2.143)​

New Detectors

• GitLab Incoming Mail Token – Detects tokens used for GitLab incoming mail.
• Coze Personal Access Token – Detects personal access tokens for Coze services.
• Tavus API Key – Recognizes API keys for Tavus services.
• Heroku Platform Key – Detects prefixed variants of Heroku Platform Keys.
• SSH Credentials – New detector ssh_password_with_port allows matching SSH passwords with ports.
• Tableau Cloud PAT – Detects personal access tokens for Tableau Cloud.
• Notion Integration Token v2 – Detects the new Notion token format.
• AI71 API Key – Detects API keys for AI71 services.
• AMP API Token – Recognizes API tokens for AMP services.
• Kubernetes User Certificate with Port – Extracts port numbers for Kubernetes user certificates.
• NVIDIA API Key – Detects API keys for NVIDIA services.
• Alchemy API Key v2 – Identifies API keys for Alchemy services.
• OpenRouter API Key – Detects API keys for OpenRouter services.
• Duffel API Key – Recognizes API keys for Duffel services.
• Apify Token – Captures tokens for Apify services.
• Jina API Key – Detects API keys for Jina services.
• Deno Account Token – Identifies tokens for Deno accounts.
• Segment Workspace Key v2 – Detects workspace keys for Segment services.
• Resend API Key – Recognizes API keys for Resend services.
• VKontakte Access Token – Detects access tokens for VKontakte services.
• Fireworks AI API Key – Captures API keys for Fireworks AI services.

New Checkers These checkers are implemented to verify the detected secrets, adding another layer of security and ensuring their validity and correct application:

• Coze Personal Access Token
• Tavus API Key
• Heroku Platform Key
• Tableau Cloud PAT
• Notion Integration Token v2
• Salesforce OAuth2
• AI71 API Key
• AMP API Token
• Kubernetes User Certificate with Port
• Alchemy API Key v2
• OpenRouter API Key
• Duffel API Key
• Apify Token
• Jina API Key
• Deno Account Token
• Resend API Key
• VKontakte Access Token
• Fireworks AI API Key

Detector Improvements

• Google OAuth2 Keys – Improved precision for Google OAuth2 detector and enhanced regex for better detection accuracy.
• Zendesk Token – ZendeskTokenAnalyzer has been rewritten in Rust for improved performance.
• Sendinblue Key – SendinblueSecretAnalyzer has been rewritten in Rust.
• Generic High Entropy Secret – No longer considers IDs in ServiceNow migration files as secrets and removed AWS ECR images that were misclassified as secrets.
• Algolia Keys – AlgoliaKeysSecretAnalyzer has been rewritten in Rust.
• Fastly Personal Token – FastlySecretAnalyzer has been rewritten in Rust.
• [Hugging Face User Access] – Migrated analyzer to Rust for improved performance.
• Kubernetes Docker Secret – Enhanced detection for kubernetes.io/dockercfg secrets with more precise regex for JWTs.
• MySQL Assignment – Restricted the maximum number of secrets per document to prevent combinatorial explosion.
• Sourcegraph Token – Updated regex for sourcegraph_access_token_v3 as per customer request.
• GitHub Access Token – GitHub classic analyzer has been rewritten in Rust for improved performance.
• HashiCorp Vault Token – Improved precision for HashiCorp Vault token detection.
• Confluent Keys – Updated checker for Confluent API keys.
• GitHub Fine-Grained PAT – Analyzer now handles archived repositories.
• Slack Tokens – SlackBot analyzer has been rewritten in Rust for improved performance and applies to Slackbot, Slack App, and Slack User tokens.
• DigitalOcean Spaces Token – Fixed checker for tokens that do not have permission to list buckets.
• Checkout Secret Key – Updated endpoint to avoid deprecated usage.
• Checkout Sandbox Secret Key – Enhanced pattern and updated endpoint for improved accuracy.
• Bunny.net API Key – Fixed checker for better validation.
• Dify API Key – Updated checker endpoint for enhanced detection.

Engine Enhancements

• All JWT detectors will now only catch signed JWTs, enhancing security.

Enhancements​

• Jira Data Center Integration: Enhanced Jira Data Center incident creation to include leaker email addresses for historical comments occurrences.
• Custom Tags API: Enhanced the custom tags filter in the public API to support filtering by key/value pairs in addition to IDs, improving search flexibility for better incident management. Learn more.
• Playbook: "Auto-resolve secrets incidents when valid secrets are revoked" playbook is officially activated for all accounts. Learn about Playbooks
• Custom remediation: Added dynamic links to custom remediation pages, providing users with seamless access to relevant documentation and revocation support.
• Public API: Custom Tags (custom_tags) query parameters have been documented as part of the API documentation.
• GitLab integration: Configuration of multiple GitLab integrations using both system hooks and group hooks simultaneously is now supported.

Fixes​

• Custom Tags: Fixed an issue where assigning tags to selected filtered issues was incorrectly applying tags to all issues instead of only the selected ones.
• Azure DevOps Integration: Improved token handling to prevent unnecessary revocation of Azure DevOps installations due to intermittent 401 errors.
• Email Notifications: Improved email delivery logic for Microsoft Teams integrations to prevent excessive notification sending during periodic scans.
• GitHub Integration: Fixed an issue where dangling GitHub installations were being unnecessarily checked when no installations were present.
• User Management: Ensure SCIM user provisioning matches emails case-insensitively to prevent duplicate or mismatched user entries.
• Incidents Management: Resolved a regression where secrets detected on deletion lines could reopen incidents. Deletion lines are no longer scanned for secrets, as per the expected "Scan only addition line" behavior.

Hotfixes​

2025.7.1​

  Release Date: August 8, 2025

Fixes​

• Embedded Cluster with Embedded Redis: Updated 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.

Version	Release Date
2025.6.0	June 20, 2025

System Requirements Update​

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

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.

Securely Access Secret Values via API with GitGuardian's New “Secrets” Endpoint​

GitGuardian is excited to announce a new API endpoint /v1/secrets/{secret_id}, allowing users to securely access secret values directly through our API.

This feature introduces several key benefits:

1. Enhanced Security Automation - Integrate secret remediation into existing security workflows and tools with secure API access to secret values.
2. Reduced Manual Intervention - Eliminate the need to manually copy secrets from the UI, saving time and reducing human error.
3. Comprehensive Security Controls - Multiple security layers (PAT permissions, workspace settings) ensure secrets are accessed only by authorized users.
4. Complete Secret Context - Receive both the secret value and detector information in a single API call for efficient remediation.

Read more in the documentation

Secrets Detection in Microsoft Teams​

We’re pleased to introduce hardcoded secret detection for Microsoft Teams!

What’s new?

Our platform now scans Microsoft Teams messages for hardcoded secrets—such as API keys, credentials, and tokens—across both new activity and historical content. This means you can instantly identify and remediate exposed secrets, whether they were just shared or left unnoticed in your Teams environment.

Why is this important?

Once a secret is leaked, it remains a security risk until addressed—regardless of when it was exposed. By providing both real-time and historical scanning, we offer:

• Comprehensive coverage: Instantly detect newly introduced secrets and uncover old leaks hiding in past conversations or shared files.
• Proactive risk management: Take swift action to rotate, revoke, or investigate secrets, minimizing the window of exposure.
• Complete peace of mind: Ensure your Teams environment is continuously monitored and secured against secret sprawl.

Secure your collaboration. Protect your business.

Simply connect your Microsoft Teams instance and let our enhanced detection engine do the rest. Our solution will automatically scan both ongoing and historical Teams content, surfacing any hardcoded secrets for prompt remediation.

Check out our documentation to start protecting your MS Teams communications!

Historical Scanning now available for Jira and Confluence Cloud sources.​

We’re excited to announce a significant enhancement to our secret detection capabilities for Jira and Confluence Cloud: historical scanning is now available!

What's new?

Previously, our integration would surface hardcoded secrets in real-time, alerting you to newly introduced risks as soon as they appeared. With this update, we’re extending our detection to include secrets that were leaked in the past—not just those introduced going forward.

Why does this matter?

Once a secret is leaked, it should always be considered compromised, regardless of when the leak occurred. By surfacing historical secrets, you can now:

• Identify and remediate old, forgotten leaks that may still pose a security risk.
• Reach a comprehensive security posture by ensuring that no secrets—past or present—slip through the cracks.
• Take proactive action to rotate or revoke secrets that may have been exposed long ago.

Check out our documentation to enable the feature now:

• Jira Cloud
• Confluence Cloud
• Scaling

Detect hardcoded secrets in your Container Registries​

We are excited to introduce Secret detection for Container Registries, including:

• Azure Container Registry
• Google Artifact Registry
• JFrog Container Registry
• DockerHub

Secrets often end up in container images due to common mistakes during development and image creation, mainly:

• Hardcoding Secrets in Code: Developers may directly embed sensitive credentials, such as API keys or passwords, into application code, which gets packaged into container images.
• Misconfigured Dockerfiles: Commands like ENV or RUN in Dockerfiles can inadvertently expose sensitive data during the build process.

By identifying and addressing hardcoded credentials early in the development pipeline, this feature significantly minimizes the risk of security breaches, helping you prevent the unintended exposure of sensitive information before it even reaches production.

Check out our Blog Post to learn more and our documentation to enable the feature now:

• Azure Container Registry
• Docker Hub
• Google Artifact Registry
• JFrog Container Registry
• Scaling

Export self-hosted GitGuardian logs to Splunk and more​

You can now forward GitGuardian application logs to external log aggregation systems including Splunk, Loki, Elasticsearch, Kafka, and Datadog.

This allows you to integrate GitGuardian's logs with your existing observability infrastructure for centralized monitoring and analysis.

Check out our documentation to configure custom pipelines and start exporting your logs!

Secrets Detection Engine (v2.140)​

New Detectors

• GitLab Feature Flags Client Token – Detects tokens used for managing feature flags in GitLab projects, crucial for controlling feature rollouts and ensuring smooth deployment processes.
• Laravel Encryption Key with Host – Detects Laravel encryption keys associated with a host.
• GitLab Feature Flags Client Token with Project ID – Identifies tokens and project IDs for GitLab feature management.
• Kubernetes JWT with Host – Detects JWTs used in Kubernetes environments.
• GitLab Trigger Token – Recognizes tokens for triggering GitLab pipelines.
• Brave Search API Key – Detects API keys for accessing Brave Search.
• GitLab Deploy Token – Identifies deploy tokens for managing GitLab project deployments.
• Firecrawl API Key – Detects API keys for Firecrawl services.
• Dify API Key – Detects API keys for Dify services.
• GitLab Runner Authentication Token – Captures authentication tokens for GitLab runners.
• Ubidots API Key – Detects API keys for Ubidots.
• Vapi API Key – Detects API keys for Vapi services.
• Llama Cloud API Key – Ensures detection of API keys for Llama Cloud.

New Checkers These checkers are implemented to verify the detected secrets, adding another layer of security and ensuring their validity and correct application:

• Laravel Encryption Key with Host
• GitLab Feature Flags Client Token with Project ID
• Kubernetes JWT with Host
• Brave Search API Key
• Firecrawl API Key
• Dify API Key
• GitLab Runner Authentication Token

Detector Improvements

• Ubidots Token – Now includes new secret prefixes and improved checker responses for tokens from disabled accounts.
• Azure Cosmos DB Credentials – Enhanced host pattern to improve recall and detection accuracy.
• GitLab Token – Refined pattern to minimize false positives.
• ODBC Connection String – Advanced detection precision for ODBC strings.
• AMQP Credentials – Detector Upgrade: Enhanced multimatch selection to reduce false positive combinations, vital for secure message queuing in distributed systems.
• Confluent Keys – Detector Upgrade: Improved multimatch selection for better accuracy and fewer false positives, essential for managing access to Kafka clusters.
• Generic High Entropy Secret – Detector Upgrade: Excludes secrets ending with '.certificate' from being reported, reducing noise by ignoring non-sensitive certificates.
• Artifactory Token – Analyzer Upgrade: Improved stability by preventing crashes when analyzing secrets with multiple scopes, key for managing and securing software artifacts.
• Microsoft Azure Storage Connection String – Checker Upgrade: Enhanced to accept additional fields, crucial for accessing and managing Azure storage resources securely.
• Microsoft Azure Storage Account Key – Detector Upgrade: Increased precision, reducing false positives, critical for safeguarding data in cloud storage.

Engine Enhancements

• Established a priority rule favoring the confluent_api_keys detector over amqp_assignment and amqp_assignment_attached_port detectors.
• Expanded detection pattern list for encrypted strings to increase precision.
• Enhanced AssignmentRegexMatcher for N prefixed strings in SQL, supporting Microsoft SQL Server.

Enhancements​

• Teams: Optimized the /teams API endpoint to reduce loading times for workspaces with large team structures.
• 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​

• Emails: Resolved an issue where email alerts were being sent to inactive workspace members.
• Custom Tags: Resolved pagination issues in the custom_tags endpoint that were causing incorrect next page URLs.
• GitLab: Improve permission checking for GitLab group integrations to properly handle inherited permissions from parent groups.
• Severity rules: Corrected an issue preventing Self-Hosted customers from adding or editing custom severity rule sets.
• Secret analyzer: Improved behavior to ensure secret analyzer is properly disabled when validity checking is turned off.
• Self-Hosted Deployment on GCP and Azure: 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.

Version	Release Date
2025.5.0	May 22, 2025

System Requirements Update​

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

Helm & Upgrade Considerations​

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

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.

ServiceNow secret scanning​

ServiceNow is now supported for secrets detection and honeytoken detection, enabling automated tracking of security incidents. Learn more

Customize Your Incidents View for Enhanced Context Exploration​

With this new feature, users can create fully customized views of their incidents, displaying specific properties and exploring their security data in an entirely new way.

This customization capability offers two key advantages:

1. Leverage the Generic Secret Enricher model (read 2025.3 release page) - You can now explore and prioritize generic incidents more effectively by visualizing the AI-classified secret categories and providers
2. Harness extensive incident context - Access the rich contextual data we provide for each incident, which is essential for efficient prioritization efforts

Context is critical for effective remediation. CyberSecurity is fundamentally a data business, and by collecting and presenting the richest, most structured context possible, we enable you to filter, sort, and prioritize incidents effectively and make informed decisions.

Read more in the documentation

Automate User Onboarding & Offboarding with SCIM​

SCIM (System for Cross-domain Identity Management) integration now supports both automatic user provisioning and deprovisioning in GitGuardian. When users are added or removed from your Identity Provider (IdP)—such as Okta or Microsoft Entra ID—they are automatically created or deactivated in your GitGuardian workspace.

Now, all your developers can be automatically onboarded to GitGuardian and are ready to handle security incidents as soon as they are added to your IdP. This means you can fully automate the onboarding and offboarding of users, directly from your IdP, ensuring your entire development team is always prepared to respond to incidents.

Why is this important?

• Streamlined onboarding: New users are automatically provisioned in GitGuardian as soon as they are added to your IdP—no more manual invites or user creation.
• Automated offboarding: When a user is removed or deactivated in your IdP, their access to GitGuardian is automatically revoked, reducing security risks.
• Real-time synchronization: User changes in your IdP are reflected in GitGuardian almost instantly, ensuring your workspace always stays up to date.
• Improved compliance: Automated user lifecycle management helps you meet security and compliance requirements by ensuring only authorized users have access.
• Reduced manual work: Save time and reduce errors by eliminating manual user management tasks.

Note: Team provisioning via SCIM is not yet available, but is planned for a future update.

How to get started?

• SCIM is available for workspaces using Okta or Microsoft Entra ID as their IdP.
• To enable SCIM, go to your workspace Settings > Authentication and follow the setup instructions for your IdP.
• For detailed configuration steps and best practices, check out our product documentation.

NHI Policies improvements​

Identify quick wins and areas of improvement thanks to improved policy breach visibility and management, including the ability to:

• Filter breaches by type on the inventory page,
• View detailed analytics on NHI breaches over time,
• Benefit from Secret Reuse policy for better secret management and security across environments.

Want to discover more about NHI Governance? Check out our public materials:

• Product Overview
• Documentation
• Blog Post

Secrets Detection Engine (v2.138)​

This release brings major enhancements to the Secrets Detection Engine, with a strong focus on expanding coverage for Artifactory and Azure services. New detectors have been added for a wide range of secrets—including Perplexity AI, Azure Entra ID, Communication Services, App Configuration, and more—helping organizations better protect sensitive credentials across their software supply chain and cloud infrastructure.

Key improvements include:

• Expanded Azure Coverage: New detectors for Entra ID tokens, Communication Services, App Configuration, DevOps PATs, and SignalR, strengthening security for Azure environments.
• Broader Secret Detection: Added support for Perplexity AI, Anthropic admin keys, Laravel encryption keys, X AI API keys, and GitGuardian Platform Magic Links.
• Enhanced Accuracy: Upgrades to existing detectors (LDAP, JWT, Cloudinary, Auth0, Claude, Jira, SMB, ODBC, Octopus, and more) improve precision, recall, and reduce false positives.

For full details on new detectors and improvements, see the list below.

New Detectors

• Perplexity AI API Keys – Added a new detector for Perplexity AI API keys.
• Azure SignalR Connection String – Introduced a new detector for Azure SignalR Connection Strings.
• Azure Event Grid Access Key – Added new detectors for Azure Event Grid Access Keys and a New Checker for the azure_event_grid_access_key_with_host detector.
• Anthropic Admin Keys – Introduced a new detector and New Checker for Anthropic admin keys.
• GitGuardian Platform Magic Link – Added a new detector for GitGuardian Platform Magic Links.
• Azure Entra ID Tokens – Detects tokens used for authentication within Azure's identity management service, Entra ID.
• Azure Communication Services Connection Strings – Identifies connection strings for Azure's comprehensive communication platform.
• Azure DevOps Personal Access Token – Recognizes personal access tokens used to authenticate with Azure DevOps.
• Laravel Encryption Key – Detects encryption keys used in Laravel applications for data security.
• Azure App Configuration Connection String – Identifies connection strings for managing application settings in Azure.
• X AI API Keys – Detects API keys for accessing X AI's artificial intelligence services.

Detector Improvements

• LDAP Credentials – Checker Upgrade: Improved the LDAP checker to better distinguish between connection errors and invalid credentials. Updated ldap_credentials_assignment_with_dn to remove false positives.
• JSON Web Token – Detector Upgrade: The detector will now detect all JWTs regardless of their contents.
• Cloudinary API Keys – Detector Upgrade: Extended charset of cloudinary_api_key_config to improve recall.
• Auth0 Keys – Detector Upgrade: Improved recall of the detector to detect more domains.
• Claude API Key – Detector Upgrade: Refined regex for Claude API keys.
• Riot Games API Key – Checker Updated: Banlist checker will be deleted.
• LINE Notify Token – Checker Updated: Banlist checker as the service has been discontinued.
• Microsoft Azure Storage Connection String – Detector Upgrade: Improved regex precision for more accurate detection.
• ODBC Connection String – Detector Upgrade: Enhanced regex precision to better identify ODBC connection strings.
• Jira Token – Detector Upgrade: Corrected host regex to accurately match ports.
• SMB Credentials – Detector Upgrade: Now allows percent sign as a separator between username and password in host matches.
• Octopus API Key – Checker Upgrade: Updated to use the correct API endpoint, resolving issues with secret validity checks.

Enhancements​

• Emails: Included the number of incidents to both weekly digest and historical scan emails subject line
• Jira Data Center Issue Tracking Integration: Creating Jira tickets now only requires regular user permissions. Administrator privileges on the Jira Data Center site are only needed when setting up the two-way synchronization (Auto-resolve feature).
• 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.
• Security: Implemented a Content Security Policy in response headers to better control which resources can be loaded, strengthening overall security.

Fixes​

• GitLab Integrations: Resolved a problem where system hook checks returned a 403 forbidden error when using a read-only token.
• Dashboard: Resolved an issue where a toast message displayed "unknown error" in certain situations.
• Historical Scan: Resolved an issue where scans of empty GitHub repositories were incorrectly marked as failed.
• API: Resolved an issue where deleted sources were incorrectly displayed as monitored.
• 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.

Version	Release Date
2025.4.0	April 25, 2025
2025.4.1	April 30, 2025
2025.4.2	August 8, 2025

System Requirements Update​

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

Helm & Upgrade Considerations​

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

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

Get full control of your Non-Human Identities​

We're proud to introduce our brand new NHI Governance product! This solution is designed to help you manage and secure your Non-Human Identities (NHIs) and related secrets.

As organizations face exponential growth in machine identities, NHI Governance delivers a comprehensive observability and lifecycle management across all your environments. Integrating with leading secrets managers and other sources from your infrastructure, it centralizes inventory, helps you assess your posture, and enforces security policies. The solution includes:

• Deep contextual insights, mapping relationships between secrets, their consumers, and resources, drastically reducing incident response times.
• Advanced analytics helps you identify risks like overprivileged NHIs and track hygiene metrics.
• Policy enforcement aligns your posture with standards such as the OWASP NHI Top 10.

NHI Governance empowers you to regain control over your NHIs and tied secrets, reduce risk, accelerate compliance tasks, and improve hygiene by addressing orphaned, untracked, or overprivileged credentials.

Ready to start your journey towards safer secrets management? Request access to GitGuardian NHI Governance by contacting your sales representative.

Learn more:

• Product Overview
• Documentation
• Blog Post

Prioritize faster with Secrets Analyzer​

We're excited to announce Secrets Analyzer, a new enhancement to our secrets detection capabilities.

Secrets Analyzer automatically gathers additional context for detected secrets, including their associated scopes, permissions, ownership, and relevant perimeter information where available.

This added intelligence helps security teams:

• Evaluate the potential impact of a secret incident more accurately.
• Prioritize remediation efforts based on risk level.
• Streamline the overall incident response process.

For details on how each analyzer works, including metadata collected and validation calls:

• Explore the Secret Analyzers documentation.
• View the full list of Available Analyzers.
• See a specific example for the Jira Token Secret Analyzer.

Improve incident remediation with custom tags​

Take control of incident management with custom tags. This feature allows you to categorize, filter, and search incidents using customized labels, offering greater flexibility in tracking and prioritizing incidents, and improving remediation workflows.

For developers, you can interact with custom tags via the API. For more information, visit the API documentation.

For more details on how to use custom tags within the GitGuardian platform, check out our detailed guide.

Email notifications enhancement​

You now have two options for receiving incident email notifications: "All incidents" (default) or "Only incidents involving yourself (based on your Git commit email)", learn more about email preferences.

Log collector for Self-Hosted​

Our self-hosted deployments now include a seamless log collection system, leveraging Loki, MinIO, and Fluent Bit under the hood. This enhancement ensures that relevant logs are efficiently gathered and stored, supporting faster troubleshooting and support—without requiring any manual setup from users.

This log collection system is now enabled by default for all installation types (Helm or KOTS).
Learn more about the log collector.

Secrets Detection Engine (v2.135)​

Improved accuracy and broader coverage in this latest release:

New Detectors

• Azure Logic App Shared Access Signature – New detector for Azure Logic App Shared Access Signature.
• Multiple new detectors have been added for Artifactory:
  • Artifactory Reference Token
  • Artifactory Reference Token With Host
  • Artifactory Master Key
  • Artifactory Basic Auth Credentials

Detector Improvements

• Snowflake Credentials – The Snowpark API credentials detector has been enhanced to identify more patterns.
• IBM Cloud Key – We reduced false positives in the IBM Platform API key detector.
• PlanetScale Database Password - Expanded detection to cover more host names for the Planetscale database password detector.
• Artifactory Token With Host - Improved precision for host names.
• LINE Messaging OAuth2 – Removed false positives from the LINE Messaging OAuth2 detector.
• OpenAI API Key – Fixed a bug in the analyzer for OpenAI API Key that prevented it from reporting threads:* scopes.

Detector changes

• FCM API Key – Removed FCM API Key checker since its API was removed.

Miscellaneous

• Add User Agent GitGuardian in HTTPClient class used by analyzers.

Enhancements​

• Incidents: Added a new filter to improve incident categorization based on the presence or absence of Jira Data Center tickets.
• Custom Tags: Users can now create custom tags directly from search queries in the dashboard.
• Custom webhook: Add the team name and webhook name to the custom webhook payload for incidents and occurrences. Learn more.
• Jira Configuration: Introduced a new layout for the Jira Configuration form to enhance user experience and streamline configuration tasks.
• Navigation Improvements:
  • Added persistent section state to remember your navigation preferences and updated browser tab titles for better identification when managing multiple tabs.
  • Added a "Skip to Main Content" button for better accessibility. When using keyboard navigation, pressing the Tab key reveals the button, which allows users to bypass navigation menus and jump directly to the main content area.
• Invitation: Added GET /v1/invitations/{invitation_id} endpoint to retrieve invitation details through the Public API.
• Self-Hosted:
  • Email Configuration: Improved error messages to provide clearer guidance when setting up email configurations.
  • Troubleshooting: Enhanced debug capabilities by adding network diagnostic tools (netcat, openssl) to the debug image. Learn more.
  • Helm:
    • Extended the readiness probe timeout on public-api to enhance stability and prevent premature failures.
    • Resolved an issue where the host was not specified in the health ingress configuration.
    • Added global.compatibility.openshift.adaptSecurityContext configuration to support OpenShift's restricted-v2 Security Context Constraints (SCC). Values include auto (default), force, and disabled for flexible security context adaptation. Learn more.
    • Added default support-bundle Role and optional ClusterRole creation (configurable via replicated.supportBundle.rbac.clusterRole.create).
    • The PostgreSQL pgvector extension is now required by default (postgresql.plugins.pgvector.enabled). Please follow the installation instructions to enable vector similarity search capabilities for upcoming machine learning features.
  • Ingress:
    • Improved response times for issue occurrence queries through optimized request routing. Particularly useful when autoscaling webapp-public_api.
    • Standardized health check endpoint routing by removing the wildcard host configuration from gim-ingress-health and consolidating /api/v1/health under the main API hostname.

Fixes​

• Jira Cloud Issue Tracking Integration: Fixed an issue where Jira project keys were incorrectly changed during synchronization.
• GitLab Integration:
  • Fixed an issue where multiple emails were sent for failures in multiple group hooks on the same GitLab instance, ensuring only one email is sent per instance.
  • We improved the process for read-only token installations by automatically detecting and updating the webhook ID if the webhook was created manually.
  • Resolved an issue where system hook checks returned a 403 forbidden error when using a read-only token.
  • Fixed unnecessary scans triggered by webhooks related to unmonitored repositories.
• Incidents: Fixed a bug that could cause unnecessary data refresh on the incidents list when switching browser tabs.
• Self-Hosted:
  • Licensing: Updated the notification message for license expiration on self-hosted environments to provide clearer guidance.
  • Security: Added Content Security Policy (CSP) headers to HTTP responses to strengthen browser security controls.

Hotfixes​

2025.4.1​

  Release Date: April 30, 2025

Fixes​

• Helm: Disabled Support Bundle Role creation by default to accommodate customers with high security requirements.

2025.4.2​

  Release Date: August 8, 2025

Fixes​

• Embedded Cluster with Embedded Redis: Updated configuration to use bitnamilegacy/redis registry following Bitnami's registry changes.

  Release Date: March 20, 2025

System Requirements Update​

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

Helm & Upgrade Considerations​

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

Explore and prioritize your Generic Incidents​

We are excited to unveil the "Generic Secret Enricher V1", a machine learning model designed to enhance our capabilities in generic secret detection. This innovative model analyzes the entire context of a document, identifying the company and category associated with a secret, thereby providing meaningful insights to help users understand the origin and type of a discovered secret.

New Features​

• Contextual Analysis: Upon detection of a generic secret, our platform analyzes the full document context to determine the associated provider or category of a secret.

• Efficient Classification: This feature reduces the need for manual classification, enabling users to quickly comprehend the source and nature of a discovered generic secret.

• New Filters: We've introduced three new filters - Provider, Category, Family - to help identify critical generic incidents. To use these, filter your incidents by the "Generic" type, then apply a combination of these filters.

Goals​

Our long-term goal is to provide you with actionable insights, prioritize their generic incidents, and improve their remediation efforts.

Usage​

To use the new filters, simply filter your incidents by the "Generic" type, then apply a combination of the Provider, Category, and Family filters. This will help you identify the most significant or critical generic incidents, such as those classified under "Data Storage" or linked to the provider "Postgresql".

Leverage insights from your Secrets Managers​

GitGuardian now integrates with AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, Google Secret Manager, Delinea, and Akeyless through ggscout, letting you sync secret incidents with your Secrets Managers—without exposing sensitive data.

What’s in it for you?

• Prioritize Faster – Instantly see which secrets are already vaulted and focus on real risks.
• Remediate Quicker – Vault unprotected secrets in a click and speed up fixes.
• Streamline Workflows – Leverage vaulted secrets insights directly in GitGuardian.
• Improve Secrets Hygiene – Spot duplicate, weak, or mismanaged secrets with ggscout.
• Simplify Vault Consolidation – Track migrations, filter secrets, and purge outdated ones effortlessly.

Secrets Detection Engine (v2.133)​

Bringing enhanced accuracy and broader coverage:

• New Detectors
  • OpenAI Project API Key (v2) – Added support for detecting the new format of OpenAI project API keys.
  • OpenAI Admin API Key – New detection capability for OpenAI admin API keys.
  • Netlify Token (v2) – Introduced detection for the latest version of Netlify tokens.
  • 1Password Service Account Token – New detector added to identify 1Password service account tokens.
  • DeepSeek API Key – Now detecting DeepSeek API keys.
• Improved Detection
  • OpenAI Service Account – Expanded pattern coverage for better identification.
  • Rails Master Key – Updated detection rules to minimize false positives.
  • GitHub Tokens – Improved recall and validation for GitHub authentication tokens.
  • Groq API Key – Enhanced detection rules for greater accuracy.
  • Artifactory Token – New checker added to improve detection effectiveness.
  • Generic Passwords – Excluded secrets containing ***** as they are likely false positives.
  • Dropbox Key – Detector group split into Dropbox Key and Dropbox Access Token for improved granularity.
  • FCM API Key – Validity check is no longer available since the API has been removed. While we can no longer retrieve the validity status for FCM secrets, we still detect the keys.

Enhancements​

• Jira Issue Tracking Integration:
  • Added Incident ID as an optional variable in Jira ticket templates for improved customization.
  • Enabled instant ticket creation in Jira without requiring a predefined template.
• ggscout: Additional improvements to the integration of ggscout with self-hosted. Learn more.
  • Ensured Vault configurations are reachable via the preflight check for Helm and KOTS.
  • Hardened Helm chart (custom CA support, optional GitGuardian hostname).
  • Used Replicated Proxy to pull the ggscout image.
  • Enabled support for embedded cluster deployment (HashiCorp Vault only).
  • Included ggscout logs in the support bundle.
• Self-Hosted:
  • Public API: Added ability to customize maximum page size for the Public API pagination. More info here.
  • Embedded cluster: Machine learning is now activated by default for embedded cluster installations.
  • License: GitGuardian will now automatically synchronize license information for non-air-gap environments, eliminating the need for manual license syncs after installation or upgrades.
  • Helm: Added support for nodeSelector in Helm jobs to enhance node scheduling flexibility.

Fixes​

• Jira Cloud Issue Tracking Integration: Resolved an issue where integration entered an invalid state after being uninstalled.
• Microsoft Teams Alerts for Security Incidents: Resolved an issue where the wrong team was displayed during configuration.
• Self-Hosted:
  • Machine Learning: Added support for using custom security contexts, allowing to configure security settings for the machine learning pods.
  • Preflights: Fixed an issue with Redis TLS that could cause connection errors.

  Release Date: February 20, 2025

System Requirements Update​

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

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.

Search Incidents by Secret Value​

GitGuardian allows you to monitor secret leaks across thousands of your repositories and over 30 different types of sources. It is reassuring to know that this critical secret, which provides access to your corporate LDAP, has not been detected anywhere.

Bitbucket Cloud Scanning​

Secure your Bitbucket Cloud repositories with secrets detection powered by GitGuardian.

• Detect exposed credentials and secrets in real-time.
• Gain visibility into security incidents directly in your dashboard.
  Learn more

Custom Tags Early Access​

Improve incident organization and tracking with Custom Tags, allowing users to filter, sort, and categorize incidents more effectively. For now, custom tag management (CRUD) and tag assignments to incidents can only be done via the API (API documentation), with UI support coming soon.

To activate this feature, enable custom_tags_enabled in the Preferences page.

Autoscaling​

HPA now supports web applications (e.g., webapp-public_api), allowing automatic scaling based on demand for improved performance and resource efficiency. Learn more on the autoscaling page.

Secrets Detection Engine (v2.131)​

Bringing enhanced accuracy and broader coverage:

• New Detectors
  • Artifactory Token With Host
  • HubSpot Private App Token
  • Microsoft Azure Storage Connection String
  • Hashicorp Vault AppRole Authentication
• Improved Detection for GitHub Tokens
  • Enhanced validation for GitHub Enterprise Token
  • Refined rules for various GitHub authentication tokens:
    • OAuth Access Token
    • Personal Access Token
    • Server-to-Server Token
    • GitHub Token
    • User-to-Server Token

Enhancements​

• Scan Only Addition Lines in Commits: Now, when using ggshield or our check runs integration, we only scan for added lines in commits. Developers will no longer be blocked while remediating incidents.
• Jira Issue Tracking Integration: Added support for "Numbers (or float)" and "Group Pickers (single group)" custom fields in Jira templates, allowing more customization in notifications and issue tracking.
• Enhanced Email Incident Alerting Controls for Members: You can now manage email notification settings more effectively with an option that allows updates through the API, and customize account-level defaults, ensuring a more tailored communication experience for all members. Learn more

Fixes​

• Sources:
  • Azure Repos Integration: Fixed an issue where organization deletions were not properly synced when using ADO installations in Organization-mode.
  • GitLab Integration: Resolved an issue where GitLab installations were incorrectly revoked due to temporary plan downgrades or admin status changes.
• Users & Teams:
  • Incidents: Resolved an issue where restricted users could not view the Vulnerable Sources block.
  • Users: Resolved an issue where user deletion was prevented due to the presence of saved views associated with the user.
  • Teams Management: Resolved an issue where action menus were not displayed in the teammates table for non-admin users in certain cases.
• Alerting:
  • Confluence Cloud Integration: Fixed an issue where some Confluence Cloud events without a spaceKey were incorrectly ignored.
  • PagerDuty Alerts for Security Incidents: Fixed an issue where the integration was not sending alerts for real-time incidents.
  • Email Notifications: Fixed an issue where emails for ignored and valid incidents were sent to all teams a user belongs to, instead of only the teams managing the affected repository.
• Self-Hosted:
  • Helm: Fixed an issue where connecting to Redis Sentinel failed when using a password with special characters.
  • Kots: Restore the left navigation menu in the KOTS admin console for embedded cluster installations.

Version	Release Date
2025.1.0	January 20, 2025
2025.1.1	January 23, 20255

System Requirements Update​

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

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.

Microsoft Teams Security Alerts​

Never miss a critical security event with real-time GitGuardian alerts in Microsoft Teams.

• Instant notifications when security incidents occur.
• Direct links to investigate issues inside GitGuardian.
  Learn more

Jira Auto-Tracking for Security Incidents​

Streamline incident response with Jira Data Center integration.

• Auto-create Jira issues when new incidents are detected.
• Sync custom fields for better tracking.
• Auto-resolve incidents when Jira issues are closed.
  Learn more

False Positive Remover v1​

Our first internal machine learning model halves false positives, ensuring data security and privacy without third-party dependencies. This in-house capability is now available for Self-Hosted. More information is available in the documentation.

Slack Secret Scanning​

Slack integration is now supported for scanning the full history of your public and private Slack channels to detect leaked secrets.

Remediation tracking​

Enhanced the secrets remediation workflow with precise location details for code fixes and real-time tracking of remediation progress. Learn more here.

⚠️ You can adjust the scan rate limit for the file tracking engine via the scan_after_push_force_rate_limit preference on the Preferences page. Historical scans are recommended to ensure incidents requiring fixes are available in the dashboard.

User management with SCIM​

SCIM integration now supports automatic user deprovisioning in GitGuardian when users are removed from your Identity Provider (IdP). Provisioning for users and teams will be included in a future update. Setup details are available in our documentation.

Secrets Detection Engine (v2.129)​

Bringing enhanced accuracy and broader coverage:

• New Detectors
  • GitLab OAuth Application Token
  • Jenkins API Token
  • chpasswd Username Password
  • Nessus Agent Key
  • Statsig Server Secret Key
• Improved Detection for Sensitive Credentials
  • Enhanced identification of Base64 Generic High Entropy Secret
  • Improved detection of GitGuardian Test Token Checked
  • Refined rules for MSSQL Credentials
  • Expanded coverage for Zendesk Token
  • Improved handling of FTP Credentials Assignment

Enhancements​

• Navigation: The menu has been redesigned with a collapsible left sidebar for a cleaner, more organized experience.
• Jira Data Center integration: Added support for the "User Picker (single user)" custom field in Jira templates. More information is available here.
• GitHub integration:
  • Improved handling of real-time events to retrieve more than 100 commits when necessary, ensuring complete coverage.
  • Enhanced processing of large patches by making additional API calls to retrieve missing files, up to the policy__maximum_scan_size limit defined in the Preferences page.
• Commit length configuration: Admins can configure the maximum total length of commits to scan, with larger commits truncated. This can be set via the repo_scan_max_commit_length preference on the Preferences page.

Self-Hosted​

• Helm: The ReplicatedSDK image is now pulled from the Replicated registry instead of Docker Hub. For airgap installations, ensure you update your automation processes for pulling and pushing images to your private registry. For more information, refer to the Airgap Installation page.
• Installation and upgrade: Improved error messages for partially initialized databases, providing clear instructions to check logs and ensure the PostgreSQL database is empty before retrying.
• Admin Area: Introduced a Periodic Tasks page to adjust schedules and fine-tune periodic task execution.
• Queues: Merged the secrets_checks queue with the background validity checks queue to optimize performance.

Fixes​

• Secrets:
  • Check runs: Updated messages to note flagged secrets lack commit references and remain compromised once leaked.
  • Validity check: Fixed an issue where the tooltip incorrectly indicated a token was valid for all endpoints when it was valid for only one.
• Sources:
  • GitLab: Enable viewing of more than 50,000 GitLab projects in the integration settings.
• Alerting:
  • Jira issue tracking: Fixed an issue where line feeds (\n) were not properly translated to hardBreak nodes, ensuring correct spacing in Jira tickets.
• Self-Hosted:
  • Admin area: Corrected sorting and filters on the Worker Tasks page for improved usability.

Hotfixes​

2025.1.1​

  Release Date: January 23, 2025

Fixes​

• Self-Hosted:
  • Embedded cluster installation:
    • Fix an issue where the GitGuardian dashboard returns a 404 error. Note this fix does not apply to legacy embedded clusters using Kurl.
    • Resolved the inability to deploy an embedded cluster with a custom CA.
  • Helm:
    • Fixed a 404 error on the /metrics endpoint for fetching GitGuardian applicative metrics on Webapp pods and Celery workers.
    • Fixed Replicated RBAC resources being created despite rbac.enabled: false in Helm values, causing issues in RBAC-restricted environments.

Browse all past GitGuardian Self-Hosted releases, feature updates, and hotfixes below.

2024.12.1​

Bug fixes​

• Jira Issue tracking integration: Fixed an issue where the project page did not display any items.
• SCA: Removed SCA from the left bar menu, which was incorrectly displayed for Managers.

2024.12.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to version 2.127.0:

  • Added 7 detectors:
    • X-API-Key Secret
    • Azure Functions App Key Header
    • Azure Functions App Key Query Parameter
    • Jenkins API token
    • chpasswd Username Password
    • Nessus Agent Key
    • Statsig Server Secret Key
  • Modified 1 detector:
    • FTP credentials assignment

• Secret pattern exclusion: This feature allows users to define patterns and therefore hide any secret matching the pattern defined. Secret pattern can be applied to all repositories or a defined set of repositories. It provides greater control over exclusion rules, allowing for more precise management of incidents. Learn more.

• Jira Data Center integration: Jira Data Center integration is now supported for real-time secret detection and honeytoken detection. For more details, refer to the documentation here.

Platform​

• Jira Data Center issue tracking integration: We now support Jira Data Center integration for issue tracking. This feature includes:
  • automatic creation of a Jira issue as soon as a new incident is triggered,
  • management of Jira custom fields,
  • and an auto-resolve feature that marks the incident as resolved in your dashboard when the issue is closed in Jira. More information available in the documentation.
• GitLab integration: Added the ability to configure an instance-level GitLab integration using a read-only admin token. However, since the token lacks permissions for creating system hooks, manual setup is required. Learn more.
• Check runs: Added the option to improve your code security by enabling GitGuardian check runs on their GitHub forked repositories. Learn more here.
• VCS integration: Workspace Managers can now disable automatic repository monitoring in GitGuardian, giving you more control when adding new repositories to your perimeter. For an example, see GitHub integration.

Self-Hosted​

• Helm: front.ingress has been renamed ingress to improve consistency and standardize the ingress object across the Helm chart. ⚠️ This release includes breaking changes. Upgrade to 2024.12.0 using the upgrade notes.
• Cluster management: Replaced the nginx container with Ingress support, compatible with several controllers (ingress-nginx, traefik, contour, aws_alb, openshift, istio). This feature is optional and disabled by default. For more details, refer to the ingress page.
• Admin Area: Added a Worker Tasks page for monitoring task activity and worker usage to help optimize scaling and performance.
• Applicative Metrics: Added the following metrics: gim_periodic_task_period_seconds, gim_periodic_task_not_run_for_seconds, gim_check_runs_long_running, gim_health_check_result_count, and gim_outdated_health_check_count for better monitoring and insight. For more details, refer to the Applicative metrics page.
• Support Bundle: Enhanced diagnose_instance to include celery worker data.
• KOTS: Minor UI updates to the KOTS Admin Console, replacing radio buttons with dropdowns in some cases.
• Historical Scan: Added minutes_between_scans_per_source in the preference table.
• License: The license check is now managed by the ReplicatedSDK for all installation types, replacing the previous reliance on KOTS for this function in KOTS installations.

Bug fixes​

• Health Check: Fixed issue where health checks were run for all GitHub installations. Now only the first installation is checked.
• License: Corrected license info display in the Admin Area for Helm installations.
• Historical Scans: Categorized certain unknown scans that should have been identified as timeout failures.

Deprecation notice​

• Policy breaks: Starting with the 2024.12 version, the Policy Breaks module will be removed from your dashboard as we enhance our focus on our core Secrets Security offering.
  Deprecating the Policy Breaks module will not affect your overall security coverage; it will only reduce the number of alerts you receive. Previously, alerts for Policy Breaks incidents (such as an exposed .env  file) required manual investigation to determine if they contained secrets. Our “Secrets detection” module already handles the detection, incident creation, and alerting for these secrets.

2024.11.2​

Bug fixes​

• Performance: Fixed an issue to retrieve the memberships, which sometimes lead to "504 Gateway Time-out" errors.
• Tasks Management: Fixed an issue in Celery where database connection errors were not properly handled, leading to errors while handling tasks in rare cases.

2024.11.1​

Bug fixes​

• Historical Scan: Resolved an issue where historical scans failed due to the repository size being represented as a float instead of an integer.
• License: Resolved an issue with the Replicated license (impact limited to GitGuardian internal operations).

2024.11.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to version 2.125.0:

  • Added 5 detectors:
    • BitBucket App Password
    • Cloudflare Tunnel Credentials
    • InfluxDB Token
    • InfluxDB Token with Host
    • Rails Master Key Assignment
  • Modified 5 detectors:
    • Generic CLI Option Secret
    • MongoDB CLI Credentials
    • MySQL CLI Credentials
    • PostgreSQL CLI Credentials
    • Redis CLI Password

• Confluence Data Center integration: Confluence Data Center integration is now supported for real-time secret detection and honeytoken detection. For more details, refer to the documentation here.

Platform​

• ServiceNow integration: This new issue tracking integration allows to create ServiceNow issues from GitGuardian incidents. The feature includes the following:

  • possibility to create a ServiceNow issue directly from a GitGuardian incident;
  • possibility to automate the creation of a ServiceNow issue for any new GitGuardian incident;
  • auto-resolve setting to mark the incident as resolved in your dashboard when the issue is closed in ServiceNow.

  Follow our documentation to configure the integration.

• Check runs: GitHub's custom properties can now be leveraged to override the GitGuardian global configuration of check runs. This allows customization at both the repository and organization levels. For more details, please refer to our dedicated documentation.

• Historical Scan: New "Bulk Historical Scans Management" page for easy tracking, filtering, and detailed insights on all scans.

• Members: You now have the option to deactivate a member instead of deleting them. For more details, refer to our documentation.

• API:

  • All Sources endpoints now require specific scopes for access. The new sources:read scope is required for all GET endpoints to retrieve source information, while the sources:write scope is required for the PATCH endpoint to update a source's attributes, monitoring status, and business criticality.
  • A new parameter, send_email: true|false, is now available on endpoints that trigger an email notification, such as when an invitation is created. This allows you to determine whether an email should be sent when using these endpoints. By default, if the parameter is not specified, the email will be sent.

Self-Hosted​

• Helm:

  • Replace the legacy parameter replicated.images.replicated-sdk with the new parameters replicated.image.repository and replicated.image.tag. ⚠️ This release includes breaking changes. Upgrade to 2024.11.0 using the upgrade notes.
  • Added replicated.privateCASecret parameter to specify a custom CA when using a proxy. Learn more.

• Health Check: Distribute health checks over time rather than executing them simultaneously. This reduces system load, avoids bottlenecks, and enhances monitoring accuracy.

  ⚠️ The settings.healthCheck.periodicInterval in the Helm chart is now deprecated and replaced by spread_periodic_range_minutes in the admin area.

• Applicative Metrics: If you are using Prometheus to export GitGuardian metrics or to leverage our autoscaling capabilities, and your installation type is KOTS, ensure that you update the Kubernetes Application RBAC by adding the patch permission to the servicemonitors resource.

Bug fixes​

• Incidents: Notify team leaders only when a valid secret is intentionally ignored.
• Perimeter: Fixed inaccurate historical scanning statistics displayed on the side panel of the perimeter page.
• Historical Scans:
  • Fixed UI count on the perimeter page so that "sources successful" now shows the total count of monitored sources, regardless of failed or unscanned sources.
  • Standardized the date format for start and end dates in the status tooltip.
  • Corrected the repo size display in the status tooltip.
• API: Resolved an issue where an error was raised if the IP address could not be found, even when the IP allowlist setting was disabled. This occurred in an on-premises instance, causing the PAT endpoint of the public API to become non-functional.
• Proxy: Support HTTP proxy when customCA is used for the Replicated SDK used for license management and telemetry collection. Nothing to do if you are using KOTS, if you are using helm, set isAirgap to false and configure your HTTP proxy following the example.

2024.10.2 - Required​

Bug fixes​

• Cluster Management: Added an option to disable server side Postgres cursors (for better PGBouncer compatibility).

2024.10.1​

Bug fixes​

• Secrets detection engine: Resolved an issue where GitLab keys for disabled accounts were incorrectly flagged as valid.

2024.10.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to version 2.122.1: Enhance recall and coverage while expanding the range of detectable secrets with new and updated detectors.
  • Added 3 detectors:
    • Atlassian Access Token
    • Bitbucket Access Token
    • Mistral AI API Key
  • Modified 1 detector:
    • Base64 Generic High Entropy Secret
• VSCode extension: We are excited to announce the release of GitGuardian CLI (ggshield) as a VS Code extension! Files are now automatically scanned upon saving, with detected secrets highlighted in your code and listed as warnings. Additionally, custom remediation messages are provided within your IDE to guide you in resolving any issues efficiently. Download from the marketplace

Platform​

• Occurrence grouping: Added ability to group secret occurrences per secret x source, allowing separate secret incidents for the same secret found in different sources. This enhances remediation processes tailored to your company's data privacy policies. Learn more.
• Filepath exclusion: File path exclusions are now applicable to one or more repositories. By targeting file path exclusions to specific repositories, users can significantly reduce the number of irrelevant incidents, enabling more accurate incident management. Learn more.
• Saved views: Saved views can now be created in the Honeytoken module.

Self-Hosted​

• Certificate-based authentication: Introduced support for multi-authentication alongside certificate-based authentication and Certificate Revocation List (CRL). For more details, see the documentation here.
• New Embedded Cluster Install (Early Access): Installation is now 4x faster, improving the proof-of-concept experience. Simplified management of Kubernetes, KOTS, and app updates streamlines maintenance. More information in the Embedded cluster V2 page.
• Cluster Management:
  • ⚠️ Before upgrading GitGuardian, you must upgrade to KOTS version 1.117.3 or later for optimal performance and compatibility.
  • Removed resources limits for Postgres and Redis on the Embedded cluster installation.
  • Added two new worker types long-ods (Productivity tools such as Slack, Jira Cloud, Confluence, ...) and long-ods-io (long tasks specialized in Input/Output).
• Historical Scan: Added minutes_between_scans_per_source in the preference table.
• Teams: Added max_teams in the preference table.

Bug fixes​

• Personal access token: Resolved a bug to ensure the lifetime of a newly generated personal access token is strictly less than the maximum permissible duration.
• Validity check: Fixed GitLab checker wrongly marking some secrets as valid by improving token validation (impacting custom host validity checks).

2024.9.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to v2.120: Enhance recall and coverage while expanding the range of detectable secrets with updated detectors.

  • Added 2 detectors:

    • Generic Password YAML
    • Buildkite API Token V2

  • Modified 6 detectors:

    • Generic Database Assignment
    • Base64 Generic High Entropy Secret
    • Generic Password
    • Username Password
    • DigitalOcean Spaces Keys
    • reCAPTCHA Key

    Note concerning the reCAPTCHA Key detector: Due to changes in the behavior of some Google APIs, we are no longer able to ensure the validity of reCaptcha keys. As this detector could be quite "noisy" the validity of the keys was a mandatory prerequisite in the detection flow and this can no longer be the case. We have however improved this detector to be as efficient as possible.

• Validity check: Specify the host of your own provider instances for GitGuardian to perform validity checks and obtain the exact validity information. For example you can perform a validity check for a GitLab token secret against your own GitLab instance. For more details, refer to our dedicated documentation.

Platform​

• GitGuardian CLI (ggshield) custom remediation message: Admins can now customize remediation messages at pre-commit, pre-push or pre-receive stages and provide to developers useful guidance on how to use internal Vaults etc ... See documentation here.
• Historical Scan: Streamline source management with new filters for failure reasons, instances (e.g. prod/staging), and last scan date.

Self-Hosted​

• Horizontal Pod Autoscaling (HPA): Dynamically scale worker pods based on application load, reducing infrastructure costs and optimizing resource usage. Learn more in the Scaling page. Exclusive to the new architecture.
  
• Kubernetes Version Support: GitGuardian now supports Kubernetes version 1.30. More information in the System requirements page.
• Historical Scan: Removed is_repo_size_controlled (redundant with repo_scan_size_limit) in the preference table.
• Support Bundle: Improve troubleshooting by adding an option to customize the maximum amount of logs captured for Helm and KOTS installations.

Bug fixes​

• Jira Cloud Alerting: Fixed an issue where the assignee dropdown in Jira template creation was incomplete for projects with a large number of assignees due to pagination limits.
• Historical Scan: Improved handling of pending states and fixed an issue where sources were reaching the timeout limit.
• API: Corrected the pagination link in the header to use HTTPS instead of HTTP when querying the API.
• Helm preflights: Fixed an issue with Redis and PostgreSQL preflight checks where passwords containing special characters were not functioning correctly.

2024.8.2​

Bug fixes​

• Cluster Management: Resolved an issue where the Scanner pod was spawning zombie processes (legacy architecture).

2024.8.1​

Bug fixes​

• Cluster Management: Resolved an issue where the Scanner pod was spawning zombie processes (new architecture).
• Historical Scan: Resolved an issue with the formatting of days in the last scan duration on the perimeter page.
• Secrets detection engine: Due to changes in the google reCAPTCHA API, the checker for reCAPTCHA key detector has been removed and the detector has been updated to remove false positives.
• Helm preflights: Resolved an issue with Redis preflights where passwords containing special characters were not properly URL encoded.

2024.8.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to version 2.117: Enhance recall and coverage while expanding the range of detectable secrets with new and updated detectors.

  Added 3 detectors

  • JetBrains TeamCity config value
  • Serpapi Token
  • Tavily API Key
  Modified 3 generic detectors

  • Base64 Generic High Entropy Secret
  • Base64 Generic High Entropy Secret
  • Generic Password
  Modified 78 specific detectors

  We have enhanced our approach to searching for the prefix linked to the secret, considering more complex scenarios. This allows us to improve recall.

  
  

  • Adafruit IO API Key
  • Airtable API Key v2
  • Alchemy API Key
  • Amazon MWS Token
  • Checkout.com Sandbox API Secret Key
  • CircleCI Personal Token
  • Claude API Key
  • Clojars Deploy Token
  • Cloudinary API key URL
  • Contentful Content Management API Key
  • DigitalOcean OAuth Application Token V1
  • DigitalOcean Personal Access Token V1
  • DigitalOcean Refresh Token V1
  • Discord Webhook URL
  • Docker Swarm Join Token
  • Docker Swarm Unlock Key
  • EasyPost API Key
  • Firebase Cloud Messaging API Key
  • Figma Personal Access Token
  • Flutterwave API Key
  • Frame IO Token
  • GitHub fine-grained personal access token
  • GitHub Oauth Access Token
  • GitHub Personal Access Token
  • GitHub Server-to-server Token
  • GitHub User-to-server Token
  • GitLab Token
  • Grafana Cloud API Key
  • Grafana Service Account Token
  • Groq API Key
  • Heartland API key
  • Langchain API Key
  • Linear API Key
  • Base64 Midtrans API Key
  • Notion Integration Token
  • npm Token Prefixed
  • Nylas API Key
  • OpenAI Project API Key
  • Paystack Key
  • Plaid Access Token
  • PlanetScale OAuth Token
  • Postman API Key
  • PubNub Publish Key
  • Readme API Key
  • Riot Games API Key
  • RubyGems.org API Key
  • Samsara API Key
  • SendinBlue Key v3
  • Sentry Org Auth Token
  • Sentry User Auth Token v2
  • Shippo API token
  • Shopify Generic App Token
  • Shopify Private App Token
  • Slack App Token
  • Slack Configuration Refresh Token
  • Slack Configuration Token
  • Slack User Token
  • Sourcegraph Access Token v3
  • Sourcegraph Enterprise subscription Token
  • Sourcegraph License Key Token
  • Sourcegraph Access Token v2
  • Sourcegraph User Gateway Access Token
  • Sqreen Token
  • Square Access Token
  • Stripe Webhook Secret
  • Tailscale API Key
  • Tailscale OAuth Key
  • Tailscale Pre-Authentication Key
  • Tailscale SCIM Key
  • Tailscale Webhook Key
  • Typeform API Token
  • Ubidots Token
  • Vercel Blob Token
  • WakaTime API Key
  • WePay token
  • Yandex Predictor API Key
  • Zillow Key
  • Zuplo API Key

• API Enhancements: User feedback on secret incidents is now accessible via the API, providing better incident management and insights. This information is included in the feedback_list field within the secret incidents' payload.

• Incident Notifications: Team managers will receive email notifications when incidents with valid secrets are ignored, ensuring critical issues are not overlooked.

• Weekly Email Recap: New section displaying ignored incidents with valid secrets, improving visibility and actionability for security teams.

Platform​

• Saved views: You can now save your most frequently used filters as views for quicker access. Learn more about about saved views here.
• Historical Scan Enhancements: These enhancements provide better visibility and management of the scanning process. They include progress estimation for both individual and bulk scans, along with comprehensive scan status details such as size, duration, start/end dates, number of commits, branches, queue duration, and more.
• Health Check: Let managers manually start health checks from the GitGuardian dashboard so they can address any failed checks immediately without waiting for the next scheduled run.
• GitLab integration: Upon installing a new integration for GitLab Community Edition, it is now possible to skip the historical scan (to launch it manually later).
• Teams: Get simplified team management with a clear designation of team leaders. Changing "can_manage|cannot_manage team permissions" to a "team leader" boolean attribute to designate the team owner. ⚠️ The team_permissions field has been deprecated and replaced by the is_team_leader field in our API for the endpoints /v1/teams/{team_id}/team_memberships and /v1/teams/{team_id}/team_invitations.

Self-Hosted​

• Certificate-based authentication: Support for CAC or PIV cards, enhancing security for organizations with strict authentication requirements. For more information, see the documentation here. This feature is available upon request and is exclusive to the new architecture.
• Helm: You can now customize the rolling upgrade strategy with the updateStrategy parameter, providing greater control over deployments. More info on the upgrade page.
• Cluster Management:
  • Productivity tools (such as Slack, Jira Cloud, Confluence, ...) tasks are now defaulted to the worker-worker node in KOTS installations, with the option to scale using dedicated workers. More info on the Scaling page.
  • Added user input validation in KOTS configurations to prevent errors and improve user experience.

Bug fixes​

• API: Fixed an issue where a 502 error returned HTML instead of a JSON response in the legacy architecture.
• Health Check: Corrected the error code for Slack refresh token errors.
• SSO: When force-SSO is deactivated but SSO is configured, users now have the option to log in via SSO in the invitation email.
• Audit Logs: Resolved missing audit logs for Scan All operations.
• SMTP Configuration: Fixed an issue with sending emails using an SMTP server with a custom CA.
• Incident: Fixed an issue in the commit cache preventing incidents from being raised in some cases.

2024.7.0 - Required​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Confluence Cloud integration: Now supports real-time secret and honeytoken detection for seamless security.
• Secrets detection engine upgrade to version 2.115: Enhance recall and coverage while expanding the range of detectable secrets with new and updated detectors.
  • 4 detectors added: Sentry Org Auth Token, Sentry User Auth Token v2, Slack Configuration Refresh Token, Slack Configuration Token
  • 5 detectors updated: Equinix Authentication Token, Sentry User Auth Token v1, Signifyd API Key, Slack Bot Token, Slack User Token
• Incident details: Added a 'per page' selector on the occurrences table for improved navigation.
• Historical Scan:
  • Skip historical scan of unchanged repositories since the last scan to save time and resources.
  • Filter and sort repositories by scan duration on the Perimeter page for better management.
  • Introduced pending_timeout status in the API to differentiate between scans failing due to timeouts (timeout) and those in the queue (pending_timeout).

Platform​

• Members: Renamed 'role' to 'access level' for clarity.
  ⚠️ The role field has been deprecated and replaced by the access_level field in our API for the endpoints /v1/members and /v1/invitations.
• Health Check: Moved the periodic_interval preference to the KOTS Admin Console or Helm value file.

Self-Hosted​

• Helm: Standardize existingSecret across the Helm chart to ensure uniform configuration for Redis Sentinel, Ingress, and CustomCA. ⚠️ This release includes breaking changes. Upgrade to 2024.7.0 using the upgrade notes.
• Cluster Management:
  • New embedded cluster installations now use PostgreSQL 16 for better performances and security. Follow the migration guide to migrate your existing embedded cluster to PostgreSQL 16.
  • Reorganized KOTS Admin Console configuration for better clarity, including moving the TLS certificate configuration to its own section.
  • Added a pre-deploy job check to ensure asynchronous migrations are complete before upgrading to a new version.
  • Included missing scaling parameters webapp-internal_api and webapp-public_api in KOTS Admin for the new architecture.
• API: Removed monthly sliding quotas for API calls in the preference table.
• Applicative Metrics: Removed gim_version_info and added the following metrics: gim_celery_queue_length, gim_celery_active_consumer_count, gim_repo_scan_active_statuses_total, gim_http_request_started_total, gim_http_request_success_total, and gim_http_request_failure_total for better monitoring and insight. For more details, refer to the Applicative metrics page.

Bug fixes​

• Filepath Exclusion: Fixed a bug causing the * character in exclusion patterns to match at least one character instead of zero or more.
• Check Runs: Added an optional Skip action for check runs on forked repositories that detect secrets, preventing a complete blockage for developers.
• Argo CD: Fixed the upgrade-path-check tool to ensure unskippable versions are not bypassed during upgrades.
• API: Corrected the base URL in the API documentation for new architecture installations.
• KOTS: Fixed an error with preflights failing due to "Analyzer Failed file secrets/default.json was not collected".

2024.6.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine upgrade to version 2.114: Enhance recall and coverage while expanding the range of detectable secrets with new and updated detectors.
  • 14 new detectors added: Nylas API Key,Sourcegraph Access Token v3, Duplo Cloud API Key,Fernet Key, Vercel Blob Token, 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, WakaTime API Key
  • 14 detectors updated: Base64 Generic High Entropy Secret, Generic Database Assignment, Generic High Entropy Secret , PostgreSQL CLI Credentials, Postgres assignment attached port, PostgreSQL Pgpass Credentials, PostgreSQL URI, Sourcegraph Access Token v2, Yelp API Key, Google Gemini API Key,Sentry Token, Generic Database assignment, Generic FTP Assignment, Generic Username Password
• Incidents details: merge commit authors from GitHub are now identified. It is not retroactive.
• Incidents: periodic secret validity checks enable for ignored incidents. See documentation here.
• GitLab integration: when a GitLab webhook is found disabled, GitGuardian now attempts to reactivate it automatically (by sending a test payload) before triggering an error message.
• API: new endpoint to query the secret incidents of a source.
• Filepath exclusions: when adding a new rule, show how many new secret incidents will be hidden by the new filepath exclusion, without recalculating existing hidden incidents.

Platform​

• Health Check:
  • implement periodic health checks on all integrations type (VCS, Messaging, Ticketing, Documentation) to run every hour, with the frequency being configurable in the Admin Area.
  • send email notifications when a integration health check fails. For further details, refer to the Configure email preferences page. Note that the notification is not enabled by default for existing accounts and must be turned on manually.
• Audit Logs:
  • introduce audit logs for actions in the Admin Area visible only for promoted-admin users.
  • alert in the event of an audit logging process failure. More information is available on the email alerts for audit log failures page.

Self-Hosted​

• Cluster management:
  • Kubernetes 1.30 is now under experimental support.
  • you have now the ability to use a load balancer in front of an embedded cluster installation, for further details, refer to the Load balancer page.

Bug fixes​

• Jira Cloud Alerting: fix an issue where Jira automatic configurations remained invisible to 'member' role users within the 'All Incidents' team, ensuring uniform visibility across teams.
• API:
  • fix a problem causing conflicting information between the UI and the API regarding team permissions.
  • fix an incorrect self-hosted instance URL in the API documentation.
• Historical scan: attribute automatic historical scans of new repositories to "GitGuardian Bot" in audit logs.
• Cluster management:
  • add missing readiness/liveness probes in gitguardian-app pods in the legacy architecture.
  • fixed issue preventing bundle generation in Openshift environments.

2024.5.1​

Bug fixes​

• Custom webhook: fix a bug sending notifications for deactivated secret detectors.
• Helm: fix an issue with the upgrade-path-check job failing on OpenShift cluster due to RBAC resource creation order.

2024.5.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine: upgrade to version 2.111 with the addition of 7 new detectors (Dropbox Key, Midtrans API Key, Sanity Token, Zuplo API Key, Grafana Cloud API Key, Groq API Key, Nx Cloud Token) and the improvement of 4 detectors (Artifactory Token, GoCardless API Key, Plivo Auth Tokens, Generic High Entropy Secret)
• Secrets detection engine: Generic CLI Secret and Generic Database Assignment detectors are now supported and active by default for data sources other than VCS.
• Jira Cloud Issue tracking integration: introduction of a new version of our Jira Cloud integration for issue tracking. It now offers
  • automatic creation of a Jira issue as soon as a new incident is triggered,
  • management of Jira custom fields,
  • and an auto-resolve feature that marks the incident as resolved in your dashboard when the issue is closed in Jira Cloud. More information available in the documentation.
• Check runs: a comment is posted on the pull request when a secret is uncovered.
• Historical scan: improve historical scan status overview on the perimeter page side bar.

Honeytoken​

• Context creation strategies for honeytoken deployment jobs now allow to choose only dynamic contexts.

Platform​

• Privacy mode: this (mode) allows to obfuscate secrets and other sensitive information on the GitGuardian UI.
• Filters: the history of AI queries can now be deleted.
• API: the workspace_id is now included in the payload of API tokens.

Self-Hosted​

• Argo CD: we officially support Argo CD, please refer to the Argo CD specifics page to learn more.
• Helm:
  • ⚠️ This release includes breaking changes. Upgrade to 2024.5.0 using the upgrade notes.
  • add istio.gateway.enabled parameter to be able to disable Istio Gateway handling when Istio is enabled.
  • give the ability to specify dedicated labels and podLabels for migrations resources.
  • give the ability to customize the RefreshInterval parameter for externalSecrets.
  • it is now possible to set the initial admin password in an existing secret.
• Cluster management:
  • GitGuardian currently supports PostgreSQL 13 to 16 (previously, versions 15 and 16 were experimental).
  • Check CA validity during preflight for both KOTS and Helm installation. If you previously installed GitGuardian on an existing cluster and planning to upgrade to 2024.5.0, you must modify the rule for the core api group in your configuration by adding:

    - apiGroups: [""]
        resources: ["events"]
        verbs: ["list"]
    

    Refer to the Kubernetes Application RBAC page.

Bug fixes​

• GitLab integration:
  • fix an issue where the installation status was incorrectly displaying as 'no longer monitored' in the tooltip, despite being actively monitored.
  • when re-enabling a disabled webhook in GitLab, the error on the GitGuardian dashboard is now cleared automatically within 20 minutes.
• Filters: the "per-page" selection for each table is now persisted.
• API: correct a bug that allowed members to view sources they should not have been able to access when using the /sources endpoint.
• Check runs: fix a bug that is causing related incident IDs to be missing in the check run summary.
• Cluster management:
  • rename celeryWorkers.realtime_ods to celeryWorkers.realtime-ods.
  • ensure consistent naming for pre-post release jobs throughout the application lifecycle, preventing pod accumulation.
  • introduce Time-to-Live (TTL) functionality to remove pre-post jobs after 30 days.
• Helm: fix an issue when Helm installation using a custom CA fails when pod security policy is enforced.

2024.4.2​

Bug fixes​

• Check runs: display accurate error message when a check run fails due to rate limiting.

2024.4.1 - Required​

Bug fixes​

• Bitbucket integration:
  • fix an issue where uninstalling a Bitbucket project inadvertently occurred when a token was removed, despite other valid tokens being present.
  • enhance logging mechanisms surrounding Bitbucket token operations for better troubleshooting.
• Azure repos integration: fix a problem with updating a repository when the token is either invalid or missing.
• Cluster management:
  • fix an issue where the no-proxy list wasn't correctly applied for KOTS installation.
  • add missing debug image to the KOTS airgap bundle.
• Migration new architecture: fix an issue occurring when the KOTS admin password contains special characters.
• Prometheus exporter:
  • fix error 500 from the /metrics path of the exporter when using AWS Elasticache Redis.
  • fix RBAC error occurring when activating GitGuardian Prometheus exporter in the new architecture with KOTS. If you previously installed GitGuardian on an existing cluster you must modify the rule for monitoring.coreos.com in your configuration. Refer to the Kubernetes Application RBAC page.

    - apiGroups: ['monitoring.coreos.com']
      resources: ['servicemonitors']
      verbs: ['get', 'list', 'watch', 'create', 'update', 'delete']
    

2024.4.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Jira Cloud integration: Jira Cloud integration is now supported for real-time secret detection and honeytoken detection.
• Secrets detection engine: upgrade to version 2.109 with the addition of 5 new detectors (Snowflake API credentials, Replicate User Access Token, Workato API Key, Azure Open AI API key, Kubernetes Docker Secret) and the improvement of 7 detectors (Rails Master Key, Generic password, Generic High Entropy secret, GitLab Token, Google API Key, Okta Keys, Slack Bot Token)
• Incidents: it is now possible to filter on Occurrences count.
• Incidents details: introduction of a secret identity card on each secret incident detail page.
• Check runs: skip actions are now aligned with the ignored reasons (false positive, test credential, low risk). Tags (Tagged as [false positive|test credential|low risk] in check runs) are added to the corresponding secret incident when this action is taken.
• API: the breakdown of secret incidents by severity is displayed in the payload of the sources.

Honeytoken​

• Honeytoken deployment jobs: automate the deployment of honeytokens in your code repositories from GitLab, GitHub and GitHub Enterprise Server! This is a business-only feature. Read more about Deployment jobs in our documentation.

Self-Hosted​

• Helm:
  • to ensure your existing cluster meets the Gitguardian's requirements, you can run our new preflight script.
  • add version check before Helm upgrade to ensure no required versions are skipped. If using a private registry for deployment, make sure to download the new image helm-tooling.
• Helm Chart:
  • add custom labels to differentiate multiple GitGuardian deployments within the same Kubernetes cluster. Refer to commonLabels in Helm Chart Values. Example:

    commonLabels:
      env: staging
    

  • add an option to use Generic Ephemeral Inline Volumes for all worker pods. For further details, refer to the Scalling page.
• Scaling: a new pod called worker-realtime-ods was added in the new architecture. If Slack or Jira Cloud scanning isn't needed, set its replicas to 0 to save resources via your Helm value file or the KOTS Admin Console.
• Health Check: remove VCS health checks from the Admin Area, now available under Settings > Workspace > Integrations.

Bug fixes​

• Jira integration: fix an issue that was hindering the assignment on JIRA tickets upon creation.
• Audit log: correct the logs related to the creation and removal of teammates through the API.
• Cluster management:
  • add missing links to KOTS Admin Console for embedded cluster in the Admin Area.
  • fix an issue with the KOTS preflights in the legacy architecture for embedded installation when an ElastiCache Redis instance is configured with TLS enabled.
  • set default number of replicas for scanner_ods pod to 0 for legacy architecture running on openshift.

2024.3.2​

Bug fixes​

• GitHub integration: fix an issue where managers and owners were unable to add new GitHub sources to the dashboard.
• Check runs:
  • improve error collection on check runs.
  • fix an issue where GitHubNotFound errors prevented the completion of check runs.

2024.3.1​

Bug fixes​

• Incidents: resolve a bug triggered by secret incidents detected by custom detectors, causing the incidents list to fail to load.
• GitLab integration:
  • fix GitLab installation check task issue affecting system hook installations.
  • fix an issue with sending emails to users who are no longer token owners within the GitLab installation.

2024.3.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Slack integration: Slack integration is now supported for real-time secret detection and honeytoken detection on Self-Hosted.
• Secrets detection engine: upgrade to version 2.106 with the improvement of 3 detectors (Generic Password, Generic High Entropy Secret, Base64 Generic High Entropy Secret).
• Secret SLAs: add the "First detected" date in incidents details and the associated filter in the Secret incident dashboard.
• Incidents:
  • tags are exposed in the All occurrences CSV report.
  • a new filter on "Occurrences count" is available
  • enable AI filter via the ai_filters_enabled option in the preferences.
• Check runs: add check_runs_overrides_labels_ghe option in the preferences to enable overriding the check run settings with repository labels on GitHub Enterprise Server.

Platform​

• Health Check: introduce tracking for last execution and last success times, refine error messaging, and adopt non-HTTP status codes.

Self-Hosted​

• Images: GitGuardian images are now signed with Cosign, exclusive to the new architecture.
• Kubernetes Version Support: GitGuardian now supports Kubernetes versions 1.28 and 1.29 (experimental). More information in the System requirements page.
• Cluster management:
  • support for air gap installation in KOTS during installation in the new architecture.
  • support for snapshots with velero for KOTS install in the new architecture.
  • update Kubernetes version to 1.28 for embedded cluster. For further details, refer to the Upgrade page.

Bug fixes​

• Incident details: fix an issue on the git patch restricted visibility feature that was preventing members from seeing the patch they were involved in based on email matching.
• GitHub integration: performance improvement when a lot of repositories are added at the same time.
• GitLab integration:
  • fix an issue where the GitLab instance URL was incorrectly displayed instead of the GitLab token name.
  • remove the "Check Again" button from the health check for users on the Free plan.
• Bitbucket integration: improve handling of token revocation to prevent issues when a repository changes ownership.
• Cluster management:
  • preflight checks now confirm support for Redis version 7.
  • remove the link to the KOTS Admin Console from the Admin Area for existing cluster installations (both Helm and KOTS). For further details, refer to the Access to the Admin Area page.
  • set default number of replicas for scanner_ods pod to 0 for new architecture.
  • fix an issue with the periodic task related to the database encryption key rotation.
• Helm Chart: add missing podAnnotations in webapp object definition.

2024.2.1​

Bug fixes​

• Incident: fix an issue with validity check failure hitting a timeout in some specific cases
• Cluster management: fix an issue with KOTS preflights failing with PostgreSQL or Redis with TLS enabled
• SMTP configuration: make the option to support SMTP servers using a self-signed certificate permanent. More details in the Configure the email system page.

2024.2.0​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine: upgrade to version 2.105 with the addition of 7 new detectors (Square Token, Bunny.net API Key, Hugging Face user access token, CircleCI Project Token, Claude API Key, Grafana Service Account Token With Host, Klaviyo API Key) and the improvement of 8 detectors (Beamer API Key, NuGet API Key, Paypal OAuth2 Keys, Twitter Tokens, CircleCI Personal Token, Django Secret Key, Generic High Entropy Secret, Heroku Platform Key).
• Incidents: exporting CSV secret incidents now allows changing the separator used, comma (default) or tab. More details in the Export data section of the documentation.
• Incident details: update of the default remediation workflow.
• Check runs:
  • the preview of the "How to remediate" instructions in markdown is enhanced when you customize them.
  • the incident status is displayed in the GitHub check run details.
  • improve causes of errors transparency and timeouts in the check run summary.
  • is_actionable_checkrun_enabled preference in the Admin area is deprecated. Action buttons on checkruns are now enable by default.
• Custom detectors: improve error messages for invalid regex when requesting a custom detector.
• GitHub integration: add commit_collector_max_workers option in the preferences to use more workers to collect commits.
• GitLab integration: we now detect and notify by email and raise a health check error when a GitLab group hook was disabled by GitLab, causing the monitoring not to work anymore.
• Azure repos integration: improvement of the billing metrics. You now must check the Graph:Read scope in your Personal Access Token. More information in our VCS integrations documentation.

Platform​

• SSO: the option 'Force SSO' applies to owners as well when enabled. More details in the Force SSO section of the documentation.

Self-Hosted​

• Cluster management:
  • add support of HTTP proxy setup in KOTS and Helm installs in the new architecture. More details in the Configure a proxy server page.
  • add support Redis Sentinel in KOTS and Helm installs in the new architecture.
  • add support of multiple CA certificates concatenated in KOTS install in the new architecture.
• Helm Chart: replace deprecated v1alpha1 API version of External Secret Manager with the latest version v0.9.11.
• Applicative Metrics: rename appExporter to webAppExporter and celeryExporter to statefulAppExporter in the Helm-based Prometheus activation. For more details in the Applicative metrics page.
• SMTP configuration: provide an option to support SMTP servers using a self-signed certificate. More details in the Configure the email system page.

Bug fixes​

• Force SSO activation: fix an issue where authentication page “Force SSO Toggle” enabled “By default to all incident team” toggle as well.
• GitLab integration: fix an issue where revoked tokens weren't detected as such if not actively used by a configured GitLab group.
• GitHub integration: disable repositories are now marked as such when searching GitHub integrations.
• Bitbucket integration:
  • correct failure message and re-check button when the Bitbucket integration stops working.
  • syncing installs with a new token now correctly retains projects linked to the old token, preventing unintended deletion of all projects.
  • adds a default timeout to all requests made by the Bitbucket client.
• Cluster management:
  • fix a "failed to verify certificate" error when a proxy is configured in the KOTS config during a migration.
  • adjusted embedded cluster settings: system time zone to UTC, maximum database connections to 500, and idle timeout to 1 hour.
  • fix an issue with liveness probes failing.
• Historical scan: fix an issue with missing audit logs for historical scans.

2024.1.3 - Required​

Bug fixes​

• Cluster management:
  • remove the rqlite DB data dump from support bundles generated by KOTS.
  • fix migration by using specific models, avoiding variable external dependencies.
  • enable ability to perform the database encryption key rotation in the Admin area.

2024.1.2​

Bug fixes​

• Bitbucket integration: fix an issue which revoke the access token when the project only has read permission.

2024.1.1​

⚠️ Check the Helm values file changes from the previous version here.

Secrets Detection​

• Secrets detection engine: upgrade to version 2.102 with the addition of 8 new detectors (Base64 AWS IAM Keys, Base64 AWS SES Keys, Readme API Key, Tailscale API key, Tailscale oauth key, Tailscale pre-auth key, Tailscale SCIM key, Tailscale webhook key) and the improvement of 1 detector (Vercel API Access Token).
• Source criticality: a new parameter at the source level to help users prioritize their Secret incidents. Refer to the documentation for more details.
• Check runs: the preview of the "How to remediate" instructions in markdown is enhanced when you customize them.
• Custom detectors: improve error messaging for invalid regex when requesting a custom detector.

Self-Hosted​

• Chainguard: Chainguard-based GitGuardian images are now used by default, enhancing security by reducing CVE exposure. Available only on the new GitGuardian architecture. Additionally, both KOTS admin version 1.104.4 and Replicated SDK version 1.0.0-beta.12 are built using a distroless base image from Chainguard.
• SMTP configuration: the system now supports unauthenticated SMTP server, allowing for more flexible email service integration.
• KOTS preflights: update preflights to support TLS for Redis and PostgreSQL.
• Helm Chart:
  • Private registries: introduce support for the replicated SDK image and offer an option to include a custom nginx image for private CA insertion. For detailed information, refer to the Install on Airgap page.
  • RBAC: add Kubernetes Roles and RoleBindings required for the app in the Helm Chart (optional but enabled by default). Refer to rbac in Helm Chart Values.
• Cluster management: update Kubernetes version to 1.27 for embedded cluster. For further details, refer to the Upgrade page.

Bug fixes​

• Airgap: add missing Replicated SDK image in airgap bundle.
• SSO: fix a server error (500) issue with login via SSO on KOTS install in the new architecture.
• Helm: fix a Nil Pointer error that occurs during a helm upgrade of GitGuardian when specifying the djangoSecretKey in the local-values.yaml.
• Custom webhook: fix webhook event serialization error when no hmsl_hash is present in the secret.

2023.12.1​

Bug fixes​

• Bitbucket integration: add auth_error_grace_period option in preferences for setting a grace period before token revocation.
• Cluster management: fix an issue with the database migration when schema name is not "public".
• API: fix random HTTP/502 errors while navigating in the application.

2023.12.0​

- apiGroups: ["apps"]
    resources: ["daemonsets", "deployments", "deployments/scale", "replicasets", "statefulsets"]
    verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]

Secrets Detection​

• Azure Repos integration: the monitoring of your Azure Repos repositories is now done in real-time. Refer to the documentation for more details.
• GitHub integration: improvement of check runs to support the GitHub Merge Queue feature.

Honeytoken​

• IP allow-listing for Honeytoken: it's now possible to add IP ranges to an allow-list, ensuring events from these IPs won’t trigger the honeytokens. Learn more about IP rules.

Platform​

• Jira Cloud integration: Jira issues can now be created without assigning them to anyone.
• Onboarding: implementation of an onboarding todo list to guide users in their first steps on the application
• Help Center: enrich the Help Center with additional resources.
• Filters: a new way of filtering pages, more streamlined and intuitive.

Self-Hosted​

• Kubernetes Version Support: GitGuardian now supports Kubernetes versions 1.27 and 1.28 (experimental). More information in the System requirements page.
• Helm and KOTS installation: introduce a new pod Replicated SDK for license management and telemetry collection. More information in the Replicated documentation.
• Helm Chart:
  • Private registries: support specifying existing Docker secrets and custom registries, enabling image pulls from private registries. Refer to the documentation for more details.
  • Kubernetes resource: add missing Kubernetes resources properties for Pre/Post deploy jobs and nginx init containers.
  • Pod security context: implements enhanced pod security context configurations in line with Kubernetes v1.25's Pod Security Admission feature, now customizable via Helm values for improved security compliance. Refer to containerSecurityContext in Helm Chart Values.
• Custom Telemetry: gather product usage metrics, such as VCS and incidents numbers, API call statistics. We prioritize your privacy and assure you that no personal data is collected through this process. It can be easily deactivated by adjusting the custom_telemetry_active setting found in the preferences section in the Admin area.

Bug fixes​

• GitHub integration: handling of GitHub app ownership transfer: it is now possible to change ownership without deleting the self-hosted application.
• Incidents: filtered results in CSV export: CSV export keeps the filters applied.
• API: fix /secret_detectors endpoint to filter out detectors that have been administratively disabled by GitGuardian.
• User Preferences: fix an issue where the "email not configured" banner incorrectly persists in private browsing mode due to a failure in loading user preferences.
• Historical scan: ensure UTF-8 character encoding compatibility for filenames in repositories.

2023.11.0​

Secrets Detection​

• Secrets detection engine: upgrade to version 2.99.1 with the addition of 6 new detectors:
  • Google Bard
  • Webflow API token
  • Aiven
  • Infracost API Key
  • Rollbar API Access Token
  • Vercel API
    and the improvement of 6 detectors:
    
  • Okta Keys
  • Username Password
  • Generic password
  • Microsoft Azure Storage Account key
  • SSH credentials
  • Generic High Entropy Secret
• Incident details: git patches of occurrences can now have restricted visibility to only the teams and developers involved with the occurrence, thanks to a workspace setting. If the git patch of an occurrence is too large, a link to the Version Control System is displayed instead.
• Historical scan: addition of some details in the status tooltip, including scan duration and number of commits and branches scanned. For failed scans, the tooltip now also displays the reason for the failure.
• API: New endpoint to retrieve secret incidents of a team.
• ggshield: ggshield auth login flow now asks you to confirm scopes.

Honeytoken​

• Honeytoken module is now available for Self-Hosted customers. This feature is available upon request.

Platform​

• Teams: users can now filter the incidents and the perimeter pages based on their teams. Managers have the flexibility to filter any team, while Members can only filter their own teams.
• Alerting integrations: alerting integrations are now available at team level. More information in our teams documentation.

Self-Hosted​

• Chainguard: introducing an experimental.chainguard flag in Helm chart values for enabling Chainguard-based GitGuardian images, enhancing security by reducing CVE exposure. Default is false, available only in Helm-based install on the new GitGuardian architecture.
• Kubernetes Version Support: GitGuardian now supports Kubernetes versions 1.25, 1.26, and offers experimental support for version 1.27 for Existing Cluster installations. More information in the System requirements page.
• Cluster Management:
  • support of GitGuardian installation via KOTS using the new GitGuardian architecture.
  • update Kubernetes version to 1.25 for embedded cluster. For further details, refer to the Upgrade page.

Bug fixes​

• Azure repos integration: installation status persists on all pages until the installation is complete. Removing a token no longer causes a crash in other installation.
• Bitbucket integration: prevents connection errors from revoking a Bitbucket token, letting instances go through maintenance without needing to re-enter their token afterwards.
• Teams: fix a bug that caused incidents belonging to an unmonitored repository to still be visible to the team.
• Historical scan: support for special UTF-8 characters, like Kanji, in filenames during historical scans. Improve handling of commits without dates.

2023.10.1​

Bug fixes​

• Security: update Contour (ingress controller for Kubernetes) to provide protection against CVE-2023-44487
• Cluster management: resolve an issue where migration jobs would fail and the app wouldn't start when Redis Sentinel was used.

2023.10.0 - Required​

Features​

• Secrets detection engine: upgrade to version 2.97.
• OpenShift: we officially support OpenShift, please refer to the OpenShift specifics page to learn more.

Bug fixes​

• Check runs: fix neutral check runs being created on workspaces with check runs disabled.
• Custom detectors: update the message when a custom detector request cannot be edited due to its current status.
• Incident details: fix a bug causing the absence of an expiration date on public share links generated by the Auto-healing playbook.
• Health check: prevent UI from crashing on unknown Health check error code.
• API: fix timeout issues on the /occurrences/secrets endpoint when using a date filter.
• SSO: fix conflict happening when signing up via SSO while having a pending invitation.
• Notifications: fix Linkedin link in email footer.
• Bitbucket integration: remove automatic revocation of the token when the connection is down.
• Historical scans: process incidents and occurrences in batches of 500 for efficient memory use.

2023.9.2​

Bug fixes​

• Cluster management:
  • fix an issue that hindered the generation of support bundles on Helm-based instances.
  • fix an issue that prevented the deployment of applications on an OpenShift cluster when utilizing Redis Sentinel.

2023.9.1​

Bug fixes​

• Jira integration: fix a configuration issue preventing the usage of Jira integration on a self-hosted environment.

2023.9.0​

Features​

• Secrets detection engine: upgrade to version 2.96 with the addition of four new detectors:
  • Databricks Authentication Token With Hostname,
  • Hashicorp Vault Token,
  • Generic Terraform Variable Secret,
  • CARTO API Access Token,
    and the improvement of 2 detectors:
    
  • Generic Password,
  • Base64 Basic Authentication.
• Custom detectors: self-hosted users can now extend GitGuardian's secrets detection engine to support secrets specific to their organization.
• Incident details: the public sharing is now a workspace setting.

Bug fixes​

• Incidents: fixed the sorting of incidents by severity when some severities are automatically set.
• Incidents: fixed wrong occurrence count on incident page.
• Incidents: the tooltip displaying the sources is now displayed correctly.
• Custom webhook: fixed duplicate notifications being sent when setting incident severity using a bulk action.
• API: fixed invalid link in personal access token expiration email notification.
• Custom detectors: update the message when a custom detector request cannot be edited due to its current status.
• Incident details: fixed a bug causing the absence of an expiration date on public share links generated by the Auto-healing playbook.
• Health check: prevent UI from crashing on unknown Health check error code.
• API: fix timeout issues on the /occurrences/secrets endpoint when using a date filter.
• SSO: fix conflict happening when signing up via SSO while having a pending invitation.

2023.8.0​

Features​

• Incidents: addition of the Default branch tag to secret incidents that occurred on the default git branch of a repository.
• Incident details: filters have been added to the occurrences table.
• Incident details: the public sharing toggle has been moved to the "Grant access" modal, which has been renamed to the "Share" modal. For a more detailed explanation, please refer to our collaboration and sharing documentation.
• Integrations: modification of the Integrations and Settings/Integrations pages.
• Secrets detection engine: upgrade to version 2.94 with the addition of four new detectors:
  • Azure Active Directory API Keys,
  • Docusign API Key,
  • Pinecone API Key,
  • Pinecone API Key and environment
    and the improvement of two detectors:
    
  • Generic Password,
  • Coveralls Personal Token.
• Cluster management: port for applicative metrics exposure changed from 8082 to 9808.

Bug fixes​

• API: fix an error preventing the creation of an invitation when the role was not specified.
• Personal access tokens: personal access tokens can now be searched by name, and ordering by name now works correctly.

⚠️ Deprecation​

• Custom webhook v1: the feature has been replaced by the event-based custom webhooks. More information in the documentation here.

2023.7.1 - Required​

Bug fixes​

• Custom webhook: fix notifications for when a bulk action is performed. Previously, only one notification would be sent for the first incident affected by the bulk action. However, now notifications are sent for each incident that is modified by the bulk action.

2023.7.0​

Features​

• Automated severity scoring: managers and workspace owners can now activate the automated severity scoring feature for Self-Hosted environments in order to automatically score incidents with a severity.
• Custom severity rules: the severity ruleset used by the automated severity scoring is now customizable to maximize the coverage of automatically scored incidents.
• Incident details: feedback about the incident can now be submitted in a standardized way through a form that is available on the incident's page.
  Refer to this page for more information on how to use this form effectively and involve your developer population during the remediation process.
• Incidents: addition of new filter to select the incidents that are publicly shared.
• Teams: team owners with the Member role can now invite brand new users to the workspace when adding teammates to their team. This feature can be deactivated.
  For more details, please refer to this page.
• Grant access: users with Full access incident permissions can now invite brand new users to the workspace when granting access to an incident.
  For more details, please refer to this page.
• Secrets detection engine: upgrade to version 2.93 with the addition of four new detectors:
  • Tableau Personal Access Token,
  • Yelp API key,
  • AWS SES Keys,
  • Forest Admin API Key
    and the improvement of eight detectors:
    
  • Atlassian Oauth2 Keys,
  • Contentful Content Delivery API Key,
  • Etsy Developer Key,
  • GitLab Token,
  • HubSpot API Key,
  • MS Team webhook,
  • GitHub Access Token,
  • OpenAI API Key.
• API: managers can now enforce a maximum lifetime for personal access tokens generated on their workspace.

Bug fixes​

• Emails: button URLs are now hardcoded to prevent a bad user experience when the button is not visible due to HTML-escaping by email providers.
• PagerDuty Integration: title update in PagerDuty incidents to eliminate confusion regarding the number of occurrences.
• Cluster management: fix an issue on proxy configuration that was not correctly propagated for some integrations, causing network requests time out.

2023.6.0​

Features​

• Cluster management: you can now install GitGuardian Self-Hosted using Helm Charts. This feature is currently in Beta. More information is available in the installation documentation. the installation documentation.
• Cluster management: allow self-hosted instances to use a specific Redis instance for the commit cache. More information is available in our documentation our documentation

Bug fixes​

• Authentication: fix broken email confirmation link when registering with email and password.

2023.05.1​

Bug fixes​

• Cluster management: fix an issue on Redis Sentinel that failed to start, blocking GitGuardian's launch.

2023.05.0​

Features​

• API: secret detectors are now exposed in the API.
• Incidents: filepaths can now be searched in the free text search of the secret incidents table.
• Secrets detection engine: upgrade to version 2.89 with the addition of seven new detectors:
  • Azure Cosmos DB Credentials
  • Redis Server Password
  • DigitalOcean Refresh Token
  • DigitalOcean OAuth Application Token
  • DigitalOcean Personal Access Token
  • Cloudinary API keys
  • MongoDB Atlas Keys

Bug fixes​

• Custom severity rule: fix wrong timeline when setting a manual severity to an incident having only an automatic severity.
• Grant access: copy-pasting now works correctly.
• Incidents: performance for loading secret incidents has been improved for workspaces with a large number of incidents.
• Loader: fix loader size in incident and Perimeter pages.
• API: comment field is now required on incident note creation endpoint.

2023.04.0​

Features​

• Custom remediation workflow: remediation workflow is now 100% customizable thanks to the deletion of the last static step.
• Secrets detection engine: upgrade to version 2.87 with the addition of a new detector (Keycloak API Keys).
• API: new endpoints are added for API tokens management (personal access tokens and service accounts).
• API: new fields resolver_id and ignorer_id are available in the secret incident payload.

Bug fixes​

• Members: fix invitation link for new members.
• Jira integration: Jira ticket creation CTAs are hidden for workspaces without a single Jira site installed.
• Jira integration: fix permission issues by disabling the configure button for users without a Manager role and allowing users with the Restricted role and Can edit permissions to create a Jira ticket.
• Detectors list: when the validity checks are disabled, the detectors are sorted by status.
• Notifications: fix empty emails being sent after an occurrence was found during real time scan.
• Personal access tokens: Restricted users now only see the scan scope in the personal access token form.
• Cluster management: fix password issue that was blocking application initialization during GitGuardian installation.

2023.03.1 - Required​

Bug fixes​

• Cluster management: suppression of preflight checks that were failing for new installation with embedded air-gapped configuration with PostgreSQL 13.

2023.03.0​

Features​

• Azure Repos: addition of a loader and notifications when an organization is being installed.
• API: add filters to multiple endpoints.
• Cluster management: Embedded clusters now use PostgreSQL 13. Refer to this procedure to migrate from on older version of PostgreSQL.
• Cluster management: self-hosted GitGuardian environments are now supporting Redis version 6 and Kubernetes version 1.23.

Bug fixes​

• ggshield: ggshield auth login flow now expires after 5 minutes.
• Incidents: performances when filtering incidents on a detector are improved.
• VCS integrations: fix broken links to documentation.
• GitHub: fix the integration of a GitHub installation with a large number of repositories
• GitHub: fix check-runs running forever by enforcing a timeout.

2023.02.1 - Required​

Bug fixes​

• Cluster management: self-hosted GitGuardian can now be deployed on OpenShift with default security settings.
• Cluster management: self-hosted GitGuardian is now compatible with Redis Sentinel.
• Historical scans: corrections on scans that can be automatically launched.
• Custom Certificates for Cluster Management: correction of regression on custom Certificates Authorities.

2023.02.0​

Features​

• Azure Repos: the native integration is now available. You can scan your Azure Repos repositories for secret detection and policy breaks.
• API: specify missing scopes in error message when the API token being used doesn't include the appropriate scopes.
• Custom remediation workflow: remediation workflow can now be customized in the settings.

Bug fixes​

• Health Check: on self-hosted environments, pods are no longer crashing because of integrations' health checks.

2023.01.1​

Bug fixes​

• Cluster management: Self-hosted GitGuardian containers are now running with non-root security context.

2023.01.0​

Features​

• Teams: addition of a description field for your teams.
• Teams: the "all-incidents" team is now visible in the Members table.
• Perimeter: improve the display of the historical scan's last status information.
• Playbooks: new Auto-resolution playbook to automatically close incidents that have once been valid and that become invalid.
• Secret incident: prevent valid secrets from being "marked as revoked".
• Cluster management: Self-hosted GitGuardian environments are now supporting PostgreSQL version 13. Support for PG version 12 is deprecated as of this release.

Bug fixes​

• SSO: Fix the "sign in" redirection for SSO connection.

2022.12.1​

Bug fixes​

• Incident detail: fix misplaced secret in the commit patch when detected by a historical scan and in real-time. Please contact the Support team if you have occurrences impacted in your environment.

2022.12.0​

Features​

• Historical scan: increase the maximum size of the historical scan from 1 GB to 12 GB.
• Historical scan: new email template for historical scan report.
• API: expose external_id representing the VCS id of a source in API source payload.

Bug fixes​

• GitLab integration: handle timeout errors when setting up a new instance.
• Playbooks: fix incorrect default permission can view applied with auto-access playbook instead of correct can edit.
• Filepath exclusions: ignore hidden occurrences in the auto-access playbook and notifications.
• Custom webhooks: fix incorrect event names.
• Historical scan: reduce errors during scans of large repositories and optimize memory usage on large patch sizes.
• Members: fix the sorting when navigating through pages.

2022.11.3 - Required​

Features​

• Cluster Management: integrate memory limits for Kubernetes pods. You can configure them on the Admin Console's configuration page.

Bug fixes​

• RBAC: prevent users from receiving email notifications for already existing incidents.

2022.11.2​

• Released on November 21, 2022.
• Validated for KOTS v1.90.
• Minimum Kubernetes version: 1.19.

Features​

• Teams: introducing team management within a workspace and granular incident permissions (can view, can edit, full access). You can activate the feature on the Admin Area's preference page.
• Custom webhooks: update the action field with more user-friendly messages.
• Perimeter page: update the information displayed in the Protection section.
• Analytics: add all ggshield modes to the Analytics section.
• Custom Certificates for Cluster Management: integrate custom Certificates Authorities for integrations. This feature was in beta and is now stabilized. More information is available in the dedicated documentation.
• API: add the API URL to the dashboard, in the section API >> Quota. The URL is also updated in the API documentation of those environments.

Bug fixes​

• Check runs: When deactivating a check run, finish the processing if it was already in progress.
• Check runs: Check runs are functional for forked repositories.
• Custom webhooks: Remove matches from webhooks' new occurrence.
• GitHub: fix display latency observed for big GitHub organizations.

2022.10.1​

• Released on October 26, 2022.
• Validated for KOTS v1.88.
• Minimum Kubernetes version: 1.19.

Bug fixes​

• Bitbucket Integration: when you create a branch on a monitored repository, the event now triggers a scan of the branch commits only, and not of the whole repository.

2022.10.0​

• Released on October 10, 2022.
• Validated for KOTS v1.86.1.
• Minimum Kubernetes version: 1.19.

Features​

• Members: Notification is sent to users who are removed from a Workspace.

Bug fixes​

• Check Runs: check runs are functional again for forked repositories.
• Incidents: provide a more user-friendly error message when a bulk action can't be applied to the selected incidents.

2022.09.1​

• Released on September 21, 2022.
• Validated for KOTS v1.85.
• Minimum Kubernetes version: 1.19.

Bug fixes​

• API: fix a broken link on the Settings page.
• Redis: we fixed a bug where the database memory could get filled.

2022.09.0​

• Released on September 5, 2022.
• Validated for KOTS v1.82.
• Minimum Kubernetes version: 1.19.

Features​

• API: enrich the Members section with retrieve and delete endpoints.
• API: handle invitations on grant/revoke access endpoints.
• API: add a filter by role and a search on name and email for the /members endpoint.
• API: add filters to the audit log list endpoint.
• Cluster Management: add a parameter to customize pods' CPU limits. More information is available in the dedicated documentation.
• Incidents: include the unaffected count for bulk actions.

Bug fixes​

• API: respect the validity checks setting ON/OFF.
• Custom webhooks: fix the webhook event-based signature.
• GitHub: don't display the "scan integrated repositories" modal if the auto scan is on.
• GitLab integration: keep unmonitored projects unmonitored.
• Incident details: searching GitHub pull requests associated with an issue can be performed on a specific #ID and repository name.
• Incident: secrets with validity status "failed to check" are no longer checked automatically after they have been marked as resolved.
• Incident: the button to manually check the presence in git history remains when the incident is closed.
• Incidents: fix the severity badge 'info' icon.

2022.08.0 - Required​

• Released on August 8, 2022.
• Validated for KOTS v1.78.
• Minimum Kubernetes version: 1.19.

Features​

• API: the /occurrences endpoint can be filtered by author_name and author_info.
• API: add an endpoint to fetch the audit logs. The API key needs to have the new audit_logs:read scope to query the endpoint.
• API: tags are exposed in the incidents endpoint.
• CSV: tags are exposed in the CSV report of secret incidents.
• Health Check: it checks if the GitHub integration has been suspended.
• Perimeter: the repository name is now a link to the incidents list filtered on this repository. The link to the VCS is also available as a popup icon.
• Applicative Metrics: metrics have been added: scanned commit, API quota, API usage and API tokens.

Bug fixes​

• Detectors: activating and deactivating detectors is now forbidden for Members.
• Perimeter: fix a bug preventing Members from launching historical scans.

⚠️ Deprecation​

• API: deprecated issue_id in favor of incident_id on incident note management endpoints.

2022.07.0​

• Released on July 11, 2022.
• Validated for KOTS v1.75.
• Minimum Kubernetes version: 1.19.

Features​

• ggshield: setting up ggshield is made easy with the new ggshield auth login command. More information is available in the dedicated documentation.
• Grant access: notify Restricted users by email when they are granted access to an incident.
• Members: notify users by email when their role is updated.
• CSV: add status, ignore_reason and status_revoked columns to the CSV export of secret incidents.
• CSV: add occurrence_id column to CSV export of occurrences.
• CSV: return the dates in iso format.
• Members: invitations can be resent through the dashboard.
• API: add endpoints to manage invitations. The API key needs to have the new members: write scope to query those endpoints.
• API: add an endpoint to set the severity of a secret incident.

Bug fixes​

• GitLab: adding a GitLab project that had been deleted now correctly set it as monitored.
• Analytics: pre-receive mode is displayed correctly in the shift-left panel.
• Service account: fix a permission error allowing all roles to modify service accounts.
• GitHub: fix the re-run action of old check runs to show an explicit error.

2022.06.1​

• Released on July 1, 2022.
• Validated for KOTS v1.73.
• Minimum Kubernetes version: 1.19.

Bug fixes​

• Bitbucket Integration: add a parameter in the Preferences section of the Admin Area to disable Admin Check during Bitbucket Installation creation.

2022.06.0​

• Released on June 20, 2022.
• Validated for KOTS v1.71.
• Minimum Kubernetes version: 1.19.

Features​

• Applicative Metrics: applicative metrics are added to help you monitor your self-hosted instance. More information is available in the dedicated documentation
• API: move the Personal access tokens to the API section.
• Check runs: improve success message in GitHub UI.
• GitHub: expose the base/head branch of GitHub pull requests.
• Incident: mark the third remediation step "rewrite git history" as optional.
• Health checks: Health checks are displayed in the VCS integration settings

Bug fixes​

• GitHub: explicitly neutralize old check runs that are re-run.
• Incident: fix grant access modal broken when too many Restricted users.

⚠️ Deprecation​

• ggshield: since v1.12 of ggshield, ggshield scan and ggshield ignore commands are deprecated, use ggshield secret scan and ggshield secret ignore instead.

2022.05.1 - Required​

• Released on June 6, 2022.
• Validated for KOTS v1.70.
• Minimum Kubernetes version: 1.19.

Bug fixes​

• Bitbucket Integration: when configuring a whole instance token, GitGuardian is not returning a timeout.

2022.05.0​

• Released on May 16, 2022.
• Validated for KOTS v1.70.
• Minimum Kubernetes version: 1.19.

Bug fixes​

• Grant Access: Members in Business workspaces can give access to restricted users but can’t invite new users by typing email addresses.
• Incident details: timestamp of the last presence check is updated synchronously upon manual check.
• CSV Export: disable timeouts.
• Incidents: improve performance on the incidents table.
• Detector: improve performance of table of detectors for workspaces with many incidents.
• Email: the warning banner is not displayed anymore when the email-sending system is configured.
• Health Check: the error code for an expired GitLab token has been corrected.
• PostgreSQL: configuring an external port different from the default one (5432) correctly works.

2022.04.2​

• Released on May 09, 2022.
• Validated for KOTS v1.70.

Bug fixes​

• Upgrade: Error on Ingress component deployment.
• Postgre TLS: Fixes error on deployment while Postgres TLS "Allowed" mode is activated.

2022.04.1​

• Released on April 22, 2022.
• Validated for KOTS v1.59.1.

Features​

• Health checks: We add VCS troubleshooting tools in the Admin Area. You can check the status of your integrations and gather error information on this page. More information is available in the dedicated documentation
• Personal access tokens and service accounts: We now distinguish two types of API keys: Personal Access Tokens and Service accounts. More information is available in the dedicated documentation
• GitHub check runs now handle the regression mode. If an already resolved secret incident is detected by a check run AND the regression mode is OFF, the check run won’t raise the secret.
• GitHub A comment can be posted directly to Github pull request timeline when a check run detects a secret. This can be deactivated in Settings by a Manager.
• API: We add an API endpoint to list members having access to an incident. More information is available in the dedicated documentation.
• PostgreSQL: Secrets are now encrypted in the database.

Bug fixes​

• Incident: Restricted users are no longer able to generate incident-sharing links.

1.35​

• Released on March 25, 2022.
• Validated for KOTS v1.59.1.

Features​

• TLS Support for PostgreSQL: Transport Layer Security (TLS) is an encryption protocol intended to keep data secure when being transferred over a network. When installing GitGuardian Self-Hosted, users can now activate the option for PostgreSQL.
• API: Members are now exposed in API and new fields were added to the source payload.
• Incident detail: From an incident detail page, you can grant access to a selection of Restricted users.

1.34​

• Released on February 11, 2022.
• Validated for KOTS v1.59.1.

Features​

• TLS Support for Redis: Transport Layer Security (TLS) is an encryption protocol intended to keep data secure when being transferred over a network. When installing GitGuardian Self-Hosted, users can now activate the option for Redis. You can find more information about the configuration on our official documentation

1.33​

• Released on January 13, 2022.
• Validated for KOTS v1.59.1.

Features​

• API: Added secret validity information.

1.32​

• Released on December 14, 2021.
• Validated for KOTS v1.58.1.

Features​

• API: new scope incident::share and grant access to incidents, documented here.
• Regression: added a workspace setting giving the option to control the behavior of GG when a new occurrence of an already-resolved incident is detected.
• Custom webhooks: added validity and severity to the payload.
• API: added validity to scan results.

1.31​

• Released on November 15, 2021.
• Validated for KOTS v1.56.0.

Features​

• Synchronization between ggshield and the dashboard: secrets ignored on the dashboard will also be ignored by ggshield. Detectors deactivated in the dashboard will be deactivated for ggshield too.