Objects
The methodology defines about a dozen objects, each introduced on the page where it is first needed. They are listed together here. For each object, the list gives the party or tool that creates it and how it is identified. It also names what the methodology deliberately leaves out. Nothing here is new: every object is defined on another page.
Model covers the subject matter, meaning the cryptography a document describes. The objects defined here are the documents themselves and the things that check them.
What there is
| Object | What it is | Written by |
|---|---|---|
| Subject | The product or deployment a document describes. A profile declares which kinds it accepts as its subjectTypes. Each document declares its own type, under baseline rule P5. | nobody; it is the thing being described |
| Cryptographic interface | A cryptographic relationship the subject exposes at its boundary. Most rules apply to cryptographic interfaces. CycloneDX 2.0 has its own, different "interface" concept, so the methodology uses the full term where confusion is possible. In a deployment record, each cryptographic interface names the product interface it realises (correspondsTo). See Model. | producer, as part of a document |
| CBOM revision | One revision of the record for one subject, in one carrier format (the document format that carries the CBOM). It is extracted from an inventory and does not exist on its own. A revision carries one lifecycle stage. The vendor writes the product record, at implemented. The operator writes deployment records, at configured and observed, and each deployment record cites the records it builds on. See Inventory. | producer |
| Variant | A revision exists in a public form and a restricted form. The two variants differ in who may hold them. Where the restricted variant carries a value, the public variant carries a marker in its place. See Confidentiality. | producer |
| Profile | The minimum reporting requirements for one stated consumer making one stated decision. A profile is a rules file, not a schema. | profile author |
| Profile family | A set of profiles in which each profile extends another. The profiles are ordered by depth, meaning how much each one requires a producer to disclose. Each profile contains all the requirements of the one below it. The shallowest is the entry profile. A profile that changes the consumer decision is a branch: it starts a separate line instead of adding a level (a rung) to the existing one. | nobody declares it; it follows from each profile's extends field |
| Rule | One requirement. Rules with ids beginning P are evaluated once per product. Rules beginning I are evaluated once per interface. Rules beginning G are evaluated once for each entry in a group. Rules beginning R are reference rules: they check the pointers a document carries to context it does not contain. A rule belongs to its own profile and is cited as tag#id. | profile author |
| Context pointer | A reference from a document to an artefact it does not carry, such as the companion SBOM, a vulnerability statement feed or a configuration guide. A profile defines the kinds of context. A pointer to a fixed document carries a hash. A pointer to a feed or an API names its access protocol. Conformance checks the pointer and never the target. See Context Pointers. | producer, as part of a document |
| Vocabulary | A controlled list a rule constrains values against, such as the cryptographic purposes. | profile author, or inherited |
| Conformance report | The full result of evaluating one document against one profile. It gives the result for each rule and the disclosure state of each rule. | a validator, where the evaluation ran |
| Conformance claim | A portable record of one or more evaluations. It is bound to a document by the document's digest. The claim is the artifact that is passed from one organisation to another. | whoever ran the evaluation |
| Policy | Held outside the CBOM, and versioned. Holds the judgements a CBOM deliberately does not carry, such as whether an algorithm is still acceptable. A policy is versioned data plus a named evaluation method. Two example policies are published under policies/. See Policy Evaluation. | the consuming organisation |
| Policy result | The output of evaluating a policy on a date. It names the policy id, version and digest, the evaluation date, and every CBOM it read, by SHA-256 digest. It also states what it does not assert. A result points to the records it read; a record never points to a result. | whoever evaluated the policy |
| Vulnerability statement | Held outside the CBOM. It is linked to a document rather than contained in one. It cites the document by the same digest that a conformance claim uses to bind to it. Conformance asserts nothing about the vulnerability statement. See Vulnerabilities. | whoever issues it, usually not the producer |
How they connect
How each one is identified
How each object is identified is a recurring question, and the answers were spread across five pages. Identity matters because a conformance claim has to be reproducible years later by somebody who was not present at the original evaluation.
| Object | Identified by | Stable across |
|---|---|---|
| Subject | An identifier in the form the profile names. In the baseline, a product is identified by a package URL (purl), and a deployment by a tag URI (RFC 4151), such as tag:example.org,2026:deployment/sso-prod | revisions of the document |
| Cryptographic interface | interfaceId, chosen by the producer. No profile constrains it. Across a join, a deployment interface names a product interface by a BOM-Link, urn:cdx:<serial>/<version>#<bom-ref> | nothing; it is a label. The BOM-Link is stable for the revision it names |
| CBOM revision | Serial number and version, written as a BOM-Link urn:cdx:<serial>/<version>, and a SHA-256 digest when a deployment record, a claim, a policy result or a vulnerability statement cites it | nothing; a new revision is a new document |
| Profile | profileId and version, cited together | a published version is never altered |
| Profile, in a citation | profileTag, the short handle | the life of the profile |
| Rule | tag#id, such as interface-disclosure#I9. The id belongs to the profile that introduced it, not to one that later tightened it. | every version after it appears; a released id is never reused |
| Claim | The digest of the document it is about | nothing; a new revision needs a new claim |
| Policy | Its id, version and digest, recorded in every result it produced | whatever the consuming organisation decides |
| Policy result | The policy it applied, the evaluation date and the digests of the CBOMs it read | nothing; a new evaluation is a new result |
Two axes that get confused
Capture phase and revision state were described by a single word until decision 0021. They are different things and must be kept apart.
Capture phase belongs to the facts. lifecycleStage says whether the values were implemented, configured or observed. This tells a reader how much weight the values carry. Under baseline rule P6 a document carries one stage for all its facts, natively in metadata.lifecycles. Where an interface also carries its own lifecycleStage, the two must agree. The baseline does not accept intended; only the entry profile does. See Lifecycle Data.
Revision state belongs to a document. A document can be created, signed, published or superseded. Its revision state is the same for every attribute in the document. Governance controls how a document moves from one state to the next. See Governance.
What is deliberately not an object here
A judgement. A judgement states, for example, whether an interface is adequate or how mature a supplier's disclosure is. Policy produces the judgement at evaluation time. The judgement records the policy version and the date the policy was applied. Storing a judgement in a document would freeze an answer whose criteria change over time. A depth is a profile. A maturity level is a judgement derived from a depth.
An attestation. Nothing here establishes that a disclosed value is true. A signature shows where a document came from and that it has not been altered. A claim shows what was evaluated. A producer who states the wrong protocol version still produces a document that can be signed, passes validation, and has a signature that verifies.
A registry. Profiles, documents and claims all have to be stored and served somewhere, and the model says nothing about where. Storage is left to whoever operates the inventory. The only requirement placed on that operator is the archive obligation in Governance.