Checkmarx
Checkmarx offers a portfolio covering finding or addressing weaknesses in software. The entries in this catalog include Checkmarx One, Checkmarx SAST and Checkmarx SCA. Checkmarx One focuses on application security testing and vulnerability prioritization. Checkmarx SAST focuses on source code security testing. Checkmarx SCA focuses on dependency security and software composition analysis. When reviewing Checkmarx, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for supported languages or targets, scan placement, finding quality and how developers validate proposed fixes. Portfolio detail - Checkmarx One: the catalog lists Static application security testing, Dynamic application security testing, Software composition analysis. - Checkmarx SAST: the catalog lists Static application security testing, Developer workflow integration, CI/CD integration. - Checkmarx SCA: the catalog lists Software composition analysis, Dependency vulnerability analysis, Developer workflow integration. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (3)
Checkmarx One
Checkmarx One from Checkmarx focuses on application security testing and vulnerability prioritization. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Dynamic application security testing: Tests a running application to find exposed security weaknesses. - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Infrastructure configuration analysis: Checks infrastructure definitions alongside application code where this capability is included. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. Use and operational context Checkmarx One is a platform-level application security entry. Review the testing services and modules enabled in the proposed package, how their findings are combined and how development teams receive actionable results in their existing delivery workflow. Deployment and evaluation Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. Before adoption, review supported languages or targets, scan placement, finding quality and how developers validate proposed fixes. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Checkmarx One focuses on finding or addressing weaknesses in software. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Checkmarx SAST
Checkmarx SAST from Checkmarx focuses on source code security testing. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Static application security testing: Analyzes application code without requiring the complete application to be exercised at runtime. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - Secrets detection: Looks for exposed credentials or secrets within the supported development assets. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Checkmarx SAST focuses on static analysis of application code. A trial should use representative repositories and supported languages, with developers reviewing the code location, security explanation and remediation work associated with an identified weakness. Deployment and evaluation Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. Before adoption, review supported languages or targets, scan placement, finding quality and how developers validate proposed fixes. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Checkmarx SAST focuses on finding or addressing weaknesses in software. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Checkmarx SCA
Checkmarx SCA from Checkmarx focuses on dependency security and software composition analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Software composition analysis: Examines third-party components and dependencies for the risks covered by the scanner. - Dependency vulnerability analysis: Brings third-party software components into the vulnerability review process. - Developer workflow integration: Places security findings into the development processes documented by the vendor. - Reachability analysis: Adds information about whether a vulnerable component or code path can be reached in the application. - Finding triage and remediation: Helps developers translate a security finding into a reviewable remediation task. Use and operational context Checkmarx SCA is relevant to development and application security teams when the requirement centers on finding or addressing weaknesses in software. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported languages or targets, scan placement, finding quality and how developers validate proposed fixes. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Checkmarx SCA focuses on finding or addressing weaknesses in software. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.