Skip to main content

CRY-04: Transmission Integrity

CRY 10 — Critical Protect

Cryptographic mechanisms exist to protect the integrity of data being transmitted.

Control Question: Are cryptographic mechanisms utilized to protect the integrity of data being transmitted?

General (34)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.1-POF10
CSA IoT SCF 2 SAP-07
GovRAMP Low+ SC-08
GovRAMP Moderate SC-08 SC-28(01)
GovRAMP High SC-08 SC-28(01)
IEC 62443-4-2 2019 CR 3.1 (7.3.1) CR 3.1 (7.3.3(1))
ISO 27002 2022 8.24 8.26
ISO 27017 2015 10.1.1 14.1.3
MITRE ATT&CK 10 T1020.001, T1040, T1090, T1090.004, T1550.001, T1550.004, T1552.007, T1557, T1557.001, T1557.002, T1562.006, T1562.009, T1602, T1602.001, T1602.002
NIST Privacy Framework 1.0 PR.AC-P5 PR.DS-P6
NIST 800-53 R4 SC-8 SC-16(1) SC-28(1)
NIST 800-53 R4 (moderate) SC-8
NIST 800-53 R4 (high) SC-8
NIST 800-53 R5 (source) SC-8 SC-16(1) SC-28(1)
NIST 800-53B R5 (moderate) (source) SC-8 SC-28(1)
NIST 800-53B R5 (high) (source) SC-8 SC-28(1)
NIST 800-53 R5 (NOC) (source) SC-16(1)
NIST 800-82 R3 MODERATE OT Overlay SC-8 SC-28(1)
NIST 800-82 R3 HIGH OT Overlay SC-8 SC-28(1)
NIST 800-161 R1 SC-8
NIST 800-161 R1 Flow Down SC-8
NIST 800-161 R1 Level 2 SC-8
NIST 800-161 R1 Level 3 SC-8
NIST 800-171 R2 (source) NFO-SI-1
NIST 800-207 NIST Tenet 2
NIST CSF 2.0 (source) PR.DS-02
PCI DSS 4.0.1 (source) 3.7.5
PCI DSS 4.0.1 SAQ D Merchant (source) 3.7.5
PCI DSS 4.0.1 SAQ D Service Provider (source) 3.7.5
SWIFT CSF 2023 2.1 2.4A 2.6
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) CRY-04
SCF CORE ESP Level 1 Foundational CRY-04
SCF CORE ESP Level 2 Critical Infrastructure CRY-04
SCF CORE ESP Level 3 Advanced Threats CRY-04
US (20)
Framework Mapping Values
US CERT RMM 1.2 KIM:SG4.SP1 KIM:SG5.SP3 SC:SG2.SP2 SC:SG2.SP3
US CISA CPG 2022 2.K
US CMS MARS-E 2.0 SC-8
US DHS ZTCF DPR-01
US FDA 21 CFR Part 11 11.10 11.10(c)
US FedRAMP R4 MP-5(4) SC-8 SC-28(1)
US FedRAMP R4 (moderate) SC-8 SC-28(1)
US FedRAMP R4 (high) SC-8 SC-28(1)
US FedRAMP R5 (source) SC-8 SC-28(1)
US FedRAMP R5 (moderate) (source) SC-8 SC-28(1)
US FedRAMP R5 (high) (source) SC-8 SC-28(1)
US HIPAA Administrative Simplification 2013 (source) 164.312(e)(2)(i)
US HIPAA Security Rule / NIST SP 800-66 R2 (source) 164.312(e)(2)(i)
US IRS 1075 SC-8 SC-28(1)
US NISPOM 2020 8-605
US SSA EIESR 8.0 5.9
US - MA 201 CMR 17.00 17.04(3)
US - OR 646A 622(2)(d)(C)(iii)
US - TX DIR Control Standards 2.0 SC-8
US - TX TX-RAMP Level 2 SC-8 SC-28(1)
EMEA (6)
Framework Mapping Values
EMEA EU PSD2 20 30
EMEA Germany C5 2020 OPS-09
EMEA Israel CDMO 1.0 4.22 9.8 9.20 12.10 13.6
EMEA Saudi Arabia IoT CGIoT-1 2024 2-4-1 2-4-2 2-4-3
EMEA Saudi Arabia OTCC-1 2022 2-2-1-4
EMEA South Africa 14.1
APAC (2)
Framework Mapping Values
APAC Australia ISM June 2024 ISM-0677
APAC Japan ISMAP 10.1.1 10.1.1.9.PB 14.1.3

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to Cryptographic protect the integrity of data being transmitted.

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.
  • IT personnel use an informal process to design, build and maintain secure configurations for the test, development, staging and production environments, implementing cryptographic protections controls using known public standards and trusted cryptographic technologies to protect the confidentiality and integrity of the data.
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 integrity of data being transmitted.

Assessment Objectives

  1. CRY-04_A01 the integrity of transmitted information is/are protected.
  2. CRY-04_A02 cryptographic uses are defined.
  3. CRY-04_A03 information requiring cryptographic protection is defined.
  4. CRY-04_A04 system components or media requiring cryptographic protection is/are defined.
  5. CRY-04_A05 types of cryptography for each specified cryptographic use are defined.
  6. CRY-04_A06 the integrity of transmitted cybersecurity / data privacy attributes is verified.
  7. CRY-04_A07 cryptographic mechanisms are implemented to prevent unauthorized disclosure of information at rest on system components or media.
  8. CRY-04_A08 cryptographic mechanisms are implemented to prevent unauthorized modification of information at rest on system components or media.

Evidence Requirements

E-CRY-01 Cryptographic Protections

Documented evidence of organization-approved cryptographic solutions and modules for both data at rest and in transit.

Cryptographic Protections

Technology Recommendations

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.