NIST SP 800-53 Rev. 5 SC-12 — Cryptographic Key Establishment And Management

What this control requires

Establish and manage cryptographic keys when cryptography is used within the system, in accordance with organization-defined requirements for key generation, distribution, storage, access, and destruction. This can be done using manual procedures or automated mechanisms. Key management must adhere to applicable laws, regulations, policies, and standards to ensure secure and compliant key handling. This control supports the Cryptographic Key Management System capability within the System and Communications Protection family.

In plain English

Establish and manage cryptographic keys when cryptography is used within the system, in accordance with organization-defined requirements for key generation, distribution, storage, access, and destruction. In practice, this means you can prove you policy procedures-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within System and Communications Protection, the assessor will trace your implementation back to the catalogue reference (Control SC-12) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Access. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• Storage. Document the trigger, the owner and the cadence.
• Cryptographic. Document the trigger, the owner and the cadence.
• Scope: procedures, management, cryptographic keys, organization, system, protection, generation, capability.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Cryptographic Key Establishment And Management.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• HIPAA (45 CFR Part 164) 164.530(d)(1) — Complaints to the Covered Entity
• NIST SP 800-171 Rev. 3 3.13.10 — Cryptographic Key Establishment and Management

Related controls in NIST SP 800-53 Rev. 5

• Control SC-12(2) — Symmetric Keys
• Control SC-23(3) — Unique System-Generated Session Identifiers
• Control SC-12(3) — Asymmetric Keys
• Control SC-15(4) — Explicitly Indicate Current Participants
• Control SC-18(2) — Acquisition, Development, And Use
• Control SC-28(3) — Cryptographic Keys

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SC-12

Topics: governance riskkey managementpolicy management