CMMC and AI with CUI - what the rules actually say

Published · Updated · 3 min read

Informational only, not professional or legal advice. Facts are linked to the source we checked; statuses can change after the date above.

If you use a large language model, an ML pipeline or an AI coding assistant on a defense contract, the question is whether controlled unclassified information (CUI) touches it. The CMMC rule does not answer in AI terms. It answers in system terms. For live program names and § 170.19 asset categories, see CMMC Program scoping for generative systems that handle CUI.

CMMC has no AI-specific requirements

We searched the text of 32 CFR Part 170 and the NIST SP 800-171 Rev. 3 PDF for “artificial intelligence” and “machine learning” and found no matches. That is a search of the versions available on 14 October 2026, not a legal opinion. What the rules do say is about scope: NIST SP 800-171 applies to components of nonfederal systems that process, store, or transmit CUI, or that provide protection for such components.

Step 1: is CUI in the AI system’s path?

DFARS 252.204-7021 requires a CMMC status for all information systems used in performance of the contract that process, store, or transmit FCI or CUI. Analysis: for an AI system, ask where CUI could enter. Prompts and uploaded documents, retrieval indexes, fine-tuning or training data, logs and chat history, and model outputs that reproduce CUI are all places data can be processed, stored or transmitted. If any is in scope, the component is in scope.

Step 2: who operates the AI service?

The same scoping rule also says the organization’s on-premises infrastructure connecting to the service is in the assessment scope, and that the customer responsibility matrix (CRM) must be documented in the system security plan.

Step 3: keep the requirements version straight

The CMMC rule incorporates NIST SP 800-171 Revision 2, while NIST has since published Revision 3, superseding Rev. 2. DoD says it is enforcing Rev 2 during the current suspension.

Where CMMC stands (re-verified 14 October 2026)

DoD CIO says that on July 13, 2026 the Department announced the immediate suspension of CMMC Phase II, originally scheduled for November 10, 2026, while Phase I self-assessment requirements remain in place and implementation is paused in Phase 1. During the suspension the Department will enforce cybersecurity compliance with NIST 800-171 Rev 2 through self-assessments and select government-led assessments. The same page says the Department will begin a comprehensive review of CMMC aimed at aligning with the Secretary of War Pete Hegseth’s Acquisition Transformation System (ATS) directives. An implementing memo says requiring activities may only designate CMMC Level 1 (Self) or Level 2 (Self) during the suspension. The suspension does not eliminate the requirement to protect information under DFARS clause 252.204-7012. Check DoD CIO for any announcement of the program review’s outcome.

What this article does not say

We do not say any named AI product is or is not acceptable for CUI. That depends on the product’s FedRAMP status or equivalence evidence, your contract, and your system security plan. This is general information, not legal advice. See the CMMC reference page, CMMC Level 2 vs Level 3 for AI systems, which 800-171 controls official pages actually discuss for AI tools that handle CUI, the audit evidence checklist, and the printable CMMC + AI checklist.

Sources

  1. 32 CFR Part 170 - CMMC Program - eCFR
  2. 32 CFR 170.16 - CMMC Level 2 self-assessment and affirmation requirements - eCFR
  3. 32 CFR 170.19 - CMMC scoping - eCFR
  4. 48 CFR 252.204-7021 (DFARS) - eCFR
  5. SP 800-171 Rev. 3 - NIST CSRC
  6. NIST SP 800-171 Rev. 3 (PDF) - NIST
  7. FedRAMP Authorization and Equivalency - DoD CIO
  8. About CMMC - DoD CIO
  9. Implementing Suspension of CMMC Phase II (memo) - DoD CIO

Free next step: take the AI assurance readiness self-check or create a free account. Quoted evidence stays on Pro.