Black Duck
Black Duck offers a portfolio covering finding or addressing weaknesses in software. The entries in this catalog include Black Duck SCA, Coverity and Polaris. Black Duck SCA focuses on open-source vulnerability and license analysis. Coverity focuses on static source code defect and vulnerability analysis. Polaris focuses on cloud application security testing orchestration. When reviewing Black Duck, 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 - Black Duck SCA: the catalog lists Software composition analysis, Dependency vulnerability analysis, Developer workflow integration. - Coverity: the catalog lists Source-code defect analysis, Static application security testing, Developer workflow integration. - Polaris: the catalog lists Static application security testing, Dynamic application security testing, Software composition analysis. 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)
Black Duck SCA
Black Duck SCA from Black Duck focuses on open-source vulnerability and license 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. - CI/CD integration: Supports running security checks as part of a software delivery pipeline. - License risk analysis: Helps teams review licensing obligations associated with third-party components. - 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 Black Duck SCA focuses on the third-party components included in software. Evaluate dependency identification, vulnerability and licensing findings together, then establish which findings block a release and which require a documented remediation or exception decision. Deployment and evaluation Deployment: Cloud service / SaaS. 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? Black Duck 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.
Coverity
Coverity from Black Duck focuses on static source code defect and vulnerability analysis. It is application security technology used for finding or addressing weaknesses in software. Capabilities - Source-code defect analysis: Addresses code-quality defects as well as the security weaknesses identified by static analysis. - 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. - 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 Coverity 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 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? Coverity 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.
Polaris
Polaris from Black Duck focuses on cloud application security testing orchestration. 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 Polaris is Black Duck's platform entry for application security testing. Review which analysis services are enabled, how findings from those services are presented and how development teams integrate the testing workflow into a representative application delivery process. Deployment and evaluation Deployment: Cloud service / SaaS. 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? Polaris 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.