Try our new research platform with insights from 80,000+ expert users

DefectDojo vs GitGuardian Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 28, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

DefectDojo
Ranking in DevSecOps
11th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
1
Ranking in other categories
Vulnerability Management (37th)
GitGuardian Platform
Ranking in DevSecOps
3rd
Average Rating
8.8
Reviews Sentiment
7.3
Number of Reviews
32
Ranking in other categories
Application Security Tools (8th), Static Application Security Testing (SAST) (4th), Data Loss Prevention (DLP) (6th), Threat Intelligence Platforms (6th), Software Supply Chain Security (4th), Non-Human Identity Management (NHIM) (4th)
 

Mindshare comparison

As of August 2025, in the DevSecOps category, the mindshare of DefectDojo is 3.4%, up from 0.7% compared to the previous year. The mindshare of GitGuardian Platform is 3.8%, up from 2.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
DevSecOps Market Share Distribution
ProductMarket Share (%)
GitGuardian Platform3.8%
DefectDojo3.4%
Other92.8%
DevSecOps
 

Featured Reviews

reviewer2267097 - PeerSpot reviewer
Easy to use with efficient vulnerability reporting and team collaboration
Use case, so all the reports from GitLeaks, DefectDojo, GitLeaks or dependency check or Trivy, they make reports, and we send this report to DefectDojo to have CVMs, Central Vulnerability Management. DefectDojo is Central Vulnerability Management. If you have a dashboard to set, we have…
Ney Roman - PeerSpot reviewer
Facilitates efficient secret management and improves development processes
Regarding the exceptions in GitGuardian Platform, we know that within the platform we have a way to accept a path or a directory from a repository, but it is not that visible at the very beginning. You have to figure out where to search for it, and once you have it, it is really good, but it is not that visible at the beginning. This should be made more exposed. The documentation could be better because it was not that comprehensively documented. When we started working with GitGuardian Platform, it was difficult to find some specific use cases, and we were not aware of that. It might have improved now, but at that time, it was not something we would recommend.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"With the pipeline of detection and DefectDojo, we are able to see the real vulnerabilities, and we fix them."
"GitGuardian public leak detection significantly enhances our organization's data security by continuously monitoring public repositories."
"I like GitGuardian's instant response. When you have an incident, it's reported immediately. The interface gives you a great overview of your current leaked secrets."
"When they give you a description of what happened, it's really easy to follow and to retest. And the ability to retest is something that you don't have in other solutions. If a secret was detected, you can retest if it is still there. It will show you if it is in the history."
"The most valuable feature of GitGuardian is that it finds tokens and passwords. That's why we need this tool. It minimizes the possibility of security violations that we cannot find on our own."
"GitGuardian has many features that fit our use cases. We have our internal policies on secret exposure, and our code is hosted on GitLab, so we need to prevent secrets from reaching GitLab because our customers worry that GitLab is exposed. One of the great features is the pre-receive hook. It prevents commits from being pushed to the repository by activating the hook on the remotes, which stops the developers from pushing to the remote. The secrets don't reach GitLab, and it isn't exposed."
"GitGuardian Platform has helped save significant time for the security team by eliminating the need to seek out development teams and work with them on exposed secrets, as much of this is now handled proactively."
"It's also worth mentioning that GitGuardian is unique because they have a free tier that we've been using for the first twelve months. It provides full functionality for smaller teams. We're a smaller company and have never changed in size, but we got to the point where we felt the service brought us value, and we want to pay for it. We also wanted an SLA for technical support and whatnot, so we switched to a paid plan. Without that, they had a super-generous, free tier, and I was immensely impressed with it."
"It actually creates an incident ticket for us. We can now go end-to-end after a secret has been identified, to track down who owns the repository and who is responsible for cleaning it up."
 

Cons

