Required for the site to work (login, preferences, security). Always on.
SBOM: supply-chain inventory, not a “no vulnerabilities” certificate
According to CISA, an SBOM is a software ingredients list for supply-chain risk decisions. It shows what is there; it does not by itself prove absence of vulnerabilities. 2026 minimum elements and CycloneDX.
Asking suppliers for an SBOM (Software Bill of Materials) is a request for transparency: which components make up the product. It is not, by itself, a guarantee that no CVEs exist or that the software is “safe”.

What CISA and open formats say
On the Software Bill of Materials (SBOM) page, CISA describes the SBOM as a building block for software security and supply-chain risk management: a nested inventory, an ingredients list of software components.
The joint document 2026 Minimum Elements for a Software Bill of Materials (SBOM) (publication date indicated by CISA: 29 July 2026) updates and replaces the 2021 NTIA minimum elements. CISA writes that the SBOM serves as an “ingredients list” and that organizations can use SBOM data to understand software composition and make more informed risk decisions. The minimum elements describe baseline technologies and practices an SBOM should include; CISA also states in the joint document, Scope section that they do not, by themselves, create new obligations (the joint text stresses expected elements, not an automatic new rule for every context).
An open machine-readable format is CycloneDX (JSON specification v1.6): it defines fields such as bomFormat, specVersion, metadata, components and external references. CycloneDX can represent a structured inventory, but schema validity alone does not guarantee the presence, completeness or accuracy of the component list (components is not required in schema 1.6). An SBOM is not equivalent to a penetration report or an attestation of absence of vulnerabilities. CISA, on the SBOM FAQ page, places related efforts such as VEX (Vulnerability Exploitability eXchange) alongside the SBOM: a signal that inventory and exploitability statements are distinct concepts.
Editorial recommendation: in MSP RFPs and reports use “SBOM = declared composition”; pair it with scans, patches and (if available) VEX/advisories, without promising “zero vulnerabilities thanks to the SBOM”.
Why it matters to you
Altovar editorial assessment, not prescriptions of CISA.
- Patch priority. Knowing whether a library is present speeds triage when an advisory is published.
- Supplier contracts. An SBOM and update process can be requested; “safe product” cannot be inferred from the file alone.
- AI/SaaS. CISA notes that software types such as AI or SaaS may require additional elements beyond the minimum.
What to do today
Altovar editorial checklist, to adapt to risk and client requirements.
- Define which format is accepted (for example CycloneDX) and for which critical products; also verify completeness and accuracy of components, not only schema validity.
- Link the SBOM to a process that compares it with advisories (do not stop at an “archived” PDF/JSON).
- Ask for SBOM regeneration frequency when the build changes, not a one-off.
- Treat gaps or declared “unknown” components as risk to manage, not as cosmetic detail.
READ MORE
- CISA — SBOM
- CISA — 2026 Minimum Elements for an SBOM (29 July 2026)
- PDF — 2026 Minimum Elements (Scope section)
- CycloneDX v1.6 JSON Reference
- CISA — SBOM FAQ
- Altovar editorial policy
Signature: Neska
Transparency note: Article generated by Neska (Altovar AI system) from linked CISA and CycloneDX pages. The SBOM is described by the sources as an inventory for risk decisions, not as proof of absence of vulnerabilities. No SBOM analysis performed by Altovar. No sponsored content.
Sources: cisa.gov/topics/information-communications-technology-supply-chain-security/sbom, cisa.gov/resources-tools/resources/2026-minimum-elements-software-bill-materials-sbom, cisa.gov/sites/default/files/2026-07/2026_cisa_sbom_minimum_elements_508c.pdf, cyclonedx.org/docs/1.6/json, cisa.gov/resources-tools/resources/sbom-faq