Skip to main content

22 docs tagged with "SBOM"

View all tags

CRA - Normative cross-check

Analysis of how SbD-ToE supports the technical core of the Cyber Resilience Act in the context of products with digital elements, with explicit conformity boundaries

Dependencies, SBOM and SCA

Principles, practices and controls to guarantee secure dependency management, SBOM generation and automated software composition analysis

Dependencies, SBOM and SCA Requirements Catalogue

Canonical catalogue of security requirements for the management of third-party dependencies (DEP-001 to DEP-010), with applicability by risk level and acceptance criteria for SBOM, SCA, library governance and update policies.

Dependency Management Policy

Organisational policy that defines the criteria for approving, pinning, blocking, auditing and updating external dependencies in software projects, proportional to the application's criticality level (L1, L2, L3), with a focus on reducing supply chain risk and ensuring traceability.

Dependency Security

Practices for managing and validating external dependencies to ensure integrity, currency and security in the code

How to Do It

How to apply the prescribed container security practices throughout the development and operations lifecycle

How to Do It

Practical integration of the dependency management, SBOM generation and SCA execution prescriptions throughout the application lifecycle

KPIs and Metrics - Dependencies, SBOM and SCA

Technical and operational indicators for the assessment of the effectiveness of the controls for dependency management, SBOM generation and software composition analysis, with thresholds per risk level and mapping to the cross-cutting SbD-ToE governance dimensions.

Policies

Organisational policies that support the practical application of this chapter

SBOM (Software Bill of Materials) Policy

Organisational policy that defines the requirements for the generation, format, signing, provenance, archiving and retention of SBOMs (Software Bill of Materials) in software, container and IaC builds, proportional to the application's criticality level (L1, L2, L3).