Skip to content
Zeta-Reticuli AIZeta-Reticuli AIZeta-Reticuli AI

SC-12 Cryptographic Key Establishment and Management

Control statement

Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignment: requirements].

Guidance

Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and specify appropriate options, parameters, and levels. Organizations manage trust stores to ensure that only approved trust anchors are part of such trust stores. This includes certificates with visibility external to organizational systems and certificates related to the internal operations of systems. NIST CMVP and NIST CAVP provide additional information on validated cryptographic modules and algorithms that can be used in cryptographic key management and establishment.

Implementation

OpenBao (canary)

A key management service is available: every OpenBao server pod is initialized and unsealed. Partial: canary only; the seal mechanism, key hierarchy and rotation are not assessed here, and nothing is FIPS 140-validated.

Status: partial.

Evidence:

sops/age YubiKey root secrets store

Private keys are generated on and never leave the YubiKeys; two recipients, a documented revoke procedure (remove recipient, re-key, rotate). Partial: no scheduled rotation, touch policy never, and the store is not FIPS-validated.

Status: partial.

Evidence:

All controls. Source: OSCAL component definition reti-platform and NIST SP 800-53 Rev 5 (public domain).