CBOMProfiles /Methodology ← Working group site
REFERENCE

Terms and definitions

The vocabulary this methodology uses, collected in one place. Definitions here are summaries; the section named against each term is where it is developed and is authoritative if the two differ.

How to read this section

Terms are grouped by what they describe. Where a term is borrowed from elsewhere, the source is named, because a methodology that quietly redefines an established term causes more difficulty than one that invents a new word. Attribute names follow the conventions recorded in Method: a bare name denotes present state and a Supported suffix denotes declared capability.

The definitions in the model table, together with Join, are normative. Every requirement is written in them, and a profile that uses these words must use them with these meanings. The Model section that develops them is informative.

The last table lists terms that were considered and not used, with the reason for each. They are recorded so that the same discussion does not have to be repeated.

The model

TermDefinitionDeveloped in
Cryptographic relationship
also: edge
The place where cryptography is applied between parties. A relationship is not itself a cryptographic asset. The term was introduced by this methodology.Model
Endpoint
also: node
A party to a cryptographic relationship. An endpoint need not be a running host, and the parties to a relationship need not exist at the same time.Model
Cryptographic assetAn algorithm, protocol, certificate, or key used by a relationship. Corresponds to the CycloneDX component type of the same name.Model
Cryptographic interface
also: interface
A cryptographic relationship that is a communication interface between two parties. Interfaces are a subset of relationships. The term is kept because the profile's rules are written about interfaces. An interface is a logical cryptographic boundary, not a port. Two layers of cryptography on one port are two interfaces: for example, the TLS session on Keycloak's HTTPS listener, and the signed OIDC tokens carried inside it. An application-layer interface counts when it applies cryptography of its own or is reachable without transport protection. Write "cryptographic interface" wherever the CycloneDX 2.0 blueprint "interface" could be meant.Model
Application-layer interfaceAn interface whose protocol sits above the transport, such as OIDC, SAML, an administrative API or plain HTTP. In CycloneDX 2.0 it is a component of type: "service", because CycloneDX's protocol types cover security protocols only.Model
Node fact / edge factA node fact is a property of a thing, such as a product (an endpoint, or node). An edge fact is a property of one use of that thing in a cryptographic relationship (an edge). "The product supports AES-256-GCM" is a node fact. "This connection negotiated AES-256-GCM" is an edge fact.Model

Profiles and conformance

