← CRA Glossary
Technical Security

Software Composition Analysis (SCA)

Software Composition Analysis (SCA) is the automated process of identifying open-source and third-party components in a codebase and checking them against known vulnerability databases to detect security risks. SCA is the primary technical mechanism for meeting the CRA's requirement that manufacturers identify and manage vulnerabilities in their products' components.

Software Composition Analysis (SCA) is the automated process of identifying open-source and third-party components in a codebase and checking them against known vulnerability databases to detect security risks. SCA is the primary technical mechanism for meeting the CRA's requirement that manufacturers identify and manage vulnerabilities in their products' components.

Technical Security

Last updated 19 July 2026

What Is Software Composition Analysis?

Software Composition Analysis (SCA) is an automated security testing discipline that scans a codebase, build artefact, or binary to identify all third-party and open-source components - libraries, frameworks, modules, and their transitive dependencies - and then cross-references each identified component against vulnerability databases (CVE/NVD, OSV, vendor advisories) to detect known security issues. SCA tools can also identify licence compliance risks. Modern SCA is integrated into CI/CD pipelines so that vulnerability checks run automatically at every build, providing developers with near-real-time feedback on newly discovered vulnerabilities in components they already use.

CRA reference:Article 13(5),

Why SCA Is Essential for CRA Compliance

Article 13(5) of the CRA requires manufacturers to identify and document the components contained in their products, and requires manufacturers to address vulnerabilities in those components. SCA is the scalable mechanism that makes both obligations achievable. Without SCA, manually tracking hundreds of dependencies across multiple product versions and monitoring each for new CVEs is operationally infeasible. SCA tools automatically generate SBOM artefacts (in CycloneDX or SPDX format) as a build output and alert when any component has a newly disclosed vulnerability - providing the actionable intelligence needed to meet the CRA's patching obligations without undue delay.

CRA reference:Article 13(5),

How Manufacturers Implement SCA

Effective SCA implementation requires integration at multiple points in the development lifecycle. During development, SCA should run on every pull request, blocking merges when newly introduced components carry critical vulnerabilities. In CI/CD pipelines, SCA should run on every build and fail the build on policy violations (e.g. new critical CVEs). At release, SCA output should generate the SBOM that accompanies each product version. Post-release, manufacturers should subscribe to vulnerability feeds and configure SCA tooling to alert the product security team when any component in a shipped product receives a new CVE. This continuous monitoring is what enables the timely patch response that the CRA requires.

CRA reference:Article 13(3)(5), Annex I Part I

Common Mistakes

The most common SCA implementation error is scanning only direct dependencies and missing transitive (indirect) dependencies - which often constitute the majority of a product's open-source exposure. Another error is treating SCA as a development-phase activity only: manufacturers must also monitor components in shipped products after release, as new CVEs are discovered in already-integrated packages continuously. A third mistake is configuring SCA to alert without establishing a defined remediation process: an alert that no one acts on provides no compliance benefit. Finally, manufacturers sometimes rely on package manager manifests alone, missing components bundled as binaries or copied source files.

CRA reference:Article 13(5)

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is SCA the same as vulnerability scanning?+

They are related but distinct. Vulnerability scanning typically refers to scanning a running system, network, or host for known vulnerabilities using active probing techniques. SCA analyses source code, build manifests, or binary artefacts to identify the open-source components they contain and match them against vulnerability databases - without requiring a running system. Both are valuable; SCA focuses specifically on the supply chain risk from third-party components, while vulnerability scanning assesses the broader deployed system.

What output does SCA produce for CRA compliance purposes?+

SCA tools typically produce: (1) an SBOM listing all identified components with versions, licences, and vulnerability status; (2) a vulnerability report mapping each component to its known CVEs with CVSS severity ratings; and (3) a policy evaluation result indicating whether the product meets the manufacturer's configured security policies (e.g. no critical unpatched CVEs). The SBOM output is directly relevant to the CRA's Article 13(5) documentation requirement. The vulnerability report feeds the remediation process required by .

How often should SCA be run on products already in the market?+

For products already placed on the market, manufacturers should run SCA checks at minimum when new CVEs are published against components in their product. In practice, this means subscribing to vulnerability feeds (NVD, OSV, vendor advisories) and re-evaluating the SBOM against new disclosures continuously. Most SCA platforms offer scheduled re-scanning and alerting on new CVE disclosures for existing SBOMs. Given the CRA's obligation to address vulnerabilities 'without undue delay', a re-scan interval of no more than 24 hours for critical vulnerability feeds is advisable.

Sector checklists covering Software Composition Analysis (SCA)

Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Software Composition Analysis (SCA) fits into your complete CRA compliance programme.

View checklists →