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

GitGuardian Public Monitoring vs ThreatQ comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 11, 2024

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 Public Monitoring
Ranking in Threat Intelligence Platforms
17th
Average Rating
9.0
Reviews Sentiment
7.0
Number of Reviews
2
Ranking in other categories
Application Security Tools (22nd), Static Application Security Testing (SAST) (19th), Data Loss Prevention (DLP) (23rd)
ThreatQ
Ranking in Threat Intelligence Platforms
12th
Average Rating
7.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
Security Orchestration Automation and Response (SOAR) (22nd)
 

Mindshare comparison

As of July 2025, in the Threat Intelligence Platforms category, the mindshare of GitGuardian Public Monitoring is 0.4%, up from 0.1% compared to the previous year. The mindshare of ThreatQ is 2.8%, up from 2.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Threat Intelligence Platforms
 

Featured Reviews

Theo Cusnir - PeerSpot reviewer
Detects and alerts us about leaks quickly, and enables us to filter and prioritize occurrences
One thing I really like about it is the fact that we can add search words or specific payloads inside the tool, and GitGuardian will look into GitHub and alert us if any of these words is found in a repository. For example, if I put "Payfit" in the tool, I will be alerted every time someone is committing with that word in the code. It's really useful for internal domain names, to detect if someone is leaking internal code. With this capability in the tool, we have good surveillance over our potential blind spots. It can detect a leak in 10 minutes. We had an experience with one of our engineers who had leaked a secret, and 10 minutes afterward we had a warning from GitGuardian about the leak. It's very effective. We looked at the commit date and the current date with hours and minutes and we could see that the commit had been made 10 minutes ago. As a result, we are sure it is pretty fast. Another feature, one that helps prioritize remediation, is that you can filter the findings by criticality. That definitely helps us to prioritize which secrets we should rotate and delete.
Yasir Akram - PeerSpot reviewer
Good reporting and pretty stable but needs to be simpler to use
The support team of ThreatQ set up a VM on our VPN, which was SlashNext's private VPN. Then we just initiated some system calls and ThreatQ provided us the configuration file with our settings (like our email, our API key, our URL, our category, etc.). They set up a VM on our private VPN cloud. And then they provided us the configuration file in which we just entered our details like our company URL, our API category, and API keys et cetera. We could just add it on the configuration file. We just uploaded it to the ThreatQ server. After running the system calls, we just initiated the ThreatQ and then performed tasks on the UI, such as categorizing the reports. If we only wanted the report for phishing, then we just manipulated the data on the UI and just extracted the reports. That's all. The deployment was complex. We used high hardware specifications. I don't remember the exact specifications, however, I recall them being high. There were some services that had some compatibility errors. That's why we had our VMs - to make sure that the customer would not face any errors. Everything's deployed with high specifications and custom specifications. That was the biggest challenge for us - to deploy on the customer VMs. On average, deployment takes 15-20 minutes if it's deployed without any errors. I was with one of the NetOps network admin during deployment. We were only two people and we just deployed and installed all services and we executed the deployment.

Quotes from Members

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

Pros

"One thing I really like about it is the fact that we can add search words or specific payloads inside the tool, and GitGuardian will look into GitHub and alert us if any of these words is found in a repository... With this capability in the tool, we have good surveillance over our potential blind spots."
"The Explore function is valuable for finding specific things I'm looking for."
"The reporting services are great. With reporting services, if you have customers that just visit a URL you can see the result - including why it's blocked and how and how the URL was first recognized as malicious."
"Integrating the solution with our existing security tools and workflows was easy."
 

Cons

"I would like to see improvement in some of the user interface features... When one secret is leaked in multiple files or multiple repositories, it will appear on the dashboard. But when you click on that secret, all the occurrences will appear on the page. It would be better to have one secret per occurrence, directly, so that we don't have to click to get to the list of all the occurrences."
"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."
"The tool is not user-friendly."
"The solution should be simpler for the end-user in terms of reporting and navigating the product."
 

Pricing and Cost Advice

"It's a bit expensive, but it works well. You get what you pay for."
Information not available
report
Use our free recommendation engine to learn which Threat Intelligence Platforms solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
20%
Computer Software Company
13%
Energy/Utilities Company
13%
Comms Service Provider
12%
Financial Services Firm
21%
Computer Software Company
13%
Manufacturing Company
10%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What do you like most about GitGuardian Public Monitoring?
The Explore function is valuable for finding specific things I'm looking for.
What needs improvement with GitGuardian Public Monitoring?
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...
What is your primary use case for GitGuardian Public Monitoring?
We use GitGuardian Public Monitoring for code that is exposed in public.
What do you like most about ThreatQ?
Integrating the solution with our existing security tools and workflows was easy.
What needs improvement with ThreatQ?
The tool is not user-friendly. It is not beginner-friendly. It would be very difficult for a beginner to learn the tool. It will take at least two months to get familiar with it. Building the playb...
What is your primary use case for ThreatQ?
We used the solution for threat mapping and managing IoCs.
 

Overview

 

Sample Customers

Align Technology, Automox, Fred Hutch, Instacart, Maven Wave, Mirantis, SafetyCulture, Snowflake, Talend
Radar, Bitdefender, Crowdstrike, FireEye, IBM Security
Find out what your peers are saying about GitGuardian Public Monitoring vs. ThreatQ and other solutions. Updated: June 2025.
860,592 professionals have used our research since 2012.