Skip to main content

16 posts tagged with "secrets-detection"

View All Tags

MS Teams attachment scanning is here!

calendar icon   Release Date: September 30, 2025

MS TEAMS Attachment Scanning

We're thrilled to expand our detection coverage with Microsoft Teams Attachment Scanning!

Now, you can ensure comprehensive security by detecting secrets hidden in file attachments shared within Microsoft Teams.

Why This Matters?

  • Enhanced Security: Automatically scan attachments for secrets, closing critical security gaps.
  • Seamless Integration: No extra setup required, works effortlessly with your existing GitGuardian setup.
  • No Extra Cost: Included in your current GitGuardian subscription.

Historical Scanning Consideration:

To cover your debt in file attachments shared in past messages, access your perimeter, manually select sources you want to cover, and scan them.

Get Started Today: Secure your Teams environment and protect your sensitive data now!
Check out our documentation to learn more.


Fixes

  • GitGuardian Bridge: Resolved an issue where a custom CA configured on the Bridge was applied to all integration endpoints, causing failures for services using public CAs.

Context Preview for non-VCS Secret Leaks!

calendar icon   Release Date: August 20, 2025

Secret Leak Preview Thumbnail

We're thrilled to announce a feature that will significantly enhance your investigation: Context Previews are now available for Secret Leaks in non-VCS sources like SharePoint, OneDrive, Slack, and Confluence!

What does this mean for you?

  • Immediate Context Visibility: Instantly view the surrounding content where secrets were detected, directly within GitGuardian incidents. No more switching between systems!
  • Accelerated Investigation: Reduce investigation time by up to 75% with quick access to contextual information, enabling faster, more informed remediation decisions.

Why is this important?

In today's fast-paced digital landscape, efficient incident response is crucial. By providing immediate context, this feature empowers you to act swiftly and accurately, minimizing potential risks and enhancing your organization's security posture.

Get Started Today!

Context previews are now automatically available by default for all non-VCS incidents on your workspace.
Get in touch with our Support team if you want this feature disabled.


Enhancements

  • User management: Managers can allow users with the "Can view" incident permission to comment and provide feedback, improving collaboration without granting edit rights. Learn more

Fixes

  • Analytics: Fixed timezone handling issues in the new Analytics dashboard that caused incorrect data display for users in different time zones.
  • Token Management: Removed the unnecessary service account token link from the personal access token page for members.

Now, Bring Your Own Sources!

calendar icon   Release Date: August 13, 2025

Bring Your Own Sources Thumbnail

We're excited to announce the launch of Bring Your Own Sources, a powerful new feature that allows you to extend GitGuardian's secret detection capabilities to any data source, whether it's CI logs, legacy systems, local filesystems, or SFTP servers. This feature empowers you to seamlessly integrate custom sources into your existing security monitoring workflow.

Why You'll Love It:

  • Infinite Flexibility: Scan any source, regardless of native integration support, and manage incidents directly in the GitGuardian dashboard.
  • Comprehensive Coverage: Eliminate detection gaps and ensure comprehensive coverage across all your environments, especially those highly isolated.
  • Seamless Integration: Integrate sources within minutes, incidents automatically appear in the GitGuardian interface.

How It Works:

  • Declare a Custom Integration: Use the GitGuardian dashboard to create a custom source and receive a unique ID.
  • Scan Your Data: Use ggshield, custom script or any automation tool to scan content from your custom sources.
  • Manage Incidents: View and manage all findings in the GitGuardian dashboard with full filtering and incident management capabilities.

It's Future-Proof:

We're planning enhancements in the coming months, like multi-source support per integration and larger file limits.
We'd love to hear from you: Let us know how it solved your challenges or how we can improve to help you solve them!

Get Started Today!


Enhancements

  • VCS Integrations: Added option to disable automatic repository monitoring when adding new VCS integrations, providing more control over your monitored perimeter.
  • Bitbucket Cloud Integration: Updated authentication to support API tokens as Atlassian discontinues app passwords, ensuring continued integration functionality.

