# NIST800 171 3.13.11 — Cryptographic Protection

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist800171_31311_bc8354f2c7-nist800-171-31311-cryptographic-protection
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST SP 800-171 Readiness](https://support.icompaas.com/support/solutions/c_gen_nist800171) › [Situational Awareness](https://support.icompaas.com/support/solutions/folders/f_gen_cgennist800171_situationalawareness)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 171 · Control 3.13.11 · Priority: critical · Component: Situational Awareness

### What this control covers

This control requires implementing cryptographic mechanisms to protect the confidentiality of Controlled Unclassified Information (CUI). The cryptography must align with applicable laws, regulations, and standards, with FIPS-validated cryptography recommended for CUI protection. This control supports the Cryptographic Protection capability within the Situational Awareness (3.13) family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Cryptographic Protection.

### Quick checklist

-   Information — Management / Cui
-   Protection — Management / Cui
-   Risk — Management / Cui
-   Cryptographic — Management / Cui
-   Policy — Management / Cui

### Related articles on this site

-   [NIST 800-171 3.8.6 Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.](https://support.icompaas.com/support/solutions/articles/62000229315-nist-800-171-3-8-6-implement-cryptographic-mechanisms-to-protect-the-confidentiality-of-cui-stored-on)
-   [NIST 800-171 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.](https://support.icompaas.com/support/solutions/articles/62000229245-nist-800-171-3-1-13-employ-cryptographic-mechanisms-to-protect-the-confidentiality-of-remote-access-s)
-   [NIST 800-171 3.13.11 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.](https://support.icompaas.com/support/solutions/articles/62000229252-nist-800-171-3-13-11-employ-fips-validated-cryptography-when-used-to-protect-the-confidentiality-of-c)
-   [CMMC 2.0 AC.3.014 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.](https://support.icompaas.com/support/solutions/articles/62000229414-cmmc-2-0-ac-3-014-employ-cryptographic-mechanisms-to-protect-the-confidentiality-of-remote-access-ses)

## Related compliance guidance

- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): The CUI requirements CMMC Level 2 assesses, the SPRS score, POA&M rules and the phased DFARS rollout.
- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The federal catalogue 800-171 is derived from — useful when a contract also cites a FedRAMP baseline.