We did a comprehensive evaluation on a number of critical parameters in the environment that we are in. Other popular tools that we evaluated failed to meet our expectations.
Sr. Manager/Sr. Architect at Cognizant
It has the lowest false positives with customizable triage options
Pros and Cons
- "It has the lowest false positives."
- "Reporting engine needs to be more robust."
What is our primary use case?
How has it helped my organization?
- Ease of development teams to adopt.
- Faster scanning
- Lowest false positives
- No unnecessary bloating of a huge defect list.
These have helped us to focus on the things which need attention.
What is most valuable?
- Lowest false positive rate
- Faster scanning time
- Inline context-sensitive help and other supportive artifacts which help developers.
- Customizable triage options
- Integrations with CI/CD tools, etc.
What needs improvement?
Buyer's Guide
Coverity
November 2024
Learn what your peers think about Coverity. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
For how long have I used the solution?
Less than one year.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Software Architect at a tech vendor with 10,001+ employees
Easy to set up with good static order analysis but is expensive
Pros and Cons
- "We were very comfortable with the initial setup."
- "We'd like it to be faster."
What is our primary use case?
We primarily use the solution for quality purposes. We also use it for security. That's one subset of quality. However, it's used for more dynamic behavior, such as memory leaks, et cetera.
What is most valuable?
They have a good memory-related box and a static order analysis that's very good, especially around leaks.
We were very comfortable with the initial setup.
It is stable.
What needs improvement?
The cost is very high.
They don't have SonarQube compatibility with the dashboard, which is a big negative. They were actually arrogant for not providing it. We wanted to see all the problems in a single SonarQube dashboard, and we can't do that. They need SonarQube integration. They claim that they have SonarQube integration, yet it is not there.
We'd like it to be faster.
The solution could always use a bit more security.
For how long have I used the solution?
I've been using the solution for around 12 years.
What do I think about the stability of the solution?
I consider the solution very stable. There are no bugs or glitches and it doesn't crash or freeze. It is reliable.
That said, when we are doing security analysis on bigger projects, it can be slow.
What do I think about the scalability of the solution?
To scale, you need more hardware. That way it is scalable. That said, it is already handling quite a big amount. We have a specific problem when analyzing security in a big project. It can get slow.
I'd rate it four out of five in its ability to scale.
We have around 200 people using the solution currently. 30 to 40 use it on a daily basis.
We do not have plans to increase usage based on the cost. We're actually looking for an alternative.
How are customer service and support?
Support is not so good. They're too slow. In contrast, Clockwork has very good support.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We've used Clockwork before. However, it has the same issues as this product. They're more for C# and C++.
How was the initial setup?
The solution was very simple to set up. The frontend, backend, and UI are very good and easy to navigate.
I'd rate the initial setup process a four out of five in terms of how easy it was.
What's my experience with pricing, setup cost, and licensing?
It is an expensive solution.
Their sales team is very arrogant.
I don't like their licensing mechanism. Everything is on very unfriendly terms.
There are other tools you can use that are free and open-source.
In a collaborative environment, they are very tricky. When it comes to looking at the bugs on a web interface, they try to block them. When you discuss it with them, they are quite unfriendly. Once you got stuck into the tool, they know that it's hard to leave due to the history. When you get into a tool, you need the history since the history needs to be built up, and therefore, over time, you have a dependency on the tool.
I'd rate the product a three out of five in terms of affordability.
What other advice do I have?
We're a customer.
I would rate the solution seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Coverity
November 2024
Learn what your peers think about Coverity. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Broad integration capacity and works with more languages than some competitors
Pros and Cons
- "One of the most valuable features is Contributing Events. That particular feature helps the developer understand the root cause of a defect. So you can locate the starting point of the defect and figure out exactly how it is being exploited."
- "Right now, the Coverity executable is around 1.2GB to download. If they can reduce it to approximately 600 or 700MB, that would be great. If they decrease the executable, it will be much easier to work in an environment like Docker."
What is our primary use case?
We write thousands of lines of code on a daily basis, and we cannot say that our code is free because there are a lot of other developers contributing to the source code and things like that. And this process is prone to human error, defects in the source code, etc.
How has it helped my organization?
To automate detection, we use Coverity's static analysis, which has a low false-positive ratio. That's because Coverity's analysis engine includes 20-plus patented technologies. A lot of other static analysis tools use pattern-based analysis, but Coverity's is flow based. That's why we ended up using it. Coverity is helping us identify some of the critical defects at the early stages of the development life cycle. So overall, it is giving us a greater ROI and making our application more mature and robust.
What is most valuable?
One of the most valuable features is Contributing Events. That particular feature helps the developer understand the root cause of a defect. So you can locate the starting point of the defect and figure out exactly how it is being exploited. So contributing Events lets you create that kind of a workflow.
We also need a tool that works in an environment that isn't dependent on the built environment. You point it to a folder. Then the tool picks it up, runs the scan, and gives you the report. That feature is available in Coverity. So you don't have to rely upon build artifacts or developer artifacts. So these are the two key features we use daily, and we've gotten good results.
What needs improvement?
Coverity's UI is the one thing that needs improvement. Technically speaking, it's doing an outstanding job otherwise. Also, they could reduce their executable size. Right now, the Coverity executable is around 1.2GB to download. If they can reduce it to approximately 600 or 700MB, that would be great. If they decrease the executable, it will be much easier to work in an environment like Docker.
For how long have I used the solution?
I've been using it for the past two years.
What do I think about the stability of the solution?
This product has been in the industry for more than 30 years, so it's pretty robust.
How are customer service and support?
Coverity has a decent SLA. The moment you purchase the tool, you also get an SLA agreement with all the email support. They have email support, call support, as well as WebEx and Zoom sessions on demand. Of course, that depends on the nature of the technical issue. If it's simple, it can be resolved with a couple of email exchanges, but if it really needs some attention, they're happy to get on a call. They've even delivered some custom patches as well.
Which solution did I use previously and why did I switch?
I used CodeSonar a few years back. Both tools have their advantages. In any static analysis tool, the first stage is the instrumentation of the source code. It'll try to capture the skeleton of your source code. So when I compare them based on the first phase alone, Coverity is far better than CodeSonar.
They both use a similar technique, but CodeSonar uses up way more storage resources. For example, to scan a 1GB code base, CodeSonar generates more than 5GB of instrumented files for every 1GB of code base. In total, that is 6GB. Coverity generates 500MB extra on top of 1GB, so that equals 1.5GB all in. That's a huge difference. CodeStar would eat up my disc space and hardware resources when I used it, whereas Coverity is minimal.
In terms of checkers, both CodeSonar and Coverity cover a good length and breadth, especially for C and C++ programming languages. But CodeSonar focuses only on four languages—C, C++, Java, and C#—only four programming languages, whereas Coverity supports more than 20-plus programming languages.
Also, the two are comparable with respect to their plugin offerings, but there are crucial differences. For example, CodeSonar only focuses on well-known integrations, like Jenkins and JIRA, but you cannot expect all customers to use the same tools. Coverity supports almost all CI/CD tools, including Jenkins and Bamboo. It also integrates with service providers like Azure DevOps Pipelines, AWS CodePipelines that CodeSonar hasn't added yet. The plugins are available in the marketplace, and you don't have to pay extra. You just have to download it from the marketplace, hook the plugin in your pipeline, and ready to use kind of approach. So these are some of the major use cases, three major use cases I would say when you compare apples to apples with CodeSonar and Coverity.
How was the initial setup?
Setting up Coverity is pretty simple. It comes with a normal executable. You just double click, follow the wizard, and complete the setup. It also have on screen instructions as well, which makes it pretty easy and cool. Deployment is a much broader question. It depends on how many projects you are trying to scan using Coverity and whether you are integrating this static analysis solution with your CI/CD setup, ID, bug tracking, etc. That all factors in to the total deployment time. So if we're talking about overall deployment, including bug tracking, integration, email notification, CI/CD integration, and everything, it took us 15 to 20 days to onboard 600 projects with 20 users, including all integration.
We don't have a lot of maintenance. There is a major release every quarter, and we get information on new upgrades, patches, and things like that. And we do have the option to not upgrade. The maintenance is mostly covered by the vendor itself, meaning they deliver the patches and upgrades on time. So I don't see that as a hurdle right now. It's been taken care of.
What's my experience with pricing, setup cost, and licensing?
I'm not sure about the licensing. My commercial team deals with that.
What other advice do I have?
I rate Coverity nine out of 10. It's a good choice. If you plan to use Coverity, you should read through the manual to really understand its settings. You have to tune the Coverity engine to get the best research and scalability out of it. A Coverity recently added some smart features that automatically compute the hardware requirements in your current machine. It automatically scales up. For example, it can detect how much multi-core CPU power it needs to run an analysis and how much memory is required, so it makes resources available for other applications running on the same machine. That intelligence has been built on. So initially, I recommend going over the fundamentals and fine-tuning it based on one's own requirements.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Security Engineer at a comms service provider with 10,001+ employees
Good security analysis features but it should support more languages and the user interface is not user-friendly
Pros and Cons
- "The security analysis features are the most valuable features of this solution."
- "The quality of the code needs improvement."
What is our primary use case?
We use the on-premise deployment model of this solution. Our primary use case of this solution is for auditing.
What is most valuable?
The security analysis features are the most valuable features of this solution.
What needs improvement?
The quality of the code needs improvement. They should develop a better code.
The interface, efficiency, and the performance also need improvement as well as the languages that it offers. It should have more language options.
The user interface is not user-friendly.
For how long have I used the solution?
I have been using this solution for around three years.
What do I think about the stability of the solution?
It is stable.
What do I think about the scalability of the solution?
We have 30 users licensed for this solution. We use it when we need it.
How are customer service and technical support?
Their technical support isn't so good. That needs improvement. They don't address the problems I bring up. It's not a priority for them.
Which solution did I use previously and why did I switch?
We previously used an open-source solution before Coverity.
How was the initial setup?
The initial setup was easy. The solution is complex to use but not complex to deploy.
What about the implementation team?
We deployed the solution ourselves.
What's my experience with pricing, setup cost, and licensing?
Licensing is on a yearly basis.
What other advice do I have?
I would recommend this solution depending on the language you're using, Java and C++.
I would rate it a five out of ten. Not a ten because it's not efficient for the language we use.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Security Consultant at a tech services company with 11-50 employees
Straightforward to install and reports few false positives, but it should be easier to specify your own validation and sanitation routines
Pros and Cons
- "The most valuable feature is that there were not a whole lot of false positives, at least on the codebases that I looked at."
- "It should be easier to specify your own validation routines and sanitation routines."
What is our primary use case?
I am a consultant and I work to bring solutions to different companies. Static code analysis is one of the things that I assist people with, and Coverity is one of the tools that I use for doing that.
I worked with Coverity when doing a couple of different PoCs. For these, I get a few different teams of developers together and we want to decide what makes the most sense for each team as far as scanning technologies. So, part of that is what languages are supported, part of that is how extensible it is, and part of that extensibility is do the developers have time to actually create custom roles?
We also want to know things like what the professional are services like, and do people typically need many hours of professional services to get the system spun up. Other factors include whether it deployed on-premises or in the cloud, and also, which of those environments it can operate with.
One of the things is there's not really a shining star out of all of these tools. SaaS tools have been getting more mature in the past decade, particularly in how fast they run, but also in the results they get. Of course, framework and language additions that increase the capability with results are considered.
What is most valuable?
The most valuable feature is that there were not a whole lot of false positives, at least on the codebases that I looked at.
What needs improvement?
It should be easier to specify your own validation routines and sanitation routines.
For example, if you have data coming into the application, perhaps something really simple like it's getting a parameter from a web page that is your username when you go to a website to login, and then ultimately that's being consumed by something, the data goes through some business logic and then, let's say, it enters that username into a database.
Well, what if I say my username is JavaScript calling alert hello. Now I've just entered JavaScript code as my username and you should be able to sanitize that pretty easily with a number of different techniques to remove the actual executable code from what they entered on the login page. However, once you do that, you want the program to understand that you are doing it and then remove what looks like a true positive at first glance because, in fact, the data being consumed in the SQL exec statement is not unsanitized. It's not just coming from the web.
Likewise, let's say you log in, and then it says, "Hello" Such and such. You can inject JavaScript code there and have it be executed when it says hello. So basically the ability to say that this validates and then also above and beyond that, this validates data coming from any GET parameter on the web. You should be able to specify a particular routine validates all of that, or this particular routine validates anytime we read data from a database, maybe an untrusted database.
So, if I reach for that data eight times and I say, "Hey," this validates it once, I also get the option to say it validates it the other seven times, or I could just say it's a universal validator. Obviously, a God validator so to speak is not a good practice because you're sure to miss some edge cases, but to have one routine validate three or four different occurrences is not rare and is often not a bad practice.
Another thing that Coverity needs to implement or improve is a graphical way to display the data. If you can see an actual graphical view of the data coming in, then it would be very useful. Let's say, the first node would be GET parameter from a webpage, and then it would be an arrow to another method like validate user ID, and then another method of GET data about the user. Next, that goes into the database, and so forth. When that's graphically displayed, then it is helpful for developers because they can better grab onto it.
The speed of Coverity can be improved, although that is true for any similar product.
What do I think about the stability of the solution?
It never crashed so stability has not been an issue.
What do I think about the scalability of the solution?
I have never used it for more than four relatively small to medium-sized projects at a time, so I've never needed to scale it.
How are customer service and technical support?
I have dealt with sales engineering, rather than technical support. They would sometimes provide a liaison to tech support if they didn't know the answer, but really, they guided us through the proof of concept and they knew that they were under a competitive evaluation against the other tools. They were able to resolve any issues that we came across and got us up and running fairly quickly, as far as I recall.
How was the initial setup?
Coverity is on the good side when it comes to setting it up. I think that it is pretty straightforward to get up and running.
What about the implementation team?
We implement Coverity on our own, with guidance from Coverity.
What's my experience with pricing, setup cost, and licensing?
The price is competitive with other solutions.
Which other solutions did I evaluate?
In addition to Coverity, I have experience with Checkmarx, Fortify, Veracode, and HCL AppScan, which was previously known as IBM AppScan.
Checkmarx is probably the most extensible and customizable of these products, and you're able to use the C# language to do so, which a lot of developers are familiar with.
HCL AppScan is another tool that has customization capabilities. They are not as powerful but they are easier to implement because you don't need to write any code.
I cannot give an endorsement for any particular one. They all have their merits and it just depends on the requirements. Generally, however, all of these tools are getting better.
What other advice do I have?
My advice for anybody who is considering this product is to first look around your organization to see if it has already been implemented in another group. If you're a big organization then Coverity or a similar tool may already be in use. In cases like this, I would say that it is best to adopt the same tool because your organization has already gone down that path and there are no huge differences in the capabilities of these tools. Some of them do it in different ways and some do things that others don't, but you won't have the initial bump of the learning curve and you can leverage their experience.
I would rate this solution a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Junior Software Engineer at NAVER Corp
Has a straightforward UI and helps to scan codes
Pros and Cons
- "I like Coverity's capability to scan codes once we push it. We don't need more time to review our colleagues' codes. Its UI is pretty straightforward."
- "The product should include more customization options. The analytics is not as deep as compared to SonarQube."
What is most valuable?
I like Coverity's capability to scan codes once we push it. We don't need more time to review our colleagues' codes. Its UI is pretty straightforward.
What needs improvement?
The product should include more customization options. The analytics is not as deep as compared to SonarQube.
For how long have I used the solution?
I have been using the product for one month.
What do I think about the stability of the solution?
I would rate Coverity's stability a ten out of ten.
What do I think about the scalability of the solution?
I would rate the product's scalability an eight out of ten. My company has three users for the tool.
How was the initial setup?
I would rate the tool's setup a seven out of ten. The deployment gets completed in a couple of minutes.
What's my experience with pricing, setup cost, and licensing?
I would rate the tool's pricing a one out of ten.
What other advice do I have?
Coverity's documentation is pretty straightforward and I would rate it a seven out of ten. The solution is cheap and provides us with a dedicated server.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
A stable solution that has deep scanning capabilities
Pros and Cons
- "The product has deeper scanning capabilities."
- "The tool needs to improve its reporting."
What is most valuable?
The product has deeper scanning capabilities.
What needs improvement?
The tool needs to improve its reporting.
For how long have I used the solution?
I have been working with the product for one and a half years.
What do I think about the stability of the solution?
The product's stability is good.
What do I think about the scalability of the solution?
The product is scalable since it can integrate CI/CD tools. My company has 10 users for the product.
How are customer service and support?
The solution's support is fast.
How would you rate customer service and support?
Positive
How was the initial setup?
The solution's setup is easy.
What's my experience with pricing, setup cost, and licensing?
The tool's price is somewhere in the middle. It's neither cheap nor expensive. I would rate the pricing a five out of ten.
What other advice do I have?
I would rate the solution a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Vice President at a tech vendor with 1,001-5,000 employees
Static analysis solution that exposes existing and future vulnerabilities
Pros and Cons
- "The ability to scan code gives us details of existing and potential vulnerabilities. What really matters for us is to ensure that we are able to catch vulnerabilities ahead of time."
- "When I put my code into Coverity for scanning, the code information of the product is in the system. The solution could be improved by providing a SBOM, a software bill of material."
What is our primary use case?
We use this solution to scan our products. We've integrated with our build system and it automatically completes the scanning.
What is most valuable?
The ability to scan code gives us details of existing and potential vulnerabilities. What really matters for us is to ensure that we are able to catch vulnerabilities ahead of time.
What needs improvement?
When I put my code into Coverity for scanning, the code information of the product is in the system. The solution could be improved by providing a SBOM, a software bill of material. They could also integrate a software composition analysis scan. This would make my job a bit easier.
There is scope for Coverity to look beyond static analysis. Most of people that I have spoken to use Coverity from a pure static analysis perspective. However, we also need to be able to view dynamic pages and APIs using dynamic scanning and SES scans. Currently we would need to use another solution to be able to do this.
For how long have I used the solution?
I have been using this solution for 10 years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
From a support perspective, they are pretty responsive. I would rate them a five out of five.
What was our ROI?
The the last ten years, our company has derived value from using this solution. We continuously evaluate our tech stack and if a better solution came along, we would consider it if it provided more value.
What's my experience with pricing, setup cost, and licensing?
This is a pretty expensive solution. The overall value of the solution could be improved if the price was reduced. Licensing is done on an annual basis.
There are other new tools like Veracode, Java Icon and Javascript which are better than Coverity when it comes to visualization. Their cost is significantly lower compared to Synopsys.
What other advice do I have?
Coverity is really good with CC+ and legacy technologies. However, there are other products that are probably as good or even better than Coverity when it comes to Java or cloud applications.
If someone were to ask me what tool I would recommend, my answer would depend on what technology they're using and what their use case is. My advice would be based on how they're going to use the product and what they're expecting from the tool.
I would rate this solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Coverity Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Static Application Security Testing (SAST)Popular Comparisons
SonarQube Server (formerly SonarQube)
Veracode
GitLab
Checkmarx One
OWASP Zap
SonarQube Cloud (formerly SonarCloud)
Fortify on Demand
Acunetix
PortSwigger Burp Suite Professional
HCL AppScan
Qualys Web Application Scanning
Klocwork
Invicti
Parasoft SOAtest
Kiuwan
Buyer's Guide
Download our free Coverity Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What is the difference between Coverity and SonarQube?
- What is the biggest difference between Coverity and SonarQube?
- How would you decide between Coverity and Sonarqube?
- What Application Security Solution Do You Use That Is DevOps Friendly?
- Which is the most comprehensive open source Web Security Testing tool?
- What is the best Application Security Testing platform?
- When evaluating Application Security Testing, what aspect do you think is the most important to look for?
- SAST vs. DAST: Which is better for application security testing?
- What tools do you rely on for building a DevSecOps pipeline?
- What does the Log4j/Log4Shell vulnerability mean for your company?