TermDefinitionDeveloped in
Profile
also: PKIC CBOM profile
A defined subset of mandatory attributes for a stated objective, expressed independently of any format. It sets a minimum reporting requirement and does not aim at exhaustive coverage. Its rules file is normative.Profile
PKIC CBOM profile and CycloneDX profilesTwo different things. A PKIC CBOM profile is a profile in the sense of this methodology. CycloneDX 2.0 has its own profiles element, which holds reusable data and threat characterizations. Where the two could be confused, write "PKIC CBOM profile". Each PKIC CBOM profile also publishes a CycloneDX 2.0 perspective generated from its rules. The perspective is informative only.Versioning
Profile scopeThe boundary a profile declares: the subject types it accepts, its orientation, the relationship types its rules constrain, and the lifecycle stages of reported data it accepts. The parts are decided together in Method step 2 and recorded as one object, because together they form a single boundary.Conformance
Identifier schemeThe form a profile requires for identifying a class of asset: a Package URL for a library and for a product, a tag URI for a deployment, and a named registry for algorithms and protocols. The profile declares the scheme, rather than leaving it to be agreed separately for each document, so that two disclosures about the same thing can be matched. Requirement C14 checks that the declaration and the rules agree.Conformance
Stated absenceA structural rule is satisfied in one of two ways. Either the required thing is present, or the document states explicitly that it is absent. Saying nothing satisfies neither. A subject with no administrative surface can state that it has none, and it then conforms. A subject that simply leaves out its management interface does not conform. Stated absence applies the disclosure model to the structure of a document (which interfaces it declares) rather than to the value of one attribute.Profile
Cryptographic purposeThe job that cryptography does at a relationship: establishing a key, encrypting, proving identity, protecting a message, signing for the long term, protecting keys, or deriving keys. A purpose is not the same as an operation. For example, sign/verify is one operation. It covers both a certificate signature and a firmware signature, and those two migrate a decade apart. A migration timetable attaches only to a purpose, so capability is stated per purpose. An entry is admitted to the vocabulary only if it passes a four-part test. The entry is declarable at the boundary, it can be migrated independently, it is actionable, and it is not an ingredient of another purpose. Purposes do not divide algorithms into separate sets. AES-GCM, for example, serves encryption and data integrity at once.PQC Migration
Group ruleA rule that constrains a repeated group of entries. Each entry is identified by a key from a controlled vocabulary, so an interface gives one answer for each key. The rules inside the group are evaluated within a single entry. A conditional guard (the condition that decides whether a rule applies) therefore refers to that entry and not to the interface as a whole. keyCoverage says whether an entry is required for every value in the vocabulary or only for the values the scope declares. This setting is what distinguishes a profile that addresses a problem one depth at a time from one that drops the part it defers.Conformance
OrientationWhether a profile reports present state (inventory), forward-looking capability (migration), or both. The orientation is declared in the scope, and requirement C12 checks it against the rules. This ensures that a capability attribute is never supplied in place of the present-state attribute it describes a capability for.Conformance
Forward-looking attributeAn attribute that describes what an interface could do or will do, not what it does now. Any name with a Supported suffix is one. So are capabilityStatus, blockedBy and roadmapRef, which describe a future state that has no present-state counterpart.PQC Migration
Subject typeWhat one document describes. A profile declares the set it accepts in scope.subjectTypes, and each document declares its own (baseline P5). The interface disclosure baseline accepts product and deployment. A derived profile narrows the set: PQC migration and procurement accept product, and deployment disclosure accepts deployment. The vocabulary also holds service, component, system and estate-subset, which no example profile uses yet.Profile
DeploymentOne installation of one or more products, run by an operator, such as the illustrative sso-prod deployment of Keycloak. A deployment has no Package URL. It is identified by a tag URI, and two records of the same deployment use the same one.Model
Tag URI (RFC 4151)An identifier of the form tag:<domain>,<year>:<name>, such as tag:example.org,2026:deployment/sso-prod. Anyone who controls a domain name can mint one without registering anything. Baseline P3 requires it as the subject identifier of a deployment.Profile
Accepted lifecycle stagesThe subset of lifecycle stages a profile will evaluate. A document that reports a stage outside the set fails the rule that constrains the stage. This mirrors the way a document is refused when its carrier format version (the version of the format it is written in) is outside appliesTo. A derived profile may narrow the set and may not widen it. The entry profile accepts all four stages. The disclosure baseline does not accept intended.Conformance
Lifecycle stage per documentThe rule that one document has one stage (baseline P6). The document carries it in CycloneDX metadata.lifecycles: build for implemented, operations for configured, discovery for observed, and design for intended. A per-interface lifecycleStage, where present, must agree.Profile
Literal valueA fixed word accepted in place of an algorithm for keyExchange, encryption or authentication. A literal is a value, not a disclosure marker, and it stands alone. The three literals are none, deployment-defined and peer-defined.Profile
noneA literal stating that the interface applies no algorithm for this job, such as token encryption that is off. Accepted at any stage. It differs from unknown and withheld, which report the producer's knowledge or willingness rather than the product.Profile
deployment-definedA literal stating that the product does not fix the value and the operator chooses it, such as an operator-supplied server certificate. Accepted only at implemented. Where it appears, baseline R5 requires a pointer to configuration guidance.Profile
peer-definedA literal stating that the other endpoint decides the value, or that the product negotiates it with that endpoint, such as the group on a connection the product opens to a database. Accepted only at implemented.Profile
Reference ruleA rule, with the letter R, that requires a document to point to an artefact it does not carry, such as its companion SBOM or the place where its VEX statements are published. Conformance checks the pointer, never the target. The baseline's reference rules are R1 to R6.Profile
Context kindA kind of artefact a reference rule can require, such as sbom, vulnerability-statements, advisories or configuration-guidance. A profile defines each kind in contextKinds, with the CycloneDX reference types that can carry it and its form: document (a fixed artefact, bound by a hash), endpoint (a feed or API, which names its access protocol) or document-or-endpoint. Requirement C18 checks the definitions.Profile
Context pointerThe pointer a reference rule requires. In CycloneDX it is an external reference with the property pkic:profile:context, which names the context kind. An endpoint adds pkic:profile:accessProtocol, such as osv-api or web-page. Direction follows time: a record points to artefacts that exist when it is written, and to places where later statements will appear. A judgement made afterwards points to the record by digest, never the reverse.Profile
Decision optionsThe actions a profile's consumer chooses between, stated explicitly. Listing the options is what makes the action-choice test checkable. A decision that can be answered in only one way is not a real decision. A profile written for such a decision has no principled point at which to stop adding rules.Method
Product-level rule
also: structural rule
A rule constraining the set of interfaces a product declares, such as a required count or a required kind. A product-level rule can detect an omitted interface, which per-attribute rules cannot do.Profile
Per-interface ruleA rule applied uniformly to every declared interface.Profile
Conformance level
also: obligation level
MUST, SHOULD or MAY, following BCP 14 (RFC 2119 and RFC 8174). Only MUST rules determine the verdict, which is the result of an evaluation.Conformance
WithholdableA property of a rule. If a rule is withholdable, the producer can satisfy it with a withheld marker, which states that the producer holds the value and declines to publish it. If the rule is not withholdable, a withheld marker fails the rule.Profile
AudienceWho may hold a document, which in turn determines what the document may contain. A profile expresses audience in only one way: through its choice of which rules are withholdable. Suppose a profile permits no withholding on the contested rules. Only a restricted variant of a document (one released to a limited audience) can then conform to it. Such a profile is therefore a derived profile of the public one. A rules file cannot yet declare an audience. This is open question Q54.Confidentiality
VerdictThe result of evaluating one document revision against one profile version: conforms, does not conform, or refused.Conformance
RefusedAn outcome that is distinct from non-conformance. A document is refused when its carrier format version is below the minimum the profile declares. No assessment is then performed. A refusal says nothing about the document's content.Conformance
Well-formed profileA profile satisfying the methodology's own requirements C1 to C18. A verdict issued against a profile that is not well-formed establishes nothing.Conformance
Conformance claimA statement by a named party that one revision of a document was checked against one version of a profile, and what the verdict was. The claim cites the profile version, the version of the file format and the content revision.Conformance
Self-declared claimA claim in which the evaluating party is the producer of the document. Self-declared claims are permitted and are labelled as self-declared.Conformance
Attested claimA claim in which the evaluating party is other than the producer.Conformance
Dual useThe property that one profile is both a specification for the producer and a checklist for the consumer.Profile
Independent evaluationEvaluating one CBOM against several profiles, each producing its own verdict. The profiles need not know of each other and are not combined.Profile
ExtensionA profile declaring that it inherits every rule of another and states only additions and tightenings.Profile
Base and derived profileThe profile named in extends, and the one naming it. A derived profile inherits every rule and may add to or tighten them. For a public and a restricted variant, the public profile is the base.Profile
Profile tagA short handle such as interface-disclosure. A rule citation has two parts, and the tag is the part that says which profile the rule belongs to. The tag is the only identifier that has to be unique along an inheritance chain (a chain of profiles that extend one another).Objects
Rule identifierAn identifier that is local to the profile declaring the rule. It is cited as tag#id. The letter says which kind of rule it is: P per document, I per interface, G per group entry, and R for a reference rule. A tightened rule keeps the identifier of the profile that introduced it.Objects
Key coverageA group rule's keyCoverage: whether an entry is required for every key in its vocabulary (all-purposes) or only for the keys the profile's scope declares (in-scope). Distinct from the product attribute coverage, which says how complete a document's interface list is. Both were called coverage until decision 0021.Profile
Claim verificationRe-running the evaluation a claim records, against the document its digest names, to establish that the claim still holds. It does not establish that the disclosed values are true.Conformance
Monotonic extensionThe rule that a derived profile may add and tighten but never relax. It guarantees that conforming to the derived profile means conforming to the base.Profile
Profile familyA set of profiles related by extension. In a family ordered by depth, each deeper profile asks more about the same consumer decision. The shallowest member is the entry profile. A document that conforms at one depth also conforms at every shallower depth. Monotonic extension is what guarantees this. The example family has Interface Enumeration v0.3 and the Interface Disclosure Baseline v0.9 as its two depths, and three branches from the baseline: PQC Migration v0.8 (with PQC Migration Extended v0.1 one depth deeper), Procurement v0.1 and Deployment Disclosure v0.2.Maturity
DepthHow much a profile asks about the same subject matter and the same decision. A deeper profile adds rules but does not change what the family is about. Depth differs from coverage, which brings more subject matter into scope at the same depth. It also differs from a branch, which changes the decision the profile serves.Maturity
Entry profileThe shallowest profile in a family: the least a producer can disclose and still be checked against something. It asks for more than untargeted scanner output provides and for less than full disclosure. A producer that starts disclosing today therefore has a verdict to show for its work.Maturity
BranchA derived profile serving a different consumer decision. A branch is recognised by a different objective or a different scope.orientation. Like any extension, a branch is monotonic: it only adds and tightens rules. It is not a greater depth, however. For example, the PQC migration profile is a branch of the interface family, not a deeper level within it.Maturity
DeferralSomething a profile does not require at this depth, as distinct from something excluded on principle at every depth. A rules file lists both kinds in one exclusions list and gives no mechanical way to tell them apart. This is recorded as open question Q52.Maturity
TighteningRaising a conformance level, narrowing a constraint, or removing withholdability. Permitted in an extension.Profile
RelaxingLowering a level, widening a constraint, removing a rule, or adding withholdability. Not permitted in an extension. A profile that needs to relax a rule is written as an independent profile.Profile

