NIST SP 800-171 Rev 3
03.13 SC (System and Communications Protection)

NIST SP 800-171 Rev 3 03.13.10: Cryptographic Key Establishment and Management

Establish and manage cryptographic keys for cryptography employed in the system in accordance with key management requirements.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 13 controls

  • 2.3.2 2.3.2 Wireless encryption keys changed on triggers
  • 3.5.1.3 3.5.1.3 Disk encryption access independent of OS authentication
  • 3.6.1.1 3.6.1.1 Service provider cryptographic architecture documented
  • 3.6.1.2 3.6.1.2 Permitted storage forms for secret and private keys
  • 3.6.1.4 3.6.1.4 Cryptographic keys kept in fewest locations
  • 3.7.2 3.7.2 Secure distribution of cryptographic keys
  • 3.7.3 3.7.3 Secure storage of cryptographic keys
  • 3.7.4 3.7.4 Key changes at end of cryptoperiod
  • 3.7.5 3.7.5 Retirement, replacement or destruction of keys
  • 3.7.7 3.7.7 Prevent unauthorized substitution of keys
  • 4.2.1.1 4.2.1.1 Inventory of trusted transmission keys and certificates
  • 3.6.1 3.6.1 Procedures protect keys against disclosure and misuse
  • 3.7.1 3.7.1 Generation of strong cryptographic keys
  • ASBv3-DP-5 Use customer-managed key option in data at rest encryption when required
  • ASBv3-DP-6 Use a secure key management process
  • ASBv3-DP-7 Use a secure certificate management process
  • ASBv3-DP-8 Ensure security of key and certificate repository
  • SEC08-BP01 Implement secure key management
  • SEC09-BP01 Implement secure key and certificate management

C5 (Germany) · 2 controls

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

FedRAMP High · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-17 Public Key Infrastructure Certificates

FedRAMP Moderate · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-17 Public Key Infrastructure Certificates

NIST SP 800-53 Rev 5 · 2 controls

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.24 Use of cryptography

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
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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 03.13 SC (System and Communications Protection)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.13.10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 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. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

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