Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Software Composition Analysis?

Software composition analysis identifies the open-source components in an application, matches them against known vulnerabilities and licences, and tracks them as they change.

Illustration for the cybersecurity term Software Composition Analysis
Home / Blog / Cybersecurity Terms / What Is Software Composition Analysis?
17 November 2026

What Is Software Composition Analysis?

What Is Software Composition Analysis?

Most of the code in a modern application was written by someone else. A typical JavaScript service resolves well over a thousand packages, a Java service a few hundred, and almost none of them were chosen deliberately: they arrived as dependencies of dependencies. Software composition analysis is the practice of knowing exactly what those components are, which published vulnerabilities apply to them, what licences they carry, and when any of that changes.

How the Analysis Works

A scanner builds an inventory first. The reliable method reads the resolved dependency graph, from a lockfile, a build output, or a compiled artefact, rather than the declared manifest, because the manifest states intent and the lockfile states fact. Container images are analysed layer by layer, which picks up operating system packages alongside application libraries.

Each component is then matched against vulnerability data: the National Vulnerability Database, the OSV database that aggregates ecosystem-specific advisories, GitHub’s advisory database, and vendor feeds. Matching is the part that goes wrong. Version strings differ between ecosystems, vendored and repackaged code hides its origin, and advisories sometimes name a product rather than a package. Expect both missed components and false matches, and expect to verify rather than to accept.

Transitive Dependencies and Reachability

The dependency you installed is rarely the one that is vulnerable. Fixing a transitive issue means persuading the direct dependency to accept a newer version of its own, and when it will not, the options are a version override, a fork, or replacement. Scanners that report only direct dependencies miss most of the real exposure.

Reachability analysis is what makes the output manageable. A vulnerability in a function your code never calls still deserves patching, and it is not an emergency. Tools that trace call paths from your code into the dependency can separate the two, which commonly reduces the urgent list by an order of magnitude. Treat the result as prioritisation rather than as permission to ignore, since a future change may make the unreachable path reachable.

Two Incidents Worth Remembering

Log4Shell, CVE-2021-44228, was published on 9 December 2021. A logging library present in an enormous share of Java applications evaluated JNDI lookups found inside logged strings, so writing a crafted string into any logged field produced remote code execution. The exploit was trivial and the hardest part of the response, for nearly every organisation, was answering the question of where the library was installed. Teams with a dependency inventory answered in hours; teams without one spent weeks.

The xz-utils backdoor, CVE-2024-3094, was disclosed on 29 March 2024. A maintainer account built up over years inserted obfuscated code into release tarballs of a widely used compression library, targeting SSH authentication on systems that linked it indirectly. No scanner would have flagged it before disclosure, because the component was not known to be vulnerable; what mattered was knowing quickly whether the affected versions were present. That is the argument for an inventory independent of the argument for vulnerability matching.

Making It Work in Practice

  1. Scan the resolved graph, not the manifest, and scan container images as well as application dependencies.
  2. Generate a software bill of materials per release in CycloneDX or SPDX format and store it with the artefact, so the inventory question can be answered for any version still in production.
  3. Automate the routine updates. Dependabot or Renovate raising pull requests for patch and minor versions, gated by your test suite, removes most of the backlog before anyone looks at it.
  4. Prioritise on reachability, exploitability, and exposure, using signals such as the CISA Known Exploited Vulnerabilities catalogue and EPSS alongside the CVSS score.
  5. Fail builds on new critical findings only, with the existing backlog baselined and worked separately, as described in DevSecOps.
  6. Check licences at the same time, since a copyleft obligation discovered after shipping is a different kind of incident.

The Regulatory Direction

The NCSC’s supply chain security guidance expects organisations to understand and manage the components they depend on, and to hold suppliers to the same standard. The EU Cyber Resilience Act, which entered into force on 10 December 2024, will require manufacturers placing products with digital elements on the EU market to maintain a software bill of materials and to handle vulnerabilities throughout the product lifetime, with the main obligations applying from December 2027. UK organisations selling into the EU are in scope. Since this control also addresses dependency confusion and other build-time manipulation, it is a standard area of review during our penetration test services.

FAQ – Frequently Asked Questions

Is SCA the Same as Vulnerability Scanning?

They answer different questions. A network vulnerability scanner probes running hosts and services for known weaknesses from the outside. Software composition analysis reads your dependency graph and matches it against advisories, which finds libraries embedded in an application that no network probe would reveal. Most programmes need both, since neither sees what the other does.

Do We Have to Fix Every Reported Vulnerability?

No, and attempting it exhausts the team. Prioritise by whether the vulnerable code is reachable from your own, whether the component is exposed to untrusted input, whether exploitation is known to be occurring, and what the realistic impact would be. Record the reasoning for anything deferred, with an owner and a review date, so the decision is visible later.

What Is Reachability Analysis?

It determines whether your code can actually invoke the vulnerable function in a dependency, rather than merely including the package. Tools trace call paths from your entry points into library internals. The distinction matters because a large majority of reported issues sit in code paths an application never executes, and separating those from the genuinely exposed ones makes the backlog tractable.

Does an SBOM Solve the Problem on Its Own?

It solves the inventory half. An SBOM tells you what is in a release, which is exactly what organisations could not answer during Log4Shell and the xz-utils backdoor. It does not tell you what is vulnerable today, so it has to be checked continuously against advisory data as new issues are published against components you already shipped.

Related Terms

You May Be Interested In These

What Are Security Maturity Models?

Cybersecurity Terms

17 November 2026

What Are Security Maturity Models?

Read More
What Is Key Management and Key Rotation?

Cybersecurity Terms

17 November 2026

What Is Key Management and Key Rotation?

Read More
What Are CSIRT and CERT?

Cybersecurity Terms

17 November 2026

What Are CSIRT and CERT?

Read More