We performed a comparison between Snyk and SUSE NeuVector based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Snyk is highly regarded for its developer-friendly approach, broad feature set, and seamless integration with other tools. SUSE NeuVector is praised for its wide range of features, informative user interface, ISO certification checks, and automation capabilities. Reviewers say Snyk should improve its vulnerability database and reporting mechanism. SUSE NeuVector needs to expand scanning support and work on monitoring, reporting, and integration.
Service and Support: Snyk customers say support could improve the way they organize and prioritize assistance. SUSE NeuVector's support is praised for being supportive, prompt, and well-informed, although a few reviewers consider the process to be complex.
Ease of Deployment: Snyk's setup is generally considered to be simple, with good support from the vendor team. SUSE NeuVector can be either easy or difficult, depending on the user. Some users find it straightforward, while others find it complex and challenging. Integrating SUSE NeuVector with pipelines is particularly difficult, often requiring the use of custom scripts.
Pricing: Snyk is regarded as pricey, but users believe the cost is justified because of the features it offers. The pricing and licensing experiences of SUSE NeuVector users vary, with some considering it affordable and others indicating a need for improvement.
ROI: Snyk offers a cost-effective way to detect vulnerabilities, and customers can realize a solid ROI by resolving bugs earlier. SUSE NeuVector provides the largest ROI for high-risk sectors such as financial services, although its benefits may be limited for some sectors, such as retail.
Comparison Results: Snyk is preferred over SUSE NeuVector. Snyk is oriented toward developers, and users appreciate the scanning feature, automatic pull request creation, and software composition analysis tools. The setup is regarded as straightforward, with the Snyk team providing exceptional support. SUSE NeuVector's setup is more intricate and demanding, often requiring custom scripts for integration with pipelines.
"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."
"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."
"Snyk has given us really good results because it is fully automated. We don't have to scan projects every time to find vulnerabilities, as it already stores the dependencies that we are using. It monitors 24/7 to find out if there are any issues that have been reported out on the Internet."
"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."
"Provides clear information and is easy to follow with good feedback regarding code practices."
"The solution's vulnerability database, in terms of comprehensiveness and accuracy, is very high-level. As far as I know, it's the best among their competitors."
"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."
"When it comes to the price, we got a really good deal from the vendor instantly."
"The tool's deployment is simple. Also, I am impressed with its risk capabilities."
"The features of image scanning and anti-malware are really valuable."
"The most valuable feature of SUSE NeuVector is its run-time security."
"The most valuable feature of SUSE NeuVector is the performance, deployment, and cost."
"The UI has a lot of features."
"The initial setup is quite good, it's straightforward."
"The solution's reporting and storage could be improved."
"Snyk's API and UI features could work better in terms of speed."
"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."
"It would be great if they can include dynamic, interactive, and run-time scanning features. Checkmarx and Veracode provide dynamic, interactive, and run-time scanning, but Snyk doesn't do that. That's the reason there is more inclination towards Veracode, Checkmarx, or AppScan. These are a few tools available in the market that do all four types of scanning: static, dynamic, interactive, and run-time."
"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"
"A feature we would like to see is the ability to archive and store historical data, without actually deleting it. It's a problem because it throws my numbers off. When I'm looking at the dashboard's current vulnerabilities, it's not accurate."
"We use Bamboo for CI.CD, and we had problems integrating Snyk with it. Ultimately, we got the two solutions to work together, but it was difficult."
"They were a couple of issues which happened because Snyk lacked some documentation on the integration side. Snyk is lacking a lot of documentation, and I would like to see them improve this. This is where we struggle a bit. For example, if something breaks, we can't figure out how to fix that issue. It may be a very simple thing, but because we don't have the proper documentation around an issue, it takes us a bit longer."
"SUSE NeuVector should provide more security protection rules and better container image scanning."
"We are also working with IaaS VMS, but NeuVector doesn't support virtual machines."
"The tool should offer seamless integration of other security tools while in a hybrid environment."
"The image-scanning features need improvement."
"SUSE NeuVector could improve by increasing its visibility into other elements of the DevSecOps pipeline. Additionally, scanning around infrastructure would be helpful."
"The documentation needs to improve a bit."
"I would say that this solution should improve monitoring and reporting. I would also like to see more integrations so that we could essentially make it a part of a developing pipeline."
Snyk is ranked 5th in Container Security with 41 reviews while SUSE NeuVector is ranked 19th in Container Security with 7 reviews. Snyk is rated 8.2, while SUSE NeuVector is rated 7.8. The top reviewer of Snyk writes "Performs software composition analysis (SCA) similar to other expensive tools". On the other hand, the top reviewer of SUSE NeuVector writes "Good value for money; great for policy management". Snyk is most compared with SonarQube, Black Duck, GitHub Advanced Security, Fortify Static Code Analyzer and Veracode, whereas SUSE NeuVector is most compared with Prisma Cloud by Palo Alto Networks, Aqua Cloud Security Platform, Red Hat Advanced Cluster Security for Kubernetes, Sysdig Falco and Wiz. See our SUSE NeuVector 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.