The best tool for securing your repositories against secret loss
January 10, 2022

The best tool for securing your repositories against secret loss

Alexander Bergmann | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with GitGuardian Internal Monitoring

We are running a micro-service architecture that is split into a lot of different repositories. Therefore it is hard to manage repository security ( in the manner of secrets) by hand. And here comes GitGuardian into play. With GitGuardian it is possible to find secrets in the single repositories. Which can be used to make attacks on our infrastructure. Also, it helps to empathize with the handling of secrets. Special the visualization makes it clear that in some points there is some action needed.
  • Finding secrets
  • Visualizing problematic handling of secrets
  • Free tier!
  • Good support
  • Nice webinars
  • Really hard to find things to improve
  • A little bit confusing GUI at the beginning (but really not that big)
  • Finding secrets in private repositories
  • Finding secrets in public repositories
  • Increasing overall security with that
  • No negative impact at all
We selected GitGuardian because I attended a webinar from them. And they explained excellent which security issues can be in secrets in public/private repositories and to mitigate this risks we decided to use GitGuardian. Also, the free tier is one of the things which are really great and good starting point into repository security. And it does what they promise, really good.

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

As I already wrote: It is excellent at finding secrets and declare the secrets into categories. Like when accidentally secrets are in a public repository or similar. Also to see and empathize the handling of secrets. Like it is possible to show to the colleagues (blameless!!!) that we have secrets in there which can be handled differently.