No more typing reviews! Try our Samantha, our new voice AI agent.

GitGuardian Platform vs Legit Security comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 8, 2026

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

GitGuardian Platform
Average Rating
8.8
Reviews Sentiment
7.1
Number of Reviews
33
Ranking in other categories
Application Security Tools (13th), Non-Human Identity Management (NHIM) (8th)
Legit Security
Average Rating
10.0
Reviews Sentiment
7.8
Number of Reviews
4
Ranking in other categories
Software Supply Chain Security (17th), Application Security Posture Management (ASPM) (13th)
 

Mindshare comparison

While both are Application Lifecycle Management solutions, they serve different purposes. GitGuardian Platform is designed for Non-Human Identity Management (NHIM) and holds a mindshare of 3.4%.
Legit Security, on the other hand, focuses on Software Supply Chain Security, holds 3.7% mindshare, down 4.7% since last year.
Non-Human Identity Management (NHIM) Mindshare Distribution
ProductMindshare (%)
GitGuardian Platform3.4%
Saviynt Identity Cloud12.5%
Astrix10.7%
Other73.4%
Non-Human Identity Management (NHIM)
Software Supply Chain Security Mindshare Distribution
ProductMindshare (%)
Legit Security3.7%
JFrog Xray11.7%
Mend.io8.1%
Other76.5%
Software Supply Chain Security
 

Featured Reviews

Ney Roman - PeerSpot reviewer
DevOps Engineer at Deuna
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.
Tim Crothers - PeerSpot reviewer
CISO at Mandiant / FireEye
Provides strong visibility, straightforward integration, and reduces the risk of attacks
Legit Security is a product that hyper-focuses on the various aspects of the software development pipeline. For example, if an engineer spins off a new project and stands up a new Git project, Legit automatically detects it, connects Snyk and other tools, and ensures the engineering team doesn't have to think about it. This way, we stay on top of security from the beginning. On the other hand, Legit provides a clear view of the controls around repositories. We have standards requiring code reviews and similar practices, and Legit shows us whether these are being followed. Additionally, Legit helps us identify unmaintained repositories, which often arise when engineering teams try something and leave it behind. This knowledge allows us to determine the appropriate action for these neglected projects. One area where Legit falls short is secret detection. While it functions well overall, the feature has a 10-20 percent false positive rate, requiring some manual intervention. Almost everything else works flawlessly. The true value proposition of Legit lies not in its features but in its ability to support our product security program's focus on creating guardrails instead of toll gates. Unlike traditional programs that require security reviews at specific stages, hindering development flow, we strive to partner with the product engineering team to ship secure code seamlessly within their existing workflows. Legit plays a crucial role in this by automatically notifying us of new projects, eliminating the need for manual communication. This partnership approach, enabled by Legit, allows us to work much closer with our engineering teams than ever before.

Quotes from Members

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

Pros

"The breadth of the solution detection capabilities is pretty good. They have good categories and a lot of different types of secrets... it gives us a great range when it comes to types of secrets, and that's good for us."
"Transferring code from another platform to GitGuardian enabled us to see open passwords in old repositories and enabled us to clean them well and create a barrier against security leaks."
"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."
"Time to remediation is now in minutes or hours, whereas it used to take days or weeks previously."
"We have scanned over 20,000 commits in the last month and found 256 secrets that would have made it to production."
"GitGuardian has helped to increase our security team's productivity. Now, we don't need to call the developers all the time and ask what they are working on. I feel the solution bridged the gap between our team and the developers, which is really great. I feel that we need that in our company, since some of the departments are just doing whatever and you don't know what they are doing. I think GitGuardian does a good job of bridging the gap. It saves us about 10 hours per week."
"What is particularly helpful is that having GitGuardian show that the code failed a check enables us to automatically pass the resolution to the author. We don't have to rely on the reviewer to assign it back to him or her. Letting the authors solve their own problems before they get to the reviewer has significantly improved visibility and reduced the remediation time from multiple days to minutes or hours. Given how time-consuming code reviews can be, it saves some of our more scarce resources."
"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, as it is saving us about $35,000 a year, so I would say the ROI is about $20,000 a year."
"Legit has increased my security posture to a level I couldn't achieve before. I don't need to worry as much about what's happening within my developer environments. I can rest assured that my vulnerabilities are being detected."
"We implemented Legit Security to gain visibility into all development teams and ensure that consistent controls are in place and accounted for on every route."
"The true value proposition of Legit lies not in its features but in its ability to support our product security program's focus on creating guardrails instead of toll gates."
"Legit has had a positive effect on our overall security posture."
 

