Skip to content
-
Subscribe to our newsletter & never miss our best posts. Subscribe Now!
  • https://www.facebook.com/
  • https://twitter.com/
  • https://t.me/
  • https://www.instagram.com/
  • https://youtube.com/
Cloud Security Tips Cloud Security Tips

What is cloud security

Cloud Security Tips Cloud Security Tips

What is cloud security

  • Home
  • About us
  • Contact us
  • Home
  • About us
  • Contact us
Subscribe
Close

Search

Server settings and security checklist on a screen — system hardening
Security Tips

Who Can Decontrol Controlled Unclassified Information (CUI)?

By admin
November 18, 2026 13 Min Read
0

CUI decontrol is the process of removing the Controlled Unclassified Information designation from information that no longer needs that protection. Only the designating agency can decontrol CUI. An authorized holder, a contractor, a subcontractor, or another recipient cannot decontrol CUI on their own, even if they believe the information is no longer sensitive. They can ask the designating agency to decontrol it, but the decision, and the authority to remove the markings, stays with the agency that designated it.

That short answer is the one most people are looking for, whether they are studying for a security exam, handling a government contract, or trying to share a document that is marked CUI. This guide explains who can decontrol CUI, who cannot, when decontrol happens, how to request it, and what must happen after decontrol. It is general information based on the CUI Program rules in 32 CFR Part 2002 and Department of Defense Instruction 5200.48, not legal advice. Always follow your agency CUI policy and your contract.

Table of Contents

Toggle
  • What Is Controlled Unclassified Information?
  • What Does Decontrol Mean?
  • Who Can Decontrol CUI?
  • Who Cannot Decontrol CUI?
  • When Does Decontrol Happen?
  • How to Request Decontrol of CUI
  • What Happens After CUI Is Decontrolled?
  • CUI Decontrol for Contractors and CMMC
  • Common Mistakes About CUI Decontrol
  • Decontrol, Declassification, and Downgrading: How They Differ
  • Frequently Asked Questions
    • Can a contractor decontrol CUI?
    • Can an authorized holder decontrol CUI?
    • Does CUI decontrol automatically after a certain number of years?
    • Is decontrolled CUI public?
    • What is the difference between CUI Basic and CUI Specified for decontrol?
    • Who do I contact to request CUI decontrol?
    • What should a decontrol request include?
  • Bottom Line

What Is Controlled Unclassified Information?

Controlled Unclassified Information, or CUI, is information that is not classified under Executive Order 13526, but still needs safeguarding or dissemination controls because a law, regulation, or government-wide policy requires it. Examples include export-controlled technical data, certain law enforcement information, privacy information, and unclassified information related to critical infrastructure, procurement, and defense.

CUI is divided into two types. CUI Basic is handled under the standard safeguarding and dissemination rules in 32 CFR Part 2002. CUI Specified is subject to additional handling controls because the underlying law or policy requires them, for example export controls. The distinction matters for decontrol, because Specified CUI may have extra steps, approvals, or restrictions before it can be decontrolled.

When information is designated as CUI, it is marked to show that it is CUI, which category or categories apply, and who designated it. A common marking is CUI, sometimes with a category such as CUI//SP-EXPT for export-controlled information, or CUI//PRVCY for privacy information. Those markings tell everyone who handles the information that it is not public, that it must be protected, and that it must not be shared outside authorized channels.

Decontrol is different from declassification. Declassification removes a classified designation from information that was classified as Confidential, Secret, or Top Secret. Decontrol removes a CUI designation from information that was never classified. The two processes are governed by different rules, and the people who can declassify classified information are not automatically the people who can decontrol CUI, although in some cases the same authority is involved.

What Does Decontrol Mean?

Decontrol means the information is no longer CUI. The CUI designation is removed, the CUI markings are removed or struck through, and the information no longer has to be safeguarded as CUI. That does not automatically mean the information is public, releasable to anyone, or free of all controls.

Decontrolled information may still be subject to other laws and controls. For example, information that was CUI because it was export-controlled may still be export-controlled after decontrol, and it may still need to be handled under export control rules. Personal information may still be protected by privacy law. A document may still be subject to copyright, to a non-disclosure agreement, or to a contract restriction. Decontrol removes the CUI controls, not every other control that might apply.

Decontrol is also different from destruction. Destroying a CUI document does not decontrol the information in it; it simply destroys that copy. Decontrol is a decision about the information itself, not about a single copy. And decontrol is different from downgrading, because CUI does not have classification levels to downgrade in the way classified information does.

For a broader explanation of how sensitive information is labelled and protected, see our Security Classification Guide: How to Classify Data and Protect What Matters Most. Classification, CUI, and handling rules work together, and confusing them is a common source of errors.