Disclosure states

Four outcomes are possible for any attribute. The 2026 SBOM minimum elements guidance requires the last three to be distinguished from one another. Neither carrier format can express that distinction natively.

StateMeaningEffect on a MUST rule
valueA value was supplied and checked against the constraint.Passes if valid.
withheldThe producer holds the information and declines to publish it.Passes only where the rule is withholdable.
unknownThe producer does not have the information.Fails, reported separately from an absent attribute.
undeclaredNeither a value nor a marker was supplied.Fails.

Attributes

Attributes shared across profiles, followed by those introduced by the PQC migration profile and by the drafted use cases.

AttributeDefinitionIntroduced in
interfaceIdThe producer's own label for an interface. Profiles do not constrain its value, and consumers should not treat it as a stable cross-organization identifier.Profile
interfaceTypeThe role of an interface, from a controlled vocabulary. The controlled vocabulary is what allows a rule such as "declare a management interface" to be evaluated.Profile
protocolThe protocol securing the interface, such as TLS, SSH or IPsec, or the application-layer protocol, such as OIDC or SAML. Not required of a storage interface.Profile
protocolVersion / protocolVersionsSupportedThe version in use, and the set of versions the interface can negotiate.Profile / PQC Migration
keyExchange / keyExchangeSupportedThe key-agreement or key-encapsulation algorithm in use, and the set the interface is able to use. On a token interface, how a content encryption key reaches the recipient. Accepts the literals none, deployment-defined and peer-defined.Profile / PQC Migration
encryptionThe bulk or AEAD algorithm protecting data on the interface. Accepts the same literals.Profile
authentication / authenticationSupportedThe signature algorithm that proves the sender: a certificate signature for TLS, a host key for SSH, a token signature for OIDC or SAML. Accepts the same literals.Profile / PQC Migration
endpointRolesThe roles of the parties to the interface, such as client and server, or issuer and relying party.Profile
lifecycleStageThe stage the facts come from. A document has one stage, and a per-interface value must agree with it. See the lifecycle table below.Lifecycle Data
implementationPurlThe Package URL of the library implementing the interface's cryptography. This is the value that is matched against vulnerability feeds. It is an implementation fact, so a deployment interface inherits it through correspondsTo.Profile
keyWrapping / keyWrappingSupportedOn a storage interface: the algorithm that protects the data keys at rest, or none, and the set the product can use.Profile / PQC Migration
defaultStateWhether a product interface is active in the product's default configuration: enabled or disabled. SHOULD, at implemented only. Keycloak's plaintext HTTP listener is disabled by default.Profile
coverageA document-level statement of how complete the declared interface set is. Required by baseline P4.Profile
correspondsToOn a deployment interface: the interface in a cited record that it realises, as a BOM-Link urn:cdx:<serial>/<version>#<bom-ref>, or the literal no-product-document. Carried as the property pkic:profile:correspondsTo.Model
peerInterfaceOn a deployment interface: the interface at the far end of the connection, as a BOM-Link into a cited record, or the literal peer-not-recorded. A list, because a server interface usually has several clients. Either end may state it. Carried as the property pkic:profile:peerInterface (decision 0026).Model
observationMethod / observedAtOn an observed interface: how each value was obtained (for example an active probe, a passive sensor or an endpoint query), and the time or ISO 8601 interval of the observation.Lifecycle Data
capabilityStatusThe class of commitment the producer makes to a capability the interface does not yet have, expressed without a date.PQC Migration
blockedByWhat must change before a capability becomes available. The value therefore also shows who is able to make that change.PQC Migration
roadmapRefA reference to a roadmap entry carrying a target release and, where offered, a date. Kept outside the interface so that a slipping date does not force a CBOM revision.PQC Migration
enablementMethodWhat a consumer must do to turn a capability on.PQC Migration
minimumProductVersionThe product version at which a capability becomes available. Required where enablement is by software update.PQC Migration
providerLocationWhere key operations execute. This determines whether a new algorithm can be adopted through software at all.PQC Migration
coexistenceWhether the interface can serve classical and post-quantum peers at the same time. Determines whether migration requires a coordinated cutover.PQC Migration
negotiationControlWhether the interface can be configured to require post-quantum key exchange and refuse a classical fallback.PQC Migration
integrationConstraintsKnown effects of enabling a capability, such as handshake size limits or intermediary incompatibilities. Each entry has a category and a short description, so that entries can be counted across suppliers. The categories are listed under controlled vocabularies.PQC Migration
updateAuthority / updateAuthoritySupportedThe parties from which the product's update mechanism accepts new software or firmware now, and the set it can be configured to accept. In a product record, updateAuthority is the default as shipped. In a deployment record, it is the value as configured. Not required when updateMechanism is none. It may be withheld.IoT Device Estate (draft)
resourceBoundThe hard limits that decide what a device could ever support: usable flash and RAM, and the maximum frame or message size its link imposes, in bytes. It records the limit, not a conclusion. The consumer decides whether the limit rules out a new algorithm for good.IoT Device Estate (draft)
verifierPopulation / verifierPopulationRefOn an interface that signs: who must be able to verify the signature. The optional pointer names the rules that set what those verifiers must support, such as a scheme rulebook. The weakest verifier sets the upper limit on what the signer can use. The relationship stays between two parties. It may be withheld.Model (draft)
trustDomain / trustAnchorRefOn an interface: the kind of trust anchor under which it accepts the other party's credentials, and optionally the anchor itself. It is an attribute of the interface, not the endpoint, because one server can accept different anchors on different interfaces. trustAnchorRef may be withheld.Model (draft)

