CBOMProfiles /Use Cases ← Working group site
GROUP

Operation: the operator describes what it runs

Use cases in which the CBOM is produced by the operator of a system rather than by the supplier of a product. The subject is a deployed system, a service or an estate, and what is reported is mostly configured or observed. An operator can state facts no supplier knows: what data crosses an interface and how long it must stay confidential, what was actually negotiated, which instances are still running, and what has changed since the last report.

What the group shares

The Disclosure and Change planning groups are each defined by the facts their profiles ask for. The Operation group is defined by who produces the document: the operator of the system. The operator can see the whole deployed system. A supplier cannot see how its product is deployed, so supplier profiles only ask for facts that can be known from the product itself. That limit does not apply to an operator, so a profile in this group can ask for more. It can require the deployment facts that the interface disclosure baseline excludes because a vendor cannot know them: the payload an interface carries, its confidentiality lifetime, the number of instances, and the configuration as observed rather than as declared.

An operator document usually draws on supplier documents rather than repeating them. It cites the supplier CBOM for each product it runs, by BOM-Link and SHA-256 hash, and adds what only the operator knows. A document that cites other documents and adds to them is an overlay, as defined in Maturity. The substation system document has the same relation to its component documents.

A use case belongs in this group when the operator produces the document. An operator describing what it runs may also be planning a change. A profile in this group can therefore extend either the interface disclosure baseline or the change core, which is the shared base of the change-planning profiles. Each use case decides which of the two to extend. The first profile, deployment disclosure, extends the baseline.

Questions this group owns

QuestionWhy it belongs to this group
Q36, Q45Where vendor-stated data facts end and operator-stated ones begin, and how the operator's half is linked to the supplier's document. Settled provisionally: the vendor states intrinsic data, and the operator states the payload in its data register, linked by rule R3.
Q37The confidentiality-lifetime bands an operator would report against. Settled provisionally: the five bands proposed in Data Exposure.
Q67Whether an estate is a subject a profile can declare, with its own completeness statement. Settled provisionally: no. An estate is read as a set of product and deployment documents.
Q68What an overlay's verdict says about the supplier documents it cites. Settled provisionally: each cited document's verdict is reported beside the overlay's own.

Worked example: deployment disclosure v0.2

The profile is profile-deployment-disclosure.rules.json, version 0.2. It extends the interface disclosure baseline v0.9. Its consumer is an operator, or an assessor acting for one, responsible for a deployment built from products it did not build. The decision is, for each interface of the deployment: which published weakness affects it, whether what the deployment permits matches what it was seen to do, and where the deployment falls short of what its products can do.

The profile accepts one subject type, deployment, and two stages, configured and observed. It excludes implemented, because a deployment record that repeats the vendor's build facts adds nothing. It cites the vendor's record instead. The vendor writes the product record. The operator writes one deployment record per stage. The records are joined, not merged.

RuleLevelWhat it requires
P1MUSTThe record cites each document it builds on by BOM-Link (urn:cdx:<serial>/<version>) and SHA-256 hash. When the consumer supplies the cited document, the validator checks its serial number, version and hash.
I1MUSTcorrespondsTo: the interface in a cited document that this interface realises, as a BOM-Link to its bom-ref, or the literal no-product-document. The implementing library is inherited across this join. Present-state facts are never inherited.
I2MUST at observedobservationMethod: how each observed value was obtained (active-probe, passive-sensor, endpoint-query, platform-query, inspection).
I3MUST at observedobservedAt: the time or interval of the observation.
I4MAYpeerInterface: the interface at the far end of the connection, as a BOM-Link into a cited document, or peer-not-recorded. Either end may state it. With both ends' records, the edge-posture evaluation says which end limits the connection (decision 0026).
R1MUST at configuredA pointer to the configuration revision the record was read from.
R2SHOULD at observedA pointer to the evidence an observed value was taken from. Withholdable, because evidence often carries internal addresses.
R3SHOULDA pointer to the operator's data register, which records what data each interface carries and how long it must stay confidential. Withholdable. The record points to the register and does not carry it.
R4MAYA pointer to the certificate policy of the CA that issues the deployment's certificates.

