CRY-08: Public Key Infrastructure (PKI)
Mechanisms exist to securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider.
Control Question: Does the organization securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider?
General (26)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC6.1 CC6.1-POF10 CC6.1-POF11 |
| CSA CCM 4 | CEK-02 CEK-08 LOG-10 LOG-11 |
| CSA IoT SCF 2 | CLS-01 IAM-10 IAM-11 IAM-12 IAM-13 IAM-14 IAM-15 IAM-22 IOT-09 SDV-01 |
| GovRAMP Low | SC-12 |
| GovRAMP Low+ | SC-12 SC-17 |
| GovRAMP Moderate | SC-12 SC-17 |
| GovRAMP High | SC-12 SC-17 |
| IEC 62443-4-2 2019 | CR 1.8 (5.10.1) CR 1.9 (5.11.1) |
| MITRE ATT&CK 10 | T1072, T1606 |
| NIST 800-53 R4 | SC-12 SC-12(4) SC-12(5) SC-17 |
| NIST 800-53 R4 (low) | SC-12 |
| NIST 800-53 R4 (moderate) | SC-12 SC-17 |
| NIST 800-53 R4 (high) | SC-12 SC-17 |
| NIST 800-53 R5 (source) | SC-12 SC-17 |
| NIST 800-53B R5 (low) (source) | SC-12 |
| NIST 800-53B R5 (moderate) (source) | SC-12 SC-17 |
| NIST 800-53B R5 (high) (source) | SC-12 SC-17 |
| NIST 800-82 R3 LOW OT Overlay | SC-12 |
| NIST 800-82 R3 MODERATE OT Overlay | SC-12 SC-17 |
| NIST 800-82 R3 HIGH OT Overlay | SC-12 SC-17 |
| NIST 800-171 R2 (source) | 3.13.10 |
| NIST 800-171A (source) | 3.13.10[a] 3.13.10[b] |
| NIST 800-171 R3 (source) | 03.13.10 |
| NIST 800-207 | NIST Tenet 2 |
| SCF CORE ESP Level 2 Critical Infrastructure | CRY-08 |
| SCF CORE ESP Level 3 Advanced Threats | CRY-08 |
US (23)
| Framework | Mapping Values |
|---|---|
| US CERT RMM 1.2 | KIM:SG4.SP1 |
| US CJIS Security Policy 5.9.3 (source) | 5.10.1.2.3 |
| US CMMC 2.0 Level 2 (source) | SC.L2-3.13.10 |
| US CMMC 2.0 Level 3 (source) | SC.L2-3.13.10 |
| US CMS MARS-E 2.0 | SC-12 SC-17 |
| US DoD Zero Trust Execution Roadmap | 1.9.1 2.1.2 2.3.6 |
| US DHS ZTCF | DPR-01 |
| US FDA 21 CFR Part 11 | 11.2 11.2(a) 11.100 |
| US FedRAMP R4 | SC-12 SC-17 |
| US FedRAMP R4 (low) | SC-12 |
| US FedRAMP R4 (moderate) | SC-12 SC-17 |
| US FedRAMP R4 (high) | SC-12 SC-17 |
| US FedRAMP R4 (LI-SaaS) | SC-12 |
| US FedRAMP R5 (source) | SC-12 SC-17 |
| US FedRAMP R5 (low) (source) | SC-12 |
| US FedRAMP R5 (moderate) (source) | SC-12 SC-17 |
| US FedRAMP R5 (high) (source) | SC-12 SC-17 |
| US FedRAMP R5 (LI-SaaS) (source) | SC-12 |
| US HIPAA HICP Large Practice | 1.L.B |
| US IRS 1075 | SC-12 SC-17 |
| US NISPOM 2020 | 8-303 |
| US - TX DIR Control Standards 2.0 | SC-12 |
| US - TX TX-RAMP Level 2 | SC-12 SC-17 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Israel CDMO 1.0 | 8.2 8.9 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2024 | ISM-0485 ISM-1449 |
| APAC New Zealand NZISM 3.6 | 17.1.51.C.01 17.1.51.C.02 17.1.51.C.03 23.3.21.C.01 23.3.22.C.01 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 | 03.13.10 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider.
Level 1 — Performed Informally
Cryptographic Protections (CRY) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Data classification and handling criteria govern requirements to encrypt sensitive/regulated data during transmission and in storage.
- Network communications containing sensitive/regulated data are protected using a cryptographic mechanism to prevent unauthorized disclosure of information while in transit (e.g., SSH, TLS, VPN, etc.).
- Wireless access is protected via secure authentication and encryption.
Level 2 — Planned & Tracked
Cryptographic Protections (CRY) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Cryptographic management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for cryptographic management.
- Data classification and handling criteria govern requirements to encrypt sensitive/regulated data during transmission and in storage.
- Decentralized technologies implement cryptographic mechanisms on endpoints to control how sensitive/regulated data is encrypted during transmission and in storage.
- Systems, applications and services that store, process or transmit sensitive/regulated data use cryptographic mechanisms to prevent unauthorized disclosure of information as an alternate to physical safeguards.
- The IT department implements Public Key Infrastructure (PKI) key management controls to protect the confidentiality, integrity and availability of keys.
- The IT department implements and maintains an internal PKI infrastructure or obtains PKI services from a reputable PKI service provider.
- The PKI infrastructure enables the secure distribution of symmetric and asymmetric cryptographic keys using industry recognized key management technology and processes.
- The PKI infrastructure ensures the availability of information in the event of the loss of cryptographic keys by individual users.
- The PKI infrastructure enables the secure distribution of symmetric and asymmetric cryptographic keys using industry recognized key management technology and processes.
- The PKI management function enables the implementation of cryptographic key management controls to protect the confidentiality, integrity and availability of keys.
Level 3 — Well Defined
Cryptographic Protections (CRY) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Implements Public Key Infrastructure (PKI) key management controls to protect the confidentiality, integrity and availability of keys. o Implements and maintains an internal PKI infrastructure or obtains PKI services from a reputable PKI service provider.
- The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns, analyzes the organization's business strategy to determine prioritized and authoritative guidance for cryptographic protections.
- The CISO, or similar function, develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures for cryptographic protections.
- A Governance, Risk & Compliance (GRC) function, or similar function, provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data using cryptographic protections.
- A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program, including cryptographic protections.
- Data classification and handling criteria govern requirements to encrypt sensitive/regulated data during transmission and in storage.
- Centrally-managed technologies implement cryptographic mechanisms on endpoints to control how sensitive/regulated data is encrypted during transmission and in storage.
- Certificate management is centrally-managed and the use of certificates is monitored.
- Cryptographic keys are proactively managed to protect the Confidentiality, Integrity and Availability (CIA) of cryptographic capabilities.
- Systems, applications and services that store, process or transmit sensitive/regulated data use cryptographic mechanisms to prevent unauthorized disclosure of information as an alternate to physical safeguards.
- An IT infrastructure team, or similar function:
- IT/cybersecurity personnel perform an annual review of deployed cryptographic cipher suites and protocols to identify and replace weak cryptographic cipher suites and protocols.
Level 4 — Quantitatively Controlled
Cryptographic Protections (CRY) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
- Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
- Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
- Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
- Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider.
Assessment Objectives
- CRY-08_A01 requirements for key generation, distribution, storage, access and destruction are defined.
- CRY-08_A02 a certificate policy for issuing public key certificates is defined.
- CRY-08_A03 public key certificates are issued under an organization-defined certificate policy or public key certificates are obtained from an approved service provider.
- CRY-08_A04 only approved trust anchors are included in trust stores or certificate stores managed by the organization.
- CRY-08_A05 cryptographic keys are established whenever cryptography is employed.
- CRY-08_A06 cryptographic keys are managed whenever cryptography is employed.
Technology Recommendations
Micro/Small
- Microsoft Cloud PKI (https://microsoft.com)
- Digitcert (https://digicert.com)
- Entrust (https://entrust.com)
- Vault (https://vaultproject.io)
Small
- Microsoft Cloud PKI (https://microsoft.com)
- Digitcert (https://digicert.com)
- Entrust (https://entrust.com)
- Vault (https://vaultproject.io)
Medium
- Microsoft Cloud PKI (https://microsoft.com)
- Digitcert (https://digicert.com)
- Entrust (https://entrust.com)
- Vault (https://vaultproject.io)
Large
- Microsoft Cloud PKI (https://microsoft.com)
- Digitcert (https://digicert.com)
- Entrust (https://entrust.com)
- Vault (https://vaultproject.io)
Enterprise
- Microsoft Cloud PKI (https://microsoft.com)
- Digitcert (https://digicert.com)
- Entrust (https://entrust.com)
- Vault (https://vaultproject.io)