Controlled vocabularies

AttributePermitted values
interfaceTypemanagement · service · interconnect · peer · storage
lifecycleStageintended · implemented · configured · observed
a profile accepts a subset of these; the disclosure baseline does not accept intended; see profile scope
subjectTypeproduct · deployment · service · component · system · estate-subset
the example profiles use product and deployment
defaultStateenabled · disabled
literal values for keyExchange, encryption, authenticationnone · deployment-defined · peer-defined
the last two only at implemented
management absence (baseline P2)no-configuration-surface · configured-out-of-band · not-applicable-to-subject · not-reached
not-reached only at observed with coverage partial
context formdocument · endpoint · document-or-endpoint
access protocolweb-page · csaf-provider · osv-api · ghsa-api · vex-document · other
context absencenot-published · not-applicable-to-subject
orientationinventory · migration · both
cryptographicPurposekey-establishment · encryption · entity-authentication · data-integrity · non-repudiation · key-protection · key-derivation
a sector profile might add values to this list; whether it is allowed to do so mirrors question Q35 and is unresolved
coverageall-external · all · partial
capabilityStatusavailable · committed · planned · under-evaluation · not-planned
blockedByprovider · product · hardware · standard · certification
enablementMethodalready-enabled · configuration · software-update · hardware-change · licence · not-available
providerLocationsoftware · hsm · tee · unspecified
coexistencesimultaneous · exclusive · unknown
updateAuthorityoperator · vendor · platform · installer
a set: more than one value may apply
verifierPopulationcounterparty · scheme-members · public
trustDomainpublic · private · scheme-administered
integrationConstraints categoryhandshake-size · interoperability · performance · certification · hardware · other

