Which NIST SP 800-171 controls matter most when AI tools handle CUI?

Practitioner question: if an AI tool, coding assistant or model pipeline touches CUI, which NIST SP 800-171 requirements should you treat as the ones that matter most?

The official pages we cite do not publish that ranking. This article records what they do say.

Status as of 14 October 2026: we re-searched the NIST SP 800-171 Rev. 3 PDF for “artificial intelligence”, “machine learning” and “ai system” and still found no matches. COSAiS remains an SP 800-53 overlay project, not an 800-171 publication: the project page’s latest note is January 8, 2026 (annotated outline of Using and Fine-Tuning Predictive AI; initial feedback asked by February 13, 2026). CMMC Model Overview 2.13 and the About page still describe Rev 2 / 110 requirements / 14 families during the Phase II suspension recorded on earlier articles.

There is no AI-specific 800-171 control list

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 (14 October 2026). That is a search of those versions, not a legal opinion.

NIST SP 800-171 applies to components of nonfederal systems that process, store, or transmit CUI, or that provide protection for such components. 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. If CUI is in the AI path, the component is in scope. The rule does not name a shorter control set for AI. See CMMC and AI with CUI.

Which version of 800-171 CMMC actually enforces

DoD’s CMMC Model Overview Version 2.13 says the model incorporates the security requirements from NIST SP 800-171 Rev 2 and that the security requirements in Level 2 are identical to the requirements in NIST SP 800-171 Rev 2. DoD CIO’s About CMMC page says the Department is enforcing Rev 2 during the current suspension. NIST has published Revision 3, superseding Rev. 2. Use the revision your contract and the CMMC rule name, not the newest NIST PDF by default.

The 14 families CMMC names (Rev 2)

The Model Overview lists 14 domains that align with the families specified in NIST SP 800-171 Rev 2: Access Control (AC); Awareness and Training (AT); Audit and Accountability (AU); Configuration Management (CM); Identification and Authentication (IA); Incident Response (IR); Maintenance (MA); Media Protection (MP); Personnel Security (PS); Physical Protection (PE); Risk Assessment (RA); Security Assessment (CA); System and Communications Protection (SC); and System and Information Integrity (SI).

The same overview says Level 2 focuses on the protection of CUI and incorporates the 110 security requirements specified in NIST SP 800-171 Rev 2. Official pages do not say that only some of the 14 families apply when the in-scope system is an AI tool.

What official AI-security pages discuss, without ranking 800-171

Two official pages discuss AI-system security in control language. Neither is an 800-171 overlay.

NSA / CISA / FBI Deploying AI Systems Securely (April 2024) is joint cybersecurity information for organizations deploying and operating externally developed AI systems on premises or in private cloud environments. It tells deployers to ensure the use of an access control system for the AI model weights, encrypt data at rest including model weights, outputs, and logs, use strong authentication and TLS, collect logs to cover inputs, outputs, intermediate states, and errors, integrate an incident detection system, and apply role-based or attribute-based access controls. Those topics overlap the CMMC/800-171 family names AC, AU, IA, IR, MP, SC and SI. The CSI does not map them to 800-171 requirement numbers and does not say the other families drop out.

NIST COSAiS is a project to develop a series of overlays for securing AI systems using the NIST SP 800-53 controls, covering training and test data, model weights and configuration settings. Proposed use cases on the live page include adapting/using generative AI, using and fine-tuning predictive AI, single-agent and multi-agent systems, and security controls for AI developers. The concept paper (14 August 2025) and later annotated outlines are drafts. COSAiS is not an SP 800-171 publication and is not a CMMC assessment source.

Cloud AI services that handle CUI

For CMMC Level 2, an organization may use a cloud environment for CUI only if the offering is FedRAMP Authorized at the Moderate (or higher) baseline, or meets security requirements equivalent to it. The organization’s on-premises infrastructure connecting to the service is in the assessment scope. A service provider that is not a cloud provider is in the organization’s assessment scope and assessed as part of it. Those are scoping rules, not a reduced control list.

What this article does not say

It does not name a “top N” of the 110 requirements. It does not say any named AI product is acceptable for CUI. It does not treat the NSA/CISA CSI or COSAiS as CMMC assessment criteria. This is general information, not legal advice. See the CMMC reference page, CMMC Level 2 vs Level 3 for AI systems, and the printable CMMC + AI checklist.

Questions

Does NIST SP 800-171 have AI-specific controls?

The Rev. 3 PDF and 32 CFR Part 170 versions we searched do not use the words “artificial intelligence” or “machine learning”.

Can I assess only the families the CSI discusses?

No official page we cite says that. CMMC Level 2 is the 110 Rev. 2 requirements for in-scope systems. The CSI is best practices that may not be applicable to all environments.