Compare Sonatype Nexus Lifecycle vs. Veracode
Sonatype Nexus Lifecycle is ranked 3rd in Application Security with 17 reviews while Veracode is ranked 1st in Application Security with 27 reviews. Sonatype Nexus Lifecycle is rated 8.6, while Veracode is rated 8.0. The top reviewer of Sonatype Nexus Lifecycle writes "Checks our libraries for security and licensing issues". On the other hand, the top reviewer of Veracode writes "Keys for us are the static scanning and the ability to set policy profiles specific to us". Sonatype Nexus Lifecycle is most compared with SonarQube, Black Duck and WhiteSource, whereas Veracode is most compared with SonarQube, Checkmarx and Micro Focus Fortify on Demand. See our Sonatype Nexus Lifecycle vs. Veracode report.
Most Helpful Review | |||||
|
| ||||
 Find out what your peers are saying about Sonatype Nexus Lifecycle vs. Veracode and other solutions. Updated: February 2020. 406,070 professionals have used our research since 2012. | |||||
Quotes From Members
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
Pros | |
With the plugin for our IDE that Sonatype provides, we can check whether a library has security, quality, or licensing issues very easily. Which is nice because Googling for this stuff can be a bit cumbersome. By checking it before code is even committed, we save ourselves from getting notifications. It integrates well with our existing DevOp tools because we can integrate it in our build pipeline. We can also trigger our build pipeline to create warnings and let the build fail if there is a critical vulnerability that violates our policy. The REST API is the most useful for us because it allows us to drive it remotely and, ideally, to automate it. Some of the more profound features include the REST APIs. We tend to make use of those a lot. They also have a plugin for our CI/CD; we use Jenkins to do continuous integration, and it makes our pipeline build a lot more streamlined. It integrates with Jenkins very well. The proxy repository is probably the most valuable feature to us because it allows us to be more proactive in our builds. We're no longer tied to saving components to our repository. For us, it's seeing not only the licensing and security vulnerabilities but also seeing the age of the open-sources included within our software. That allows us to take proactive steps to make sure we're updating the software to versions that are regularly maintained and that don't have any vulnerabilities. The integration of Lifecycle is really good with Jenkins and GitHub; those work very well. We've been able to get it to work seamlessly with them so that it runs on every build that we have. The key feature for Nexus Lifecycle is the proprietary data they have on vulnerabilities. The way that they combine all the different sources and also their own research into one concise article that clearly explains what the problem is. Most of the time, and even if you do notice that you have a problem, the public information available is pretty weak. So, if we want to assess if a problem applies to our product, it's really hard. We need to invest a lot of time digging into the problem. This work is basically done by Sonatype for us. The data that it delivers helps us with fixing or understanding the issue a lot quicker than without it. | We used it for performing security checks. We have many Java applications and Android applications. Essentially it was used for checking the security validations for compliance purposes. I have used this solution in multiple projects for vulnerability testing and finding security leaks within the code. The most valuable feature comes from the fact that it is cloud-based, and I can scale up without having to worry about any other infrastructure needs. We are using the Veracode tools to expose the engineers to the security vulnerabilities that were introduced with the new features, i.e. a lot faster or sooner in the development life cycle. One of the valuable features is that it gives us the option of static scanning. Most tools of this type are centered around dynamic scanning. Having a static scan is very important. It has an easy-to-use interface. Veracode provides faster scans compared to other static analysis security testing tools. It has almost completely eliminated the presence of SQLi vulnerabilities. |
Cons | |
One of the things that we specifically did ask for is support for transitive dependencies. Sometimes a dependency that we define in our POM file for a certain library will be dependent on other stuff and we will pull that stuff in, then you get a cascade of libraries that are pulled in. This caused confusing to us at first, because we would see a component that would have security ticket or security notification on it and wonder "Where is this coming in from?" Because when we checked what we defined as our dependencies it's not there. It didn't take us too long effort to realize that it was a transitive dependency pulled in by something else, but the question then remains "Which dependency is doing that?" We cannot currently use the automated pull requests because we are missing the Bitbucket port. We use Bitbucket as our Git repository and automated pull requests only work with GitHub currently. So, we are missing this feature, but we have already addressed this with Sonatype. We do not use it for more because it is still too immature, not quite "finished." It is missing important features for making it a daily tool. It's not complete, from my point of view... It's the right kind of tool and going in the right direction, but it really needs to be more code-driven and oriented to be scaled at the developer level. Some of the APIs are just REST APIs and I would like to see more of the functionality in the plugin side of the world. For example, with the RESTful API I can actually delete or move an artifact from one Nexus repository to another. I can't do that with the pipeline API, as of yet. I'd like to see a bit more functionality on that side. It would be helpful if it had a more detailed view of what has been quarantined, for people who don't have Lifecycle licenses. Other than that, it's pretty good. We use Azure DevOps as our application lifecycle management tool. It doesn't integrate with that as well as it does with other tools at the moment, but I think there's work being done to address that. In terms of IDEs, it integrates well. We would like to integrate it into our Azure cloud deployment but the integration with Azure Active Directory isn't quite as slick as we would like it to be. We have to do some workarounds for that at the moment. We had some issues, and I think we might still have some issues, where the Sonatype Nexus Repository has integrations with IQ and SonarQube. We're getting some errors on the UI, so we've had Sonatype look into that a little bit. | One of the things that we have from a reporting point of view, is that we would love to see a graphical report. If you look through a report for something that has come back from Veracode, it takes a whole lot of time to just go through all the pages of the code to figure out exactly what it says. We know certain areas don’t have the greatest security features but those are usually minor and we don’t want to see those types of notifications. Ideally, I would like better reporting that gives me a more concise and accurate description of what my pain points are, and how to get to them. I would like to see expanded coverage for supporting more platforms, frameworks, and languages. Veracode should make it easier to navigate between the solutions that they offer, i.e. between dynamic, static, and the source code analysis. We would like a way to mark entire modules as "safe." The lack of this feature hasn't stopped us previously, it just makes our task more tedious at times. That kind of feature would save us time. Veracode scans provide a higher number of false positives. The overall reporting structure is complicated, and it's difficult to understand the report. It needs more timely support for newer languages and framework versions. |
Pricing and Cost Advice | |
The license fee may be a bit harder for startups to justify. But it will save you a headache later as well as peace of mind. Additionally, it shows your own customers that you value security stuff and will protect yourselves from any licensing issues, which is good marketing too. In addition to the license fee for IQ Server, you have to factor in some running costs. We use AWS, so we spun up an additional VM to run this. If the database is RDS that adds a little bit extra too. Of course someone could run it on a pre-existing VM or physical server to reduce costs. I should add that compared to the license fee, the running costs are so minimal they had no effect on our decision to use IQ Server. Our licensing costs are on an annual basis. The Sonatype licensing model is transparent with no hidden costs or holes. The price is good. We certainly get a lot more in return. However, it's also hard to get the funds to roll out such a product for the entire firm. Therefore, pricing has been a limiting factor for us. However, it's a fair price. Pricing is decent. It's not horrible. It's middle-of-the-road, as far as our ranking goes. They're a little bit more but that's also because they provide more. Pricing is comparable with some of the other products. We are happy with the pricing. We're pretty happy with the price, for what it is delivering for us and the value we're getting from it. Its pricing is competitive within the market. It's not very cheap, it's not very expensive. | They have just streamlined the licensing and they have a number of flexible options available, so overall it is quite good, albeit pricey. They just changed their pricing model two weeks ago. They went from a per-app license to a per-megabyte license. I know that the dynamic scan was $500 per app. Static analysis was about $4500 yearly. The license is only for the number of users, it doesn't matter what data you put in there. That was the old model. I do not know how the new model works. Veracode has been fair. We use their SaaS solution and it's just an annual subscription. No issues, the pricing seems reasonable. It is pricey. There is a lot of value in the product, but it is a costly tool. I recommend going for a one-year licensing with CA, because currently they are the leaders in this field with more features and a much better turn around time with a cheaper position, but there are a lot of new companies coming up in the market and they are building up their platforms. Costs are reasonable. No special infrastructure is required and the license model is good. I think the pricing is in line with the rest of the tools. I think you get what you pay for. It is certainly not inexpensive, but the value proposition is there. There are certainly cheaper tools, but I don't think we'd be getting the support that we get with those, and that is what separates this product from the others. |
 Use our free recommendation engine to learn which Application Security solutions are best for your needs. 406,070 professionals have used our research since 2012. | |
