💼 SC-12 Cryptographic Key Establishment and Management
- Contextual name: 💼 SC-12 Cryptographic Key Establishment and Management
- ID:
/frameworks/nist-sp-800-53-r5/sc/12
- Located in: 💼 SC System And Communications Protection
Description​
Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction].
Similar​
- Sections
/frameworks/aws-fsbp-v1.0.0/data-firehouse/01
/frameworks/aws-fsbp-v1.0.0/eks/03
/frameworks/aws-fsbp-v1.0.0/kms/03
- Internal
- ID:
dec-c-7db512e5
- ID:
Similar Sections (Take Policies From)​
Section | Sub Sections | Internal Rules | Policies | Flags |
---|---|---|---|---|
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DataFirehose.1] Firehose delivery streams should be encrypted at rest | ||||
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EKS.3] EKS clusters should use encrypted Kubernetes secrets | ||||
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [KMS.3] AWS KMS keys should not be deleted unintentionally |
Similar Sections (Give Policies To)​
Section | Sub Sections | Internal Rules | Policies | Flags |
---|---|---|---|---|
💼 FedRAMP High Security Controls → 💼 SC-12 Cryptographic Key Establishment and Management (L)(M)(H) | 1 | 9 | 11 | |
💼 FedRAMP Low Security Controls → 💼 SC-12 Cryptographic Key Establishment and Management (L)(M)(H) | 11 | |||
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected | 117 | |||
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected | 97 |