Cons

"It took us a while to get new patterns introduced into the pattern reporting process."
"There is room for improvement in GitGuardian on Azure DevOps. The implementation is a bit hard there. This is one of the things we requested help with. I would not say their support is not good, but they need them to improve in helping customers on that side."
"For some repositories, there are a lot of incidents. For example, one repository says 255 occurrences, so I assume these are 255 alerts and nobody is doing anything about them. These could be false positives. However, I cannot assess it correctly, because I haven't been closing these false positives myself. From the dashboard, I can see that for some of the repositories, there have been a lot of closing of these occurrences, so I would assume there are a lot of false positives. A ballpark estimate would be 60% being false positives. One of the arguments from the developers against this tool is the number of false positives."
"An area for improvement is the front end for incidents. The user experience in this area could be much better."
"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."
"It could be easier. They have a CLI tool that engineers can run on their laptops, but getting engineers to install the tool is a manual process. I would like to see them have it integrated into one of those developer tools, e.g., VS Code or JetBrains, so developers don't have to think about 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."
"GitGuardian encompasses many secrets that companies might have, but we are a Microsoft-only organization, so there are some limitations there in terms of their honey tokens. I'd like for it to not be limited to Amazon-based tokens. It would be nice to see a broader set of providers that you could pick from."
"The one we're working on right now is the ability to dynamically rerun development teams and groups."
"I would like them to have their own static code scanner, and I'd like them to have their own open-source software scanners."
"One issue is that engineering teams don't always embed secrets in the same way, making it difficult for the tool to consistently identify them."
"Legit Security could do a little better with detecting publicly exposed keys. It's not bad. The detections that they are running get to everything eventually, but it would be great if they could increase some of that awareness."
 

Pricing and Cost Advice

"The pricing is reasonable. GitGuardian is one of the most recent security tools we've adopted. When it came time to renew it, there was no doubt about it. It is licensed per developer, so it scales nicely with the number of repos that we have. We can create new repositories and break up work. It isn't scaling based on the amount of data it's consuming."
"It's not cheap, but it's not crazy expensive either."
"I am only aware of the base price. I do not know what happened with our purchasing team in discussions with GitGuardian. I was not privy to the overall contract, but in terms of the base MSRP price, I found it reasonable."
"It's a little bit expensive."
"It's fairly priced, as it performs a lot of analysis and is a valuable tool."
"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."
"The internal side is cheap per user. It is annual pricing based on the number of users."
"It could be cheaper. When GitHub secrets monitoring solution goes to general access and general availability, GitGuardian might be in a little bit of trouble from the competition, and maybe then they might lower their prices. The GitGuardian solution is great. I'm just concerned that they're not GitHub."
"The pricing is reasonable."
report
Use our free recommendation engine to learn which Non-Human Identity Management (NHIM) solutions are best for your needs.
902,588 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
13%
Outsourcing Company
10%
Government
10%
Financial Services Firm
9%
Financial Services Firm
13%
University
12%
Construction Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise9
Large Enterprise20
No data available
 

Questions from the Community

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...
What is your primary use case for GitGuardian Internal Monitoring ?
Our current use cases for GitGuardian Platform involve monitoring external and internal GitHub and GitLab, Bitbucket, and other code repositories that it supports for secrets.
Ask a question
Earn 20 points
 

Also Known As

GitGuardian Internal Monitoring, GitGuardian Public Monitoring
No data available
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

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.
Google, NYSE, Kraft-Hienz, Takeda Pharmaceuticals, and many other large enterprise and Fortune 500 customers. Learn more by going to: https://www.legitsecurity.com/...
Find out what your peers are saying about One Identity, Astrix Security, Entro Security and others in Non-Human Identity Management (NHIM). Updated: June 2026.
902,588 professionals have used our research since 2012.