Who Can Decontrol CUI?

Under 32 CFR Part 2002 and DoD Instruction 5200.48, decontrol authority rests with the designating agency. In practice, that authority is exercised by three kinds of officials, depending on how the CUI was created and what kind of information it is.

Who can decontrol When they can act What they must do
The originator or creator When they created or designated the CUI Decide the information no longer meets the CUI criteria, document the decision, and notify holders
The Original Classification Authority, or OCA When the CUI was derived from, or is associated with, classified information Decontrol the CUI when the related classified information is declassified or the CUI no longer needs protection
A designated decontrol authority When agency policy names them, for example a senior agency official, a CUI program manager, or an official designated in the agency CUI policy Act within the scope of their written designation, and follow the agency decontrol procedure

Some agency guidance describes this as three parties: the originator, the Original Classification Authority, and a designated official. The exact titles vary by agency, but the principle is the same: the person who decontrols CUI must have been given that authority by the designating agency, in writing, for that information.

A senior agency official for CUI, a CUI program manager, and an information owner may all be involved in a decontrol decision, but involvement is not the same as authority. A program manager may recommend decontrol, a security officer may review the request, and a legal office may advise on the underlying law. The decontrol itself must be approved by the authorized official.

Who Cannot Decontrol CUI?

Just as important as who can decontrol CUI is who cannot. The following people and organizations do not have decontrol authority, even if they handle CUI every day.

Role Can they decontrol? What they can do instead
Authorized holder in a government office No Request decontrol from the designating agency, through their CUI program office
Prime contractor No Ask the contracting officer or government point of contact to seek a decontrol decision
Subcontractor or supplier No Raise the request with the prime contractor, who passes it to the government
FOIA or public records officer No, not by releasing the record Process a release request, and ask the designating agency whether the CUI can be decontrolled first
IT or records manager No Update markings and systems only after a written decontrol decision is received
Employee who created a derivative document No Ask the originator of the source CUI to consider decontrol
Anyone who finds CUI online No Report the apparent disclosure, and do not copy or share the information further

A common misunderstanding is that CUI becomes decontrolled automatically when it appears in public, when it is old, or when a contract ends. None of those events decontrols CUI by itself. Public availability, age, and contract end may be reasons to ask for decontrol, but the designation remains until the designating agency decontrols it. Treating information as decontrolled without that decision is a handling violation, and it can lead to a spill, a contract finding, or a loss of trust with the agency.

Another misunderstanding is that a contractor can decontrol CUI it created under a contract. In most contracts, CUI created by a contractor for the government is still designated by the government, or is designated under the contract terms. The contractor should check the contract, the CUI marking guidance, and the government point of contact before assuming it has decontrol authority. If in doubt, ask in writing and keep the answer.

When Does Decontrol Happen?

Decontrol happens when the information no longer meets the criteria for CUI. The most common triggers are:

  • The underlying law or policy changes: The law that required the information to be controlled is repealed, amended, or no longer applies to that information.
  • The information is no longer sensitive: The facts have changed, the program has ended, or the information is now publicly available through an official release.
  • A decontrol date or event arrives: Some CUI is marked with a decontrol date or a decontrol event, for example the end of a program or the publication of a report. When that date or event arrives, the agency should review and decontrol the information, if the conditions are met.
  • The related classified information is declassified: CUI that was derived from classified information may be decontrolled when the classified source is declassified, if there is no other reason to keep it as CUI.
  • A review finds the designation was wrong: A periodic review, an audit, or a challenge finds that the information never met the CUI criteria, or that it was marked CUI in error.
  • A request is approved: A holder, a contractor, or a member of the public asks for decontrol, and the designating agency agrees.

Some CUI has no decontrol date. That does not mean it is CUI forever. Agencies are expected to review CUI periodically and decontrol it when it no longer needs protection. Contractors and holders should not assume that old CUI is decontrolled, but they can, and should, ask for a review when a document is clearly out of date, superseded, or publicly available.

How to Request Decontrol of CUI

