AI and CUI Training Gaps Risk Federal Information

Quick Answer

AI and CUI training teaches personnel what controlled unclassified information can and can’t go into an AI tool, and why. The core rule is simple: CUI goes only into systems your agency has authorized for it, never into a public or personal AI account.

Good training goes further. It teaches people to recognize CUI when it isn’t marked, to treat AI outputs built from CUI as CUI, to know which approved tools exist, and to report a spill fast instead of hiding it. With enterprise AI platforms now on DoD desktops, this is a live workforce readiness requirement, not a future one.

Key Facts

CUI has a legal basis. Executive Order 13556 established the program, and 32 CFR Part 2002 implements it government-wide. The National Archives serves as executive agent.
DoD sets a stricter cadence. DoD Instruction 5200.48 requires initial CUI training and annual refresher training for DoD personnel with access to CUI. The government-wide rule requires refresher training at least every two years.
Enterprise AI is already here. The Department launched GenAI.mil in December 2025 with Google’s Gemini for Government, authorized for CUI at Impact Level 5. ChatGPT and Grok options were added later.
Existing CUI training has gaps. A January 2026 DoD Inspector General management advisory found conflicting guidance in CUI training materials and inconsistent marking across DoD documents.
Federal AI policy expects training. OMB Memorandum M-25-21, issued in April 2025, directs agencies to accelerate responsible AI use and encourages AI training to build workforce capability.

Why AI and CUI Training Can’t Wait for the Next Annual Cycle

Picture a program analyst at 4:45 on a Friday. A deadline is due Monday, the draft is rough, and an AI assistant is one browser tab away. The document isn’t marked, but it includes contract figures, a vendor’s proprietary pricing, and a paragraph pulled from a For Official Use Only memo that was never re-marked as CUI.

Nothing in that moment feels like a security decision. It feels like editing. That gap between how the action feels and what it actually is sits at the center of AI and CUI training.

Most CUI courses were built for a world of email, shared drives, and printers. They teach marking, safeguarding, and dissemination, and they do it reasonably well. What they rarely address is a tool that invites people to paste in whole documents and ask for a summary, a rewrite, or a comparison.

That is now a daily workflow across the federal enterprise. When GenAI.mil launched, department leadership told the workforce to log in and start using it right away. Adoption at that speed needs AI and CUI training that keeps pace.

Approved AI vs. Public AI: The Distinction Your Workforce Must Get Right

The most important lesson is also the easiest to blur. Not all AI tools are equal. “It’s an AI tool the government uses” doesn’t mean “it’s authorized for my data.”

An enterprise platform authorized at Impact Level 5 was built and assessed to handle CUI. A public chatbot on a personal account was not. A commercial product with AI features added to an existing app sits somewhere in between, and the answer depends on how your agency authorized that specific service.

Tool type	Example	Can CUI go in?	What training should emphasize
Enterprise AI authorized for CUI	GenAI.mil (IL5)	Yes, within its authorization and your need-to-know	Still mark outputs, still verify, and never enter classified data
Agency-licensed commercial AI	An AI feature inside an approved productivity suite	Only if your agency authorized it for CUI	Check the authorization, not the vendor’s reputation
Public or personal AI accounts	Consumer chatbots, browser extensions	No	Treat any CUI entry as a potential spill and report it

The table looks simple. The hard part is that personnel often can’t tell which row they’re in. AI and CUI training should show people exactly where to check, whether that’s an approved-tools list, the system’s login banner, or the local security office.

Where AI and CUI Training Usually Falls Short

Standard CUI instruction teaches people to protect marked information. AI raises three problems that marking alone doesn’t solve.

Unmarked CUI is still CUI. The Inspector General’s 2026 advisory found that marking practices were inconsistent across DoD. If personnel rely on banner markings to decide what’s safe to paste, every marking gap becomes an AI exposure. Training has to build recognition of CUI categories by content, not just by label.

AI outputs inherit the sensitivity of their inputs. A summary of a CUI document is still CUI. So is a table extracted from it or a draft rewritten from it. AI and CUI training should make this reflex automatic, because generated text looks new and unmarked even when its content isn’t.

Compilation creates new sensitivity. AI is very good at pulling scattered, individually harmless details into one clean summary. The combined product can reveal more than any single source. Policy treatment of aggregation varies, so this is best taught as an operational judgment call: when a compiled output starts to look sensitive, stop and ask your security office.

The Trade-Off: Blanket Bans vs. Trained Enablement