Fixes

  • Email Notifications: Fixed an issue where integration health check emails were sent without respecting user email notification preferences.
  • Confluence Data Center Integration: Resolved an issue where private spaces were not being retrieved during integration setup.

Automatically Ignore Invalid Incidents with New Playbook

calendar icon   Release Date: July 28, 2025

Incident Playbook Thumbnail

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


Fixes

  • 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.

New Analytics - Gain Deeper Insights into Your Security Posture

calendar icon   Release Date: July 23, 2025

illustration

We're excited to announce a major update to Internal Monitoring: comprehensive analytics dashboards that empower you to monitor, investigate, and improve your organization's security posture across four key dimensions—Protect, Detect, Remediate, and Prevent.

Get answers to your most important security questions with new, interactive charts and tables:

Are your code repositories fully monitored for secrets? See the Count of sources chart to track the percentage of monitored repositories over time.

Which types of secrets are most frequently detected in your codebase? Explore the Most detected secrets chart to identify the most common secret types found.

Which teams and sources are most at risk for secret leaks? Check the Top teams by incident count and Top sources by incident count tables to pinpoint where incidents originate.

Is your team resolving security incidents quickly enough? Review the Median time to remediate chart to monitor how fast incidents are being resolved.

How effective are your secret prevention tools in stopping leaks before they happen? Analyze the Total count of incidents avoided by GGShield and GGShield scans over time charts to measure prevention and adoption.

With these new analytics, you can:

  • Visualize monitoring coverage and trends
  • Identify the most common and riskiest secrets
  • Track incident detection and remediation performance
  • Measure the impact of prevention tools like GGShield
  • Drill down by team, source, and severity for targeted action

Start exploring the new dashboards today to drive smarter, data-driven security decisions!

Read documentation


Enhancements

  • GitLab integration: Configuration of multiple GitLab integrations using both system hooks and group hooks simultaneously is now supported

Historical Scanning now available for Jira Data Center

calendar icon   Release Date: July 7, 2025

Jira DC Historical Scan Thumbnail

Following the introduction of the historical scanning for Confluence Data Center, we’ve kept the pace with the support of that capability for Jira Data Center!

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 Jira Data Center documentation to see how to use this feature now!


Fixes

  • Email Notifications: Improved email delivery logic for Microsoft Teams integrations to prevent excessive notification sending during periodic scans.

Historical Scanning now available for Confluence Data Center

calendar icon   Release Date: June 30, 2025

Confluence DC Historical Scan Thumbnail

We’re excited to announce a significant enhancement to our secret detection capabilities for Confluence Data Center: 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 Confluence Data Center documentation to see how to use this feature now!


Enhancements

  • Jira Data Center Integration: Enhanced Jira Data Center incident creation to include leaker email addresses for historical comments occurrences.

Fixes

  • GitHub Integration: Fixed an issue where dangling GitHub installations were being unnecessarily checked when no installations were present.

Secrets Scanning now available for Microsoft SharePoint and OneDrive

calendar icon   Release Date: June 26, 2025

In the era of agentic AI, safeguarding your organization's knowledge database is more crucial than ever.

We're excited to announce that GitGuardian now supports secrets scanning for Microsoft SharePoint and OneDrive, empowering you to protect sensitive information from inherent breaches and mitigate risks effectively.

MS Teams historical scanning thumbnail

What does this mean for you?

  • Comprehensive Security: Automatically detect and remediate exposed secrets in your SharePoint and OneDrive files, ensuring your data remains secure.
  • Proactive Protection: Identify and address potential vulnerabilities before they can be exploited or ingested by your LLM providers or internal AI agents.
  • Seamless Integration: Easily incorporate this new scanning capability into your existing GitGuardian setup for a unified security approach.

Why is this important?

