Sken vs CheckMarx

Sken performs more comprehensive AppSec coverage at a fraction of the cost.

CheckMarx and Sken offer different capabilities with a dramatic price difference.

CheckMarx performs source code scanning with SAST and coverage for SCA but has poor coverage for securing applications at run-time. It is also much more expensive to acquire, as well as more expensive to run on an on-going basis. CheckMarx products are not well-integrated and don’t prioritize between the various types of results.

Sken.ai also provides a comprehensive view of application security, and adds sophisticated correlation and prioritization across SAST, DAST, SCA, Secrets and vulnerability management at a fraction of the cost of GitLab. Security add-on in GitLab is 5x the cost of CheckMarx.

Sken also correlates across these different application security testing methods to weed out false positives and identify real issues that have an impact on the security posture of the application.

CheckMarx Provides:

Source code scanning based on a proprietary rules engine
Visibility into open-source software components
Limited run-time analysis with their new IAST product

CheckMarx does not (while Sken does) provide:

Dynamic scanning of deployed/production applications with DAST
Understanding of unknown security issues, including OSS, application code and third-party interfaces via DAST
Lower false positives via correlation of source code scanning and run-time application security testing
Fraction of the cost of CheckMarx, and easier to implement and use