CMMC 2.0
System and Communications Protection

CMMC 2.0 SC.L2-3.13.11: CUI Encryption

Use FIPS validated cryptography wherever cryptography is relied on to protect the confidentiality of CUI.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 42 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-3.10 Encrypt Sensitive Data in Transit
  • CIS-3.11 Encrypt Sensitive Data at Rest
  • CIS-3.6 Encrypt Data on End-User Devices
  • CIS-3.9 Encrypt Data on Removable Media
  • ASBv3-DP-5 Use customer-managed key option in data at rest encryption when required
  • DP-3 Encrypt sensitive data in transit
  • DP-4 Enable data at rest encryption by default

ISO 27001:2022 · 3 controls

  • 5.33 Protection of records
  • 8.24 Use of cryptography
  • 8.33 Test information

PCI DSS 4.0 · 3 controls

  • 4.2.1 4.2.1 Strong cryptography safeguards PAN over public networks
  • 3.6.1 3.6.1 Procedures protect keys against disclosure and misuse
  • 3.7.1 3.7.1 Generation of strong cryptographic keys
  • ANSSI-HYG-18 Encrypt Sensitive Data Transmitted Over the Internet
  • ANSSI-HYG-42 Prefer Products and Services Qualified by ANSSI

FedRAMP High · 2 controls

  • IA-7 Cryptographic Module Authentication
  • SC-13 Cryptographic Protection

FedRAMP Moderate · 2 controls

  • IA-7 Cryptographic Module Authentication
  • SC-13 Cryptographic Protection

HIPAA Security Rule · 2 controls

  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • ASD37-17 TLS encryption between email servers (Limited)

C5 (Germany) · 1 control

  • C5-CRY-01 Policy for the use of encryption procedures and key management

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls

NIS2 Directive · 1 control

  • Art.21.2.h Policies and procedures on the use of cryptography and, where appropriate, encryption

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in System and Communications Protection

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 SC.L2-3.13.11 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

The graph holds this control, the 42 it maps to, and the evidence behind each claim, over MCP and REST.