"We need something to notify the team responsible for a product when vulnerabilities are found."
"An area for improvement is the front end for incidents. The user experience in this area could be much better."
"There has been a little bit of downtime of late, and it has been reasonably impactful when it's not been scanning."
"There are some features that are lacking in GitGuardian. The more we grow and the more engineers we have, the more it will become difficult to assign an incident because the assignment is not automatic. I know they are working on that and we are waiting for it."
"If a developer commits code into their repo, it generates an alert. The alert comes into Slack, but by the time someone looks at it through the Slack alerting channel, the developer might have gone and already fixed or closed the issue. There's no sort of feedback loop to come back into the notification channel to show that it's been addressed."
"It took us a while to get new patterns introduced into the pattern reporting process."
"One of our current challenges is that the GitGuardian platform identifies encrypted secrets and statements as sensitive information even though they're secured."
"I'm excited about the possibility of Public Postman scanning being integrated with GitGuardian in the future. Additionally, I'm interested in exploring the potential use of honeytokens, which seems like a compelling approach to lure and identify attackers."
"GitGuardian could have more detailed information on what software engineers can do. It only provides some highly generic feedback when a secret is detected. They should have outside documentation. We send this to our software engineers, who are still doing the commits. It's the wrong way to work, but they are accustomed to doing it this way. When they go into that ticket, they see a few instructions that might be confusing. If I see a leaked secret committed two years ago, it's not enough to undo that commit. I need to go in there, change all my code to utilize GitHub secrets, and go on AWS to validate my key."
 

Pricing and Cost Advice

Information not available
"It's a little bit expensive."
"The pricing and licensing are fair. It isn't very expensive and it's good value."
"It's a bit expensive, but it works well. You get what you pay for."
"We don't have a huge number of users, but its yearly rate was quite reasonable when compared to other per-seat solutions that we looked at... Having a free plan for a small number of users was really great. If you're a small team, I don't see why you wouldn't want to get started with it."
"GitGuardian is on the pricier side."
"The internal side is cheap per user. It is annual pricing based on the number of users."
"We have seen a return on investment. The amount of time that we would have spent manually doing this definitely outpaces the cost of GitGuardian. It is saving us about $35,000 a year, so I would say the ROI is about $20,000 a year."
"The pricing for GitGuardian is fair."
report
Use our free recommendation engine to learn which DevSecOps solutions are best for your needs.
866,286 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
16%
Comms Service Provider
13%
Retailer
8%
Government
19%
Computer Software Company
18%
Financial Services Firm
7%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise9
Large Enterprise13
 

Questions from the Community

What is your experience regarding pricing and costs for DefectDojo?
The pricing is great. It is much cheaper compared to other solutions. We don't want to pay for things we are able to do on our own.
What needs improvement with DefectDojo?
We need something to notify the team responsible for a product when vulnerabilities are found. We are able to attach a team or a manager for a product, however, we are not able to send them a notif...
What is your primary use case for DefectDojo?
Use case, so all the reports from GitLeaks, DefectDojo, GitLeaks or dependency check or Trivy, they make reports, and we send this report to DefectDojo to have CVMs, Central Vulnerability Managemen...
What do you like most about GitGuardian Internal Monitoring ?
It's also worth mentioning that GitGuardian is unique because they have a free tier that we've been using for the first twelve months. It provides full functionality for smaller teams. We're a smal...
What is your experience regarding pricing and costs for GitGuardian Internal Monitoring ?
It's competitively priced compared to others. Overall, the secret detection sector is expensive, but we are happy with the value we get.
What needs improvement with GitGuardian Internal Monitoring ?
GitGuardian Platform does what it is designed to do, but it still generates many false positives. We utilize the automated playbooks from GitGuardian Platform, and we are enhancing them. We will pr...
 

Also Known As

No data available
GitGuardian Internal Monitoring, GitGuardian Public Monitoring
 

Overview

 

Sample Customers

Information Not Available
Widely adopted by developer communities, GitGuardian is used by over 600 thousand developers and leading companies, including Snowflake, Orange, Iress, Mirantis, Maven Wave, ING, BASF, and Bouygues Telecom.
Find out what your peers are saying about GitLab, Snyk, GitGuardian and others in DevSecOps. Updated: August 2025.
866,286 professionals have used our research since 2012.