|
+ENISA Technical Advisory for Software Bill of Materials ---+1. Introduction ------+1.1 Introduction ------+1.2 Scope and Context ------+1.3 Note on the current version of the document ---+2. SBOM Architecture and Data Flows ------+2.1 How Software Bill of Materials works ---------+2.1.1 Data Model ---------+2.1.2 SBOM Formats ---------+2.1.3 SBOM Types ------+2.2 SBOM Lifecycle ---------+2.2.1 SBOM Lifecycle Phases ---------+2.2.2 SBOM as part of a CI/CD Pipeline ---------+2.2.3 SBOM Open-source Tooling Landscape ---+3. SBOM Threats and Risks ------+3.1 SBOM Threats ------+3.2 SBOM General Risks ---+4. SBOM Best Practices ------+4.1 SBOM Integration and Automation ---------+4.1.1 Integration Patterns ---------+4.1.2 Common Configuration Requirements ------+4.2 General Security Recommendations |
ENISA Technical Advisory for Software Bill of MaterialsThis document provides practical guidance on the adoption of SBOM, and it is intended for organizations especially micro-, small and medium enterprises (SMEs) and stewards seeking to set up the initial capabilities to enhance the software supply chain transparency. It aligns with the security principles from the ENISA Secure by Design and Default Playbook. In particular, this advisory: outlines the SBOM implementation architecture and data flows based on a defined lifecycle; presents an indicative SBOM threat model along with targeted risks; lists measures to address the security issues across the SBOM ecosystem. https://www.enisa.europa.eu/publications/enisa-technical-advisory-for-software-bill-of-materials – PDF 1. Vue d’ensemble
1.1 Références1.2 Exigences identifiées1.3 Réglementations associées2. Exigences identifiées
3. Réglementations associées
Tickets liés
|