This document is under active development and has not been finalised.
Skip to content

Chapter 5: Supply Chain Security ​

Overview ​

Securing the software supply chain is a core CRA requirement. Manufacturers must exercise due diligence when integrating third-party components and ensure the integrity of the entire supply chain.

LEGAL BASIS

Art. 13(5) CRA: "The manufacturer shall exercise due diligence when integrating components sourced from third parties, to ensure that those components do not compromise the security of the product."

Annex I, Part II, No. 1: "The manufacturer shall identify and document the vulnerabilities and components contained in the product, including by drawing up a software bill of materials."

Security Measures ​

Implemented Measures ​

MeasureToolWorkflowStatus
Dependency Vulnerability ScanningTrivy, Grype, OSV-Scannermodules-security-scan.yml, cra-scan.yml✅
Automated Dependency UpdatesDependabotdocker-maintenance-dependabot.yml✅
License ComplianceFOSSA / Custommodules-license-compliance.yml✅
Secret ScanningGitleaks, GitGuardianmodules-security-scan.yml✅
Docker Base Image MonitoringCustom Workflowmodules-docker-base-image-monitor.yml✅
Container Image SigningCosigndocker-build.yml✅
SBOM GenerationTrivy / Syftmodules-license-compliance.yml✅

Chapter Structure ​

SectionTopicDescription
5.1Dependency PolicyPolicies for dependencies
5.2Base Image PolicyDocker base image management
5.3Third-Party AssessmentAssessment of third-party components
5.4Economic Operator Identification (Art. 23)Supply chain traceability

NIS2 Synergy

IT service provider and infrastructure vendor assessment is described in the NIS2 Compliance Documentation. CRA focuses on software supply chain, NIS2 on service provider assessment.

Documentation licensed under CC BY-NC 4.0 · Code licensed under MIT