Skip to content

Commit 8c71517

Browse files
Content update
1 parent cb889f5 commit 8c71517

11 files changed

+38
-4223
lines changed

SBOM/en/0x10-Introduction.md

+14
Original file line numberDiff line numberDiff line change
@@ -64,11 +64,13 @@ CycloneDX provides advanced supply chain capabilities for cyber risk reduction.
6464
* Software-as-a-Service Bill of Materials (SaaSBOM)
6565
* Hardware Bill of Materials (HBOM)
6666
* Machine Learning Bill of Materials (ML-BOM)
67+
* Cryptography Bill of Materials (CBOM)
6768
* Operations Bill of Materials (OBOM)
6869
* Manufacturing Bill of Materials (MBOM)
6970
* Bill of Vulnerabilities (BOV)
7071
* Vulnerability Disclosure Report (VDR)
7172
* Vulnerability Exploitability eXchange (VEX)
73+
* CycloneDX Attestations (CDXA)
7274
* Common Release Notes Format
7375

7476
<div style="page-break-after: always; visibility: hidden">
@@ -100,6 +102,13 @@ privacy, safety, and ethical considerations. CycloneDX standardizes model cards
100102
and datasets can be used independently or combined with the inventory of software and hardware components or services
101103
defined in HBOMs, SBOMs, and SaaSBOMs.
102104

105+
### Cryptography Bill of Materials (CBOM)
106+
A Cryptography Bill of Materials (CBOM) describes cryptographic assets and their dependencies. Discovering, managing,
107+
and reporting on cryptographic assets is necessary as the first step on the migration journey to quantum-safe systems
108+
and applications. Cryptography is typically buried deep within components that are used to compose and build systems
109+
and applications. As part of an agile cryptographic approach, organizations should seek to understand what cryptographic
110+
assets they are using and facilitate the assessment of the risk posture to provide a starting point for mitigation.
111+
103112
### Operations Bill of Materials (OBOM)
104113
OBOMs provide a full-stack inventory of runtime environments, configurations, and additional dependencies. CycloneDX is a
105114
full-stack bill of materials standard supporting entire runtime environments consisting of hardware, firmware, containers,
@@ -134,6 +143,11 @@ subset of VDR. Oftentimes, products are not affected by a vulnerability simply b
134143
component. VEX allows software vendors and other parties to communicate the exploitability status of vulnerabilities,
135144
providing clarity on the vulnerabilities that pose a risk and the ones that do not.
136145

146+
### CycloneDX Attestations (CDXA)
147+
CycloneDX Attestations enable organizations to communicate security standards, claims and evidence about security
148+
requirements, and attestations to the veracity and completeness of those claims. CycloneDX Attestations is a way to
149+
manage "compliance as code."
150+
137151
### Common Release Notes Format
138152
CycloneDX standardizes release notes into a common, machine-readable format. This capability unlocks new workflow
139153
potential for software publishers and consumers alike. This functionality works with or without the Bill of Materials

SBOM/en/0x15-Object-Model.md

+18-3
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,21 @@ individuals or organizations. Annotations can be independently signed and verifi
8787

8888
![Annotations](../../images/Object-Model/Annotations.svg)
8989

90+
### Definitions
91+
Standards, requirements, levels, and all supporting documentation are defined here. CycloneDX provides a general-purpose,
92+
machine-readable way to define virtually any type of standard. Security standards such as OWASP ASVS, MASVS, SCVS, and
93+
SAMM are available in CycloneDX format. Standards from other bodies are available as well. Additionally, organizations
94+
can create internal standards and represent them in CycloneDX.
95+
96+
![Definitions](../../images/Object-Model/Definitions.svg)
97+
98+
### Declarations
99+
Declarations describe the conformance to standards. Each declaration may include attestations, claims, counter-claims,
100+
evidence, counter-evidence, along with conformance and confidence. Signatories can also be declared and supports both
101+
digital and analog signatures. Declarations provide the basis for "compliance-as-code".
102+
103+
![Declarations](../../images/Object-Model/Declarations.svg)
104+
90105
### Extensions
91106
Multiple extension points exist throughout the CycloneDX object model, allowing fast prototyping of new capabilities and
92107
support for specialized and future use cases. The CycloneDX project maintains extensions that are beneficial to the
@@ -101,10 +116,10 @@ CycloneDX can be represented in JSON, XML, and Protocol Buffers (protobuf) and h
101116
| **Format** | **Resource** | **URL** |
102117
|------------|---------------|--------------------------------------------------|
103118
| JSON | Documentation | https://cyclonedx.org/docs/latest/json/ |
104-
| JSON | Schema | https://cyclonedx.org/schema/bom-1.5.schema.json |
119+
| JSON | Schema | https://cyclonedx.org/schema/bom-1.6.schema.json |
105120
| XML | Documentation | https://cyclonedx.org/docs/latest/xml/ |
106-
| XML | Schema | https://cyclonedx.org/schema/bom-1.5.xsd |
107-
| Protobuf | Schema | https://cyclonedx.org/schema/bom-1.5.proto |
121+
| XML | Schema | https://cyclonedx.org/schema/bom-1.6.xsd |
122+
| Protobuf | Schema | https://cyclonedx.org/schema/bom-1.6.proto |
108123

109124

110125
CycloneDX relies exclusively on JSON Schema, XML Schema, and protobuf for validation. The entirety of the specification
403 KB
Binary file not shown.

0 commit comments

Comments
 (0)