If you are an authorized holder or a contractor, you cannot decontrol CUI yourself, but you can make a clear, documented request. The following steps work for most agency and contract situations.

  1. Identify the information precisely: Give the document title, date, markings, control number if there is one, and the agency or office that designated it. Do not include the CUI itself in an unprotected email.
  2. Find the right point of contact: Start with your agency CUI program office, your contracting officer, or the government point of contact named in the contract. Ask who the designating agency is, if you do not already know.
  3. Explain why decontrol is appropriate: State which CUI criteria no longer apply, what has changed, and whether there is a decontrol date or event. Attach evidence, such as an official public release, a superseding document, or a change in law, without disclosing CUI outside authorized channels.
  4. Ask in writing, through authorized channels: Send the request through the approved system or email channel for CUI, and keep a copy of the request and any acknowledgement.
  5. Wait for a written decision: Do not remove markings, share the information more widely, or change handling until you receive a written decontrol decision. Verbal advice is not a decontrol decision.
  6. Record the decision: File the decontrol approval with the document, note the date and the authorizing official, and update any inventory, register, or tracking system.
  7. Notify other holders: Tell everyone who received the CUI that it has been decontrolled, so they can update their copies, markings, and systems.

If the request is denied, ask for the reason in writing and ask what would need to change for decontrol to be possible. A denial is not necessarily final; a later change in law, a new public release, or the end of a program may justify a new request.

What Happens After CUI Is Decontrolled?

A decontrol decision is not complete until the markings, the systems, and the people who hold the information are updated. The designating agency, or the holder acting on its written decision, should take the following steps.

  1. Remove or strike the CUI markings: Remove the CUI banner, portion markings, and control markings from the document, or strike them through and note the decontrol date and authority. Do not simply delete the marking and leave no record of what happened.
  2. Notify all holders: Tell every office, contractor, and subcontractor that received the CUI that it has been decontrolled. A holder who does not know about the decision will keep protecting, and restricting, information that no longer needs those controls.
  3. Update inventories and systems: Change the handling, storage, and sharing controls in document management, email, and collaboration systems. If a system automatically labels the document as CUI, update the label so it does not re-mark the document.
  4. Check for other controls: Confirm whether export controls, privacy law, copyright, or contract restrictions still apply. If they do, note them on the document so the next person who handles it does not assume it is unrestricted.
  5. Keep the record: File the decontrol decision, the authorizing official, the date, and the reason. That record is what an auditor, a contracting officer, or a future holder will ask for.
  6. Review derivative documents: Check documents, briefings, and reports that were based on the decontrolled information. They may also need their markings updated, or they may still contain other CUI that has not been decontrolled.

Decontrol does not mean the information must be published. It means it may be handled under normal, non-CUI rules, subject to any other controls that still apply. A decontrolled document can still be internal, confidential business information, or subject to a release review. Do not post it publicly, share it with a foreign person, or send it outside the organization until you have checked those other controls.

CUI Decontrol for Contractors and CMMC

Contractors who handle CUI under a Department of Defense contract face a practical problem: they must protect CUI under NIST SP 800-171, and under the Cybersecurity Maturity Model Certification (CMMC) program, but they cannot decontrol it themselves. That creates a clear rule for contract teams: protect it as CUI until the government says otherwise, in writing.

Do not decontrol CUI because a contract ended, because a system was migrated, or because a document is old. At the end of a contract, return or destroy CUI as the contract requires, and ask the contracting officer about any information you think should be decontrolled. Do not keep a copy marked as decontrolled without a government decision.

Use data discovery tools and inventories to find where CUI lives in your systems before you ask for decontrol. If you cannot find all the copies, you cannot notify all the holders, and the decontrol will be incomplete. That is a common finding in contract reviews and audits.

For export-controlled CUI, decontrol is especially sensitive. Information that is subject to the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR) may still be controlled after it is decontrolled as CUI. Our guide to What Is ITAR? explains why export-controlled technical data needs a separate review before it can be shared, even with a decontrol decision in hand.

Common Mistakes About CUI Decontrol

Mistake Why it is wrong What to do instead
Removing markings because the information is old Age alone does not decontrol CUI Ask for a periodic review and a written decision
Assuming a public leak decontrols CUI An unauthorized disclosure does not decontrol information Report the disclosure and keep protecting the information
Treating decontrol as public release Decontrolled information may still be restricted Check export, privacy, and contract controls before sharing
Decontrolling a whole file when only part is decontrolled Other parts may still be CUI Decontrol only the portions named in the decision, and re-mark the rest
Not notifying other holders Other holders will keep treating it as CUI, or will share it wrongly Notify every recipient, in writing, with the decision date
Relying on verbal approval Verbal approval is hard to prove and may be misunderstood Get the decision in writing, with the authorizing official named
Confusing decontrol with declassification They are different processes, with different authorities Use the CUI decontrol procedure, not the classified declassification procedure

Decontrol, Declassification, and Downgrading: How They Differ

These three terms are often confused, and using the wrong one in a request or a marking can delay a decision.

Process Applies to Who decides Result
Decontrol CUI Designating agency, through the originator, OCA, or designated authority Information is no longer CUI
Declassification Classified information Original Classification Authority, or an authorized declassification authority Information is no longer classified
Downgrading Classified information Original Classification Authority Classification level is lowered, for example from Secret to Confidential

