Past release notes
Browse all past GitGuardian Self-Hosted releases, feature updates, and hotfixes below.
2024.12.1
Release Date: January 13, 2025 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
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
Release Date: December 23, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
⚠️ Check the Helm values file changes from the previous version here.
Secrets Detection
-
Secrets detection engine upgrade to version 2.127.0:
-
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 renamedingress
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
, andgim_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
Release Date: November 28, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 ⚠️ | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
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
Release Date: November 21, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 ⚠️ | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
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
Release Date: November 18, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
⚠️ Check the Helm values file changes from the previous version here.
Secrets Detection
-
Secrets detection engine upgrade to version 2.125.0:
-
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 thesources: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.
- All Sources endpoints now require specific scopes for access. The new
Self-Hosted
-
Helm:
- Replace the legacy parameter
replicated.images.replicated-sdk
with the new parametersreplicated.image.repository
andreplicated.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.
- Replace the legacy parameter
-
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 byspread_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 theservicemonitors
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
tofalse
and configure your HTTP proxy following the example.
2024.10.2 - Required
Release Date: October 31, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 ⚠️ | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
Bug fixes
- Cluster Management: Added an option to disable server side Postgres cursors (for better PGBouncer compatibility).
2024.10.1
Release Date: October 25, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 ⚠️ | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
Bug fixes
- Secrets detection engine: Resolved an issue where GitLab keys for disabled accounts were incorrectly flagged as valid.
2024.10.0
Release Date: October 21, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.117.3 ⚠️ | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
⚠️ 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:
- Modified 1 detector:
- 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
- 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, ...) andlong-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
Release Date: September 24, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.107.7 | latest |
Kubernetes Version | 1.25 | 1.30 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
⚠️ 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:
-
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 withrepo_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
Release Date: August 30, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.107.7 | latest |
Kubernetes Version | 1.25 | 1.29 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
Bug fixes
- Cluster Management: Resolved an issue where the Scanner pod was spawning zombie processes (legacy architecture).
2024.8.1
Release Date: August 29, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.107.7 | latest |
Kubernetes Version | 1.25 | 1.29 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
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
Release Date: August 20, 2024 | Minimum | Recommended |
---|---|---|
KOTS Version | 1.107.7 | latest |
Kubernetes Version | 1.25 | 1.29 |
PostgreSQL Version | 13 | 16 |
Redis Version | 6 | 7 |
⚠️ 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
Modified 3 generic detectors
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 theis_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.
- Productivity tools (such as Slack, Jira Cloud, Confluence, ...) tasks are now defaulted to the
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
Release date | July 17, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
⚠️ 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.
⚠️ Therole
field has been deprecated and replaced by theaccess_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
andwebapp-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
, andgim_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
Release date | June 17, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
⚠️ 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.
- add missing readiness/liveness probes in
2024.5.1
Release date | May 29, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | May 22, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
We strongly recommend that all our customers currently using the legacy architecture transition to our new architecture, which offers numerous advantages! For a detailed overview of the new architecture and guidance on determining whether you're using the New or Legacy GitGuardian architecture, please visit the New GitGuardian Architecture page.
⚠️ 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
andpodLabels
for migrations resources. - give the ability to customize the
RefreshInterval
parameter forexternalSecrets
. - 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:
Refer to the Kubernetes Application RBAC page.
- apiGroups: [""]
resources: ["events"]
verbs: ["list"]
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
toceleryWorkers.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.
- rename
- Helm: fix an issue when Helm installation using a custom CA fails when pod security policy is enforced.
2024.4.2
Release date | May 10, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
Bug fixes
- Check runs: display accurate error message when a check run fails due to rate limiting.
2024.4.1 - Required
Release date | April 25, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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']
- fix error 500 from the
2024.4.0
Release date | April 17, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
⚠️ 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.
- add custom labels to differentiate multiple GitGuardian deployments within the same Kubernetes cluster. Refer to
- 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 to0
for legacy architecture running on openshift.
2024.3.2
Release date | April 5, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | March 28, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | March 19, 2024 |
---|---|
Minimum KOTS version | 1.107.7 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
⚠️ 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 to0
for new architecture. - fix an issue with the periodic task related to the database encryption key rotation.
- Helm Chart: add missing
podAnnotations
inwebapp
object definition.
2024.2.1
Release date | March 4, 2024 |
---|---|
Minimum KOTS version | 1.107.4 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | February 20, 2024 |
---|---|
Minimum KOTS version | 1.107.4 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
⚠️ 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
towebAppExporter
andceleryExporter
tostatefulAppExporter
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
Release date | February 6, 2024 |
---|---|
Minimum KOTS version | 1.107.4 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | January 25, 2024 |
---|---|
Minimum KOTS version | 1.104 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
Bug fixes
- Bitbucket integration: fix an issue which revoke the access token when the project only has read permission.
2024.1.1
Release date | January 17, 2024 |
---|---|
Minimum KOTS version | 1.104 |
Minimum Kubernetes version | 1.25 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
Ensure the btree_gin
PostgreSQL extension is installed for optimized text search performances. Manual installation by the user or sufficient privileges for the database user utilized by GitGuardian are required. Failure to install manually or insufficient privileges may result in an error during the upgrade, hinting at the necessity of CREATE
privilege on the current database for extension installation. More details in the System requirements page.
⚠️ 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
andRoleBindings
required for the app in the Helm Chart (optional but enabled by default). Refer torbac
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 thedjangoSecretKey
in thelocal-values.yaml
. - Custom webhook: fix webhook event serialization error when no
hmsl_hash
is present in the secret.
2023.12.1
Release date | December 19, 2023 |
---|---|
KOTS version validated | v1.104 |
Minimum Kubernetes version | 1.24 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
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
Release date | December 13, 2023 |
---|---|
KOTS version validated | v1.104 |
Minimum Kubernetes version | 1.24 |
Minimum PostgreSQL version | 13 |
Minimum Redis version | 6 |
For customers upgrading to the new version:
- Before upgrading GitGuardian, you must upgrade to KOTS version 1.104 or later for optimal performance and compatibility.
- If you previously installed GitGuardian on an existing cluster using KOTS and either lack
cluster-admin
rights in your Kubernetes cluster or wish to limit permissions for the KOTS Admin Console, you must modify the rule forapps
in your configuration by addingreplicasets
resource. Refer to the Kubernetes Application RBAC documentation page.
- 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
Release date | November 16, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
Secrets Detection
- Secrets detection engine: upgrade to version 2.99.1 with the addition of 6 new detectors:
- 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 isfalse
, 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
Release date | November 2, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | October 23, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | October 5, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | September 25, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
Bug fixes
- Jira integration: fix a configuration issue preventing the usage of Jira integration on a self-hosted environment.
2023.9.0
Release date | September 21, 2023 |
---|---|
KOTS version validated | v1.102 |
Minimum Kubernetes version | 1.24 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | August 22, 2023 |
---|---|
KOTS version validated | v1.94 |
Minimum Kubernetes version | 1.23 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | July 17, 2023 |
---|---|
KOTS version validated | v1.94 |
Minimum Kubernetes version | 1.23 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | July 17, 2023 |
---|---|
KOTS version validated | v1.94 |
Minimum Kubernetes version | 1.23 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | June 12, 2023 |
---|---|
KOTS version validated | v1.94 |
Minimum Kubernetes version | 1.23 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |
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
Release date | May 29, 2023 |
---|---|
KOTS version validated | v1.94 |
Minimum Kubernetes version | 1.23 |
PostgreSQL supported version | 13 |
Redis supported version | 6 |