Domain: 0. Basic Security | Level:
MUST | Type: Preventive
Statement of Requirement:
A Node Operator MUST securely manage Keys and Key material in
accordance with the requirements in the BSSC Key Management Standard [KMS] or equivalent standards.
Provide resilience against key compromise by malicious actors
Audit Procedures
Interview appropriate staff to verify that staff generally understand
and implement the requirement, and are familiar with the most recent
evaluation report. If staff do not understand and implement the
requirements in practice, the requirement is effectively not met:
FAIL.
If the assessor determines that staff understand the requirements and
the most recent report, if within the last 12 months
the Node Operator is attested as meeting the requirements of the
current BSSC Key Management Standard [KMS] by an independent third-party
assessor recognized by the BSSC, or
the Node Operator is credibly attested as meeting the level II
requirements of the [CCSS],
the Node Operator is credibly attested as meeting an equivalent
standard,
and appropriate management reviewed the final assessment near the
time it was completed,
and any material exceptions, non-conformities, or compensating
controls are identified,
the requirement is met: PASS
To assess whether an alternative standard met is equivalent, inspect
the materials and verify that the presented materials establish
equivalence to the BSSC Key Management Standards in the following
areas:
Key governance & ownership
Key generation & entropy
Key derivation
Key storage & protection
Key distribution
Key usage controls
Key rotation/retirement
Key destruction
Separation of duties
Audit logging/auditability
Backup & recovery
Custody architecture
Key Evidence
Attestation of conformance to BSSC Key Management Standard [KMS] or [CCSS]
A key management policy explicitly aligned with BSSC KMS or
equivalent
Success Criteria
Comprehensive key management policy exists, aligned with BSSC KMS,
and is demonstrably followed
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No Key Management policy, or staff do not understand and implement
the policy in practice
Key Management policy does not align with KMS
Critical keys for signing or withdrawal are stored in plaintext
The key inventory is outdated or does not exist
Key access not logged or monitored
No incident response plan for key compromise
Common Failure Patterns
No key inventory, with keys scattered across systems and no
consolidated register
Plaintext keys in config files, environmental variables, or CI/CD
pipelines
Over-permissioned access (e.g. all engineers can reach production
signing keys)
Key rotation policy is not followed
Backup keys are stored insecurely (unencrypted USB, shared cloud
storage)