Whether you are looking to prevent attackers from using public GitHub as a backdoor to your systems or reduce the risk of exposing secrets in your SDLC, GitGuardian has something for you.
Learn how organizations use the GitGuardian platform to fight secrets sprawl and strengthen their security posture.
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.
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.