Black Duck® software composition analysis (SCA) helps teams manage the security, quality, and license compliance risks that come from the use of open source and third-party code in applications and containers.
Finds parts of open source code that have been copied within proprietary code, which can potentially expose you to license violations and conflicts.
Build an accurate SBOM
Black Duck’s discovery technology lets you compile a complete SBOM (Software Bill of Materials) of the open source, third-party, and proprietary software components used to build applications and containers. Exporting an SBOM in NTIA-compliant formats such as SPDX and CycloneDX enable you to establish trust in your applications and track related security, license, and operational risk.
Timely. Thousands of security feeds are monitored and enhanced to provide same-day notification of most vulnerabilities—weeks before they appear in the National Vulnerability Database.
Accurate. Our team of security experts review and verify vulnerability data to ensure accurate reporting on vulnerability descriptions, severity, exploit risk, and affected versions.
Actionable. Mitigation and remediation guidance detailed by our teams help prioritize vulnerabilities, select optimal patch or upgrade path, and identify evidence of attack or compromise.
Automated. Vulnerabilities are prioritized for remediation based on critical vulnerability data, such as severity, available solutions, exploitability, CWE, and call path analysis.
Integrate and automate open source governance into DevSecOps
Black Duck automated policy management allows you to define policies for open source use, security risk, and license compliance up front, and automate enforcement across the software development life cycle (SDLC) with the tools your developers already use. Learn more about our DevOps Integrations.
Identify, avoid, or automatically remediate components that are higher risk or violate policy, as you code.
Development and DevOps Teams
Automate scans, alerting or halting builds based on policy violations using CI tools like Jenkins.
Security and Operations Teams
Inspect apps and containers before they are deployed and get automated security alerts after.
Maintain compliance with open source licenses
Whether your software is delivered via the web or embedded in a hardware device, compliance with open source licenses is critical. Mitigate the cost and risk to intellectual property with greater insight into license obligations and attribution requirements. Learn more about open source license compliance.
Black Duck maps identified components to one of over 2,700 licenses tracked in our KnowledgeBase, and flags components with unknown licenses so they can be reviewed.
Obligation summaries explain license requirements in simple and standard terms so development and legal teams can quickly assess the impact of including a component in their application.
Black Duck automatically flags potential license conflicts so teams stay in compliance with policy enforcement, and helps them accurately report license terms for customers.
Select the plan that fits your needs
Enable developers and DevOps teams to address open source policy concerns without slowing innovation.
Starting at $500
per team member
(20-150 team members)
Rapid open source dependency analysis Address policy violations before building or merging code into release branches
Detection of partial code snippets Find parts of open source code that have been copied into applications and containers, and that still carry license obligations
Binary file and firmware analysis Analyze the contents of an application without access to its source code
Undeclared component identification Find open source dependencies not explicitly declared, and in languages that don’t use package managers, like C/C++
Custom component detection Find non–open source, internal, and third-party components
Software Bill of Materials (SBOM) export
Open source, third-party, proprietary code
Black Duck Security Advisories
Severity, prioritization, and reachability metrics
Declared and undeclared open source license identification
Full license text
Obligation fulfillment guidance & tracking
Deep copyright data
Open source database
Complete access to projects, vulnerabilities, and licenses
Custom security and license policy configuration
Automatic policy enforcement, notification, and reporting
Implementation and integrations
Continuous monitoring of applications before and after deployment
Integrations across entire SDLC
Implementation and adoption services Add on enhanced technical support and assistance with workflow integrations, custom implementations, and program/project management for your Synopsys tools
FREQUENTLY ASKED QUESTIONS
How is software composition analysis (SCA) different from other application security tools?
Open source security is often overlooked due to the misconception that vulnerabilities in proprietary code and open source code can be detected and remediated in similar ways. The reality is that SAST, DAST, and other application security testing tools cannot effectively detect open source vulnerabilities. Enter SCA.
The key differentiator between SCA and other application security tools is what these tools analyze, and in what state. SCA analyzes third-party open source code for vulnerabilities, licenses, and operational factors, while SAST analyzes weaknesses in proprietary code, and DAST tests running applications for vulnerable behavior.
Do you need both SAST and software composition analysis?
A comprehensive software security program contains both SAST and SCA. Organizations that adopt such an approach see improvements throughout the SDLC, including improved quality through early identification of issues, better visibility across proprietary and open source code, lower remediation costs by detecting and fixing vulnerabilities early in the development process, minimized risk of security breaches, and optimized security testing that is both effective and compatible with agile development.
What integrations does Black Duck support?
Black Duck offers easy-to-use open source integrations for the most popular development tools and REST APIs, allowing you to build your own integrations for virtually any commercial or custom development environment. Black Duck offers a wide range of integrations across the SDLC, including IDEs, package managers, CI/CD, issue trackers, and production capabilities.
Where does Black Duck’s vulnerability information come from?
Most solutions rely solely on data from the National Vulnerability Database (NVD). This limitation presents a problem, as many vulnerabilities are never documented in the NVD, and others are not listed until weeks after they become public. Black Duck Security Advisories (BDSAs) go beyond the NVD, with enhanced data that is researched and analyzed by the Synopsys Cybersecurity Research Center (CyRC) to ensure completeness and accuracy, providing early warning and complete insight.
Why should I care about scanning for more than declared dependencies?
Most solutions use package manager declarations to identify open source components. But failing to scan for more than declared dependencies guarantees that you’ll miss some open source. And if you don’t know it’s there, you can’t ensure it’s secure and compliant.
Package manager scanning will overlook open source that developers don’t declare in package manifests, languages like C and C++, open source built into containers where no package manager is used, open source that has been modified, or partial snippets of code that still carry license obligations. By combining file system scanning and snippet scanning with build process monitoring, Black Duck provides visibility into open source components not tracked by a package manager, partial open source, and open source that was potentially modified or not declared, as well as component and version verification for dynamic and transitive dependencies.
What should I look for in a software composition analysis solution?
The short answer is an extensive and powerful solution that provides end-to-end control of open source risks. A solution like Black Duck provides a comprehensive approach to open source management throughout the entire SDLC.
More specifically, the following capabilities should be considered when selecting an SCA solution:
Comprehensive scanning, beyond what is declared
Persistent Bill of Materials
Policy, workflow, and SDLC integrations
Robust vulnerability database, beyond the NVD
License compliance functionality
Monitoring and alerting
What languages and platforms does Black Duck support?
Black Duck supports the most common package managers. Black Duck’s snippet scanning covers the top and most frequently used languages. The expert KnowledgeBase team is constantly monitoring for and adding new languages, ensuring that all common languages are supported.
Additionally, Black Duck’s proprietary signature scanning approach is language-agnostic. This scanning approach searches for signatures based on file and directory layouts along with other metadata that is independent of language.
Does SCA support binary code in addition to source code?
Yes. Some solutions can scan binaries for package manager information or binaries pulled directly from a repository without any modification. Black Duck’s sophisticated binary scanning solution can crack binaries open to detect modified binaries and provide legacy language and broad artifact support.
How comprehensive is Black Duck’s licensing data in the KnowledgeBase?
Black Duck’s open source KnowledgeBase is the industry’s most comprehensive database of open source project, license, and security information, sourced and curated by the Synopsys Cybersecurity Research Center (CyRC). The KnowledgeBase contains more than 2,650 unique open source licenses (GPL, LGPL, Apache, etc.), with full license text for the most popular open source licenses and dozens of encoded attributes and obligations for each license. Black Duck also includes deep copyright data and the ability to pull out embedded open source licenses for complete open source compliance.
Does Black Duck scan containers?
Yes. Black Duck allows teams that package and deliver applications using Docker (and other) containers to confirm and attest that any open source in their containers meets use and security policies, is free of vulnerabilities, and fulfills license obligations. Open source management includes ongoing monitoring for new vulnerabilities affecting existing applications and containers.