CMMC backup requirements come down to one line in NIST SP 800-171 Rev 2. Requirement 3.8.9 says to protect the confidentiality of backup CUI at storage locations. It does not tell you to make backups, how often to run them, or how long to keep them. If a backup holds Controlled Unclassified Information (CUI), the backup must be protected wherever it sits.

That surprises people in both directions. Some shops assume CMMC mandates a full disaster recovery program, and it does not. Others assume a backup is safe because it is out of sight, and that is where 3.8.9 catches them. You should still back up your data, because losing it would hurt your business. Just know which part is the rule and which part is good sense. This is explanatory content, not legal advice, so check your own contract for anything stricter.

Does NIST 800-171 require backups?

No. Section 2.2 of NIST SP 800-171 Rev 2 states that contingency planning requirements are not included in the publication, with one exception: a requirement to protect the confidentiality of system backups, derived from the federal control CP-9. NIST placed that requirement in the Media Protection family as 3.8.9.

The reason is the purpose of the document. 800-171 protects the confidentiality of CUI. Appendix E marks the rest of the contingency planning controls, including backup testing (CP-9(1)) and system recovery (CP-10), as not directly related to protecting confidentiality. Availability is your business problem, not an 800-171 requirement. Confidentiality of the copies you choose to make is the requirement.

The three self-assessed paths line up like this:

PathWhat it says about backups
CMMC Level 1 (Self)The safeguards in FAR 52.204-21 have no backup requirement. You must still sanitize or destroy media containing Federal Contract Information before disposal or reuse, and that includes old backup drives.
CMMC Level 2 (Self)3.8.9 applies to any backup containing CUI, and it is assessed like the other 109 requirements.
SPRS scoreThe same 3.8.9, scored under the DoD Assessment Methodology. An unmet requirement costs 1 point.

What an assessor looks at for 3.8.9

NIST SP 800-171A gives 3.8.9 a single assessment objective: determine if the confidentiality of backup CUI is protected at storage locations. It is one of the shorter entries in the document, but "storage locations" is plural on purpose. Every place a copy lands counts.

800-171A lists what may be examined: procedures addressing system backup, system configuration settings, the security plan, the backup storage locations themselves, and backup logs or records. An assessor may interview the person responsible for backups and test the backup process or the mechanism behind it. Our post on 800-171A assessment objectives explains how objectives are judged.

NIST's discussion text offers two ways to comply: cryptographic mechanisms or alternative physical controls. Encryption is the usual answer. A locked safe inside a controlled area can also work for physical media. The discussion also notes that backups can hold system-level information as well as user files, so a full image of a machine that stores CUI is a backup of CUI.

Where backups go wrong in small shops

Most failures here are not exotic. They are copies nobody remembered when the system security plan (SSP) was written.

Backup locationThe problemWhat fixes it
Network storage box in the officeUnencrypted, shared to everyone, in an unlocked closetFIPS-validated encryption or a locked controlled space, plus access limited to the backup administrator
USB drive taken home as the "offsite" copyPortable, unencrypted, and now outside your controlled areaEncrypt it, assign an owner, log where it goes, or replace it with a compliant offsite service
Consumer cloud backup on a laptopCUI copied to a provider that does not meet the DFARS cloud requirementRemove it from any machine that handles CUI
Backup add-on for your email or file platformCopies CUI out of your compliant tenant into the vendor's cloudConfirm the vendor's FedRAMP Moderate or equivalent status before you turn it on
MSP-run backupsYou do not know where the copies live or who can restore themGet the location, encryption and access in writing, and list it in your SSP
Old drives and tapesRetired without being wipedSanitize or destroy them and keep the record

Cloud backup is a DFARS question first

If a cloud service stores covered defense information for you, DFARS 252.204-7012 requires you to ensure the provider meets security requirements equivalent to the FedRAMP Moderate baseline and complies with the clause's incident reporting and related paragraphs. A backup service stores your data, so this applies.

Encrypting the backup first does not get you out of it. The DoD CMMC FAQ (Revision 2.2, January 2026) addresses this directly and answers no to whether a cloud offering without FedRAMP Moderate can store encrypted CUI, unless it meets the equivalent requirements. Ask the vendor for its status in writing before any data moves.

The encryption has to be FIPS-validated

When encryption is what protects the backup, requirement 3.13.11 applies: employ FIPS-validated cryptography when used to protect the confidentiality of CUI. A backup program with an "AES-256" checkbox is not automatically validated. Look up the cryptographic module, and see our guide to FIPS-validated encryption. Keep the keys away from the backup too. An encryption key stored in a text file on the same drive protects nothing.

Why 3.8.9 is only 1 point, and what that means

The DoD Assessment Methodology, version 1.2.1 weights 3.8.9 at 1 point. Its neighbors can weigh far more:

RequirementPlain EnglishSPRS points
3.8.3Sanitize or destroy media containing CUI before disposal or reuse5
3.8.6Encrypt CUI on digital media during transport unless physically safeguarded1
3.8.7Control the use of removable media5
3.8.9Protect the confidentiality of backup CUI at storage locations1
3.13.11Use FIPS-validated cryptography when protecting CUI3 to 5

Because it is worth 1 point, 3.8.9 is eligible for a plan of action and milestones (POA&M) under 32 CFR 170.21, and it is not among the six requirements that can never be deferred. A Conditional Level 2 (Self) status still needs a score of at least 80 percent, and the POA&M must be closed within 180 days. You can check the effect on your own number with the free SPRS calculator.

Do not read the low weight as low risk. A careless backup is usually a full copy of everything sensitive you hold, and the fix tends to touch 3.8.7 and 3.13.11, which cost more. A drive failing 3.8.9 often fails those too.

Backups you should have anyway

800-171 will not make you do this, but ransomware will make you wish you had. Requirement 3.6.1 does require an incident-handling capability that includes recovery activities, and it is worth 5 points, so expect to be asked how you would actually recover. Our suggestions, not rules:

One distinction worth knowing: routine backups are not the same as the preservation duty in DFARS 252.204-7012. After a reportable cyber incident, that clause requires you to preserve images of affected systems and relevant monitoring data for at least 90 days from your report. Do not let a backup rotation overwrite them. Our post on the 72-hour reporting rule covers the rest.

What to do this week

  1. List every place a copy of your data lands: servers, storage boxes, USB drives, cloud services, MSP tools, and machines with personal backup software.
  2. Mark which of those hold CUI, and add them to your scoping inventory.
  3. For each one, write down what protects it: FIPS-validated encryption or a physical control.
  4. Get written FedRAMP Moderate or equivalent status from any cloud backup vendor. If your MSP runs backups, get the details from them too.
  5. Turn off anything that fails, then find and sanitize stray copies.
  6. Write one paragraph in your SSP covering what is backed up, where, how it is protected, and who can restore it.
  7. Save a backup log and a configuration screenshot as evidence.

CMMC Map, CMMC compliance software for small defense contractors, walks you through 3.8.9 in the free assessment and keeps the evidence list with the requirement, so the backup paragraph in your SSP is written once and stays current.

See how 3.8.9 fits your score

The free CMMC Map assessment walks through 3.8.9 and the other 109 requirements and shows which gaps block Level 2 (Self).

Start free in CMMC Map
Free to assess · Documents $149/mo · No credit card