We performed a comparison between Mirantis Container Cloud and Snyk based on real PeerSpot user reviews.
Find out in this report how the two Container Security solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The offensive security where they do a fix is valuable. They go to a misconfiguration and provide detailed alerts on what could be there. They also provide a remediation feature where if we give the permission, they can also go and fix the issue."
"We like PingSafe's vulnerability assessment and management features, and its vulnerability databases."
"The mean time to detect has been reduced."
"We really appreciate the Slack integration. When we have an incident, we get an instant notification. We also use Joe Sandbox, which Singularity can integrate with, so we can verify if a threat is legitimate."
"Cloud Native Security offers attack path analysis."
"The visibility is the best part of the solution."
"PingSafe's most valuable feature is its unified console."
"I did a lot of research before signing up and doing the demo. They have a good reputation as far as catching threats early on."
"I think the volume binding is a really interesting feature."
"This solution has improved our organization with the agility, microservices approach, and scalable solutions for distributed systems."
"The product's initial setup phase is simple."
"The product is easy to use."
"When you have Kubernetes, you can use Mirantis Container Cloud to manage your Kubernetes for easy access and security. It also helps you to manage your CI/CD system. It helps you to build a container-oriented developer workflow. So, if you're building an application in Kubernetes, it provides you with a Kubernetes engine."
"I use Docker in combination with Kubernetes. Management of software packages is easy. It also can be done fast. Rolling out new software updates is smoother and faster due to Mirantis Container Cloud."
"One of the most valuable feature is its scalability because it is easy to work with. Even though I haven't fully removed it before, it's simple to get started and develop further. It's comparable to working with languages like C++ and Python. Python. It is easy to understand and more user-friendly."
"This solution has cut down on our development time and allows us to spin off new instances for inner development, testing, productions, and security testing."
"It has improved our vulnerability rating and reduced our vulnerabilities through the tool during the time that we've had it. It's definitely made us more aware, as we have removed scoping for existing vulnerabilities and platforms since we rolled it out up until now."
"A main feature of Snyk is that when you go with SCA, you do get properly done security composition, also from the licensing and open-source parameters perspective. A lot of companies often use open-source libraries or frameworks in their code, which is a big security concern. Snyk deals with all the things and provides you with a proper report about whether any open-source code or framework that you are using is vulnerable. In that way, Snyk is very good as compared to other tools."
"It's very easy for developers to use. Onboarding was an easy process for all of the developers within the company. After a quick, half-an-hour to an hour session, they were fully using it on their own. It's very straightforward. Usability is definitely a 10 out of 10."
"From the software composition analysis perspective, it first makes sure that we understand what is happening from a third-party perspective for the particular product that we use. This is very difficult when you are building software and incorporating dependencies from other libraries, because those dependencies have dependencies and that chain of dependencies can go pretty deep. There could be a vulnerability in something that is seven layers deep, and it would be very difficult to understand that is even affecting us. Therefore, Snyk provides fantastic visibility to know, "Yes, we have a problem. Here is where it ultimately comes from." It may not be with what we're incorporating, but something much deeper than that."
"We're loving some of the Kubernetes integration as well. That's really quite cool. It's still in the early days of our use of it, but it looks really exciting. In the Kubernetes world, it's very good at reporting on the areas around the configuration of your platform, rather than the things that you've pulled in. There's some good advice there that allows you to prioritize whether something is important or just worrying. That's very helpful."
"There are many valuable features. For example, the way the scanning feature works. The integration is cool because I can integrate it and I don't need to wait until the CACD, I can plug it in to our local ID, and there I can do the scanning. That is the part I like best."
"The most valuable features of Snyk are vulnerability scanning and automation. The automation the solution brings around vulnerability scanning is useful."
"The solution has great features and is quite stable."
"One of the issues with the product stems from the fact that it clubs different resources under one ticket."
"The recommended actions aren't always specific, so it might suggest recommendations that don't apply to the particular infrastructure code I'm reviewing."
"In terms of ease of use, initially, it is a bit confusing to navigate around, but once you get used to it, it becomes easier."
"When you find a vulnerability and resolve it, the same issue will not occur again. I want PingSafe to block the same vulnerability from appearing again. I want something like a playbook where the steps that we take to resolve an issue are repeated when that issue happens again."
"The categorization of the results from the vulnerability assessment could be improved."
"PingSafe takes four to five hours to detect and highlight an issue, and that time should be reduced."
"If I had to pick a complaint, it would be the way the hosts are listed in the tool. You have different columns separated by endpoint name, Cloud Account, and Cloud Instances ID. I wish there was something where we could change the endpoint name and not use just the IP address. We would like to have custom names or our own names for the instances. If I had a complaint, that would be it, but so far, it meets all the needs that we have."
"After closing an alert in Cloud Native Security, it still shows as unresolved."
"Areas for improvement are the privacy of container management and the documentation. In the next release, I would like to see best practices on how to manage distributed containers and networks."
"I would also like to see more features inside Docker as well as more integration with different solutions."
"You need to have system knowledge to deploy the product. It should be improved."
"In my previous years, I have brainstormed about the development of Container software. I have recently shifted focus, but the knowledge gained from those were really helpful. In my experience, Containers have their own complexities and to implement them, open source information is crucial. A software with new features would be beneficial. I suggest to implement a flow-based approach for container sequences, similar to Google Cloud's machine learning. The current process of deploying containers involves too many steps, and a more streamlined method would be appreciated. I've even automated deployment using APIs. Overall, simplifying container management and deployment processes would be valuable."
"The orchestration and tracing should be improved."
"The initial setup was quite complex."
"Mirantis Container Cloud needs to improve its documentation."
"More integrations with other platforms would be beneficial."
"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."
"We have to integrate with their database, which means we need to send our entire code to them to scan, and they send us the report. A company working in the financial domain usually won't like to share its code or any information outside its network with any third-party provider."
"Offering API access in the lower or free open-source tiers would be better. That would help our customers. If you don't have an enterprise plan, it becomes challenging to integrate with the rest of the systems. Our customers would like to have some open-source integrations in the next release."
"The solution could improve the reports. They have been working on improving the reports but more work could be done."
"I would like to give further ability to grouping code repositories, in such a way that you could group them by the teams that own them, then produce alerting to those teams. The way that we are seeing it right now, the alerting only goes to a couple of places. I wish we could configure the code to go to different places."
"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."
"Compatibility with other products would be great."
"DAST has shortcomings, and Snyk needs to improve and overcome such shortcomings."
More SentinelOne Singularity Cloud Security Pricing and Cost Advice →
Mirantis Container Cloud is ranked 14th in Container Security with 29 reviews while Snyk is ranked 5th in Container Security with 41 reviews. Mirantis Container Cloud is rated 8.8, while Snyk is rated 8.2. The top reviewer of Mirantis Container Cloud writes "An easy-to-manage solution that helps to manage web pages ". On the other hand, the top reviewer of Snyk writes "Performs software composition analysis (SCA) similar to other expensive tools". Mirantis Container Cloud is most compared with SUSE Rancher, whereas Snyk is most compared with SonarQube, Black Duck, GitHub Advanced Security, Fortify Static Code Analyzer and Veracode. See our Mirantis Container Cloud 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.
