GitGuardian saving secrets leakage
June 15, 2022
GitGuardian saving secrets leakage
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with GitGuardian Internal Monitoring
We had a very bad incident with one junior developer that pushed some secrets to a personal and public repository. In minutes we were hacked and we didn't see the notifications after 3 days of being hacked. Because of that now we are using GitGuardian for 2 things: scanning our repos and the ggshield pre-commit hook installed on every developer to avoid such future problems. The scanning let us discover even more exposed secrets on private repos mostly done by junior developers and helped us a lot with new security policies. The pre-commit hook is also a very nice security feature with are now using for everything.
- Scanning for secrets
- Validating secrets
- Some false positives for secrets
- Secrets scanning
- Avoid secrets leakage.
Did not explore other alternatives.
Do you think GitGuardian Internal Monitoring delivers good value for the price?
Yes
Are you happy with GitGuardian Internal Monitoring's feature set?
Yes
Did GitGuardian Internal Monitoring live up to sales and marketing promises?
Yes
Did implementation of GitGuardian Internal Monitoring go as expected?
Yes
Would you buy GitGuardian Internal Monitoring again?
Yes