WEBVTT

00:00:14.890 --> 00:00:29.499
<v Host>Today we’re looking at a phrase you’ve probably seen on a government contract or a defense document-"information may be CUI in accordance with". That wording can feel vague, but it actually signals a specific set of obligations and a chain of authority.

00:00:29.762 --> 00:00:50.488
<v Analyst>Exactly. CUI stands for Controlled Unclassified Information, a program that started with Executive Order 13556, signed November 4, 2010. The order created a national framework, and 32 CFR Part 2002 is the government-wide rule that implements it.

00:00:50.834 --> 00:00:57.532
<v Host>So the origin is federal, not just a contractor’s discretion. But what does that mean in practice for a defense contractor?

00:00:58.026 --> 00:01:19.073
<v Analyst>When a contractor receives or generates information that falls under a law, regulation, or policy that designates it as CUI, the contractor must follow the full safeguarding requirements of NIST SP 800-171. That includes the 110 controls that cover access, audit, configuration, and more.

00:01:19.348 --> 00:01:23.887
<v Host>That’s a big jump from the 15 basic safeguards for Federal Contract Information.

00:01:24.199 --> 00:01:47.166
<v Analyst>It is. The 15 safeguards are governed by FAR 52.204-21 and are the baseline for any contractor handling federal contract information, or FCI. CUI, however, triggers the 110 controls, and it also activates DFARS clauses and, if the contract calls for it, CMMC requirements.

00:01:47.495 --> 00:01:53.671
<v Host>Let’s break down the marking requirements. I hear that every page of a CUI document must have a banner.

00:01:53.953 --> 00:02:12.045
<v Analyst>Under 32 CFR 2002.20, each page containing CUI must carry a CUI banner. The document also must have a designation indicator naming the designating agency. For DoD documents, that agency is typically the Department of Defense.

00:02:12.318 --> 00:02:17.304
<v Host>And if it’s a DoD technical drawing, does a distribution statement replace the banner?

00:02:17.700 --> 00:02:37.142
<v Analyst>No, that’s a common mistake. DoD Instruction 5230.24 governs distribution statements on technical documents, but those statements do not satisfy CUI marking requirements. You need both the distribution statement and the CUI banner and designation indicator to be compliant.

00:02:37.450 --> 00:02:42.519
<v Host>So a document can be marked for distribution and still be CUI if it meets those criteria.

00:02:42.815 --> 00:02:52.201
<v Analyst>Correct. The two controls run in parallel. You can have a DoD technical document that is CUI, and you must apply both sets of markings.

00:02:52.498 --> 00:02:56.415
<v Host>What about the difference between CUI Basic and CUI Specified?

00:02:56.912 --> 00:03:22.664
<v Analyst>32 CFR Part 2002 splits CUI into two categories. CUI Basic carries a uniform moderate confidentiality baseline that applies to all CUI unless the underlying authority adds more. CUI Specified carries handling controls written directly into the underlying law, regulation, or policy-so you might have additional dissemination limits or destruction requirements.

00:03:22.926 --> 00:03:26.094
<v Host>So you first identify the authority that designates the information.

00:03:26.441 --> 00:03:41.892
<v Analyst>Exactly. The first step in the decision process is to locate the cited authority-whether it’s a law, regulation, or policy-and read it. That authority tells you whether the information is CUI Basic or CUI Specified.

00:03:42.179 --> 00:03:45.498
<v Host>And then you confirm that the government is the designating source.

00:03:45.800 --> 00:03:58.767
<v Analyst>Yes. Because CUI designation is a government act, the designation indicator must name the designating agency. That confirms that the agency has officially marked the information as CUI.

00:03:59.035 --> 00:04:01.641
<v Host>After that you need to separate FCI from CUI.

00:04:01.959 --> 00:04:03.273
<v Analyst>That fork is critical. FCI triggers the 15 basic safeguards, while CUI triggers the full 110 controls of NIST SP 800-171. The contract clauses that apply are different: DFARS 252.204-7012 requires the 110 controls on covered contractor information systems; FAR 52.204-21 applies to FCI.

