The answer to what is the purpose of the isoo CUI registry: it is the government-wide catalog of Controlled Unclassified Information categories, established under Executive Order 13556 with the National Archives and Records Administration as Executive Agent.
This guide is written for defense contractors, subcontractors, and compliance leaders at regulated businesses that handle federal information and need to understand how the CUI registry drives their security obligations. We cover what the registry actually is, how it connects to NIST SP 800-171 and CMMC, what marking and handling rules apply, and how to evaluate your own CUI exposure. It reflects the day-to-day experience of Petronella Technology Group, Inc., a Cyber AB Registered Provider Organization that prepares contractors for CMMC assessment.
Key Takeaways
- The National Archives and Records Administration is the Executive Agent for the CUI Program, and 32 CFR Part 2002 is the government-wide rule that implements it.
- Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation; contractors handling only Federal Contract Information must meet the 15 basic safeguarding requirements of FAR 52.204-21.
What the CUI Registry Actually Is and What It Contains
The Two Broad Types: CUI Basic and CUI Specified
- CUI Basic. Information that requires uniform controls across the government, protected at a moderate confidentiality baseline.
The distinction matters operationally.
The Governing Rules Behind the Registry
Three instruments work together:
- Executive Order 13556 established the CUI Program and named NARA as Executive Agent.
- 32 CFR Part 2002 is the government-wide rule that implements the program, including how agencies designate, mark, and handle CUI.
- DoD Instruction 5200.48, issued March 6, 2020, implements the CUI program inside the Department of Defense, which is the department most defense contractors deal with.
If you want to read the source rules directly, the full text of the CMMC Program rule and its structure is available at https://www.law.cornell.edu/cfr/text/32/part-170, and NIST's publication page for the CUI protection requirements is at https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final.
What Is the Purpose of the ISOO CUI Registry for Contractors?
The Registry Determines Your Security Baseline
Here is the chain, end to end. That information arrives on your systems under a contract. Under DFARS 252.204-7012, adequate security on every covered contractor information system means implementing the 110 controls of NIST SP 800-171. If the material were only Federal Contract Information with no CUI, your obligation would instead be the 15 basic safeguarding requirements of FAR 52.204-21, with an annual self-assessment and an annual senior official affirmation to DoD under CMMC Level One.
The Registry Connects to CMMC Levels
- Level One covers Federal Contract Information: the 15 basic safeguarding requirements from FAR 52.204-21, an annual self-assessment, and an annual senior official affirmation.
- Level Two covers Controlled Unclassified Information: all 110 practices of NIST SP 800-171 Rev 2, organized into 14 domains, with a C3PAO assessment for most programs, triennial reassessment, and annual senior official affirmation.
- Level Three adds selected controls from NIST SP 800-172 on top of Level Two and is assessed by the government through DCMA DIBCAC, not a C3PAO.
When DFARS 252.204-7021 appears in a contract or solicitation, the contractor must hold a valid CMMC certificate at the specified level before award. On July 13, 2026, the DoD CIO announced the suspension of the 2026-11-10 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice. Our 2026 CMMC Compliance Guide walks through the full timeline.
The Registry Connects to SPRS Scores and Flow-Down
Two DFARS clauses extend the registry's reach deeper into your business development and subcontracting:
- DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in SPRS when an offer is submitted. That score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points. DFARS 252.204-7020 governs how the assessment is conducted and gives DoD access to verify it.
- DFARS 252.204-7012 must be flowed down to subcontractors, including for commercial products and services, when performance involves covered defense information. A subcontractor reports its own incidents to DoD and gives the report number to the next higher tier.
Ask. The Department of Justice's Civil Cyber-Fraud Initiative has produced settlements including Verizon at $4.09M in 2023, Penn State at $1.25M in 2024, Raytheon at $8.4M in May 2025, and Georgia Tech at $875K on September 30, 2025.
How the Registry Works in Practice: Marking and Handling
Understanding the registry's purpose also means understanding how its categories show up on the documents you handle every day.
Banner Markings and Designation Indicators
32 CFR 2002.20 requires the CUI banner marking on every page that contains CUI, along with a designation indicator naming the designating agency. 32 CFR 2002.16 allows only the designating agency to apply limited dissemination controls.
One confusion we resolve on nearly every engagement: DoD Instruction 5230.24 governs distribution statements on technical documents, and a distribution statement does not satisfy CUI marking requirements. The two are applied in parallel. A document can carry a distribution statement and still be CUI.
Encryption Requirements Flow From the CUI Baseline
NIST SP 800-171 requires FIPS-validated cryptography to protect the confidentiality of CUI. Strong but unvalidated encryption does not meet the requirement. VDI endpoints are out of scope only in a KVM-only configuration.
Incident Reporting When CUI Is Affected
If a cyber incident affects covered defense information, DFARS 252.204-7012 requires you to report it to DoD within 72 hours of discovery through the DoD reporting portal at dibnet.dod.mil. After a reported incident, you must preserve images of affected systems and monitoring data for at least 90 days, submit isolated malicious software to the government, and hold cloud providers to a FedRAMP Moderate baseline.
Comparing Your Obligations by Information Type
| Question | FCI Only (No CUI) | CUI Basic | CUI Specified |
|---|---|---|---|
| Where the category comes from | FAR 52.204-21 definition of Federal Contract Information | ||
| Security baseline | 15 basic safeguarding requirements | All 110 controls of NIST SP 800-171 Rev 2 | All 110 controls of NIST SP 800-171 Rev 2, plus any specified handling controls |
| CMMC level | Level One: annual self-assessment and annual senior official affirmation | Level Two: C3PAO assessment for most programs, triennial reassessment, annual affirmation | Level Two, with handling per the underlying authority |
| Marking on documents | Not CUI-marked | CUI banner marking on every page plus designation indicator per 32 CFR 2002.20 |
How to Evaluate Your Own CUI Exposure
Step One: Inventory What You Hold
Go contract by contract.
Step Two: Decide Whether to Enclave
Enclaving CUI into a narrowly scoped boundary, for example a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across your entire enterprise network. It reduces audit surface, shortens timelines, and lowers ongoing cost.
Step Three: Build the Program the Registry's Requirements Demand
If you hold CUI, the work is the full NIST SP 800-171 control set: a system security plan covering all 110 controls with owners and evidence pointers, 14 control-family policies plus an incident response plan, a live POA&M, and a baselined SPRS score. POA&Ms are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout. A typical Level Two readiness engagement runs 12 to 14 weeks for a mid-size contractor, and the path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on starting posture and CUI environment complexity.
First, only a C3PAO can issue a CMMC Level Two certificate; an RPO such as Petronella Technology Group, Inc. prepares a contractor but does not perform certification assessments for any organization. Second, compliance is continuous after certification: the SSP is a living document, the POA&M is reviewed at least quarterly, and reassessment occurs every three years.
A Step-by-Step Plan to Put the Registry to Work in Your Compliance Program
The plan below reflects what we walk through with defense contractors during the Discovery and Gap Analysis phases of a typical readiness engagement, which for a mid-size contractor runs 12 to 14 weeks: Discovery in week 1, Gap Analysis in weeks 2 through 4, a Remediation Sprint in weeks 5 through 12, and C3PAO Readiness Handoff in weeks 13 and 14.
- Inventory your contracts and identify who designated the CUI.
- Classify what you hold as CUI Basic or CUI Specified. The government-wide rule divides CUI into these two categories. CUI Basic carries uniform controls at a moderate confidentiality baseline. CUI Specified carries handling controls written into the underlying law, regulation, or policy.
- Check your markings against the rule. 32 CFR 2002.20 requires the CUI banner marking on every page that contains CUI, along with a designation indicator naming the designating agency.
- Do not confuse distribution statements with CUI markings. DoD Instruction 5230.24 governs distribution statements on technical documents, and a distribution statement does not satisfy CUI marking requirements. The two are applied in parallel, not interchangeably.
- Scope your environment around CUI. Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation; every DoD contractor handling Federal Contract Information must meet the FAR 52.204-21 baseline of 15 basic safeguarding requirements. Enclaving CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across your entire enterprise network.
- Map your controls to NIST SP 800-171 Revision 2. Level Two of CMMC 2.0 aligns directly with all 110 practices of that framework, organized into 14 domains. Build a system security plan covering all 110 controls with named owners and evidence pointers, plus the 14 control-family policies and an incident response plan.
- Score yourself and post it. DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in the Supplier Performance Risk System when an offer is submitted. The score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points. DFARS 252.204-7020 governs how the assessment is conducted and gives DoD access to verify it.
- Track gaps in a live POA&M. Under the CMMC Program rule, POA&Ms are allowed only for "not met" requirements within the limits of 32 CFR 170.21, with a 180-day closeout.
- Prepare for third-party assessment. Only a C3PAO can issue a CMMC Level Two certificate. The C3PAO submits results to eMASS and the certificate is stored in SPRS. A mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist round out a readiness handoff.
The path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on your starting security posture and the complexity of your CUI environment.
The Most Common Mistakes We See (and How to Avoid Them)
- Assuming encryption alone solves everything. NIST SP 800-171 requires FIPS-validated cryptography to protect the confidentiality of CUI; strong but unvalidated encryption does not meet the requirement. DoD CIO FAQ clarifications add that encrypted CUI is still CUI, and encrypted CUI in a cloud still needs FedRAMP Moderate or an equivalency.
- Confusing distribution statements with CUI markings. As noted above, a distribution statement under DoD Instruction 5230.24 runs in parallel with CUI marking requirements.
- Letting subcontractor flow-down lapse. DFARS 252.204-7012 must be flowed down to subcontractors, including for commercial products and services, when performance involves covered defense information. A subcontractor reports its own incidents to DoD and gives the report number to the next higher tier.
- Waiting until after an incident to set up reporting. DFARS 252.204-7012 requires a cyber incident affecting covered defense information to be reported to DoD within 72 hours of discovery through the reporting portal at dibnet.dod.mil, which requires a DoD-approved medium assurance certificate obtained in advance. After a reported incident, you must preserve images of affected systems and monitoring data for at least 90 days and submit isolated malicious software to the government.
- Treating the SSP as a one-time document. The system security plan is a living document and the POA&M is reviewed at least quarterly, with re-assessment every three years.
- Over-scoping the environment. Enclaving into a narrow boundary reduces audit surface, shortens timelines, and lowers ongoing cost.
The DOJ Civil Cyber-Fraud Initiative has made these gaps a legal risk, not just a compliance one, with settlements including Verizon at $4.09M in 2023, Penn State at $1.25M in 2024, Raytheon at $8.4M in May 2025, and Georgia Tech at $875K on 2025-09-30.
How to Choose a Provider: The Questions to Ask
- Are you an RPO or a C3PAO? Only a C3PAO can issue a CMMC Level Two certificate. An RPO prepares your organization but cannot conduct the assessment or issue a certificate. You can verify RPO and C3PAO listings at the Cyber AB marketplace, cyberab.org/marketplace.
- Who exactly will work on our engagement, and what credentials do they hold?
- What does your readiness engagement actually deliver? A credible deliverable set includes an SSP covering all 110 NIST SP 800-171 controls with owners and evidence pointers, 14 control-family policies plus an incident response plan, acceptable use and media protection policies, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist with warm introductions.
- How will you scope our CUI boundary? A narrowly scoped boundary is one of the biggest drivers of quote variance, and
- What is the timeline, honestly? A typical Level Two readiness engagement runs 12 to 14 weeks for a mid-size contractor, but the full path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on starting posture and CUI environment complexity.
- What happens after the assessment? Compliance is continuous. Look for a maintenance model covering quarterly control reviews, policy refresh, training, and incident response capacity, with the POA&M reviewed at least quarterly.
How Petronella Technology Group, Inc. Helps
Petronella Technology Group, Inc. is a Cyber AB Registered Provider Organization, RPO #1449. We prepare organizations for assessment; we are not a C3PAO and we do not perform CMMC certification assessments for any organization. Authorized C3PAOs conduct Level Two certification assessments, and we do not promise "guaranteed pass" outcomes.
Every engineer assigned to a defense client holds the CMMC Registered Practitioner (CMMC-RP) credential: Blake Rea, Justin Summers, Jonathan Wood, and Craig Petronella. Craig Petronella also holds CCNA, CWNE, NC Licensed Digital Forensic Examiner license #604180, and an MIT AI certificate, and has 30+ years of experience since founding the company in 2002.
For CUI and CMMC work specifically, we run a structured readiness engagement: Discovery in week 1, Gap Analysis in weeks 2 through 4, a Remediation Sprint in weeks 5 through 12, and C3PAO Readiness Handoff in weeks 13 and 14. Deliverables include the SSP, the policy set, a live POA&M, a mock assessment, a baselined SPRS score, and a C3PAO shortlist. Post-certification, most clients continue under a maintenance retainer covering quarterly control reviews, policy refresh, training, and incident response capacity.
If you need senior security leadership to own the program, our CMMC consulting team can scope a fixed-fee engagement, often within two business days of a twenty-minute discovery conversation.
Related guides from Petronella Technology Group, Inc.
Related reading
- CMMC Compliance: Gap Assessment, Levels 1 to 3
- What DoD Instruction Implements CUI? DoDI 5200.48
- CUI Handling for DoD Subcontractors: Sanctions & Flowdown
- CUI Handler Field Manual: 9 Questions Answered (2026)
- CMMC Pharmacy Compliance Guide for Secure Healthcare Data
Frequently Asked Questions
What is the purpose of the ISOO CUI registry?
It was established under Executive Order 13556, signed 2010-11-04, with the National Archives and Records Administration as the Executive Agent and 32 CFR Part 2002 as the government-wide rule.
What is the purpose of the ISOO CUI registry for defense contractors?
Those answers drive your obligations under DFARS 252.204-7012, which requires adequate security defined as the 110 controls of NIST SP 800-171 on every covered contractor information system.
How does the CUI registry relate to CMMC Level Two?
CMMC Level Two covers Controlled Unclassified Information and requires all 110 practices of NIST SP 800-171 Revision 2, organized into 14 domains, with a C3PAO assessment for most programs, triennial reassessment, and annual senior official affirmation.
Do I need to worry about CUI if I only handle Federal Contract Information?
No, the full NIST SP 800-171 obligation applies only to contractors that receive or generate CUI. Every DoD contractor handling Federal Contract Information must meet the FAR 52.204-21 baseline of 15 basic safeguarding requirements, with an annual self-assessment and an annual senior official affirmation to DoD.
What is the difference between CUI Basic and CUI Specified?
32 CFR Part 2002 divides CUI into CUI Basic, which carries uniform controls at a moderate confidentiality baseline, and CUI Specified, which carries handling controls written into the underlying law, regulation, or policy.
Where does the CMMC program stand right now?
The CMMC Program rule, 32 CFR Part 170, took effect 2024-12-16, and the 48 CFR acquisition rule took effect 2025-11-10. On 2026-07-13 the DoD CIO announced the suspension of the 2026-11-10 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice.
Questions about your CUI exposure or CMMC readiness? Call Penny, our AI assistant, at 919-348-4912, or use our contact form to schedule a free 30-minute scoping consultation with a CMMC Registered Practitioner.
Online course from the Petronella Technology Group, Inc. Training Academy
CMMC Level 2 Security Awareness: Common Core
Foundational CMMC Level 2 awareness for all roles: CUI, insider threat, phishing, passwords and MFA, physical security, and incident reporting.
Price: $49
Free, practical, and specific to regulated environments. We will email it to you.
No spam. Unsubscribe anytime.