Use cases
A CBOM profile is written for someone who has a decision to make. A use case names that person and that decision: a buyer comparing tenders, a responder tracing an advisory, a grid operator planning a migration. The use cases the working group has identified are collected here. The most developed ones are taken further: each is turned into a profile, the profile is applied to a real product, and the resulting documents can be checked against it.
| Kind of page | What it gives you |
|---|---|
| Group pages | What the use cases in a group have in common, and a description of each: Disclosure, Change planning, Operation, Assurance |
| Worked examples | One use case taken through to a profile, applied to a real product, with a document that conforms and one that does not. Three are complete, and all three are applied to Keycloak 26.7.3: PQC migration, Procurement and the deployment disclosure profile in Operation |
| Writing a use case | How to propose a use case, and the template a worked example follows |
Use case groups
Use cases are split into groups. A group clusters use cases that share a common goal and need similar information in the CBOM. There are currently two groups. In Disclosure, the goal is to know what cryptography a product uses. In Change planning, the goal is to decide how to change it. The table below compares the two groups. Two further groups, Operation and Assurance, are proposed but not yet settled. The Operation group already has its first profile, deployment disclosure v0.2.
| Disclosure: know what a product uses | Change planning: decide how to change it |
|---|---|
| The profile chooses which facts a CBOM must carry from the set every CBOM already describes: interfaces, protocols, algorithms and the libraries that implement them. | The profile adds facts a basic CBOM does not have: what each interface could support, what is blocking it, and what changing it costs. |
| One CBOM from a supplier can answer every profile in this group. | A supplier has to produce a richer CBOM. That CBOM then answers the disclosure profiles as well. |
| Procurement, vulnerability response, compliance reporting, due diligence. | PQC migration, IoT device estates, substation automation, crypto-agility. |
Use cases are not grouped by sector. A telecom operator and a grid operator planning a migration make the same kind of decision, so they share a use case. Terms specific to a sector go into the profile, not into a separate use case.
All use cases
| Use case | Who decides, and what | Group | Status | Worked example |
|---|---|---|---|---|
| Procurement and tender conformance | A buyer: whether a tender's cryptographic disclosure is complete enough to compare and hold the supplier to | Disclosure | Worked example | Read |
| Supply-chain transparency | A supplier: how to disclose once to every customer | Disclosure | Described | — |
| Vulnerability management and incident response | A responder: which services a published advisory reaches | Disclosure | Described | — |
| Regulatory and compliance reporting | An auditor or regulator: whether a position meets a framework | Disclosure | Described | — |
| Mergers and third-party due diligence | An acquirer: where the cryptographic risk sits in an estate it cannot inspect | Disclosure | Described | — |
| Managed and cloud service disclosure | A customer: whether to rely on a service it does not run | Disclosure | Proposed | — |
| Service assurance | An assurance team: which customer services a weakness or a change reaches | Disclosure | Proposed | — |
| Deployment disclosure | An operator: which published weakness affects each interface of a deployment, and where the deployment falls short of what its products can do | Operation | Worked example | Read |
| PQC migration | A migration lead: which interfaces to migrate, in what order, at what cost | Change planning | Worked example | Read |
| IoT device estate | A fleet operator: for each device model, update, replace, shield or accept | Change planning | Draft worked example | Read |
| Substation automation (OT) | A grid operator: for each communication path, migrate, shield or replace | Change planning | Draft worked example | Read |
| Crypto-agility assessment | An architect: how hard replacing an algorithm would be | Change planning | Described | — |
| PKI and certificate estate migration | A PKI owner: which hierarchies move, in what order, while relying parties catch up | Change planning | Proposed | — |
| Code and firmware signing migration | A publisher: when signing keys can move, given the verifiers already deployed | Change planning | Proposed | — |
| Stored data and archive protection | A data owner: which stores and archives to re-encrypt first | Change planning | Proposed | — |
| Shared-trust network migration | A scheme operator: when every participant can move to a new trust anchor | Change planning | Proposed | — |
Worked example: a checked profile with conforming and non-conforming documents. Draft worked example: written in that shape, not yet settled. Described: consumer, decision and what the profile needs are written. Proposed: consumer and decision named. Full definitions are on Proposing a use case.
What is not a use case
Two things are often suggested as use cases. Both are ways of applying a profile instead.
- Continuous integration quality gate. A pipeline fails a build when a CBOM does not conform. Any profile can be applied this way. What the gate needs is a validator that returns a usable exit status and report. The reference validator,
validate_cbom.py, exits with 0 when a document conforms and 1 when it does not conform. A gate must not treat every non-zero code as a failure: exit code 4 means the document was refused on its carrier version and never assessed. This is covered in Conformance and the Demo. - Change impact between versions. Comparing two CBOMs of the same product to see what changed. This is a comparison between two documents. It is covered in Versioning.
How this section relates to the methodology
The methodology is the working group's deliverable. It says how to define a profile, and Starting from a use case explains why every profile begins with a consumer and a decision. The methodology illustrates its concepts with the Keycloak 26.7.3 example. It does not list any use cases. Everything about particular use cases, including the worked examples, is in the Use Cases section.