00:04:03.474 --> 00:04:05.367
<v Host>Who bears those responsibilities?

00:04:05.734 --> 00:04:24.035
<v Analyst>Every DoD contractor handling FCI must meet FAR 52.204-21. Only contractors that receive or generate CUI take on the full NIST SP 800-171 obligation. So the scope of your contracts determines who is responsible.

00:04:24.382 --> 00:04:28.736
<v Host>Speaking of scope, how do you decide where CUI will live in your environment?

00:04:29.298 --> 00:04:48.756
<v Analyst>You trace the data flow. If you enclave CUI into a narrowly scoped boundary-say a GCC High tenant or a dedicated cloud landing zone-you limit the 110 controls to that boundary. That reduces audit surface, shortens timelines, and lowers ongoing costs.

00:04:49.078 --> 00:04:54.849
<v Host>So the enclave approach is a practical way to keep the 110 controls from bleeding across the entire network.

00:04:55.137 --> 00:05:03.433
<v Analyst>Exactly. Our consulting team treats the CUI boundary decision as the first major milestone of any engagement for that reason.

00:05:03.758 --> 00:05:06.705
<v Host>Once you know CUI is in scope, what changes for you?

00:05:07.240 --> 00:05:29.781
<v Analyst>DFARS 252.204-7012 kicks in, requiring the 110 controls on every covered contractor information system. The clause also flows down to subcontractors, so if you perform commercial products or services that involve covered defense information, those subcontractors must also meet the controls.

00:05:29.923 --> 00:05:50.172
<v Analyst>Incident response duties are also added. Any cyber incident affecting covered defense information must be reported to DoD within 72 hours through the DoD reporting portal at dibnet.dod.mil. You need a DoD-approved medium assurance certificate to access that portal.

00:05:50.478 --> 00:05:53.065
<v Host>And after you report, what else do you have to do?

00:05:53.590 --> 00:06:16.419
<v Analyst>You must preserve images of affected systems and monitoring data for at least 90 days, submit isolated malicious software to the government, and hold your cloud providers to a FedRAMP Moderate baseline. NIST SP 800-171 also requires FIPS-validated cryptography; strong but unvalidated encryption does not meet the requirement.

00:06:16.531 --> 00:06:18.196
<v Host>So encryption alone isn’t enough.

00:06:18.454 --> 00:06:30.776
<v Analyst>Right. The DoD CIO FAQ clarifies that encrypted CUI is still CUI, and if it’s in a cloud it still needs FedRAMP Moderate or an equivalent.

00:06:31.084 --> 00:06:34.291
<v Host>What about the Supplier Performance Risk System, the SPRS?

00:06:34.694 --> 00:07:02.072
<v Analyst>DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in SPRS when an offer is submitted. DFARS 252.204-7020 governs how that assessment is conducted under the DoD Assessment Methodology and gives DoD access to verify it.

00:07:02.377 --> 00:07:06.452
<v Host>The SPRS score ranges from minus 203 to 110, right?

00:07:06.836 --> 00:07:15.139
<v Analyst>Yes, controls are weighted at 1, 3, or 5 points. That score must be current at the time you submit an offer.

00:07:15.457 --> 00:07:21.871
<v Host>And the CMMC program comes into play when DFARS 252.204-7021 is in the contract.

00:07:22.185 --> 00:07:44.753
<v Analyst>Exactly. DFARS 252.204-7021 requires a valid CMMC certificate at the specified level before award. The CMMC Program rule, 32 CFR Part 170, was published October 15, 2024 and took effect December 16, 2024.

00:07:45.024 --> 00:07:46.613
<v Host>So there are three levels to consider.

00:07:46.910 --> 00:08:13.962
<v Analyst>Level One covers FCI with the 15 basic safeguards, an annual self-assessment, and an annual senior official affirmation. Level Two covers CUI with 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 affirmation.

00:08:14.130 --> 00:08:27.903
<v Analyst>Level Three adds selected controls from NIST SP 800-172 on top of Level Two and is assessed by the government through DCMA DIBCAC rather than a C3PAO.

