GitGuardian in the news

Credential exposure is rapidly expanding beyond traditional security controls due to accelerated software development and AI agents, necessitating comprehensive detection and contextual understanding of secrets across all environments.

GitGuardian's ggshield prevents AI coding assistants from leaking secrets by scanning code interactions in real-time, integrating with pre-commit hooks, AI tools, and CI pipelines.

Corporate secrets are leaking at an alarming rate, exacerbated by AI, necessitating robust incident response processes and accessible vulnerability reporting channels.

GitGuardian introduces Agents Analysis to its Public Monitoring, providing clear verdicts and reasoning on public secret leaks to help companies identify and prioritize relevant credential exposures.

AWS Dogwood enhances AI agent authorization by adding temporal policy to evaluate sequences of actions, while GitGuardian provides tools to manage the underlying credential layer and facilitate migration from long-lived secrets.

GitGuardian details how an AI gateway can detect and prevent sensitive data leaks in generative AI interactions, revealing a significant increase in AI-related secret exposures.

GitGuardian identifies and provides a solution for AI coding agents leaking credentials through various unmonitored local storage locations on developer endpoints.

AI coding agents are leaking credentials by storing them in various unsecured locations on developer endpoints, a gap that GitGuardian's Developer Endpoint Protection aims to close with comprehensive endpoint scanning and detection.

A leaked GitHub private key for the CDC remained valid for 17 months, posing a significant security risk for data exposure.

GitGuardian partners with Docker to secure AI coding by integrating its secret-scanning hooks into Docker Sandboxes, providing automated, two-layer protection against credential exposure.

GitGuardian and Docker partnered to create a Sandbox Mixin Kit that integrates GitGuardian's secret-scanning tools into Docker Sandboxes, enhancing security for AI-assisted coding by automatically detecting and protecting against exposed credentials.

Hundreds of GitHub App private keys were leaked in public repositories, with some remaining active and granting broad administrative access.

AI coding agents exacerbate secrets sprawl by rapidly exposing credentials, transforming secrets management into an identity problem requiring new security approaches beyond traditional detection.

A leaked GitHub private key exposed CDC code to potential tampering for 17 months, as revealed by GitGuardian's report on forgotten secrets in code.

Leaked GitHub App private keys can remain valid indefinitely, posing a severe security risk by allowing unauthorized access and potential takeover of an organization's GitHub account.

Hundreds of GitHub App private keys, some with administrative access, have been leaked and remain active due to their non-expiring nature, posing significant security risks to organizations.

A significant number of GitHub App private keys were found to be leaked and still active, posing a substantial supply chain security risk due to their non-expiring nature and broad permissions.

GitGuardian research shows 474 GitHub App private keys are still active after being leaked, posing significant supply chain security risks due to their non-expiring nature and broad permissions.

This guide provides a comprehensive review of eight secrets management tools, categorized by organizational maturity, from cloud-native options to advanced multi-cloud and privileged access management integrations, emphasizing both preventing future leaks and detecting past ones.