Item: GitGuardian Internal Monitoring
Rating: 9
Author: Abhishek Nayak

Use Cases and Deployment Scope

I use GitGuardian Internal Monitoring mainly for vulnerability and leaks detection. I use it to scan my codebase and commits for secrets before pushing to any remote git repositories. In the past it has detected major leaks and helped protect my secrets and give steps to remedy the situation whenever such a situation happens.

Pros and Cons

Scan codebase
Detect leaks
Send notifications when vulnerabilities exposed

Web UI can improve

Return on Investment

Protect data
Ensure security

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

Other Software Used

GitHub, AWS CloudTrail

Likelihood to Recommend

Any scenario where you are exposing your code publicly and there are concerns for leaks. Like I had said before, we use it in our codebases for detection before commits and pushes to the remote git repository. Any leaks for private API keys can be tracked and also remedial steps to fix the situation.

GitGuardian Internal Monitoring protected my data from leaks

Overall Satisfaction with GitGuardian Internal Monitoring