The DoD CUI Program is implemented by DoD Instruction 5200.48, "Controlled Unclassified Information (CUI)," issued March 6, 2020. That instruction is the department-level rule that adopts the national CUI framework set by 32 CFR Part 2002 and directs every DoD component to designate a CUI senior official, mark and handle unclassified information under the CUI banner, and report to the Department of Defense CUI Office. Everything else — component supplements, marking guides, training requirements — hangs off it.
What the 2020 instruction actually contains
DoD Instruction 5200.48 arrived on March 6, 2020, and it replaced a patchwork of legacy designations — For Official Use Only, Sensitive But Unclassified, and dozens of component-specific labels — with a single controlled unclassified information category. That replacement is the core of why the instruction exists. The document establishes policy, assigns responsibilities, and prescribes procedures for CUI across the Department of Defense, and it applies to the Office of the Secretary of Defense, the military departments, the Joint Staff, the combatant commands, and defense agencies and field activities.
The instruction has three functional pillars. First, it puts a named senior official in charge of each component's CUI program — the CUI Senior Official — and charges that person with implementing the program locally. Second, it sets marking and safeguarding duties so that a document marked CUI carries the required banner and a CUI category marking indicating which authority (for example, Privacy or Export Controlled) drives the protection. Third, it establishes oversight and reporting through the Department of Defense CUI Office and requires periodic assessment of component programs.
The instruction is deliberately slim. It does not reproduce the marking tables, the safeguarding matrices, or the decontrol timelines. Those live in the DoD CUI Registry, in component-level implementing instructions, and in training materials maintained by each component's CUI office. That is a common source of confusion: a reader who downloads the four corners of DoDI 5200.48 and expects a complete operating manual will find a policy document, not a procedures binder. The procedures are delegated.
One detail the top-ranking explainers often skip: the instruction is a DoD issuance under the 5000 series, which means it answers to DoD Directive 5000.01 and the department's general issuance system. It is not a statute and not a regulation in the Code of Federal Regulations sense. The binding legal force on contractors and the public comes from 32 CFR Part 2002, the National Archives and Records Administration's CUI regulation, and from the Federal Acquisition Regulation clauses that flow it down. Component officials enforce the instruction internally through the chain of command.
That distinction matters to anyone who has to cite the authority in a policy memo or a marking guide. For uniformed and civilian DoD personnel, DoDI 5200.48 is the governing instruction. For a defense contractor's information system, the operative driver is typically the DFARS 252.204-7012 clause and NIST SP 800-171, which reference CUI as the category of information to be protected. Same label, different legal hook.
Where 5200.48 sits in the issuance chain
The instruction sits at the top of a three-tier chain, and knowing which tier you are reading tells you how to use it. Tier one is the national framework: 32 CFR Part 2002, issued by the Information Security Oversight Office within the National Archives, defines what CUI is, requires agencies to designate a CUI program, and sets the government-wide marking standard. Tier two is the DoD instruction itself, which adopts the national framework for the department. Tier three is the component implementation — an Army, Navy, Air Force, or defense agency regulation or supplement that translates the instruction into local offices, forms, and training records.
The time gap between tiers is instructive. The national rule took effect in 2017 after the CUI program was established under Executive Order 13556 in 2010. DoD issued its implementing instruction in March 2020, roughly three years later. Components then took additional months to publish their own implementing guidance. That lag created a real-world window in which DoD personnel were still using legacy FOUO markings while the instruction was being staffed, and some component documents from 2020 and 2021 still carry mixed legacy-and-CUI marking errors as a result. Auditors who find FOUO on a document dated after a component's CUI implementation date have a finding.
The chain also explains a frequent citation error. Writers sometimes attribute the marking requirements to the instruction when the marking tables actually come from the CUI Registry maintained by the National Archives, or from the DoD CUI Program Office's marking guide. The instruction directs compliance; the registry specifies the labels and the category codes. If you are building a marking guide for a unit, you need both documents open at once.
A third-tier nuance: DoD components are permitted to issue supplements but not to relax the instruction. A component can add stricter handling requirements, designate additional category codes with proper authority, or set a shorter decontrol review cycle. A component cannot create a new CUI category, exempt itself from the senior official requirement, or permit legacy markings to continue past its implementation date. When a component supplement appears to conflict with 5200.48, the instruction controls and the supplement gets revised — a revision cycle that has played out across several components since 2020.
If you need the current text, pull it from the DoD Issuances site rather than a secondary PDF library, because the instruction has been administratively revised since issuance and the change record is tracked there. Confirm the current version and any administrative change on the DoD Issuances site before quoting a paragraph number in an official document.
The CUI senior official requirement, component by component
The instruction requires each DoD component to designate a CUI Senior Official with authority to implement the program. In practice those officials sit in different offices depending on the component, and that placement changes what the office can actually enforce. The table below summarizes the general pattern; verify the current office and incumbent for any component on that component's own CUI program page before routing correspondence.
| Component | Implementing issuance (check current version) | Where CUI authority typically sits |
|---|---|---|
| Department of the Army | Army regulation implementing DoDI 5200.48 | Deputy Chief of Staff, G-2 (intelligence and security) |
| Department of the Navy | SECNAV instruction implementing DoDI 5200.48 | Deputy Under Secretary for information management |
| Department of the Air Force | DAF instruction implementing DoDI 5200.48 | Director of information protection |
| Defense agencies and field activities | Agency-level instruction or policy memo | Agency security or information management office |
| Combatant commands | Command directive implementing DoDI 5200.48 | Command security office, J-2 or J-3 |
Placement matters because a CUI office hosted inside an intelligence or security directorate tends to emphasize classification-adjacent handling, while one hosted in an information management office tends to emphasize records and decontrol. Both are compliant with the instruction. The difference shows up in what each component's training emphasizes and how quickly decontrol reviews get scheduled.
The senior official requirement also creates a named point of accountability that did not exist under the legacy FOUO regime. Before 2020, an FOUO determination could be made informally by any originator, and there was no single office tracking the total volume of unclassified-but-sensitive information a component held. Under 5200.48, the senior official is expected to know the inventory, the training completion rates, and the self-inspection results. That is a meaningful governance shift: it converts an ad hoc practice into a managed program with a named owner and a reporting line.
A practical consequence for anyone writing to a component: route CUI program questions to the senior official's office, not to the records manager or the security manager individually. On a base with a joint tenant footprint, two components may each have a senior official, and a document originating in one component's workspace but stored in a shared system raises a question about which program owns the handling rules. The instruction's answer is that the originating component's program governs the marking, while the hosting component's system security rules govern storage.
Edge case worth flagging: a component that has not yet published its implementing issuance but is operating under the DoD instruction directly. That is permitted — the DoD instruction applies to the component regardless — but it creates ambiguity about local training records and local decontrol review. If you are auditing such a component, cite 5200.48 directly and note the absence of a component supplement as a finding rather than assuming the program is unimplemented.
Marking, safeguarding, and decontrol duties that flow from the instruction
Under 5200.48, an originating official has three duties on every CUI document: mark it, safeguard it, and set a decontrol date or event. Marking means the "CUI" banner at top and bottom of each page and a category marking indicating the authority — for example, "CUI//SP-PRIV" for privacy information or "CUI//SP-EXPT" for export-controlled technical data. The category codes themselves come from the CUI Registry, not the instruction, but the instruction requires their use.
Safeguarding under the instruction is deliberately scalable. The rule is that CUI must be protected using controls commensurate with the risk and the category, and the instruction points to the DoD CUI Registry for the specific handling requirements per category. This is not a one-size-fits-all "lock it in a safe" rule. Privacy CUI in a personnel file and export-controlled technical data on a program server carry different protection profiles, and both are CUI. That scalability is a feature, but it is also where most component-level implementation errors occur, because originators apply a blanket handling rule instead of looking up the category.
Decontrol is the duty most often neglected. The instruction requires that CUI be decontrolled when the underlying authority no longer applies — when a contract ends, when a privacy interest lapses, when an export license expires. DoD components are expected to set a specific decontrol date or event at the time of designation, not leave it open-ended. An open-ended CUI marking with no decontrol trigger is a finding under the instruction, and it is common in practice because originators mark documents years before anyone reviews them.
Here is where a computation helps. Suppose a component marks 4,000 documents a year as CUI and 25 percent carry no decontrol date. That is 1,000 documents a year entering an indefinite holding status. If a two-person decontrol review team can process 40 documents per day, clearing one year's backlog takes 25 working days — but the backlog regenerates every year at the same rate, so the team never catches up. That arithmetic, derived from the instruction's decontrol duty, is why component programs have moved toward default decontrol dates of five, ten, or twenty-five years depending on category rather than event-based marking alone.
One failure scenario worth knowing: a document marked CUI for a privacy reason, stored in a shared drive, whose decontrol event was the departure of the subject employee. The employee departs, nobody reviews the file, and the document sits marked CUI for years. When a records review later finds it, the file has been over-protected for longer than the authority justified — a compliance problem in the other direction from under-protection, and one the instruction's decontrol duty is designed to prevent.
Training obligations and what a self-inspection actually checks
The instruction requires CUI training for personnel who handle CUI, and it requires components to conduct self-inspections of their CUI programs. Neither requirement is spelled out to the hour or the checklist in the instruction itself; both are implemented at component level. The general pattern across DoD components is annual training delivered through the component's learning management system, with completion tracked by the CUI senior official's office. Many components tie completion to system access, so an uncompleted training module blocks access to a CUI repository.
Self-inspection under the instruction typically examines five things: whether documents are correctly marked with banner and category, whether the component has a current CUI senior official designated in writing, whether training completion meets the component's threshold, whether decontrol reviews are scheduled and performed, and whether incidents involving CUI are reported through the proper channel. The specific checklist belongs to each component. If you are preparing for one, request the component's self-inspection checklist from the CUI senior official's office rather than reconstructing it from the instruction.
A common training gap is category-specific knowledge. General CUI awareness training teaches the banner and the basic handling rule. It does not teach an originator which of the registry's categories applies to a given document, and that judgment is where mis-marking happens. Components with strong programs layer category-specific job aids on top of the general module, and those job aids — not the instruction — are what an originator should keep at hand.
Incident reporting is another component-level procedure that flows from the instruction. If CUI is lost, compromised, or found on an unauthorized system, the instruction requires reporting through the component's incident channel and to the DoD CUI Office as appropriate. The instruction does not set a universal reporting deadline; components do. Know your component's deadline before an incident happens, because the reporting clock starts when the loss is discovered, not when the report is drafted.
How 5200.48 relates to the legacy FOUO markings
The single most consequential thing 5200.48 did was retire FOUO. Before the instruction, "For Official Use Only" was the default label for unclassified-but-sensitive DoD information, and it was applied loosely, inconsistently, and often without any underlying statutory or regulatory authority. The instruction requires that unclassified information needing protection be categorized under a registry category with a proper authority, and it directs components to stop using FOUO and other legacy markings after their implementation dates.
That transition created a real records problem. Documents marked FOUO before the component's implementation date remain valid historical records; they are not retroactively mis-marked. Documents marked FOUO after the implementation date are non-compliant. The distinction turns on the component's implementation date, which varies — which is why the compliance question "is this FOUO marking a problem?" cannot be answered without knowing which component produced the document and when.
Other legacy labels met the same fate: Sensitive But Unclassified, Law Enforcement Sensitive in its pre-CUI form, and a long list of component-specific designations. Each was mapped to a registry category or retired. A component that still has an active local label not mapped to the registry has an implementation gap. Auditors look for exactly this.
The practical takeaway for a document originator is a decision sequence, not a label. Ask: does an authority — statute, regulation, or government-wide policy — require this information to be protected? If yes, find the registry category and mark accordingly. If no, the information is not CUI and should not be marked as such. The instruction's whole design is to force that question at the point of creation rather than permit a reflexive FOUO stamp.
The contractor and CUI overlap, and where the instruction stops
DoDI 5200.48 governs DoD personnel and DoD components. It does not, by itself, govern a defense contractor's information systems. Contractors encounter CUI through the Federal Acquisition Regulation and the Defense Federal Acquisition Regulation Supplement, chiefly DFARS 252.204-7012, which requires contractors handling covered defense information to implement NIST SP 800-171 security requirements and report cyber incidents. "Covered defense information" overlaps heavily with CUI but is a contract-law term, not a CUI-program term.
That overlap confuses people constantly. A contractor's security officer may be told "you must comply with DoDI 5200.48," which is imprecise. The accurate statement is that the contract clauses flow down the CUI marking and handling requirements, and the contractor's obligations are defined by the clause language and NIST SP 800-171, with the DoD instruction as the government-side policy the clause reflects. When a contractor and a government contracting officer disagree about a marking, the contract and the clause govern the dispute, not the instruction.
There is also a practical asymmetry in training. Government personnel train under their component's CUI program. Contractor personnel train under their company's program, which is built to satisfy the clause and NIST requirements, not the DoD instruction. The two training curricula overlap on marking and handling but diverge on incident reporting channels — government personnel report through their component, contractors report through their company's incident response and to the DoD cyber crime center per the clause. Assuming one channel serves both is a common error during joint incidents.
For a program office writing a contract, the useful move is to specify in the contract which CUI categories the effort will involve and what the marking expectations are, rather than citing the instruction number and leaving the contractor to infer. The instruction directs the government side; the contract must carry the requirement to the contractor side in enforceable language.
Common misreadings of the instruction and how to correct them
The most frequent misreading is that DoDI 5200.48 is a classification guide. It is not. CUI is unclassified information. The instruction deals with information that is not classified but still requires protection under an authority. If information is classified, the classification guides and Executive Order 13526 govern, not 5200.48. Mixing the two frameworks produces documents marked with both a classification banner and a CUI banner, which is an error — a classified document is not also CUI.
The second misreading is that the instruction itself lists every CUI category. It does not. Categories come from the CUI Registry. The instruction requires their use and delegates the list. A reader who searches the instruction for "what counts as CUI" will not find the answer there.
A third misreading treats the instruction as a contractor compliance document. As covered above, contractors are governed by contract clauses and NIST standards, with the instruction as the government-side referent. Citing the instruction to a contractor in a compliance letter is a category error unless the contract also cites it.
The fourth and most operationally damaging misreading is that marking a document CUI is a discretionary protective measure an originator may apply "to be safe." Under the instruction, CUI designation must rest on an authority. Over-marking is a compliance defect, not a conservative virtue, because it imposes handling costs, restricts information sharing, and creates decontrol obligations the originator may never discharge. Components with mature programs train originators to ask the authority question first and to mark only what the authority requires.
FAQ
Does DoDI 5200.48 apply to classified information?
No. The instruction covers unclassified information requiring protection under an authority, and classified information remains governed by the classification system under Executive Order 13526 and the associated DoD classification guides. A document carrying both a classification banner and a CUI banner is mis-marked; the correct handling for classified material is classification marking plus any special handling caveats, not the CUI banner. If you encounter a mixed marking, treat the classification marking as controlling for protection and flag the CUI banner as an error for correction.
Is DoDI 5200.48 the same as 32 CFR Part 2002?
No. The Code of Federal Regulations part is the National Archives' government-wide CUI rule, and the DoD instruction is the department's implementing policy that adopts it. The regulation binds agencies across the federal government; the instruction translates it for DoD components and personnel. For a policy citation, cite both when you need the legal authority and the DoD implementation, and cite the regulation alone when addressing a non-DoD audience.
What happens if a DoD document still carries an FOUO marking after implementation?
If the document was created before the producing component's CUI implementation date, the legacy marking is a valid historical artifact and should be retained as part of the record. If it was created after that date, the marking is non-compliant and should be corrected with a properly authorized CUI category marking, with the correction documented. The implementation date varies by component, so confirm which component produced the document and when before deciding which case applies.
Can a defense contractor be cited for violating DoDI 5200.48?
Not directly. The instruction governs DoD components and personnel. Contractor obligations flow through contract clauses such as DFARS 252.204-7012 and the NIST SP 800-171 requirements those clauses incorporate. A contracting officer enforces the contract, not the instruction. Contractors who receive a citation citing only the instruction should ask which contract clause is alleged to have been breached and request the specific clause language.
Who is the CUI senior official for a given DoD component?
The senior official is designated in writing by each component, and the office that hosts the role varies — intelligence and security directorates in some components, information management offices in others. The current incumbent and office are published on the component's CUI program page. Request the designation memorandum from the component's CUI office if you need to confirm authority before routing a program question or a self-inspection request.
How long can CUI remain marked before decontrol?
There is no single answer, because decontrol is tied to the underlying authority rather than a fixed clock. A privacy-based marking may decontrol when the subject's interest lapses; a contract-based marking when the contract closes; an export-controlled marking when the license expires. Components are expected to set a specific date or event at marking time. Open-ended markings with no trigger are a common audit finding, and components with mature programs use default maximum retention periods by category to prevent indefinite holding.
What is the difference between CUI and covered defense information?
CUI is the government-wide category for unclassified information requiring protection under an authority; covered defense information is a contract-law term in DFARS 252.204-7012 describing information a contractor must protect under NIST SP 800-171. The categories overlap substantially, and most covered defense information is CUI, but the terms come from different legal frameworks and are enforced through different mechanisms — the CUI program on the government side, the contract clause on the contractor side.
Does the instruction require a specific training course or number of hours?
No. The instruction requires CUI training for personnel who handle CUI and leaves the course, duration, and delivery to each component. Components typically deliver annual training through their learning management systems and track completion through the CUI senior official's office, with some tying completion to system access. For the specific requirement that applies to you, check your component's CUI program page rather than the instruction text, which sets the obligation but not the curriculum.