We performed a comparison between Red Hat Advanced Cluster Security for Kubernetes and Snyk based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Red Hat Advanced Cluster Security for Kubernetes is highly regarded for its exceptional resource-sharing and segmentation capabilities. Snyk earns praise for its developer-friendly approach and range of scanning features. Snyk also stands out for its software composition analysis and compatibility with containers. Red Hat Advanced Cluster Security reviewers stressed a need for better documentation. They would also like the solution to incorporate features like zero trust and access control. Users said Snyk should work on improving compatibility and enhancing their vulnerability database.
Service and Support: Red Hat has been praised for its efficient and effective technical support. Some Snyk customers said support could better organize and prioritize requests.
Ease of Deployment: Red Hat Advanced Cluster Security for Kubernetes requires users to create various customer resource files and deploy an image as a container, which is a time-consuming process that can take days or weeks to configure. Snyk's setup is simple and uncomplicated, with users reporting positive experiences and excellent support from the vendor team.
Pricing: Advanced Cluster Security for Kubernetes is moderately priced, and Red Hat offers affordable bundled pricing options. Snyk is considered expensive relative to other solutions. Users say it is better suited for larger companies or enterprises that can afford it.
ROI: Red Hat Advanced Cluster Security for Kubernetes provides extensive security features, while Snyk emphasizes cost-effective vulnerability identification.
Comparison Results: Red Hat Advanced Cluster Security for Kubernetes is preferred over Snyk. Users appreciate its comprehensive setup process, scalability, and ability to run multiple containers. It also offers a hybrid cloud approach and seamless integration with other solutions. Some users encountered difficulties integrating Snyk with existing tools.
"PingSafe offers comprehensive security posture management."
"PingSafe's most valuable feature is its unified console."
"Cloud Native Security's best feature is its ability to identify hard-coded secrets during pull request reviews."
"As a frequently audited company, we value PingSafe's compliance monitoring features. They give us a report with a compliance score for how well we meet certain regulatory standards, like HIPAA. We can show our compliance as a percentage. It's also a way to show that we are serious about security."
"The solution helped free other staff to work on other projects or other tasks. We basically just had to do a bunch of upfront configuring. With it, we do not have to spend as much time in the console."
"It is fairly simple. Anybody can use it."
"The management console is highly intuitive to comprehend and operate."
"Cloud Native Security helps us discover vulnerabilities in a cloud environment like open ports that allow people to attack our environment. If someone unintentionally opens a port, we are exposed. Cloud Native Security alerts us so we can remediate the problem. We can also automate it so that Cloud Native Security will fix it."
"Scalability-wise, I rate the solution a nine out of ten."
"I like virtualization and all those tools that come with OpenShift. I also like Advanced Cluster Management and the built-in security."
"The technical support is good."
"I am impressed with the tool's visibility."
"The most valuable feature is the ability to share resources."
"The most valuable feature of the solution is its monitoring feature."
"The benefit of working with the solution is the fact that it's very straightforward...It is a perfectly stable product since the details are very accurate."
"Segmentation is the most powerful feature."
More Red Hat Advanced Cluster Security for Kubernetes Pros →
"Snyk is a developer-friendly product."
"The most valuable features are their GitLab and JIRA integrations. The GitLab integration lets us pull projects in pretty easily, so that it's pretty minimal for developers to get it set up. Using the JIRA integration, it's also pretty easy to get the information that is generated, as a result of that GitLab integration, back to our teams in a non-intrusive way and in a workflow that we are already using."
"The code scans on the source code itself were valuable."
"The CLI feature is quite useful because it gives us a lot of flexibility in what we want to do. If you use the UI, all the information is there and you can see what Snyk is showing you, but there is nothing else that you can change. However, when you use the CLI, then you can use commands and can get the output or response back from Snyk. You can also take advantage of that output in a different way. For the same reason, we have been using the CLI for the hard gate in the pipeline: Obtain a particular CDSS score for vulnerability. Based on that information, we can then decide if we want to block or allow the build. We have more flexibility if we use the CLI."
"Its reports are nice and provide information about the issue as well as resolution. They also provide a proper fix. If there's an issue, they provide information in detail about how to remediate that issue."
"I find SCA to be valuable. It can read your libraries, your license and bring the best way to resolve your problem in the best scenario."
"Our customers find container scans most valuable. They are always talking about it."
"The most valuable feature of Snyk is the software composition analysis."
"Customized queries should be made easier to improve PingSafe."
"Currently, we would have to export our vulnerability report to an .xlsx file, and review it in an Excel spreadsheet, and then we sort of compile a list from there. It would be cool if there was a way to actually toggle multiple applications for review and then see those file paths on multiple users rather than only one user at a time or only one application at a time."
"They need more experienced support personnel."
"I export CSV. I cannot export graphs. Restricting it to the CSV format has its own disadvantages. These are all machine IP addresses and information. I cannot change it to the JSON format. The export functionality can be improved."
"They could generally give us better comprehensive rules."
"The cost has the potential for improvement."
"There's room for improvement in the graphic explorer."
"I used to work on AWS. At times, I would generate a normal bug in my system, and then I would check PingSafe. The alert used to come after about three and a half hours. It used to take that long to generate the alert about the vulnerability in my system. If a hacker attacks a system and PingSafe takes three to four hours to generate an alert, it will not be beneficial for the company. It would be helpful if we get the alert in five to ten minutes."
"The deprecation of APIs is a concern since the deprecation of APIs will cause issues for us every time we upgrade."
"The solution's visibility and vulnerability prevention should be improved."
"The testing process could be improved."
"The documentation about Red Hat Advanced Cluster Security available online is very limited... So it's very limited to the documentation."
"Red Hat is somewhat expensive."
"The solution's price could be better."
"They're trying to convert it to the platform as a source. They are moving in the direction of Cloud Foundry so it can be easier for a developer to deploy it."
"The solution lacks features when compared to some of the competitors such as Prisma Cloud by Palo Alto Networks and has room for improvement."
More Red Hat Advanced Cluster Security for Kubernetes Cons →
"Because Snyk has so many integrations and so many things it can do, it's hard to really understand all of them and to get that information to each team that needs it... If there were more self-service, perhaps tutorials or overviews for new teams or developers, so that they could click through and see things themselves, that would help."
"Could include other types of security scanning and statistical analysis"
"The way Snyk notifies if we have an issue, there are a few options: High vulnerability or medium vulnerability. The problem with that is high vulnerabilities are too broad, because there are too many. If you enable notifications, you get a lot of notifications, When you get many notifications, they become irrelevant because they're not specific. I would prefer to have control over the notifications and somehow decide if I want to get only exploitable vulnerabilities or get a specific score for a vulnerability. Right now, we receive too many high vulnerabilities. If we enable notifications, then we just get a lot of spam message. Therefore, we would like some type of filtering system to be built-in for the system to be more precise."
"The tool needs improvement in license compliance. I would like to see the integration of better policy management in the product's future release. When it comes to the organization that I work for, there are a lot of business units since we are a group of companies. Each of these companies has its specific requirements and its own appetite for risk. This should be able to reflect in flexible policies. We need to be able to configure policies that can be adjusted later or overridden by the business unit that is using the product."
"Snyk's API and UI features could work better in terms of speed."
"The solution's integration with JFrog Artifactory could be improved."
"They need to improve the Snyk plugins and make it easier to make your optimizations based on your own needs or features."
"I think Snyk should add more of a vulnerability protection feature in the tool since it is an area where it lacks."
More SentinelOne Singularity Cloud Security Pricing and Cost Advice →
More Red Hat Advanced Cluster Security for Kubernetes Pricing and Cost Advice →
Red Hat Advanced Cluster Security for Kubernetes is ranked 16th in Container Security with 10 reviews while Snyk is ranked 5th in Container Security with 41 reviews. Red Hat Advanced Cluster Security for Kubernetes is rated 8.4, while Snyk is rated 8.2. The top reviewer of Red Hat Advanced Cluster Security for Kubernetes writes "Provides network mapping feature for visualizing container communication but complex setup ". On the other hand, the top reviewer of Snyk writes "Performs software composition analysis (SCA) similar to other expensive tools". Red Hat Advanced Cluster Security for Kubernetes is most compared with Prisma Cloud by Palo Alto Networks, Aqua Cloud Security Platform, SUSE NeuVector, CrowdStrike Falcon Cloud Security and Tenable.io Container Security, whereas Snyk is most compared with SonarQube, Black Duck, GitHub Advanced Security, Fortify Static Code Analyzer and Veracode. See our Red Hat Advanced Cluster Security for Kubernetes vs. Snyk report.
See our list of best Container Security vendors.
We monitor all Container Security 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.