Software Bill of Materials
What is Software Bill of Materials?
A comprehensive inventory of all components, libraries, and dependencies used in a software application, supporting vulnerability management and supply chain security.
Terms that appear alongside software bill of materials
Each of these is named in at least one of the same controls as software bill of materials. The number is how many controls name both.
- software bill of materials sbom 22 shared controls
- vulnerability 14 shared controls
- cybersecurity 10 shared controls
- nist 9 shared controls
- supply chain risk 8 shared controls
- audit 8 shared controls
- risk assessment 7 shared controls
- cisa 7 shared controls
Frameworks that govern software bill of materials
What the standards actually require on software bill of materials
Requirements naming software bill of materials across 6 standards, quoted from the control text.
A software bill of materials is produced and made available to consumers of software.
ISM-1730 · A software bill of materials is produced and made available to consumers of software. →UR E27 requires equipment manufacturers to provide Software Bill of Materials (SBOM) and demonstrate secure development. SBOM contents per CISA SBOM Minimum Elements + SPDX or CycloneDX format: component name + version + supplier + license + dependency relatio...
IACS-UR-E27-SBOM-SecureDev-TypeApproval-SoftwareIntegrity · IACS UR E27 - Software Bill of Materials + Secure Development Lifecycle + Type Approval + Software Integrity →Obtain and use a software bill of materials for acquired and produced software to support vulnerability management, licence compliance, and provenance tracking.
SCRM-COMP-2 · Software Bill of Materials Use →Produce a software bill of materials for each release in a machine readable format. Make it available to customers and use it internally to triage component vulnerabilities.
SP800-218-PS.3.2 · Software Bill of Materials →Article 54 establishes SUPPLY CHAIN CYBERSECURITY requirements for high-impact + critical-impact entities. Suppliers + service providers + software vendors providing components or services with cyber-physical-system implications must: (a) meet the Article 30 m...
NCCS-Art.54_55_56 · Supply chain cybersecurity (NCCS Articles 54-56) →ISMAP Cloud Infrastructure controls cover the underlying compute + network + storage + management plane. (1) Virtual Network Segmentation: VPC Virtual Private Cloud isolation + subnets + security groups + NACLs + microsegmentation + service mesh (Istio + Linke...
ISMAP-CloudInfrastructure-NetworkSegmentation-Container-Serverless-WorkloadProtection-Hardening-ConfigManagement · ISMAP Cloud Infrastructure - VPC Network Segmentation + Container/Serverless Security + Cloud Workload Protection (CWPP) + Image/Template Hardening + CIS Benchmarks + Configuration Management + IaC →Questions people ask about software bill of materials
What is Software Bill of Materials?
Why is Software Bill of Materials important for compliance?
Which compliance frameworks address Software Bill of Materials?
Where can I learn more about Software Bill of Materials?
See how Software Bill of Materials applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.