As AI continues to evolve, the potential for breaches increases. By securing your organization's knowledge base, you can prevent the ingestion of compromised secrets by LLMs or internal AI Agents, ultimately preventing your secrets from falling into the wrong hands. With GitGuardian's new scanning capabilities, you can confidently navigate the digital landscape, knowing your secrets are safe.

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 SharePoint Online and OneDrive content, surfacing any hardcoded secrets for prompt remediation.

Check out our documentation to get started now!

GitGuardian MCP Server - Security in Your AI IDE

calendar icon   Release Date: June 19, 2025

The GitGuardian MCP (Model Context Protocol) Server is now available on GitHub. This integration brings GitGuardian's security capabilities directly into your AI-powered development environment, supporting Cursor, Windsurf, and any IDE implementing the Model Context Protocol.

The MCP Server enables your AI agent to read and analyze security incidents, generate honeytokens, and perform automated remediation tasks—all without leaving your development workflow.

Key Benefits

  1. Eliminate Context Switching: Access security scanning and incident management directly within your AI IDE without switching to GitGuardian dashboards.
  2. Real-Time Security Feedback: Catch security issues immediately during development, before they enter your codebase.
  3. Enhanced Developer Autonomy: Empower developers to manage security posture independently with direct access to GitGuardian's tools.

Getting Started

Install Developer MCP Server

For Cursor users: Click the button to install the GitGuardian MCP Server directly in your IDE.

For other IDEs: Follow our setup instructions to integrate the MCP Server into your environment.


Enhancements

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

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.
    • Fixed an issue where assigning tags to selected filtered issues was incorrectly applying tags to all issues instead of only the selected ones.
  • GitLab: Improve permission checking for GitLab group integrations to properly handle inherited permissions from parent groups.
  • Azure DevOps Integration: Improved token handling to prevent unnecessary revocation of Azure DevOps installations due to intermittent 401 errors.
  • Secret analyzer: Improved behavior to ensure secret analyzer is properly disabled when validity checking is turned off.

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

calendar icon   Release Date: May 23, 2025

secret API thumbnail

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, IP allowlisting) 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

calendar icon   Release Date: May 5, 2025

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

MS Teams historical scanning thumbnail

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!


Enhancements

  • Emails: Included the number of incidents to both weekly digest and historical scan emails subject line.

Historical Scanning now available for Jira and Confluence Cloud sources.

calendar icon   Release Date: April 29, 2025

Jira Confluence historical scan Thumbnail

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:


Enhancements

  • API: Introduced a new endpoint GET to the Public API, allowing users to retrieve invitation details.

Fixes

  • ServiceNow Integration: Redirects to the proper URL when checking hardcoded secrets in ServiceNow sources.

Secure your Non-Human Identities with NHI Governance

calendar icon   Release Date: April 23, 2025

NHI Governance Thumbnail

We're proud to introduce NHI Governance our brand new solution 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, such as CI/CD pipelines or Kubernetes Clusters, it centralizes inventory, helps you assess your posture, and enforces security policies.

The solution offers:

  • 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 or Customer Success Manager.

Learn more:


Enhancements

  • 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.

Fixes

  • GitLab Integration: Resolved an issue where system hook checks returned a 403 forbidden error when using a read-only token.

Explore and prioritize your Generic Incidents

calendar icon   Release Date: March 10, 2025

GSE-filters

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".

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.

Leverage insights from your Secrets Managers

calendar icon   Release Date: February 28, 2025

Secrets Managers Thumbnail

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 Managers Tag

ServiceNow secret scanning

calendar icon   Release Date: January 28, 2025

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


Enhancements

  • Jira Data Center Integration: Added support for "User Picker (single user)" custom fields in Jira templates for improved issue tracking. Learn more

Fixes

  • GitLab Integration: Improved support for instances with over 50,000 GitLab projects, enabling better visibility in integration settings.
  • Azure Repos Integration: Fixed an issue where organization deletions were not properly synced when using ADO installations in Organization-mode.
  • PagerDuty Alerts for Security Incidents: Resolved an issue that prevented real-time alerts from being sent.