Repository navigation
docs(cbom): explain how to read and report nistQuantumSecurityLevel - #131
Lennonhaha wants to merge 1 commit into
Conversation
The interpretation guidance for this property was removed from the specification schema description at the code owner's request (CycloneDX/specification#1177): the spec keeps the definition and the meaning of an explicit zero, while the guide carries the guidance about how the value is consumed and produced. Covers: - absence and `0` are different statements, and absence is not `0` - in Protocol Buffers the field is `optional int32`, so the generated accessor returns 0 for an unset field: check presence first - when to emit `0` and when to omit the property Signed-off-by: 刘天赫 <research@fibemate.net>
d2fab0f to
f0948d1
Compare
|
DCO is green on Two things still stand between this and a merge, and neither is something I can do from here:
Content is unchanged: one file, +55/−0, the |
Adds the consumer/producer guidance for
nistQuantumSecurityLevelto the CBOM guide, so it does not have to live in the specification schema description (CycloneDX/specification#1177).What the section covers
0are different statements, and absence must not be read as0optional int32, so generated accessors return0for an unset field — check presence (has_nist_quantum_security_level()) before comparing the value0(assessment performed, no category met) and when to omit the property (no assessment, or unknown result)Placement
CBOM/en/0x30-Anatomy-of-a-CBOM.md, new## Security Level Propertiessection between the asset-type table and## Key Management. It coversclassicalSecurityLevelas well, since both are properties of the algorithm rather than of a deployment.Not included
No statement about which category number maps to which algorithm family — that belongs to the algorithm definitions and the NIST documents themselves.
Companion change: CycloneDX/specification#1177 (schema description narrowed to the definition and the meaning of an explicit zero).