Item: GitGuardian Internal Monitoring
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We utilize it as part of our CI/CD pipelines to prevent secrets from ever making it to a production environment. Additionally, if a secret is present, we are able to setup instant alerts to our security response team. Tracking secrets in this way has helped increase our git integrity.

Pros and Cons

Notifications of secret discovery
Tracking and assignment of secret incidents
Resolution tracking

Better detection of high entropy general secrets
Ability to declare a high entropy string as a public key at code level
Better resolution of false positives

Most Important Features

Alerts
Assignments
Resolutions

Return on Investment

Quicker response times to security incidents
Excessive false positives of public keys
No way to declare a key as public at the code level

Key Insights

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

Likelihood to Recommend

GitGuardian is well suited to respond to security incidents involving breaches of git. Additionally, it is an excellent tool to identify secrets from the moment they are committed to version control. it is certainly less suitable for front end applications where secrets should not be present from the beginning and consistently flags, public keys as security incidents.

Significant value in this product

Overall Satisfaction with GitGuardian Internal Monitoring