The DoD instruction that implements the Controlled Unclassified Information (CUI) program is DoD Instruction 5200.48, "Controlled Unclassified Information (CUI)," issued December 2, 2020, and updated March 6, 2023. It directs how the Department of Defense marks, safeguards, disseminates, decontrols, and self-inspects CUI, and it implements the government-wide CUI regime that the National Archives and Records Administration (NARA) administers under 32 CFR Part 2001.
The policy stack behind DoDI 5200.48
DoDI 5200.48 does not float free. It sits at the bottom of a three-layer stack, and understanding that stack explains why the answer is unambiguous.
At the top is Executive Order 13526 and its amendments, which govern classified national security information, plus Executive Order 13556, which created the government-wide CUI program in 2010. EO 13556 told NARA to run a single, government-wide CUI program, replacing a patchwork sometimes called "For Official Use Only," "Sensitive But Unclassified," and dozens of agency-specific labels.
The middle layer is 32 CFR Part 2001, NARA's implementing regulation. Part 2001 defines what counts as CUI, who may designate categories, how marking works, what safeguarding standards apply, how decontrol happens, and what self-inspection requires. It binds executive branch agencies, including DoD.
The bottom layer is DoDI 5200.48. Because DoD is enormous and handles categories from privacy data to export-controlled technical data, the instruction translates Part 2001 into DoD-specific roles, timelines, and procedures. It also names the Defense Counterintelligence and Security Agency (DCSA) as the DoD CUI Program lead and establishes the CUI Registry as the authoritative category list.
Why this matters for exam-style questions: distractors often name real documents that do related but different jobs. DoDI 5200.48 is the implementation instruction; the others are either adjacent authorities or superseded labels. If a question asks which instruction implements the DoD CUI program, the instruction number is 5200.48.
What the instruction actually changes, mechanically
The instruction's core move is to replace ad hoc legacy markings with a uniform system built on three designations: CUI Basic, CUI Specified, and unmarked controlled information where marking would itself be harmful.
CUI Basic is CUI without an underlying law, regulation, or government-wide policy that prescribes specific handling. It receives the baseline safeguarding in Part 2001: controlled environments, encryption of data at rest and in transit, and access limited to those with a lawful government purpose.
CUI Specified is CUI whose governing authority imposes handling requirements beyond the baseline, such as Privacy Act data or export-controlled technical data. Specified categories can tighten dissemination, storage, or destruction rules. The designation logic is the counterintuitive part: the label rides on the underlying authority, not on how sensitive the information feels. A document can look mundane and still be CUI Specified because a statute says so.
Marking is the visible mechanism. The instruction requires the CUI banner, a category marking, and a limited dissemination control marking where applicable. A portion marking goes on each portion containing CUI. The point is machine-checkable traceability: a reviewer can tell from the face of the document what authority applies and who may receive it.
Decontrol is the release valve. When the underlying authority expires, or when an agency determines the information no longer qualifies, the CUI marking comes off and the information becomes uncontrolled unclassified information. This sounds procedural but it is the difference between a program that decays into permanent over-labeling and one that stays honest. The instruction sets expectations for reviewing and removing markings rather than letting them fossilize.
Self-inspection is the accountability mechanism. DoD components must inspect their own CUI programs, and DCSA provides oversight. The instruction ties inspection to correction: findings feed back into training and marking discipline rather than sitting in a report.
In plain terms: the instruction is the DoD rulebook that turns a government-wide labeling scheme into daily practice for marking, storing, sharing, and eventually releasing sensitive unclassified information.
Quantified context: dates, counts, and thresholds
DoDI 5200.48 was issued December 2, 2020, and updated March 6, 2023. The update matters because it reflects refinements after the initial rollout, including adjustments to roles and procedures. The underlying authorities are older: EO 13556 dates to 2010, and 32 CFR Part 2001 has been amended repeatedly since the original CUI rule took effect.
The instruction incorporates change 1, and its associated administrative guidance appears in DoD manuals and DCSA publications rather than the instruction alone. Exam questions sometimes probe whether the instruction or the manual carries a given procedure; the instruction sets policy, and manuals carry detailed how-to.
Scale is the reason a single instruction exists. DoD comprises the military departments, defense agencies, and field activities, and CUI touches contracting, acquisition, privacy, intelligence support, and research. A uniform instruction reduces the number of ways the same category can be marked across components.
Timelines inside the program are procedural rather than fixed statutory clocks. Self-inspection cycles, decontrol reviews, and training refreshes are set by component and DCSA guidance. The instruction's contribution is requiring these activities and assigning responsibility, not prescribing a single department-wide calendar.
The CUI Registry is the controlling list. DoD components cannot invent categories; they designate within registry categories and their governing authorities. That constraint is why the instruction repeatedly points to the registry rather than enumerating categories itself.
Edge cases that trip people up
Three edge cases account for most confusion in practice and on exams.
First, classified information is out of scope. CUI is unclassified by definition. If information is classified, the CUI program does not apply, and the marking regime is the classified system. A document cannot be both.
Second, legacy markings persist in the wild. Documents marked "For Official Use Only" or "Sensitive But Unclassified" were created under prior regimes. The instruction directs transition to CUI marking, but old documents and old habits survive. A common misconception is that legacy labels are simply invalid; in practice they are being retired through training and review, and handling rules for existing documents flow from the governing authority.
Third, unmarked CUI exists. When marking would reveal the sensitivity of the information, the instruction permits withholding the marking. This is the professional caveat that surprises newcomers: the absence of a banner does not prove the absence of controls. An unmarked document can still be CUI, and mishandling it is still a violation.
Red flag: assuming "no CUI banner" means "uncontrolled" and posting the document publicly. Red flag: applying CUI markings to classified material, or mishandling CUI as if it were classified. Red flag: inventing a local category label instead of using the CUI Registry. Red flag: sharing CUI with contractors without confirming the contract's CUI and safeguarding clauses. Red flag: leaving outdated legacy markings on newly created documents.
Each flag maps to an explicit instruction requirement or a governing-authority limit. The pattern is consistent: the instruction controls the label, the underlying authority controls the handling, and the registry controls the vocabulary.
Misconceptions versus the mechanism
The most persistent misconception is that CUI is a classification level. It is not. Classification is a separate legal regime with its own authorities, markings, and adjudication. CUI is a handling designation for unclassified information that still needs protection. Conflating them produces both over-labeling and under-protection.
A second misconception is that the CUI program is optional guidance. It is mandatory for DoD components through the instruction, and it rests on a NARA regulation that binds executive branch agencies. Organizations outside the executive branch, including some contractors and non-federal partners, encounter CUI through contract clauses and information-sharing agreements rather than through the instruction directly.
A third misconception is that CUI rules are uniform across every category. CUI Basic and CUI Specified diverge, and the specified categories can impose stricter requirements. The instruction's structure assumes readers will check the governing authority for the specific category rather than applying a single mental model.
A fourth misconception is that the program only concerns paper markings. It covers electronic systems, email, storage media, and dissemination. Because most CUI now lives digitally, system-level controls matter as much as document markings.
Comparison is useful here because several related documents get confused with the implementing instruction.
| Document | Role | Relationship to DoDI 5200.48 |
|---|---|---|
| EO 13556 | Created the government-wide CUI program | Higher authority the instruction implements |
| 32 CFR Part 2001 | NARA's CUI regulation | Regulatory framework the instruction operationalizes |
| DoDI 5200.48 | DoD CUI instruction | The implementing instruction itself |
| DoD CUI Registry | Authoritative category list | Referenced by the instruction for categories |
| Legacy FOUO/SBU labels | Prior marking regimes | Superseded by the CUI marking system |
| DoDI 5200.01 | Classified information program | Separate regime for classified material |
The table's logic is simple: only one row is the instruction, and every other row either authorizes it, operationalizes it, or covers a different regime.
Timeline of the program's development
| Point in time | Development |
|---|---|
| 2010 | EO 13556 establishes the government-wide CUI program and directs NARA to administer it |
| 2016 | NARA issues the CUI regulation, 32 CFR Part 2001, creating the framework |
| 2019 | DoD issues interim CUI policy guidance while finalizing its instruction |
| December 2020 | DoDI 5200.48 is issued, becoming the DoD implementing instruction |
| 2021 | DoD components begin transitioning markings, training, and systems |
| March 2023 | DoDI 5200.48 is updated, refining roles and procedures |
| Ongoing | Self-inspection, decontrol reviews, and DCSA oversight continue |
The key takeaway from the timeline: the instruction is recent relative to the executive order, which is why legacy markings and transition friction still appear in real documents. The 2023 update is the current version to cite.
Practical actions: how to answer and how to apply it
If the task is an exam question, the procedure is short. Read the stem for the verb: "implements" points to the DoD instruction. Confirm the number is 5200.48 rather than a nearby instruction. Eliminate distractors that describe the regulation, the executive order, or the classified program. Check whether the stem asks for the instruction or the manual; the instruction sets policy and the manuals carry detailed procedure.
If the task is real-world application, the steps are also concrete.
Identify whether the information is classified first; if it is, the CUI instruction does not apply. Check the CUI Registry for the correct category and its governing authority. Determine CUI Basic versus CUI Specified, and apply the stricter handling if specified. Apply the correct banner, category marking, and limited dissemination control marking. Confirm whether dissemination to a contractor or partner is permitted by the contract or agreement. Schedule review for decontrol when the governing authority expires.
The thresholds that matter are categorical rather than numeric: classified versus unclassified, basic versus specified, marked versus unmarked, and permitted versus prohibited dissemination. Each threshold flips the handling rules, so getting the category right is the whole game.
For training and compliance, the practical rule is to treat the instruction as the policy layer and the registry plus governing authority as the detail layer. A single mental model, "the instruction sets process, the authority sets substance," resolves most day-to-day questions.
Limitations and what the instruction cannot do
DoDI 5200.48 cannot resolve ambiguity that lives in the underlying authorities. If a statute or regulation is vague about a handling requirement, the instruction inherits that vagueness. It also cannot eliminate legacy documents, legacy habits, or local shortcuts; those are training and oversight problems.
The instruction is a policy document, not a technical control. It tells components what to achieve, not which encryption product to buy or which system configuration to use. Those choices come from component guidance and DCSA publications.
Version control is a real limitation for anyone citing the instruction. The 2020 issuance was updated in 2023, and further updates are possible. Cite the current version and check for changes before relying on a specific procedure. The instruction's own language points readers to the registry and governing authorities for category specifics, which means the instruction alone is never sufficient for a handling decision.
Finally, the instruction governs DoD. Organizations outside DoD encounter CUI through contracts, grants, and information-sharing agreements, and their obligations flow from those instruments and from 32 CFR Part 2001, not from the DoD instruction directly. That boundary is the single most common source of confusion when non-DoD partners ask which document "implements" CUI for them.
For high-stakes compliance or legal questions about handling specific information, this article is general educational information, not a legal opinion or an official policy determination. Consult your organization's security office or a qualified professional, and rely on the current DoDI 5200.48 text, the CUI Registry, and your component's guidance for actual handling decisions.