The examples describe an illustrative operator, Example Org, running Keycloak 26.7.3 at sso.example.org. The operator ends TLS at an ingress (nginx with OpenSSL 3.5) and runs Keycloak behind it with its plaintext HTTP listener enabled. Both records cite the vendor's product record.

RecordWhat it showsVerdict
cbom-keycloak-deployment-configured.cdx.jsonThe deployment read from its configuration repository, realm exports and JVM settings. Values are the sets the deployment permits.conforms
cbom-keycloak-deployment-observed.cdx.jsonThe deployment observed from 18 to 25 October 2026. Each interface names its observation methods. It cites the configured record, and follows the implementing library through two joins: observed to configured to product.conforms
cbom-keycloak-deployment-configured-fail-literal.cdx.jsonThe database connection keeps the product record's peer-defined. At configured the operator knows the answer.fails baseline I3, I4 and I5 on that interface
cbom-keycloak-deployment-observed-fail-unknown.cdx.jsonThe database connection was observed through pg_stat_ssl alone, which does not report the group.fails baseline I3; conforms to the entry profile
cbom-keycloak-deployment-observed-fail-P1.cdx.jsonThe configured record it cites has changed since it was cited.fails deployment P1 (hash mismatch)
cbom-keycloak-deployment-observed-outside.cdx.jsonAn outside assessor who could not reach the management interfaces. It states them as not-reached, with coverage partial.passes P2; fails I9 on the ingress, because the library is not visible; conforms to the entry profile

The observed record shows two things the configured record cannot. 29% of ingress sessions still negotiate X25519 alone, although the deployment permits X25519MLKEM768. Tokens for one client are still signed with RS256. The readiness-gap policy evaluates the joined records and reports a class for each interface and purpose. It computes the gap from the join and never stores it in a record. Its result is result-readiness-gap-sso-prod.json. See Policy Evaluation.

The use cases in this group

Managed and cloud service disclosure

The producer is the operator of the service, so the use case shares this group's premise. Its description is in the Disclosure group, where the register lists it. Proposed.

Stored data and archive protection

Only the operator knows what a store holds and for how long, so the use case shares this group's premise. Its description is in the Change planning group, where the register lists it. Proposed.

Harvest-now-decrypt-later exposure

A security function decides which of its systems are exposed to traffic recorded today and decrypted later, and which to migrate first on that ground. Exposure depends on two facts a supplier cannot state: what data crosses an interface, and how long that data has to stay confidential. Combined with the key establishment the interface uses today, these two facts give the window during which recorded traffic remains worth decrypting.

Some of these facts are known to the supplier, however. Credentials on a management interface and key material on a key-management interface follow from the interface's design, and they often have the longest lifetimes. Q36 asks where the supplier's facts end and the operator's begin. The deployment profile already gives the operator's half a place: rule R3 points to the operator's data register. Proposed. Q36, Q37 and Q45 are settled provisionally. The attribute for the supplier's intrinsic data is still to be defined.

Migration progress over time

A migration programme lead, or a regulator receiving its reports, decides whether a migration is on track: how much has moved since the last report, how much remains, and why the numbers changed. The facts needed are two operator documents about the same estate at different dates, and the reason for each difference between them: an interface migrated, a product replaced, an instance retired, or an earlier finding that turned out to be a false positive.

Comparing two documents is covered by Versioning. This use case adds the reason for each change. Without the reason, a reader cannot tell whether a count fell because work was done or because a scanner stopped looking. Raised in member feedback on the Inventory chapter: "How much more do we have to do to be PQC ready?" Proposed.

The operator's migration register

An operator records, for each finding in its estate, the decision it took: the response, who owns it, the target date and the status. These are judgements and plans. Decisions 0002 and 0007 keep them out of a supplier's CBOM, because a supplier document records facts about a product and a date there is a promise the supplier may not control.

They belong in the operator's own document about its own estate. Documents of that kind are what this group covers. CycloneDX 2.0 gives them a native home in its root risks list, with an owner, a response strategy, a target date and a status for each risk. The validator ignores risks for conformance, and a supplier's product record should not carry them. Proposed.

PKIC CBOM Profiles Working Group ยท draft for comment.