Protocol names

The value of protocol comes from this list, so that the same protocol has the same name in every CBOM. The version is written as the protocol's own specification writes it, for example 1.3 for TLS, not TLSv1.3 or 0x0304. A protocol that is not on the list is recorded as other, with a pointer to its specification, and can be proposed for the list. No rule checks the list yet. The Keycloak examples still use two labels that are not on it, for the cluster transport and the admin API, and will be aligned.

NameSpecification
TLSIETF RFC 8446 (version 1.3) and RFC 5246 (version 1.2)
DTLSIETF RFC 9147 (version 1.3)
QUICIETF RFC 9000
SSHIETF RFC 4251 to RFC 4254 (version 2.0)
IPsecIETF RFC 4301
IKEv2IETF RFC 7296
MACsecIEEE 802.1AE
OIDCOpenID Connect Core 1.0
SAMLOASIS SAML 2.0
OAuth 2.0IETF RFC 6749
HTTPIETF RFC 9110
LDAPIETF RFC 4511
SMTPIETF RFC 5321
PostgreSQLPostgreSQL frontend/backend protocol, version 3

Keys are identified in a similar fixed way. An asymmetric key is identified by the fingerprint of its public key. A symmetric key has no public part, so it is identified by its role and the place where it is stored.

Lifecycle and provenance