00:08:28.077 --> 00:08:29.671
<v Host>That’s a lot of moving parts.

00:08:29.925 --> 00:08:31.045
<v Analyst>And they are enforced. The Department of Justice’s Civil Cyber-Fraud Initiative has produced settlements against contractors misrepresenting their security posture: Verizon at $4.09 million in 2023, Penn State at $1.25 million in 2024, Raytheon at $8.4 million in May 2025, and Georgia Tech at $875 thousand on September 30, 2025.

00:08:31.337 --> 00:08:34.832
<v Host>So it’s not just a bureaucratic exercise-there are real penalties.

00:08:35.109 --> 00:08:58.654
<v Analyst>Definitely. That’s why the decision process is so important. You need to run a contract inventory, pull every active DoD contract and subcontract, identify whether DFARS 252.204-7012 appears, whether covered defense information is defined, and whether any delivered or received document carries CUI markings.

00:08:58.993 --> 00:09:01.665
<v Host>And then you score yourself honestly before anyone else does.

00:09:01.950 --> 00:09:32.122
<v Analyst>Right. POA&Ms are allowed only for “not met” requirements within the limits of 32 CFR 170.21, with a 180-day closeout. A typical CMMC Level Two readiness engagement runs 12 to 14 weeks for a mid-size contractor: Discovery in week one, gap analysis in weeks two through four, a remediation sprint in weeks five through twelve, and a C3PAO readiness handoff in weeks thirteen and fourteen.

00:09:32.427 --> 00:09:39.988
<v Host>And the full path from gap assessment to C3PAO-ready takes 6 to 18 months depending on starting posture and complexity.

00:09:40.245 --> 00:09:51.539
<v Analyst>Exactly. And after certification, the SSP remains a living document, the POA&M is reviewed at least quarterly, and re-assessment occurs every three years.

00:09:51.840 --> 00:09:55.038
<v Host>What about the difference between an RPO and a C3PAO?

00:09:55.532 --> 00:10:19.248
<v Analyst>Petronella Technology Group is a Cyber AB Registered Provider Organization, or RPO, which means we prepare contractors for assessment but do not conduct the assessment or issue a certificate. Only a C3PAO can issue a Level Two certificate; the C3PAO submits results to eMASS and the certificate is stored in SPRS.

00:10:19.597 --> 00:10:23.247
<v Host>So if you’re looking for a readiness engagement, you need to ask the right questions.

00:10:23.560 --> 00:10:53.255
<v Analyst>Yes. Ask whether every practitioner assigned to your engagement holds the CMMC Registered Practitioner credential. Ask what deliverables you’ll receive: an SSP covering all 110 controls with owners and evidence pointers, 14 control-family policies, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist.

00:10:53.597 --> 00:10:56.269
<v Host>And about scope-how do you handle enclave decisions?

00:10:56.628 --> 00:11:11.176
<v Analyst>Ask how they will enclave your CUI environment and what that does to audit surface, timeline, and cost. Remember that you only need to apply the 110 controls within the enclave boundary, not across the entire enterprise.

00:11:11.523 --> 00:11:14.455
<v Host>What if you’re unsure whether a contract involves CUI?

00:11:14.810 --> 00:11:28.917
<v Analyst>Treat the question as a scope decision with real assessment cost. Resolve it deliberately rather than by default. Don’t assume unmarked equals uncontrolled, and don’t confuse distribution statements with CUI markings.

00:11:29.225 --> 00:11:32.996
<v Host>So the next step for an organization is to start that decision process.

00:11:33.149 --> 00:11:34.936
<v Host>What should organizations do next?

00:11:35.097 --> 00:11:39.977
<v Host>Let’s dive into what the decision process actually looks like in practice, step by step.

00:11:40.276 --> 00:11:51.339
<v Analyst>First, pull every active DoD contract and subcontract, then identify any DFARS 252.204-7012 clauses.

