CBOMProfiles /Use Cases ← Working group site
USE CASES

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 pageWhat it gives you
Group pagesWhat the use cases in a group have in common, and a description of each: Disclosure, Change planning, Operation, Assurance
Worked examplesOne 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 caseHow 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 usesChange 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 caseWho decides, and whatGroupStatusWorked example
Procurement and tender conformanceA buyer: whether a tender's cryptographic disclosure is complete enough to compare and hold the supplier toDisclosureWorked exampleRead
Supply-chain transparencyA supplier: how to disclose once to every customerDisclosureDescribed—
Vulnerability management and incident responseA responder: which services a published advisory reachesDisclosureDescribed—
Regulatory and compliance reportingAn auditor or regulator: whether a position meets a frameworkDisclosureDescribed—
Mergers and third-party due diligenceAn acquirer: where the cryptographic risk sits in an estate it cannot inspectDisclosureDescribed—
Managed and cloud service disclosureA customer: whether to rely on a service it does not runDisclosureProposed—
Service assuranceAn assurance team: which customer services a weakness or a change reachesDisclosureProposed—
Deployment disclosureAn operator: which published weakness affects each interface of a deployment, and where the deployment falls short of what its products can doOperationWorked exampleRead
PQC migrationA migration lead: which interfaces to migrate, in what order, at what costChange planningWorked exampleRead
IoT device estateA fleet operator: for each device model, update, replace, shield or acceptChange planningDraft worked exampleRead
Substation automation (OT)A grid operator: for each communication path, migrate, shield or replaceChange planningDraft worked exampleRead
Crypto-agility assessmentAn architect: how hard replacing an algorithm would beChange planningDescribed—
PKI and certificate estate migrationA PKI owner: which hierarchies move, in what order, while relying parties catch upChange planningProposed—
Code and firmware signing migrationA publisher: when signing keys can move, given the verifiers already deployedChange planningProposed—
Stored data and archive protectionA data owner: which stores and archives to re-encrypt firstChange planningProposed—
Shared-trust network migrationA scheme operator: when every participant can move to a new trust anchorChange planningProposed—

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.

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.

PKIC CBOM Profiles Working Group · draft for comment.