We performed a comparison between Forcepoint Risk Adaptive Protection for DLP and GitGuardian Platform based on real PeerSpot user reviews.
Find out in this report how the two Data Loss Prevention (DLP) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We chose Forcepoint as part of our cybersecurity strategy, and one of the key expectations was to prevent data leakage."
"It primarily influences policy enforcement, cloud application access control, and endpoint network coverage."
"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."
"You can also assign tasks to specific teams or people to complete, such as assigning something to the "blue team" or saying that this person needs to do this, and that person needs to do that. That is a great feature because you can actually manage your team internally in GitGuardian."
"Presently, we find the pre-commit hooks more useful."
"GitGuardian has also helped us develop a security-minded culture. We're serious about shift left and getting better about code security. I think a lot of people are getting more mindful about what a secret is."
"The secrets detection and alerting is the most important feature. We get alerted almost immediately after someone commits a secret. It has been very accurate, allowing us to jump on it right away, then figure out if we have something substantial that has been leaked or whether it is something that we don't have to worry about. This general main feature of the app is great."
"We have definitely seen a return on investment when it finds things that are real. We have caught a couple things before they made it to production, and had they made it to production, that would have been dangerous."
"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."
"GitGuardian has pretty broad detection capabilities. It covers all of the types of secrets that we've been interested in... [Yet] The "detector" concept, which identifies particular categories or types of secrets, allows an organization to tweak and tailor the configuration for things that are specific to its environment. This is highly useful if you're particularly worried about a certain type of secret and it can help focus attention, as part of early remediation efforts."
"The deployment is a little bit difficult. It requires two to three separate servers for databases and the application."
"From an end user's perspective, it's not always clear what's happening with the DLP. It would be beneficial to have more use cases available, perhaps on a countrywide basis."
"We have encountered occasional difficulties with the Single Sign-On process."
"GitGuardian's hook and dashboard scanners are the two entities. They should work together as one. We've seen several discrepancies where the hook is not being flagged on the dashboard. I still think they need to do some fine-tuning around that. We don't want to waste time."
"There is room for improvement in its integration for bug-tracking. It should be more direct. They have invested a lot in user management, but they need to invest in integrations. That is a real lack."
"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."
"It took us a while to get new patterns introduced into the pattern reporting process."
"One improvement that I'd like to see is a cleaner for Splunk logs. It would be nice to have a middle man for anything we send or receive from Splunk forwarders. I'd love to see it get cleaned by GitGuardian or caught to make sure we don't have any secrets getting committed to Splunk logs."
"We have been somewhat confused by the dashboard at times."
"Right now, we are waiting for improvement in the RBAC support for GitGuardian."
More Forcepoint Risk Adaptive Protection for DLP Pricing and Cost Advice →
Forcepoint Risk Adaptive Protection for DLP is ranked 26th in Data Loss Prevention (DLP) with 2 reviews while GitGuardian Platform is ranked 6th in Data Loss Prevention (DLP) with 21 reviews. Forcepoint Risk Adaptive Protection for DLP is rated 7.0, while GitGuardian Platform is rated 9.0. The top reviewer of Forcepoint Risk Adaptive Protection for DLP writes "Stable product, key part of cybersecurity strategy but country-specific configuration issues requiring manual work ". On the other hand, the top reviewer of GitGuardian Platform writes "It dramatically improved our ability to detect secrets, saved us time, and reduced our mean time to remediation". Forcepoint Risk Adaptive Protection for DLP is most compared with , whereas GitGuardian Platform is most compared with SonarQube, Cycode, GitHub Advanced Security, Snyk and Microsoft Purview Data Loss Prevention. See our Forcepoint Risk Adaptive Protection for DLP vs. GitGuardian Platform report.
See our list of best Data Loss Prevention (DLP) vendors.
We monitor all Data Loss Prevention (DLP) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