00:11:51.683 --> 00:11:55.860
<v Host>That clause is the trigger for the 110 NIST controls you’ll need to apply.

00:11:56.156 --> 00:12:02.260
<v Analyst>Next, you need to find the cited authority-read the law, regulation, or policy the agency used.

00:12:02.558 --> 00:12:07.256
<v Host>Once you locate that authority, confirm the agency is indeed the designating source.

00:12:07.547 --> 00:12:15.427
<v Analyst>That’s because CUI designation is a government act; the designation indicator on a document must name that agency.

00:12:15.685 --> 00:12:22.829
<v Host>After that, distinguish Federal Contract Information from CUI-it’s the fork that determines the regulatory regime.

00:12:23.086 --> 00:12:36.395
<v Analyst>FCI triggers the 15 basic safeguarding requirements of FAR 52.204-21, while CUI triggers the full 110 controls of NIST SP 800-171.

00:12:36.719 --> 00:12:47.113
<v Host>If a contract contains DFARS 252.204-7012, you’re looking at the full NIST set regardless of whether you think the data is FCI.

00:12:47.432 --> 00:12:54.625
<v Analyst>The next step is to trace where the CUI will live-identify the systems that will store, process, or transmit it.

00:12:54.966 --> 00:13:04.133
<v Host>DFARS 252.204-7012 requires adequate security on every covered contractor information system, so that mapping is critical.

00:13:04.415 --> 00:13:16.233
<v Analyst>You can enclave CUI into a narrow boundary-like a GCC High tenant or a dedicated cloud landing zone-to keep the 110 controls from spreading across the whole network.

00:13:16.490 --> 00:13:26.489
<v Host>Enclaving reduces audit surface, shortens timelines, and lowers ongoing cost, but it’s a design decision that must be documented in your System Security Plan.

00:13:26.767 --> 00:13:37.500
<v Analyst>Once you know the boundaries, perform a self-assessment against NIST SP 800-171 Revision 2, recording a score that reflects the weighted controls.

00:13:37.837 --> 00:13:49.255
<v Host>DFARS 252.204-7019 requires that you post that current assessment summary score in the Supplier Performance Risk System when you submit an offer.

00:13:49.550 --> 00:13:58.957
<v Analyst>The score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points, so precision matters.

00:13:59.245 --> 00:14:09.726
<v Host>After you submit that score, the contracting officer can verify it under DFARS 252.204-7020, which gives DoD a path to audit your evidence.

00:14:10.056 --> 00:14:22.637
<v Analyst>If your contract also includes DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award.

00:14:22.969 --> 00:14:31.530
<v Host>CMMC Level One covers FCI with the 15 basic safeguards, a self-assessment, and a senior official affirmation each year.

00:14:31.795 --> 00:14:44.509
<v Analyst>Level Two, which is the one you’ll need for CUI, covers all 110 practices of NIST SP 800-171 Revision 2, plus a C3PAO assessment for most programs.

00:14:44.786 --> 00:14:50.853
<v Host>Then you must go through a triennial reassessment and an annual senior official affirmation to keep the certificate valid.

00:14:51.154 --> 00:14:59.900
<v Analyst>The process from gap assessment to C3PAO readiness can take 6 to 18 months, depending on how mature your controls already are.

00:15:00.165 --> 00:15:04.372
<v Host>Common mistakes often start with the assumption that unmarked documents are uncontrolled.

00:15:04.672 --> 00:15:17.176
<v Analyst>But under 32 CFR 2002.20, every page containing CUI must have a banner and a designation indicator; absence of a banner does not mean the data is safe.

00:15:17.499 --> 00:15:22.374
<v Host>Another frequent error is confusing DoD distribution statements with CUI markings.

00:15:22.644 --> 00:15:33.728
<v Analyst>DoD Instruction 5230.24 governs distribution statements, but those statements do not satisfy the CUI banner requirement; they run in parallel.

00:15:34.058 --> 00:15:43.724
<v Host>Encryption is another area where many think they’re covered, but NIST SP 800-171 requires FIPS-validated cryptography to protect confidentiality.