Some organizations respond to AI risk by blocking everything. That approach has real advantages. It’s simple to explain, easy to audit, and it closes the most obvious spill path.

The drawbacks show up later. Banning approved tools pushes work onto personal devices and unsanctioned apps, where nobody can see it. It also leaves personnel unprepared when an authorized tool finally arrives, which in DoD’s case has already happened.

Trained enablement takes more effort. It requires clear tool guidance, AI and CUI training built on realistic scenarios, and supervisors who reinforce the rules. The payoff is a workforce that uses AI where it’s authorized and knows exactly where the line is.

Approach	Advantages	Drawbacks
Blanket ban	Simple, auditable, closes obvious spill paths	Drives shadow use, wastes approved capability, leaves people untrained
Trained enablement	Captures productivity safely, builds judgment, surfaces risks early	Requires ongoing training, clear tool lists, and supervisor engagement

For most agencies, the question isn’t whether to allow AI. It’s whether personnel will use it with training or without it.

Building AI and CUI Training That Changes Behavior

Effective programs share a few traits, and none of them require a new course catalog.

Teach with real documents. Use sanitized examples drawn from your own mission area. Ask trainees to decide what could go into an approved tool, what couldn’t, and how the output would need to be marked. Recognition improves when the material looks like actual work.

Publish a one-page tool guide. List which AI tools are authorized, at what data level, and who to call with questions. Update it whenever a tool is added. People follow guidance they can find in thirty seconds.

Make spill reporting safe and fast. If reporting a mistake feels career-ending, people won’t report it. Training should walk through exactly what to do when CUI goes into the wrong tool, and leaders should reinforce that early reporting is the right call.

Fold AI into the annual refresher. DoD personnel already complete CUI training every year. Adding AI scenarios to that existing requirement is the most efficient way to keep AI and CUI training current as tools change.

Getting AI and CUI Training Right This Year

Enterprise AI is already on federal desktops, and the workforce was told to start using it. Protecting CUI now depends on whether personnel understand how these tools fit within the rules they already know.

Workforce readiness officers don’t need to start from scratch. The CUI program, the annual training requirement, and the approved-tools model are already in place. What’s needed is AI and CUI training that connects them to the way people actually work today.

The goal isn’t fear or blanket restriction. It’s a workforce that can use AI with confidence because it knows exactly where the boundaries are.

Go Deeper: Operationalizing the Human Element

If you’re responsible for AI and CUI training, Operationalizing the Human Element: A Force Readiness Training Playbook and Reference Guide for AI Integrated Defense Workflows was written for you. Its chapter on CUI-aware AI workflows expands on everything in this article. Other chapters cover human-in-the-loop governance, human-machine trust, organizational adoption, and operational checklists you can use right away.

Purchase with a Government Purchase Card on Amazon →
Government purchase card use is subject to agency purchasing rules and cardholder authority.

Equipping a team, schoolhouse, or program office? Request bulk or organizational copies →

Need support beyond the book? Discuss your training and readiness requirements with Uply Media →

Frequently Asked Questions

Who needs AI and CUI training?
Anyone with access to CUI who also has access to AI tools, which today means most of the federal and DoD workforce. Supervisors, contracting staff, and analysts who handle vendor data should be priorities, because their daily documents often contain CUI that isn’t obviously labeled.

Can I put CUI into ChatGPT or another public AI tool?
Not through a public or personal account. CUI can only go into systems your agency has authorized for it. Some government versions of commercial models are authorized for CUI, so check your agency’s approved-tools list rather than going by the product name.

What should I do if I entered CUI into an unauthorized AI tool?
Stop, don’t delete anything on your own, and report it to your security office or supervisor right away. Prompt reporting gives your organization the best chance to contain the exposure, and hiding a spill makes the consequences worse for everyone.

Is AI-generated content based on CUI documents considered CUI?
Yes. Summaries, rewrites, and extracts derived from CUI carry the same sensitivity as the source and should be marked and handled accordingly. Effective AI and CUI training teaches this directly, because generated text looks new even when its content isn’t.

How often should AI and CUI training be refreshed?
DoD already requires annual CUI refresher training, so adding AI scenarios to that cycle is the practical baseline. Update the content, or at least the approved-tools guide, whenever a new AI capability is fielded.

Does GenAI.mil mean personnel can use any AI tool for CUI?
No. GenAI.mil is authorized at Impact Level 5 for CUI, but that authorization covers that platform only. Other tools, including consumer versions of the same models, require their own authorization before CUI goes anywhere near them.