Skip to main content

CRY-05.1: Storage Media

CRY 8 — High Protect

Cryptographic mechanisms exist to protect the confidentiality and integrity of sensitive/regulated data residing on storage media.

Control Question: Are cryptographic mechanisms utilized to protect the confidentiality and integrity of sensitive/regulated data residing on storage media?

General (12)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.7-POF3
CIS CSC 8.1 3.9
CIS CSC 8.1 IG1 3.6
CIS CSC 8.1 IG2 3.6
CIS CSC 8.1 IG3 3.6
CSA CCM 4 UEM-08
NIST Privacy Framework 1.0 PR.DS-P1
NIST 800-171 R3 (source) 03.13.08
PCI DSS 4.0.1 (source) 9.4
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) CRY-05.1
SCF CORE ESP Level 2 Critical Infrastructure CRY-05.1
SCF CORE ESP Level 3 Advanced Threats CRY-05.1
US (4)
Framework Mapping Values
US C2M2 2.1 ARCHITECTURE-5.G.MIL3
US HIPAA HICP Medium Practice 2.M.A
US HIPAA HICP Large Practice 2.M.A
US NNPI (unclass) 18.3 19.3
EMEA (3)
Framework Mapping Values
EMEA Germany C5 2020 CRY-03
EMEA Israel CDMO 1.0 15.7
EMEA Saudi Arabia OTCC-1 2022 2-3-1-8 2-3-1-9
APAC (1)
Framework Mapping Values
APAC New Zealand NZISM 3.6 8.4.13.C.01
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 03.13.08

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to Cryptographic protect the confidentiality and integrity of sensitive/regulated data residing on storage media.

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.
  • Mobile devices containing sensitive/regulated data use a cryptographic mechanism to prevent the unauthorized disclosure of information at rest (e.g., whole drive 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.
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 Cryptographic protect the confidentiality and integrity of sensitive/regulated data residing on storage media.

Assessment Objectives

  1. CRY-05.1_A01 storage media types are defined.
  2. CRY-05.1_A02 cryptographic mechanisms protect the confidentiality and integrity of the sensitive data residing on storage media.

Technology Recommendations

Micro/Small

  • NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
  • Microsoft BitLocker (https://microsoft.com)

Small

  • NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
  • Microsoft BitLocker (https://microsoft.com)

Medium

  • NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
  • Microsoft BitLocker (https://microsoft.com)

Large

  • NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
  • Microsoft BitLocker (https://microsoft.com)

Enterprise

  • NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
  • Microsoft BitLocker (https://microsoft.com)

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.