In this document, we go beyond classical definitions of DevSecOps to express our vision of an emerging collaboration between Developers, AppSec, and Ops teams: the AppSec Shared Responsibility Model.
As presented in our 2022 State of Secrets Sprawl report a single AppSec engineer has to handle more than 3.4K secrets occurrences a year! And this is only considering one type of vulnerabilityā¦
This has huge consequences if you want to release secure applications at the DevOps velocity. It means that to embed security controls into the DevOps culture, processes, and tools, you need to reduce friction and break the security silo. This is why application security needs to evolve towards a new shared responsibility model.
GitGuardian is a great tool to improve security starting from the development. I greatly appreciated the pre-commit integration that allows developers to very easily prevent accidental commits.
What I like the most about GitGuardian is the ability to automatically scan source code and detect leaked secrets. It has enabled us to add additional security control to our CI/CD pipeline, and enabled us to shift further left in the SDLC by implementing pre-commit hooks for developers to test their code before it is committed.
The perfect GitHub companion! It helps you track any sensitive data you may have shared in the repos, either public or private. Its algorithm is pretty advanced and I've never had any false positives.
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.
Verified by
Security Engineer at a Tech Services Company
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.
GitGuardian leads the way in Non-Human Identity security, offering end-to-end solutions from secrets detection in code, productivity tools and environments to strong remediation, observability and proactive prevention of leaks.
.svg)
