IA-13(1)—Protection Of Cryptographic Keys
>Control Description
Cryptographic keys that protect access tokens are generated, managed, and protected from disclosure and misuse.
>Supplemental Guidance
Identity assertions and access tokens are typically digitally signed. The private keys used to sign these assertions and tokens are protected commensurate with the impact of the system and information resources that can be accessed.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of IA-13(1) (Protection Of Cryptographic Keys)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring IA-13(1)?
- •How frequently is the IA-13(1) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures IA-13(1) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce IA-13(1) requirements.
- •What automated tools, systems, or technologies are deployed to implement IA-13(1)?
- •How is IA-13(1) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce IA-13(1) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of IA-13(1)?
- •What audit logs, records, reports, or monitoring data validate IA-13(1) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of IA-13(1) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate IA-13(1) compliance?
Ask AI
Configure your API key to use AI features.