SC-12(1)—Cryptographic Key Establishment and Management | Availability
IL4 High
IL5
IL6
>Control Description
Maintain availability of information in the event of the loss of cryptographic keys by users.
>DoD Impact Level Requirements
No specific parameter values or requirements for this impact level.
>Discussion
Escrowing of encryption keys is a common practice for ensuring availability in the event of key loss. A forgotten passphrase is an example of losing a cryptographic key.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What policies govern the implementation of availability?
- •How are system and communications protection requirements defined and maintained?
- •Who is responsible for configuring and maintaining the security controls specified in SC-12(1)?
- •What is your cryptographic key management policy?
Technical Implementation:
- •How is availability technically implemented in your environment?
- •What systems, tools, or configurations enforce this protection requirement?
- •How do you ensure that availability remains effective as the system evolves?
- •What encryption mechanisms and algorithms are used to protect data?
Evidence & Documentation:
- •What documentation demonstrates the implementation of SC-12(1)?
- •Can you provide configuration evidence or system diagrams showing this protection control?
- •What logs or monitoring data verify that this control is functioning correctly?
- •Can you demonstrate that FIPS 140-2 validated cryptography is used?
Ask AI
Configure your API key to use AI features.