00:15:43.989 --> 00:15:54.309
<v Analyst>Strong but unvalidated encryption does not meet the requirement, and DoD CIO FAQ clarifies that encrypted CUI is still CUI.

00:15:54.599 --> 00:16:00.480
<v Host>If you’re working in a cloud, the data still needs a FedRAMP Moderate baseline or an equivalent certification.

00:16:00.738 --> 00:16:10.518
<v Analyst>Scope sprawl is another common mistake-if you leave CUI across the entire enterprise, you’ll be required to apply the 110 controls everywhere.

00:16:10.789 --> 00:16:18.414
<v Host>The enclave approach keeps the controls confined, but it also requires you to clearly document the boundary in your SSP and POA&M.

00:16:18.672 --> 00:16:32.944
<v Analyst>When you submit a self-assessment score to SPRS, remember that the score must be current at the time of the offer and that DoD can verify it under DFARS 252.204-7020.

00:16:33.236 --> 00:16:40.092
<v Host>That verification step is part of the overall flow-down requirement; it ensures subcontractors also meet the same controls.

00:16:40.433 --> 00:16:53.782
<v Analyst>Speaking of subcontractors, DFARS 252.204-7012 requires you to flow down the 110 controls to any subcontractor that handles covered defense information.

00:16:54.087 --> 00:17:00.859
<v Host>They must report incidents to you, give you the report number, and keep images of affected systems for at least 90 days.

00:17:01.185 --> 00:17:10.183
<v Analyst>Incident response duties also include submitting isolated malicious software to the government and holding your cloud provider to a FedRAMP Moderate baseline.

00:17:10.470 --> 00:17:19.706
<v Host>Remember, NIST SP 800-171 requires FIPS-validated cryptography; strong but unvalidated encryption does not meet the requirement.

00:17:19.976 --> 00:17:31.031
<v Analyst>The CMMC program rule, published on October 15, 2024, took effect December 16, 2024, and it introduced the three levels of certification.

00:17:31.318 --> 00:17:41.075
<v Host>If your contract includes DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award.

00:17:41.365 --> 00:17:50.991
<v Analyst>The DoD CIO announced on July 13, 2026, that the Phase II deadline was suspended, but Phase I self-assessments remain in force.

00:17:51.256 --> 00:17:57.555
<v Host>That means you still need to submit a current assessment summary score for any offer, but you can pause the later milestones.

00:17:57.864 --> 00:18:07.858
<v Analyst>The enforcement side is real; the DOJ’s Civil Cyber-Fraud Initiative has settled cases against contractors for misrepresenting their security posture.

00:18:08.123 --> 00:18:25.976
<v Host>Recent settlements include Verizon at $4.09 million in 2023, Penn State at $1.25 million in 2024, Raytheon at $8.4 million in May 2025, and Georgia Tech at $875 k on September 30, 2025.

00:18:26.324 --> 00:18:34.553
<v Analyst>These cases remind contractors that accurate self-assessment and honest reporting are not optional; they are legal obligations.

00:18:34.899 --> 00:18:39.053
<v Host>So what do you do if you’re unsure whether a contract involves CUI?

00:18:39.492 --> 00:18:47.649
<v Analyst>Start with a contract inventory: pull every active DoD contract and subcontract, and note which clauses actually appear.

00:18:47.970 --> 00:18:55.004
<v Host>Then walk your teams through the data they receive, generate, and store for each contract, asking where it lives and who touches it.

00:18:55.279 --> 00:19:04.704
<v Analyst>If you find a document with a CUI banner or a designation indicator, you’ve identified a CUI instance that triggers the NIST safeguards.

00:19:04.967 --> 00:19:11.628
<v Host>If the marking is absent but the underlying law suggests control, flag it for a determination rather than guessing.

00:19:11.906 --> 00:19:22.464
<v Analyst>The next step is to decide whether the information is FCI or CUI, as that will dictate whether you need the 15 basic safeguards or the full 110 controls.

