CUI Handling for DoD Contractors: Marking, Storage and Controls
Published · Last updated · 9 min read

CUI handling for a DoD contractor means identifying controlled unclassified information when it arrives, keeping it only on systems that meet NIST SP 800-171, sharing it only with authorized people, and destroying it properly when the work ends. The rules come from the federal CUI program in 32 CFR Part 2002, DoD's CUI policy, and DFARS 252.204-7012 in your contract.
Key takeaways
- CUI is government information that needs safeguarding under a law, regulation or policy but is not classified. The National Archives keeps the official list of categories.
- Defense contractors usually receive CUI as drawings, specifications, technical data or contract documents, and it should arrive marked.
- Systems that store, process or transmit CUI must meet the 110 requirements of NIST SP 800-171 Revision 2 under DFARS 252.204-7012.
- The biggest risks are CUI spreading into email, personal devices and unmanaged cloud storage, and staff who do not recognize it.
- A smaller, well-defined CUI boundary is easier to protect, document and assess than a whole-company scope.
What is CUI and where does a contractor run into it?
Controlled unclassified information is information the government creates or possesses, or that a contractor creates or possesses for the government, that a law, regulation or government-wide policy requires to be protected, but that is not classified. The program is defined in 32 CFR Part 2002, and the National Archives (NARA) maintains the CUI Registry category list.
For defense contractors, the most common categories are controlled technical information (engineering drawings, specifications, test data and software), export-controlled information, and contract or procurement information. CUI usually arrives from a prime or a government program office through email, a file-sharing portal or a physical drawing package. It can also be created by you, for example a design you develop under the contract.
DoD's own policy, DoD Instruction 5200.48, sets how the department marks and handles CUI, and your contract carries those expectations through DFARS 252.204-7012. Our DFARS 7012 guide covers the clause itself.
How do you recognize and mark CUI?
CUI should carry a banner marking, at minimum "CUI" at the top of each page, and DoD documents also include a designation indicator block that names the controlling office. Some categories are "CUI Specified," which means the underlying law adds handling rules, such as limits on dissemination. Others are "CUI Basic."
Three practical rules keep marking under control:
- Do not guess. If a document looks sensitive but is unmarked, ask the prime or contracting officer. Marking decisions belong to the government or the originator.
- Keep markings on derivatives. If you copy CUI into a new drawing, quote or report, the new document carries the marking too.
- Train people to spot it. Engineers, estimators, purchasing staff and shop leads handle CUI more often than IT does. Short, role-specific training works better than a long annual course, and our security awareness training can be tailored this way.
Where should CUI be stored and processed?
Only on systems inside your defined CUI boundary that meet NIST SP 800-171. In practice, the decision is between protecting the whole company network and building a smaller enclave, a separate set of accounts, devices and cloud storage used only for CUI work.
An enclave suits companies where CUI touches a few people or programs. A whole-company scope suits companies where CUI is everywhere, such as a machine shop where drawings reach every work cell. Either way, write the boundary down in your system security plan and make it match reality.
Cloud storage needs particular care. Under DFARS 252.204-7012, a cloud provider that stores or processes covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline and support the clause's incident reporting rules. That is why many contractors evaluate Microsoft's government clouds; our GCC High guide and GCC High migration service explain the options, including when GCC High is more than you need.
What technical controls matter most for CUI?
All 110 requirements in NIST SP 800-171 Revision 2 apply to systems in scope, but a handful do most of the work of keeping CUI contained:
- Access control. Limit CUI folders and systems to named people who need them, and review that list when people change roles or leave.
- Multi-factor authentication. Required for network access to privileged accounts and for network access to non-privileged accounts.
- FIPS-validated encryption. When cryptography protects the confidentiality of CUI, it must be FIPS-validated, including on laptops, removable media and data in transit.
- Audit logging. Keep logs that show who accessed CUI and review them. A 24/7 managed SOC can watch those logs continuously.
- Media protection and sanitization. Control USB use, mark media that holds CUI, and sanitize or destroy drives and paper before disposal using methods consistent with NIST SP 800-88.
- Configuration and patching. Keep a baseline for devices in scope and apply security updates on a schedule.
How should contractors share CUI with suppliers and partners?
Share CUI only with people and companies that have a lawful government purpose and the right contract clauses. For subcontractors, that means flowing down DFARS 252.204-7012 and confirming the supplier has a current NIST SP 800-171 assessment in SPRS.
Use an approved, access-controlled file-sharing method rather than ordinary email attachments, set expiration on shared links, and keep a record of what was sent to whom. Export-controlled technical data adds another layer: it may not be shared with foreign persons without authorization, even inside your own company. Our ITAR compliance support page covers that overlap.
What evidence do primes and assessors ask for?
Expect requests for a current system security plan, a plan of action for open items, your SPRS score and date, and proof that key controls work: an access list for CUI locations, MFA settings, encryption settings, log review records, training records and media sanitization records.
The evidence matters because your SPRS score and any CMMC affirmation are statements to the government. DoD continues to rely on self-assessments while the CMMC Phase 2 third-party assessment requirement is suspended, as our CMMC timeline explains, so accurate records protect you. Our SPRS scoring guide covers how the score is calculated.
What are the most common CUI handling mistakes?
- CUI in everyday email. Drawings forwarded to personal or unmanaged accounts move CUI outside the boundary.
- Unmanaged devices. Personal phones and home computers syncing CUI folders are outside your controls.
- Consumer file sharing. Free cloud storage accounts rarely meet the FedRAMP Moderate equivalency requirement.
- Paper and media left behind. Printed drawings and old drives need the same care as files.
- A boundary that exists only on paper. If the system security plan says CUI lives in one place but staff save it everywhere, the plan is wrong.
A cybersecurity risk assessment that traces where CUI actually goes is usually the fastest way to find these problems.
What should a written CUI handling procedure include?
A short written procedure turns the controls above into daily habits. It does not need to be long, but it should answer the questions staff actually face:
- How CUI arrives, who receives it, and where it is saved first.
- Which folders, systems and devices are approved for CUI, and which are not.
- How to mark new documents that contain CUI, including quotes, travelers and inspection reports.
- How to send CUI to a supplier or customer, and what to do if it is sent to the wrong person.
- How to print, store, and destroy paper copies and removable media.
- Who to call when someone suspects CUI was exposed, so the 72-hour reporting clock in DFARS 252.204-7012 can be met.
Review the procedure with each new hire who will touch CUI, and update it whenever you add a system or change a process.
How can a small contractor keep CUI handling under control?
Keep the boundary small, write it down, and review it. Many small contractors start by moving all CUI work into one controlled environment, training the people who handle CUI, and turning on MFA, encryption and logging there first. From that base, the system security plan, SPRS score and supplier flow-down become manageable.
NorthStar helps defense contractors scope CUI, configure controls and keep evidence current through our DoD and CMMC services. We do not perform official CMMC assessments. To see where you stand today, start with our free security check, and browse more resources for DoD contractors.
What else do defense contractors ask about CUI handling?
Is all information from DoD considered CUI?
No. Only information that falls into a CUI Registry category and is required by law, regulation or policy to be protected is CUI. Federal contract information that is not CUI falls under the basic safeguarding rules in FAR 52.204-21.
Can we store CUI in commercial Microsoft 365?
It depends on whether the environment meets the FedRAMP Moderate equivalency requirement in DFARS 252.204-7012 and supports its incident reporting rules, and on whether you also handle export-controlled data. Many contractors evaluate GCC or GCC High for this reason.
How should we destroy CUI?
Use methods that make the information unreadable and unrecoverable, such as approved shredding for paper and sanitization or destruction for media consistent with NIST SP 800-88. Keep a record of what was destroyed.
Do subcontractors have to protect CUI the same way?
Yes. When a subcontract involves covered defense information, the prime must flow down DFARS 252.204-7012, and the subcontractor must meet NIST SP 800-171 and report incidents.
Sources
- 32 CFR Part 2002, Controlled Unclassified Information
- National Archives CUI Registry category list
- NIST SP 800-171 Revision 2
- NIST SP 800-88, Guidelines for Media Sanitization
- DFARS 252.204-7012
Industry Resources
DoD & CMMC Compliance Support
NorthStar helps defense contractors scope CUI, configure NIST SP 800-171 controls and keep their compliance evidence current.
Learn More →About the author

Ken Satkunam, CISM
President & Founder, NorthStar Technology Group
Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.