Checkmarx vs. Coverity Static Analysis (SAST)

Chechmarx is really suited for finding wide range of security risks. It although identifies false positives which can be confusing at times. It can do better in terms of scan duration. They are better alternate competitors in the market who can do equally good or even better. It all depends on the scope of the problem you want to address

Incentivized

Best suits for large scale and dynamic development environment. It may be best tool if you want to release your apps with less TAT. However if you have a CRM tool which is COTS product it can offer little help. Even then you should be familiar with what features of Coverity Static Analysis (SAST) are helpful for your development environment

Incentivized

• Reporting
• Language support
• Fix recommendations

Incentivized

• It can provide security scanning dashboard
• Help detect vulnerabilities and recommend remediation
• Integration of devsecops helps speed up release cycles

Incentivized

• Lots of false positives
• Hard to integrate with CI

Incentivized

• Coverage of integration with other security tools can be improved
• Customisation of dashboard to enable customer choice of tracking
• Showcase devsecops progressive tasks from SLA and violation from code scanner perspective

Incentivized

We actually use Checkmarx along with the other tools. However, the reason we chose Checkmarx is its wide support for languages and useful fix recommendations. The flowcharts help better understand the data flow and give a clear picture of what needs to be fixed and how. Also, developers can make a note of what should be avoided in the future. Overall, it's a great tool and would be a good investment to make.

Incentivized

Coverity Static Analysis (SAST) has wide coverage in terms of Owasp Top 10 vulnerabilities, various types of languages, backward integration. While other tools offer similar experience of code scanning, coverity helps in pointed recommendations for quick closure of vulnerabilities. The historical analysis of vulnerabilities is a good value add in understanding which type of code and which language is better in improving cyber security maturity.

Incentivized

• Improved ability to provide high level of IA confidence
• Improved confidence in application-level security

Incentivized

• Helped reduce efforts of development team avoiding rework
• Increased security maturity
• Increased efficiency of the teams

Incentivized