System Backup - Cryptographic Protection makes sure that the copies of your data are protected as well as the originals. Backups are a frequent blind spot, because organizations that encrypt production data sometimes leave backups readable at rest. System Backup - Cryptographic Protection (03.08.09) closes that gap. It has two (2) parts: protect the confidentiality of backup information, and implement cryptographic mechanisms to prevent the unauthorized disclosure of Controlled Unclassified Information (CUI) at backup storage locations. Per the NIST discussion, the choice of cryptographic mechanisms is based on the need to protect confidentiality, and hardware security module (HSM) devices can safeguard and manage cryptographic keys and provide hardware-accelerated cryptographic processing.
A common difficulty with this requirement is backing up CUI to storage that is not encrypted, whether that is a network share, an offline tape, or a cloud backup service. The requirement is specific that cryptographic mechanisms protect CUI at the backup storage location, so an unencrypted backup of an otherwise well-protected system is a direct failure of this control.
Where things stand for companies facing the transition from NIST 800-171 R2 to R3:
The following is reproduced verbatim from NIST 800-171 R3, requirement 03.08.09 System Backup - Cryptographic Protection. Only the formatting has been adjusted for readability. This requirement has two (2) lettered parts:
The source controls are CP-09 and CP-09(08) from NIST 800-53. There are no Organization-Defined Parameters (ODPs). Per the NIST discussion, cryptographic operations such as encryption and decryption are typically hosted on an HSM device, and this requirement is related to Cryptographic Protection (03.13.11). You can read the requirement directly at NIST 800-171 R3, 03.08.09 (p. 48).
None (0). Requirement 03.08.09 contains no bracketed assignment, so there is no organization-defined value to select and nothing for the DoD to specify. The requirement applies as written.
Your System Security Plan (SSP) narrative for 03.08.09 therefore records how the requirement is implemented rather than a parameter you chose.
NIST 800-171A R3 breaks 03.08.09 into two (2) determination statements, and it has no Organization-Defined Parameters (ODPs). These AOs are:
The two (2) objectives are protecting backup confidentiality and implementing cryptographic mechanisms specifically at backup storage locations. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.08.09 (p. 61).
Examine: contingency planning policy and procedures; procedures for system backup; contingency plan; system design documentation; system configuration settings; system security plan.
Interview: personnel with system backup responsibilities; personnel with information security responsibilities.
Test: mechanisms for supporting or implementing the cryptographic protection of backup information.
03.08.09 maps from NIST 800-171 R2 requirement 3.8.9 (protect the confidentiality of backup CUI at storage locations):
Mapped against the two (2) AOs, both (2) are direct (minimal effort), with no net-new AOs and none with no mapping. This is a clean carry-forward. The confidentiality-of-backups concept is unchanged, and R3 states the cryptographic-mechanism expectation explicitly. If you protected backup CUI confidentiality under R2, confirm that protection is cryptographic and reaches every backup storage location.
Source Controls in NIST 800-53 R5:
Secure Controls Framework (SCF) Crosswalk
Organizations running a single control set across multiple frameworks can satisfy 03.08.09 through the following SCF controls:
The crosswalks from NIST 800-171 R3 and NIST 800-171A R3 to the SCF are available at no cost through the SCF Set Theory Relationship Mapping (STRM): https://securecontrolsframework.com/start-here/set-theory-relationship-mapping-strm. The STRM also carries the relationship type for each mapping (Equal, Subset Of, Intersects With), which tells you whether an SCF control fully satisfies the requirement or only part of it. Mapping above taken from SCF 2026.3.
The following are issues teams may encounter rather than certainties. They are about covering every backup location, each of which needs documented evidence of due diligence and due care such as policies, standards, procedures, and configuration screenshots:
Reasonable objective evidence for an assessment is often subjective. The following examples of evidence to address NIST 800-171 R3 03.08.09 are sourced from the SCF Evidence Request List (ERL), available at https://securecontrolsframework.com/free-content/scf-download. These ERL artifacts are mapped to NIST 800-171 R3 03.08.09 through SCF controls. They establish a starting point for discussions on what an organization needs to have for evidence of due diligence and due care to withstand external scrutiny by an assessor or regulator.
Alongside these, keep the System Security Plan (SSP) narrative for 03.08.09.
With both AOs mapping directly, 03.08.09 is a light lift if backups are already encrypted. A realistic sequence:
How many assessment objectives does NIST 800-171 R3 03.08.09 have? NIST 800-171A R3 breaks 03.08.09 into two (2) assessment objectives. An assessor works through each one separately, so each needs its own evidence.
Which NIST 800-53 R5 controls does NIST 800-171 R3 03.08.09 come from? CP-09, CP-09(08).
How many Organization-Defined Parameters (ODPs) does NIST 800-171 R3 03.08.09 have? None (0). The requirement contains no bracketed assignment, so there is no organization-defined value and nothing for the DoD to specify.
Where does NIST 800-171 R3 03.08.09 sit in the NIST 800-171 R3 Kill Chain? Phase 18, Business Continuity & Disaster Recovery (BC/DR). The Kill Chain is a phased model for sequencing R3 implementation, and it assigns this requirement to that phase.
03.08.09 System Backup - Cryptographic Protection protects the confidentiality of backups and implements cryptographic mechanisms to prevent unauthorized disclosure of CUI at backup storage locations. It maps directly from R2 3.8.9, so there is no net-new work, but R3 states the cryptographic expectation plainly. The recurring problem is unencrypted backups of well-protected systems. Encrypt CUI at every backup location and manage the keys.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
