PUBLIC MONITORING
GitGuardian monitors GitHub round the clock for your secrets and sensitive data. We catch the leaks, you stop the intrusions.
90+ Million developers
56 M developers
300+ Million repositories
60 M repositories
Even if your company doesn't do open source, chances are your developers do. And they may be unintentionally leaking your corporate secrets or source code on their personal GitHub repos - without your knowledge.
Since 2017, we’ve scanned every contribution and event on public repositories, catching every secret — and a lot of sensitive data. Our algorithms and detectors constantly train against a dataset of %dscb% billion commits — ensuring alerts of the highest fidelity and precision.
We gathered all our findings from extensive
research on public GitHub in a report.
Prospects and customers conduct cybersecurity and privacy risk assessments to identify, evaluate, and contract with software vendors. Cover your organization from the risks associated with public GitHub, build trust, and accelerate sales with GitGuardian.
What I have found to be very effective with GitGuardian is that we can analyze the history of Talend-related alerts on the entire GitHub perimeter, whether they are our official repositories or any public directory outside the control of Talend. What was very interesting and what we didn't anticipate was that most of leaked secrets came from the personal code repositories of our developers.
Partnering with MSPs introduces potential third-party attack surfaces and unanticipated organizational risks. Proactively manage your risk on public GitHub and keep your customers’ secrets and sensitive data out of sight.
Most DLPs would put the burden of defining the perimeter on us. GitGuardian is different, it takes care of all the hard work. We now have full visibility over what’s happening on public GitHub and with real-time alerting, we can take action before it’s too late.
Compromised secrets on public GitHub give attackers easy, authorized access to your IT systems and internals. Equip your Threat Intel teams with GitGuardian's real-time GitHub monitoring and stay ahead of attackers.
If a colleague in security at another company were to say to me that secrets detection is not a priority, I'd ask them why that's the case. Arguably, secrets in source code are a very large risk, especially given its distributed nature. People may be using different kinds of machines to do their work, and we need to make sure that sensitive data is kept out of public GitHub.
Find out how GitGuardian keeps your organization safe from GitHub threats
Organization repositories monitoring
Monitor the official public repositories listed under your GitHub organization.
Developers’ personal repositories monitoring
Monitor developers’ personal public repositories – this is where 80% of corporate credentials are leaked on public GitHub. GitGuardian identifies under-the-radar activity by automatically linking developers, public commits, and repositories you may be unaware of to your organization’s dynamic perimeter.
Exposing dangerous blind spots
Identify secrets within commits supposedly deleted, but still visible within GitHub network of forks.
Specific detectors
GitGuardian's specific detectors support %ndetg%+ API providers, database connection strings, SMTP credentials, certificates...
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".
High precision detection
Reduce alert fatigue with a %sdtpr%% True Positive Rate (TPR) and the grouping of multiple instances of the same incident in one alert.
GitGuardian performs contextual analysis of the surrounding code to discard false positives and weak matches. When possible, GitGuardian also checks the validity of the detected secrets with non-intrusive HTTP calls to the host.
Keyword match
Track keywords on public GitHub to look for your organization’s internal project names, reserved IP addresses range, domain names, or any other type of sensitive data.
Explore – GitHub search
Use Explore, GitGuardian’s search engine to scour more than 12 billion documents on public GitHub for sensitive data. Save your queries in your library and schedule periodic runs.
Real-time alerting
GitGuardian’s Mean-Time-To-Detect is a few seconds after the secret is publicly exposed.
Developer alerting
Developers are at the forefront of the issue of secrets leaks. GitGuardian alerts the developers involved in the incidents alongside your Security team.
Integrations
Connect GitGuardian to your SIEM, ITSM, ticketing systems, messaging apps or configure your own webhooks.
Incident severity assignment
Start from templates and create custom rules to automate incident severity assignment.
Incident prioritization
Explore and triage your incidents with key context information: secret type, location (repository and files), incident severity, number of occurrences, live presence on GitHub, 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 its potential impact on your company or client systems.
Programmatic incident handling
Manage incidents programmatically with a REST API.
SSO
Single Sign-On functionality, compatible with any SAML 2.0 provider.
Audit logs
Browse detailed activity logs of all actions triggered on the dashboard or through GitGuardian’s REST API.
Roles and permissions
Control user permissions in the GitGuardian dashboard with "Admin" and "Member" roles.
And keep your secrets out of sight