
No stone left unturned: detecting custom patterns is now available in GitGuardian.
GitGuardian users can now extend the secrets detection engine and configure custom patterns to detect proprietary secrets and credentials.
GitGuardian users can now extend the secrets detection engine and configure custom patterns to detect proprietary secrets and credentials.
While scanning millions of documents for secrets, should we really aim at reaching absolute zero or is the story not so simple?
From benchmark analysis, here are our key takeaways on building efficient real-time data filtering pipelines.
New series focusing on performance at GitGuardian. Learn how we built the tools to produce meaningful benchmarks and track our improvements in speed over the year.
GitGuardian now supports more than 300 secrets detectors, available in both products: GitGuardian for Public GitHub Monitoring and GitGuardian for Internal Repositories Monitoring.
Discover what generic secrets detection is really about, why it's a critical component to build a performant secrets detection engine, and how GitGuardian is tackling this problem.
In this tutorial we are going to run through how to create a pre-commit git hook using GitGuardian Shield to detect secrets before they enter your repository.
This article explains how our research team develops and refines detectors. To illustrate this article, we will take the case of MongoDB credentials.
GitGuardian has been scanning every single public commit made on GitHub for secrets since 2017, now we are releasing our findings in the most comprehensive study on secrets sprawl ever conducted.
This article will expose how our algorithms detect secrets and what we have learnt from scanning, literally, billions of commits.
Secrets including API tokens, passwords and credentials are the keys to the kingdom. Yet storing secrets inside git including GitHub & GitLab is a problem. Security experts discuss why this is & how to solve this.
This article looks at how SAP built an internal secrets scanning solution to detect API keys and other credentials hardcoded in git repos and revoke them.