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

Comodo Dome Data Loss Prevention vs GitGuardian Public Monitoring comparison

 

Comparison Buyer's Guide

Executive Summary

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

Comodo Dome Data Loss Preve...
Ranking in Data Loss Prevention (DLP)
61st
Average Rating
0.0
Number of Reviews
0
Ranking in other categories
No ranking in other categories
GitGuardian Public Monitoring
Ranking in Data Loss Prevention (DLP)
23rd
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), Threat Intelligence Platforms (18th)
 

Mindshare comparison

As of June 2025, in the Data Loss Prevention (DLP) category, the mindshare of Comodo Dome Data Loss Prevention is 0.1%, down from 0.2% compared to the previous year. The mindshare of GitGuardian Public Monitoring is 0.4%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Loss Prevention (DLP)
 

Featured Reviews

Use Comodo Dome Data Loss Prevention?
Share your opinion
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.
report
Use our free recommendation engine to learn which Data Loss Prevention (DLP) solutions are best for your needs.
858,038 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Government
21%
Computer Software Company
14%
Energy/Utilities Company
14%
Comms Service Provider
11%
 

Company Size

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

Questions from the Community

Ask a question
Earn 20 points
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.
 

Also Known As

Dome Data Loss Prevention
No data available
 

Overview

 

Sample Customers

Information Not Available
Align Technology, Automox, Fred Hutch, Instacart, Maven Wave, Mirantis, SafetyCulture, Snowflake, Talend
Find out what your peers are saying about Microsoft, Zscaler, Broadcom and others in Data Loss Prevention (DLP). Updated: June 2025.
858,038 professionals have used our research since 2012.