TermDefinitionDeveloped in
Capture phaseWhat lifecycleStage records: whether the facts were intended, implemented, configured or observed. One document has one stage (baseline P6), so every interface in a document has the same capture phase. A record at another stage is a separate document, joined to the first. It is not a revision state.Lifecycle Data
Revision stateThe states a document passes through: created, signed, published and superseded. A revision state is a property of a whole document, and it is what governance controls. Validation is not a revision state. A published revision can be validated many times, and validation does not change it.Governance
intendedCryptography specified at design time. Says nothing about what was built. Accepted by the entry profile and not by the disclosure baseline. A vendor's intention is a capability status, an operator's intention is a requirement in a policy or tender, and a design document is context (baseline R6).Lifecycle Data
implementedCryptography present in the product as built. A present-state value means the product's default as shipped.Lifecycle Data
configuredCryptography the deployed configuration permits. A present-state value means the set the deployment permits.Lifecycle Data
observedCryptography seen on the wire or in the running system. A present-state value means the set seen in the observation window. It is a snapshot, and a later configuration change makes it out of date.Lifecycle Data
Product record
formerly: product CBOM
A CBOM describing a product as built. The vendor writes it at implemented, with subject type product and a Package URL.Model
Deployment record
formerly: service CBOM
A CBOM describing one deployment. The operator writes it at configured or observed, with subject type deployment and a tag URI. It cites the records it builds on.Model
Cited documentA record that a deployment record builds on, such as the product record or, for an observed record, the configured record. The deployment record cites it with an external reference of type bom, the property pkic:profile:context = cited-document, a BOM-Link and a SHA-256 hash. When the evaluator is given the cited document, it checks the serial number, version and hash.Model
JoinReading two records together along correspondsTo, without merging them. Only implementation facts, such as implementationPurl, follow a join. Present-state facts never do. If the evaluator is not given a cited record, it reports an inherited value as unresolved, not as failed. A peerInterface pointer joins the two ends of one connection in the same way, for an evaluation to read together.Model
Readiness gapThe difference between what a product is capable of and what a deployment permits and negotiates. A policy computes it from the join of the product record and the deployment records, one interface and purpose at a time. No record stores it.Model
Readiness gap classesThe classes the example readiness-gap policy assigns: target-met, enabled-not-negotiated (the deployment permits the target and sessions still negotiate a classical value), capable-not-enabled (the operator acts), capable (no deployment record), not-capable (the supplier acts), unprotected (no cryptography at all), not-deployed, not-applicable and unknown.Model
ProvenanceThe record of how a CBOM was produced: generating tool and version, inputs, lifecycle stage, and any mechanical upgrade applied.Governance
SBOM Generation Context (CISA)The lifecycle phase and data available when an SBOM was generated. This is the equivalent concept in the 2026 minimum elements guidance. It is less fine-grained than the capture phase.Lifecycle Data

Formats, mapping and versions