CUI has no classification level, so it cannot be downgraded. If a document contains both classified information and CUI, the two parts may need separate decisions: the classified part may need declassification, and the CUI part may need decontrol. A document that is declassified may still contain CUI, and a document that is decontrolled may still contain classified information in another portion. Check each portion separately.

Frequently Asked Questions

Can a contractor decontrol CUI?

No. A contractor, subcontractor, or supplier cannot decontrol CUI. Only the designating agency can decontrol it. A contractor can request decontrol through the contracting officer or government point of contact.

Can an authorized holder decontrol CUI?

No. An authorized holder can use, store, and share CUI as authorized, and can request decontrol, but cannot remove the CUI designation or markings without a written decision from the designating agency.

Does CUI decontrol automatically after a certain number of years?

Not automatically, unless a decontrol date or event was set when the information was designated. Some CUI is reviewed periodically, but it remains CUI until the designating agency decontrols it.

Is decontrolled CUI public?

Not necessarily. Decontrol removes the CUI controls, but export controls, privacy law, copyright, and contract restrictions may still apply. Check those controls before sharing decontrolled information publicly or with a foreign person.

What is the difference between CUI Basic and CUI Specified for decontrol?

CUI Basic follows the standard rules in 32 CFR Part 2002. CUI Specified is subject to additional handling controls from the underlying law or policy, so decontrol may need extra approvals or steps. Check the category and the agency policy for that category.

Who do I contact to request CUI decontrol?

Start with your agency CUI program office, your contracting officer, or the government point of contact named in your contract. They can identify the designating agency and the correct request channel.

What should a decontrol request include?

Identify the information precisely, state why it no longer meets the CUI criteria, give any decontrol date or event, and attach evidence without disclosing CUI outside authorized channels. Ask for a written decision, and keep a copy.

Bottom Line

Only the designating agency can decontrol Controlled Unclassified Information. Within that agency, decontrol is exercised by the originator, the Original Classification Authority where the CUI is tied to classified information, or an official designated in the agency CUI policy. Authorized holders, contractors, and other recipients cannot decontrol CUI themselves, even when the information is old, when a contract has ended, or when it appears to be public. They can, and should, ask for decontrol in writing, through the proper channel, with a clear reason and evidence. When decontrol is approved, remove the markings, notify every holder, update your systems and inventories, check for export, privacy, and contract controls that may still apply, and keep the written decision on file. That disciplined approach protects the information while it is CUI, and it makes sure decontrol, when it happens, is complete, documented, and defensible.

Author

admin

Follow Me
Other Articles
Black wireless router with multiple antennas, representing the Wi-Fi access points that use Hotspot 2.0 (Passpoint)
Previous

SIP ALG: What It Is, Why It Breaks VoIP Calls, and When to Disable It

Blue shield emblem with a padlock, representing compliance risk assessment and information security governance
Next

ISO 27001 Compliance: What It Is, How to Get Certified, and How to Stay Compliant

No Comment! Be the first one.

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Recent Posts

    • WAN Interface Card: What It Is, Types, and How It Works
    • Firewall for PCI Compliance: Requirements, Rules, and Best Practices
    • Examples of PHI: Protected Health Information Explained with Real Examples
    • Define Obfuscation: What It Is and How It Protects Code and Data
    • What Is a NIC Network? Network Interface Card Explained

    Recent Comments

    1. Examples of PHI: Protected Health Information Examples on BAA Agreement: What Is a HIPAA Business Associate Agreement and Who Needs One?
    2. Define Obfuscation: Code and Data Obfuscation Explained on What Is Data at Rest? Meaning, Examples and How to Protect It
    3. What Is a NIC Network? Network Interface Card Explained on APIPA: What It Is, the 169.254 Address Range, and How to Fix It
    4. WAN Interface Card: What It Is, Types, and How It Works on What Is a NIC Network? Network Interface Card Explained
    5. Firewall for PCI Compliance: Requirements and Best Practices on What Is a Network Firewall? Types, Features and How It Works

    Archives

    • November 2026
    • October 2026
    • September 2026
    • August 2026
    • July 2026
    • June 2026
    • May 2026
    • February 2026

    Categories

    • Blog
    • Business
    • Security Tips
    • Tech
    • Travel
    • Uncategorized
    Copyright 2026 — Cloud Security Tips. All rights reserved. Blogsy WordPress Theme

    Powered by CookieAdmin
    Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
    None
    Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
    None
    Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
    None
    Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
    None
    Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
    None
    Powered by CookieAdmin