What evidence do auditors commonly ask for on SC-12 Cryptographic Key Establishment and Management?

SSP SC-12 statement describing key generation, distribution, storage, rotation and destruction using FIPS-validated modules; Key management system configuration and key rotation logs; Boundary protection architecture with firewall and proxy rule documentation; Cryptographic standards specifying approved algorithms and key lengths; Key management procedures including rotation and escrow; TLS configuration scan results across in scope endpoints.

What is the most common gap auditors find on SC-12?

Firewall rule base contains stale allow any entries

FedRAMP High (NIST SP 800-53 Rev 5 baseline) · SC - System and Communications Protection

`SC-12` Cryptographic Key Establishment and Management

Establish and manage cryptographic keys per FedRAMP requirements (FIPS-validated, key escrow/recovery as appropriate).

Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), SC-12. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

artefacts

held by a system

at each review

moderate

to go live

Key management / PKI

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Key management system configuration and key rotation logs · Key management / PKI
TLS configuration scan results across in scope endpoints · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

SSP SC-12 statement describing key generation, distribution, storage, rotation and destruction using FIPS-validated modules · Policy repository / GRC workspace
Boundary protection architecture with firewall and proxy rule documentation · Policy repository / GRC workspace
Cryptographic standards specifying approved algorithms and key lengths · Policy repository / GRC workspace
Key management procedures including rotation and escrow · Policy repository / GRC workspace

First move

Start with the 2 of 6 artefacts that already live in a system (Key management / PKI); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Firewall rule base contains stale allow any entries
Internal traffic between services unencrypted within trusted zones
Legacy TLS versions remain enabled on external services

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

SC-10 Network Disconnect · SC-12(1) Availability