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."It is a stable solution. It is nearly perfect. I would rate the stability a ten out of ten."
"Now it is easier to set up the development environment and also to test the applications on the pipelines."
"Very easy solution to use as it is intuitive."
"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."
"You need to make an architectural runway before actually starting to implement Docker Compose, especially in a distributed environment."
"The product is easy to use."
"Main products are portable."
"The solution is scalable and we have plans to increase usage in the future."
"Snyk is a developer-friendly product."
"The solution's Open Source feature gives us notifications and suggestions regarding how to address vulnerabilities."
"The code scans on the source code itself were valuable."
"I am impressed with the product's security vulnerability detection. My peers in security are praising the tool for its accuracy to detect security vulnerabilities. The product is very easy to onboard. It doesn't require a lot of preparation or prerequisites. It's a bit of a plug-and-play as long as you're using a package manager or for example, you are using a GitHub repository. And that is an advantage for this tool because developers don't want to add more tools to what they're currently using."
"The most valuable feature of Snyk is the SBOM."
"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 most valuable features include enriched information around the vulnerabilities for better triaging, in terms of the vulnerability layer origin and vulnerability tree."
"The most valuable feature of Snyk is the software composition analysis."
"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."
"It will be better if the product provides dynamic load-balancing capabilities."
"I feel that the product lacks to offer a proper health status of the images which are running, making it an area where improvements are required."
"It would be very nice to have a GUI that can be used by any administrator, and not just people who have experience with Docker."
"The solution's stability could be improved."
"The orchestration and tracing should be improved."
"When it comes to the integration part, it's the basic functionality, but for any product, at the end of the day, security is extremely relevant. I personally feel like you have to constantly strive towards being more secure. You can never be 100% secure, and you have to work more toward security. It's as simple as that."
"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 reporting mechanism of Snyk could improve. The reporting mechanism is available only on the higher level of license. Adjusting the policy of the current setup of recording this report is something that can improve. For instance, if you have a certain license, you receive a rating, and the rating of this license remains the same for any use case. No matter if you are using it internally or using it externally, you cannot make the adjustment to your use case. It will always alert as a risky license. The areas of licenses in the reporting and adjustments can be improve"
"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."
"Could include other types of security scanning and statistical analysis"
"We would like to have upfront knowledge on how easy it should be to just pull in an upgraded dependency, e.g., even introduce full automation for dependencies supposed to have no impact on the business side of things. Therefore, we would like some output when you get the report with the dependencies. We want to get additional information on the expected impact of the business code that is using the dependency with the newer version. This probably won't be easy to add, but it would be helpful."
"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."
"All such tools should definitely improve the signatures in their database. Snyk is pretty new to the industry. They have a pretty good knowledge base, but Veracode is on top because Veracode has been in this business for a pretty long time. They do have a pretty large database of all the findings, and the way that the correlation engine works is superb. Snyk is also pretty good, but it is not as good as Veracode in terms of maintaining a large space of all the historical data of vulnerabilities."
"Generating reports and visibility through reports are definitely things they can do better."
"Snyk's API and UI features could work better in terms of speed."
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, Fortify Static Code Analyzer, Veracode and GitHub Advanced Security. 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.
