We performed a comparison between Check Point CloudGuard Code Security 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."Knowing what measures we must take allows us to reduce costs associated with security in the cloud by providing early identification of a risk or a possible security breach."
"The data center security system has provided real-time analytics on performance and data configuration processes."
"We have a strong sense of security assurance when utilizing CloudGuard, as it consistently delivers outstanding protection capabilities."
"Having a cloud detection response helps to very quickly identify security threats in our environment."
"You can maintain a legal framework structure at all times."
"Check Point CloudGuard Code Security helps to improve the code security of our company, generating rapid and complete assessments to be able to make decisions for improvements."
"We have had a number of real events where developers accidentally made commits of API keys, and we were able to detect and begin response actions in minutes. We had the API key revoked in less than five minutes in such events."
"Its fastest and most outstanding characteristic is ensuring a development line that will not lead to applying applications or code development."
"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."
"The entire GitGuardian solution is valuable. The product is doing its job and showing us many things. We get many false positives, but the ability to automatically display potential leaks when developers commit is valuable. The dashboards show you recent and historical commits, and we have a full scan that shows historical leaked secrets."
"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."
"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."
"GitGuardian Internal Monitoring has helped increase our secrets detection rate by several orders of magnitude. This is a hard metric to get. For example, if we knew what our secrets were and where they were, we wouldn't need GitGuardian or these types of solutions. There could be a million more secrets that GitGuardian doesn't detect, but it is basically impossible to find them by searching for them."
"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."
"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."
"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."
"I would like this solution to be extended to cellular devices or tablets."
"The costs are not transparent."
"There needs to be better security around API integration."
"The enhancements are needed in the logging system and log management processes."
"I am satisfied with the performance and results enhanced by this product since we deployed it."
"There are a lot of opportunities for how they can use their technology to do more. That would be more like sensitive data discovery and other things besides Git Repos, but then you are expanding the scope of what necessarily their product is."
"We need to have many of the baselines or development guides providing less complex writing or development."
"They could include web functionalities such as sandboxing."
"Automated Jira tickets would be fantastic. At the moment, I believe we have to go in and click to create a Jira ticket. It would be nice to automate."
"We have been somewhat confused by the dashboard at times."
"The main thing for me is the customization for some of the healthcare-specific identifiers that we want to validate. There should be some ability, which is coming in the near future, to have custom identifiers. Being in healthcare, we have pretty specific patterns that we need to match for PHI or PII. Having that would add a little bit extra to it."
"It would be nice if they supported detecting PII or had some kind of data loss prevention feature."
"An area for improvement is the front end for incidents. The user experience in this area could be much better."
"Right now, we are waiting for improvement in the RBAC support for GitGuardian."
"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 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."
More Check Point CloudGuard Code Security Pricing and Cost Advice →
Check Point CloudGuard Code Security is ranked 11th in Data Loss Prevention (DLP) with 11 reviews while GitGuardian Platform is ranked 6th in Data Loss Prevention (DLP) with 23 reviews. Check Point CloudGuard Code Security is rated 8.4, while GitGuardian Platform is rated 9.0. The top reviewer of Check Point CloudGuard Code Security writes "Good security and functionality with helpful support". 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". Check Point CloudGuard Code Security is most compared with Snyk, Aqua Cloud Security Platform and Palo Alto Networks Enterprise Data Loss Prevention, whereas GitGuardian Platform is most compared with SonarQube, Cycode, GitHub Advanced Security, Snyk and Microsoft Purview Data Loss Prevention. See our Check Point CloudGuard Code Security vs. GitGuardian Platform report.
See our list of best Data Loss Prevention (DLP) vendors and best DevSecOps 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.