00:19:22.807 --> 00:19:29.054
<v Host>Once you’ve made that determination, map the systems that will host the data-whether it’s an on-prem server or a cloud tenant.

00:19:29.387 --> 00:19:37.306
<v Analyst>Apply the 110 controls only within that enclave; the rest of your network can remain at the baseline level required for FCI.

00:19:37.605 --> 00:19:45.379
<v Host>After that, run a self-assessment against NIST SP 800-171 Revision 2, record a score, and post it to SPRS.

00:19:45.632 --> 00:19:52.935
<v Analyst>The score must include the weighted points-controls are worth 1, 3, or 5-so do the math carefully.

00:19:53.209 --> 00:19:59.555
<v Host>In the System Security Plan you’ll document the boundary, the controls you’re applying, and the owners responsible for each.

00:19:59.895 --> 00:20:07.303
<v Analyst>The POA&M should be live, with owners assigned to each gap and a deadline for remediation; review it quarterly.

00:20:07.636 --> 00:20:16.697
<v Host>Remember that POA&Ms are only allowed for ‘not met’ requirements within the limits of 32 CFR 170.21, with a 180-day closeout.

00:20:16.971 --> 00:20:29.859
<v Analyst>Once you submit your score, the contracting officer can verify it under DFARS 252.204-7020, which gives DoD a path to audit your evidence.

00:20:30.180 --> 00:20:37.451
<v Host>If you’re subcontracting, remember that the 110 controls must flow down, and your subcontractors must report incidents to you.

00:20:37.795 --> 00:20:47.833
<v Analyst>They also need to keep images of affected systems for 90 days, submit isolated malware to the government, and ensure their cloud provider meets FedRAMP Moderate.

00:20:48.135 --> 00:21:00.290
<v Host>Incident response is a big part of DFARS 252.204-7012; you must report within 72 hours to the DoD portal at dibnet.dod.mil.

00:21:00.549 --> 00:21:07.693
<v Analyst>That portal requires a DoD-approved medium assurance certificate, which you must obtain in advance of any incident.

00:21:07.995 --> 00:21:13.839
<v Host>After reporting, you must preserve evidence for 90 days and provide isolated malware to the government.

00:21:14.094 --> 00:21:23.558
<v Analyst>The CMMC assessment also requires a baseline score in SPRS, so you need to maintain a current score that reflects any changes you make.

00:21:23.904 --> 00:21:31.535
<v Host>Your System Security Plan and POA&M should be living documents, updated at least quarterly to reflect new controls or gaps.

00:21:31.875 --> 00:21:39.417
<v Analyst>The reassessment for Level Two occurs every three years, but you still need an annual senior official affirmation to keep the certificate.

00:21:39.724 --> 00:21:49.667
<v Host>A typical Level Two readiness engagement takes 12 to 14 weeks for discovery, gap analysis, remediation sprint, and C3PAO readiness handoff.

00:21:49.921 --> 00:22:00.751
<v Analyst>The full path from gap assessment to C3PAO-ready can take 6 to 18 months, depending on your starting posture and complexity of the CUI environment.

00:22:01.095 --> 00:22:05.326
<v Host>Common questions from listeners include: how do I know which clause is relevant?

00:22:05.736 --> 00:22:21.406
<v Analyst>The answer is to look for DFARS 252.204-7012, 7019, 7021, and FAR 52.204-21; those are the clauses that trigger the controls.

00:22:21.708 --> 00:22:28.021
<v Host>Another question: what if my data is marked with a DoD distribution statement but no CUI banner?

00:22:28.403 --> 00:22:36.735
<v Analyst>A distribution statement does not satisfy the CUI banner requirement; you still need to apply the CUI banner if the data is CUI.

00:22:37.026 --> 00:22:41.863
<v Host>Listeners also ask whether encrypted CUI is exempt from the 110 controls.

00:22:42.163 --> 00:22:52.936
<v Analyst>No, encrypted CUI is still CUI; it still requires the 110 controls and, in a cloud, a FedRAMP Moderate baseline.

00:22:53.094 --> 00:22:53.835
<v Host>Thank you for that.