Ranking  | |
Views 7,560 Comparisons 4,303 Reviews 10 Average Words per Review 1,629 Avg. Rating 8.7 | Views 58,372 Comparisons 31,073 Reviews 39 Average Words per Review 647 Avg. Rating 8.2 |
Top Comparisons | |
 Compared 33% of the time.  Compared 17% of the time.  Compared 12% of the time. | Compared 50% of the time.  Compared 14% of the time.  Compared 10% of the time. |
Also Known As | |
| Nexus Lifecycle | |
Learn | |
| Sonatype | Veracode Video Not Available |
Overview | |
Nexus Lifecycle gives you full control over your software supply chain and allows you to define rules, actions, and policies that work best for your organization and teams. | Veracode covers all your Application Security needs in one solution through a combination of five analysis types; static analysis, dynamic analysis, software composition analysis, interactive application security testing, and penetration testing. Unlike on-premise solutions that are hard to scale and focused on finding rather than fixing, Veracode comprises a unique combination of SaaS technology and on-demand expertise that enables DevSecOps through integration with your pipeline, and empowers developers to find and fix security defects. |
Offer | |
Learn more about Sonatype Nexus Lifecycle | Keep your software secure Application security starts with secure code. Find out more about the benefits of using Veracode to keep your software secure throughout the development lifecycle. |
Sample Customers | |
| Genome.One, Blackboard, Crediterform, Crosskey, Intuit, Progress Software, Qualys, Liberty Mutual Insurance | State of Missouri, Rekner |
Top Industries | |
Financial Services Firm43% Insurance Company29% Government7% Health, Wellness And Fitness Company7% Software R&D Company31% Comms Service Provider12% Financial Services Firm10% Insurance Company9% | Financial Services Firm31% Insurance Company15% Consumer Goods8% Healthcare Company8% Software R&D Company40% Comms Service Provider12% Financial Services Firm6% Media Company6% |
Company Size | |
Small Business22% Midsize Enterprise17% Large Enterprise61% | Small Business21% Midsize Enterprise25% Large Enterprise55% Small Business16% Midsize Enterprise9% Large Enterprise74% |
Find out what your peers are saying about Sonatype Nexus Lifecycle vs. Veracode and other solutions. Updated: February 2020.
406,070 professionals have used our research since 2012.
See also Sonatype Nexus Lifecycle Reviews, Veracode Reviews, and our list of Best Application Security Companies.
We monitor all Application 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.