Skip to main content

CRY-09: Public Key Infrastructure (PKI)

CRY 9 — Critical Protect

Mechanisms exist to securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider.

Renumbered: Formerly CRY-08 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, CRY-09 was Cryptographic Key Management. That control is now CRY-10.

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 (25)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.1 CC6.1-POF10 CC6.1-POF11
CSA CCM 4.1.0 CEK-08 LOG-11
CSA IoT SCF 2 CLS-01 IAM-10 SDV-01
GovRAMP SC-12 SC-17
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
MITRE ATT&CK 16 T1072 T1098.004 T1521.003 T1552 T1552.001 T1552.002 T1552.004 T1563.001 T1573 T1573.001 T1573.002 T1606
NIST 800-53 R4 SC-12 SC-12(4) SC-12(5) SC-17
NIST 800-53 R5.2 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 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-171 R3 (source) 03.13.10
NIST 800-171A (source) 3.13.10[a] 3.13.10[b]
NIST 800-171A R3 (source) A.03.13.10[01]
NIST 800-207 NIST Tenet 2
OWASP Top 10 2025 A04:2025
US (13)
EMEA (2)
Framework Mapping Values
EMEA Germany C5 2026 CRY-08.01B CRY-08.01B.1 CRY-08.01B.2
EMEA EU DORA RTS 2024 Article 7.5
APAC (3)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0485 ISM-1449 ISM-2050
APAC Malaysia RMiT 2025 10.23
APAC New Zealand NZISM 3.9 23.3.21.C.01 23.3.22.C.01
Americas (2)
Framework Mapping Values
Americas Argentina Reg 132 2018 A.2.3
Americas Canada ITSP-10-171 2025 03.13.10

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

Cryptographic Protections (CRY) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with CRY domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with CRY domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CRY domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Cryptographic management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Cryptographic management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Technology Assets, Applications and/or Services (TAAS) that store, process or transmit sensitive/regulated data use cryptographic mechanisms to prevent unauthorized disclosure of information as an alternate to physical safeguards. ▪ External compliance requirements for cryptography are identified and documented, based on applicable laws, regulations and contractual obligations. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to implement cryptographic mechanisms that are applicability for statutory, regulatory and/or contractual compliance obligations. ▪ 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.

Level 3 — Well Defined

Cryptographic Protections (CRY) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with CRY domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with CRY domain capabilities are well-documented and kept current by process owners. ▪ A security engineering team, or similar function, is appropriately staffed and supported to implement and maintain CRY domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of cryptographic protections operations (e.g., PKI management tool). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CRY domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to securely implement an internal Public Key Infrastructure (PKI) infrastructure or obtain PKI services from a reputable PKI service provider.

Level 4 — Quantitatively Controlled

Cryptographic Protections (CRY) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ 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. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. CRY-09_A01 requirements for key generation, distribution, storage, access and destruction are defined.
  2. CRY-09_A02 a certificate policy for issuing public key certificates is defined.
  3. CRY-09_A03 public key certificates are issued under an organization-defined certificate policy or public key certificates are obtained from an approved service provider.
  4. CRY-09_A04 only approved trust anchors are included in trust stores or certificate stores managed by the organization.
  5. CRY-09_A05 cryptographic keys are established whenever cryptography is employed.
  6. CRY-09_A06 cryptographic keys are managed whenever cryptography is employed.

Evidence Requirements

E-CRY-04 Public Key Infrastructure (PKI) Documentation

Documented evidence of Public Key Infrastructure (PKI) implementation, availability and approved Certificate Authorities (CAs).

Cryptographic Protections

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)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.