Secrets Detection
Scan and fix hardcoded secrets in source code, CI/CD pipelines, and developer productivity tools – with GitGuardian’s code security platform.
Align developers, security teams, and DevOps engineers in a single platform.
Developers
Keep your code free from secrets
Scan every push and commit, find and fix hardcoded secrets while you code
SECURITY TEAMS
Enforce security policies for everyone, everywhere
Ensure every team is compliant and empowered to fix their own mistakes
CLOUD OPERATIONS
Get continuous pipeline security
Align engineering and security with automated secrets scanning in CI/CD
Code fast and stay secure with the ggshield CLI
Harden your pipelines with the ggshield CLI
#1 Security app on
the GitHub marketplace
GitGuardian has absolutely supported our shift-left strategy. We want all of our security tools to be at the source code level and preferably running immediately upon commit. GitGuardian supports that. We get a lot of information on every secret that gets committed, so we know the full history of a secret.
GitGuardian efficiently supports a shift-left strategy. As a result, it has made things materially more secure. The ability to check for hardcoded secrets as part of pre-receive hooks is fantastic, as it helps identify issues before they reach the main codebase, and that was the ultimate goal for us.
The platform has helped to facilitate a better security culture within our organization. In addition to highlighting problems, it shows engineers how to properly remove hardcoded secrets, and provides advice on rotation.
We have definitely seen a return on investment when it finds things that are real. We have caught a couple of things before they made it to production, and had they made it to production, that would have been dangerous. For example, AWS secrets, if that ever got leaked, would have allowed people full access to our environment. Just catching two or three of those a year is our return on investment.
Overall, GitGuardian has also helped us develop a security-minded culture. We're serious about shift-left and getting better about code security. I think a lot of people in the organization are getting more mindful about what a hardcoded secret is.
Time to remediation is now in minutes or hours, whereas it used to take days or weeks previously. That's the biggest improvement. Because it is automated and visible to the author, someone from the security team doesn't have to remind them or recheck it. That means the slowdown in the deployment process has definitely been improved by an order of magnitude. There is easily a 30-hour improvement on time to remediation, which is about an 85 percent decrease.
The solution has reduced our mean time to remediation. We are down to less than a day. In the past, without context, knowing who made the commit, or kind of secret it was, sometimes it was taking us a lot longer to determine the impact and what actions needed to be taken.
Verified by
Security Engineer at a Tech Services Company
I can say that tracking down a hardcoded secret, getting it migrated out of source code, getting the secret rotated, and cleaning the Git history took much longer from commit until the full resolution before GitGuardian. We weren't notified until it was too late, but with GitGuardian, we know almost instantly.
Find out how GitGuardian reduces the risk of hardcoded secrets in your software supply chain
Source code
Continuously scan all public and private Git repositories listed under your GitHub, GitHub Enterprise, GitLab, or Bitbucket organizations.
Docker images
Scan your Docker images for hardcoded credentials before pushing them to public or private registries.
Developer productivity tools
Developers write more than code. Scan %external sources scanned for secrets% for hardcoded credentials.
Developer workstations
Set up pre-commit or pre-push hooks to scan source code on developer workstations with GitGuardian’s CLI, ggshield.
CI environments
Plug GitGuardian into your CI/CD and run secrets scanning automated tests in your pipeline.
Centralized Version Control Systems
Pull requests
Turn GitHub check runs on and scan every commit in your pull requests for hardcoded secrets.
High coverage with specific detectors
GitGuardian’s Mean-Time-To-Detect is a few seconds after the secret is publicly exposed.
Generic detectors
Capture JWT secrets, Bearer tokens, username/password pairs, and all types of high-entropy patterns not covered by specific detectors with GitGuardian’s “Paranoïd mode”.
Custom detectors
Define custom Regex rules for secrets specific to your organization.
High precision detection
Reduce alert fatigue with a %sdtpr%% True Positive Rate (TPR) and multiple occurrences grouping.
GitGuardian performs contextual analysis of the surrounding code to discard false positives and weak matches.
When possible, GitGuardian also checks the validity of the hardcoded secrets with non-intrusive HTTP calls to the host.
Developer alerting
Developers are at the forefront of the issue of secret leaks. GitGuardian alerts the developers involved in the incidents alongside your Security team.
Integrations
Connect GitGuardian natively to your SIEM, ITSM, ticketing systems, messaging apps, or configure your webhooks.
Saved views for relevant incidents
Save filter criteria to quickly display and share relevant incidents (e.g., “critical” incidents with “valid” secrets). Create views that align with your organization’s priorities.
Incident prioritization
Explore and triage your incidents with key context information (secret type, location, incident severity, number of occurrences, live presence in the git repository, secret validity).
Developer feedback collection
Generate unique links to collect developer feedback on incidents. Harness the involved developers’ knowledge to understand the nature of the incident and the security risks it poses.
Developer-driven remediation
Empower developers to fix hardcoded secrets and resolve their incidents under your supervision.
Automated workflows
Enable automated playbooks for incident details sharing and developer-led remediation.
Programmatic incident management
Manage incidents programmatically with GitGuardian’s REST API.
SaaS implementation is available in the 🇪🇺 or 🇺🇸 zones
GitGuardian is GDPR-compliant with data storage in Frankfurt, Germany. Alternatively, data can be hosted on the East Coast of the USA.
Select the best region to fulfill your compliance and latency requirements.
Self-hosted option
GitGuardian can be deployed on bare metal, private or public clouds and can be deployed on existing Kubernetes cluster. It can be installed via a user-friendly interface or automated using Helm for a streamlined setup.
SSO
Single Sign-On functionality, compatible with any SAML 2.0 provider.
Audit logs
Get detailed activity logs of all actions triggered on the dashboard or through the REST API.
RBAC
Control user permissions in the GitGuardian dashboard with "Admin", "Member" and “Restricted” roles.
And hide your secrets from the privy eyes of attackers.