TermDefinitionDeveloped in
Carrier formatThe format in which a CBOM is serialized, such as CycloneDX or SPDX. Distinct from the profile expressed in it.Versioning
MappingThe statement of where each profile attribute lives in a given format, including a canonical location where the format permits several.Formats
Format adapterThe format-specific part of a validator, which extracts abstract attributes from a concrete document. It is the only part of a validator that changes from one format to another.Formats
Acceptance range
also: appliesTo
The carrier format versions a profile accepts, expressed as a minimum version and a tested version. Every example profile declares CycloneDX min 1.6, tested 2.0.Versioning
Version bandsThe four bands into which a carrier format version can fall, measured against the acceptance range: refused below the minimum, legacy between the minimum and the tested version, target at the tested version, and newer above it. For the example profiles, CycloneDX 2.0 is the target, 1.6 and 1.7 are legacy, and anything below 1.6 is refused.Versioning
Pinned carrier schemaThe CycloneDX 2.0 schema the example profiles are tested against until Ecma ratifies the release: branch 2.0-dev of CycloneDX/specification at commit 76f185c (23 October 2026), held in tests/schemas/cyclonedx-2.0/.Versioning
BOM-Link (CycloneDX)A URN that names a CycloneDX document by serial number and version (urn:cdx:<serial>/<version>), and optionally one element in it (#<bom-ref>). Cross-document references in the methodology use it, together with a SHA-256 hash.Model
Encoding normalizationAgreement on where a value is written, where a format permits more than one valid location.Formats
Naming normalizationAgreement on how a value is expressed, so that equivalent values match. Addressed by the CycloneDX Cryptography Registry for algorithms.Formats
Content revisionA successive version of a CBOM for the same subject. The sequence of revisions is the audit trail that progress tracking relies on.Versioning

Inventory and exchange

TermDefinitionDeveloped in
Cryptographic inventoryAn organization-wide, continuously maintained record of cryptography in use, aggregated from CBOMs and other sources.Inventory
Extracted CBOM
also: output CBOM
A scoped snapshot drawn from an inventory for a specific consumer, filtered and redacted as required.Inventory
Disclosure variant
public variant / restricted variant
One of two or more documents describing the same subject at the same content revision, differing only in which values have been replaced by a withheld marker. Each variant is prepared for the audience that may hold it. A variant is not a version. Versioning tracks three axes: carrier format, profile and content revision. Audience is not one of them.Confidentiality
RedactionReplacing a value with a withheld marker on release. Redaction by deletion is a different act, and a worse one. A deleted value reads as undeclared and fails the rule. The reader then cannot tell a deliberate policy decision from a gap in the producer's tooling.Confidentiality
Central / distributed / federated inventoryArrangements for where inventory data is held. In a federated arrangement, a profile defines the subset of data that is published upward. This makes inventories that are held separately comparable with one another.Inventory
SupersedenceThe replacement of a CBOM revision by a newer one for the same subject, with the earlier revision retained for audit.Governance

Evaluation and policy

TermDefinitionDeveloped in
FactSomething a producer observes or declares, recorded in the CBOM.Policy Evaluation
Evaluation
also: derived judgement
A conclusion drawn from facts against criteria that change over time. An external policy produces it at the time the question is asked, and it is dated. It is never stored as a CBOM attribute.Policy Evaluation
PolicyVersioned data together with a named evaluation method. The example policies are the readiness gap and an algorithm transition based on the NIST IR 8547 initial public draft. evaluate_policy.py applies a policy to one or more CBOMs at a stated date.Policy Evaluation
Policy resultThe output of evaluating a policy. It names the policy id, version and digest, the evaluation date, and every CBOM it read by SHA-256 digest, and it states what it does not assert. A result points to the records it read. A record never points to a result.Policy Evaluation
Post-quantum postureAn evaluation, not an attribute. Whether an interface's algorithms are considered quantum-safe, assessed against current guidance.Policy Evaluation
Cryptographic maturityAn evaluation, not an attribute, for the same reason as post-quantum posture. The PQC Maturity Model is an instance of this kind of external policy.Policy Evaluation
AdvisoryA third party's statement that a named component, in a stated version range, carries a named weakness. An advisory is written by a maintainer, a numbering authority or a research team. It is not written by the subject's producer, and it is not part of a CBOM.Vulnerabilities
VEX statementA producer's judgement that its product is or is not affected by a named advisory. Where the product is not affected, the statement carries a justification. The judgement combines the CBOM's facts with knowledge held elsewhere, and it is revised whenever either of them changes. For that reason it is kept as a separate artifact from the document it is about.Vulnerabilities
Implementation defectA weakness in code that performs cryptography. It has a version range, a patch and an identifier in a vulnerability feed. It is found by matching the implementing library (I9) against that feed. The CBOM contributes by showing which interfaces use that library.Vulnerabilities
Algorithm or parameter weaknessA weakness in a choice rather than in code: a deprecated algorithm, an inadequate key length, or a classical key exchange used against a quantum adversary. Such a weakness usually has no identifier and never has a patch. The remedy is to use a different algorithm or parameter. It is found by a policy evaluation of the disclosed facts, and the CBOM is the only evidence for that evaluation.Vulnerabilities
Harvest now, decrypt laterCapturing encrypted traffic or stored ciphertext now, to decrypt once a cryptographically relevant quantum computer exists. The exposure depends on how long the data must stay confidential, so it cannot be seen by examining the cryptography alone.Data Exposure
Confidentiality lifetime
proposed
How long data carried over an interface must remain confidential after transmission. It is recorded in bands (fixed ranges of time) so that it is comparable between organizations. It is an attribute of a deployment, not of a product. It describes the traffic and not the document. The confidentiality of the CBOM itself is a separate subject, covered in Confidentiality.Data Exposure
Urgency rankingAn evaluation, not an attribute. An ordering of interfaces by exposure to the harvest-now-decrypt-later threat. It is computed from disclosed facts and from an external estimate of when a cryptographically relevant quantum computer will exist.Data Exposure

Related artifacts

TermDefinition
CBOMCryptography Bill of Materials. A structured description of the cryptography a subject contains or uses, at a point in time.
SBOMSoftware Bill of Materials. It is read alongside a CBOM so that cryptography can be linked to the components that implement it.
HBOMHardware Bill of Materials. It is relevant where cryptography is bound to hardware, so that changing the cryptography means replacing the hardware.
VEX (external)Vulnerability Exploitability eXchange. The statement that a product is or is not affected by a known vulnerability, expressed as a CSAF VEX document, an OpenVEX document, or a vulnerabilities array in a CycloneDX BOM. The four statuses are affected, not affected, fixed and under investigation, and not affected carries a justification.
CSAF (OASIS)Common Security Advisory Framework 2.0. The machine-readable advisory format, which includes a VEX profile.
CVE (external)An identifier for one vulnerability in a component. CVEs are issued for implementation defects. They are not issued when a product uses an algorithm that guidance has deprecated.
CWE (external)A classification of weakness types. CWE-327, CWE-326 and CWE-328 are the cryptographic entries. A CWE names a class of weakness rather than an instance, so it cannot serve as the identifier of a particular finding. See Q59.
purl (external)Package URL. The identifier scheme used to name implementing libraries and products. In CycloneDX 2.0 it is carried in identifiers[], asserted by a named party.
OSV (external)Open Source Vulnerabilities. An advisory database with an API that a consumer can query by Package URL. The Keycloak product record names it as an advisory endpoint with access protocol osv-api.
BCP 14 (IETF)RFC 2119 with RFC 8174, defining the requirement keywords MUST, SHOULD and MAY.
Cryptography Registry (CycloneDX)The registry of stable algorithm identifiers introduced in CycloneDX 1.7. It addresses naming normalization.

Terms considered and not used

Each of these was considered and set aside. Recording the reasoning prevents the discussion recurring.

TermWhy it is not used
Interface, as the general termThe word is too narrow for the general case. It suggests two parties communicating at the same time over a link. That excludes relationships whose parties are separated in time, and relationships that transfer no data. The word is kept for the subset of relationships that genuinely are interfaces.
Cryptographic context, for a relationshipCollides with established usage, where a context is the runtime state held by a cipher implementation. The word "context" alone is used, in a different sense, for the artefacts a context pointer names.
Service CBOMReplaced by deployment record, which matches the subject type the record declares. In CycloneDX 2.0, "service" is a component type, used for application-layer interfaces, so the old name could be misread.
intended, as a stage of the disclosure baselineRemoved in baseline v0.9. A design intention answers nothing about deployed interfaces. It is recorded as a capability status, a requirement, or a design document the record points to. See decision 0025.
A single subjectType per profileReplaced by the set subjectTypes in v0.9, so that one baseline serves both products and deployments and a derived profile can narrow the set. The single form is still read, as a set of one.
pqcPostureRemoved from the profile. It encodes an evaluation, and its correct value changes when guidance changes without the product changing.
vulnerable, and any vulnerability statusNot an attribute. It encodes a judgement that combines the document's facts with an advisory held by a third party. Its correct value can therefore change while the product itself does not change. It is communicated as a VEX statement alongside the CBOM. Decision 0020.
plannedAvailabilityReplaced by capabilityStatus, blockedBy and roadmapRef. A date recorded on an interface copies one underlying change event onto every interface that inherits it.
Maturity level, for a profileIn this documentation, a maturity level is a judgement about a product. External versioned policy derives it from disclosed facts. A PQC Maturity Model level is one example. A profile defines the facts that such a judgement reads. Using the same phrase for both would give one term two meanings, and one of those meanings, the judgement, is excluded from a CBOM on principle. A level within a profile family is therefore called a depth. See Maturity.
Tier, for a depthThe word already has two meanings in this area. It means a supplier's position in a supply chain. It also names the ownership arrangement in Governance, where the working group owns a baseline profile and sector bodies own the profiles they derive from it.
*Current suffixRedundant under the naming conventions, where a bare name already denotes present state.
PKIC CBOM Profiles Working Group · draft for comment.