WEBVTT

00:00:14.890 --> 00:00:25.940
<v Host>Today we’re looking at the new rules that tie Controlled Unclassified Information to the Department of Defense’s certification ladder and what that means for contractors. What does that look like on the ground?

00:00:26.303 --> 00:00:36.852
<v Analyst>Controlled Unclassified Information, or CUI, is data the federal government protects because its disclosure would harm national security, but it isn’t classified.

00:00:37.198 --> 00:00:42.025
<v Host>So it’s not the same as classified secrets, but it still demands a lot of protection.

00:00:42.299 --> 00:00:55.229
<v Analyst>Executive Order 13556 created the CUI program in 2010, and 32 CFR Part 2002 now governs how agencies mark, handle, and disseminate it.

00:00:55.503 --> 00:00:59.600
<v Host>And inside the Department of Defense, they have their own instruction to implement the program.

00:00:59.912 --> 00:01:09.876
<v Analyst>DoD Instruction 5200.48, issued March 6, 2020, translates the federal rules into DoD-specific guidance.

00:01:10.205 --> 00:01:13.683
<v Host>So what are the main categories of CUI that contractors need to know?

00:01:14.065 --> 00:01:20.519
<v Analyst>32 CFR Part 2002 splits CUI into Basic and Specified categories.

00:01:20.793 --> 00:01:23.147
<v Host>What’s the difference between Basic and Specified?

00:01:23.543 --> 00:01:37.053
<v Analyst>Basic CUI carries a uniform set of controls built around a moderate confidentiality baseline, while Specified CUI carries handling controls that are written into underlying laws or agency policies.

00:01:37.360 --> 00:01:39.926
<v Host>So a single contract could involve both, right?

00:01:40.321 --> 00:01:49.916
<v Analyst>Exactly. In practice, a defense contract may involve both Basic and Specified CUI, and the handling requirements can differ between them.

00:01:50.213 --> 00:01:53.809
<v Host>Now, how does a contractor even know if they’re dealing with CUI?

00:01:54.186 --> 00:02:11.163
<v Analyst>The first clue is the contract language. If a solicitation or contract contains DFARS 252.204-7021, the contractor must hold a valid CMMC certificate at the specified level before award.

00:02:11.425 --> 00:02:21.120
<v Host>And DFARS 252.204-7012 requires the 110 controls of NIST 800-171 on every covered system?

00:02:21.567 --> 00:02:36.448
<v Analyst>Yes. That clause also imposes incident reporting duties: any cyber incident affecting covered defense information must be reported within 72 hours through the DoD portal at dibnet.dod.mil.

00:02:36.735 --> 00:02:40.184
<v Host>And after the report, what else does the contractor need to do?

00:02:40.587 --> 00:02:53.390
<v Analyst>They 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.

00:02:53.658 --> 00:03:00.853
<v Host>So DFARS 252.204-7012 is essentially a blanket requirement for all covered information systems.

00:03:01.171 --> 00:03:08.300
<v Analyst>Correct. And that blanket requirement applies even if the contractor does not yet have a CMMC certificate.

00:03:08.641 --> 00:03:12.650
<v Host>Now, what about the difference between Federal Contract Information and CUI?

00:03:13.016 --> 00:03:29.777
<v Analyst>Federal Contract Information, or FCI, is any information the government receives or generates that is not CUI, and it triggers only the 15 basic safeguarding requirements of FAR 52.204-21.

00:03:30.123 --> 00:03:32.731
<v Host>So FCI is a lighter load than CUI?

00:03:33.174 --> 00:03:44.766
<v Analyst>Exactly. FCI only requires the 15 controls, an annual self-assessment, and an annual senior official affirmation, which is the CMMC Level 1 baseline.

00:03:45.088 --> 00:03:52.696
<v Host>Meanwhile, if a contractor receives or generates CUI, they must meet the full NIST 800-171 Rev 2 obligation.

00:03:52.984 --> 00:04:06.343
<v Analyst>That obligation translates to all 110 NIST 800-171 Rev 2 practices across 14 domains, plus the incident reporting, encryption, and cloud requirements.

00:04:06.668 --> 00:04:09.705
<v Host>The article mentions encryption requirements are stricter than they look.

00:04:10.020 --> 00:04:21.917
<v Analyst>NIST 800-171 requires FIPS-validated cryptography to protect CUI confidentiality. Strong but unvalidated encryption does not meet the requirement.

00:04:22.179 --> 00:04:26.362
<v Host>And encrypted CUI in a cloud still needs FedRAMP Moderate or equivalency?

00:04:26.767 --> 00:04:35.750
<v Analyst>Exactly. Even if you encrypt it, it remains CUI, and the cloud provider must meet FedRAMP Moderate or an equivalent baseline.

00:04:36.054 --> 00:04:39.346
<v Host>So the scope of CUI can be narrowed by enclave design?

00:04:39.697 --> 00:04:52.999
<v Analyst>Yes. Enclaving CUI into a narrowly scoped boundary, like a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across the entire enterprise network.

00:04:53.257 --> 00:04:57.167
<v Host>That reduces the assessment surface and ongoing compliance costs.

00:04:57.474 --> 00:05:03.201
<v Analyst>Exactly. It also shortens the remediation timeline and lowers the annual evidence burden.

00:05:03.505 --> 00:05:06.453
<v Host>Now, how many contractors are actually in the picture?

00:05:06.858 --> 00:05:18.152
<v Analyst>The DoD estimates about 220,966 entities in the program, and as of March 2026 there were 103 authorized C3PAOs.

00:05:18.436 --> 00:05:21.523
<v Host>And how many Level 2 certifications have been issued so far?

00:05:21.942 --> 00:05:33.156
<v Analyst>In January 2026 there were 773 Level 2 certificates, and by May 2026 that number had grown to 1,391.

00:05:33.330 --> 00:05:34.961
<v Host>So the pace is accelerating.

00:05:35.233 --> 00:05:41.948
<v Analyst>Yes, and that means scheduling a C3PAO assessment can be a real planning input for your timeline.

00:05:42.244 --> 00:05:45.481
<v Host>What happens if a contractor doesn’t have a Level 2 certificate yet?

00:05:45.869 --> 00:06:07.087
<v Analyst>If DFARS 252.204-7021 appears, the contractor must delay award until they obtain the certificate. If it doesn’t appear, they can still comply with DFARS 252.204-7012 by implementing the 110 controls and reporting incidents.

00:06:07.401 --> 00:06:11.661
<v Host>So it’s a two-tiered approach: basic for FCI, full for CUI.

00:06:11.915 --> 00:06:26.913
<v Analyst>Exactly. And remember, DFARS 252.204-7012 must flow down to subcontractors, so they must also meet the 110 controls if they handle covered defense information.

00:06:27.064 --> 00:06:28.685
<v Host>What about the POA&M limits?

00:06:29.062 --> 00:06:40.567
<v Analyst>POA&Ms are only allowed for requirements that are not met, within the limits of 32 CFR 170.21, and they must be closed within 180 days.

00:06:40.766 --> 00:06:42.489
<v Host>And they’re reviewed at least quarterly?

00:06:42.874 --> 00:06:50.284
<v Analyst>Correct. The POA&M should be a living document and reviewed at least quarterly to keep the risk profile up to date.

00:06:50.590 --> 00:06:54.807
<v Host>Now, how do contractors actually get a CMMC Level 2 certificate?

00:06:55.164 --> 00:07:07.032
<v Analyst>Only an authorized C3PAO can issue a Level 2 certificate. The C3PAO submits results to eMASS, and the certificate is stored in the Supplier Performance Risk System.

00:07:07.333 --> 00:07:10.296
<v Host>What’s the difference between a C3PAO and a RPO?

00:07:10.671 --> 00:07:23.770
<v Analyst>A Registered Provider Organization, or RPO, prepares contractors for assessment but cannot conduct the assessment or issue a certificate. Only a C3PAO can perform the Level 2 assessment.

00:07:24.119 --> 00:07:26.558
<v Host>So Petronella Technology Group is an RPO?

00:07:26.970 --> 00:07:38.843
<v Analyst>Yes. Petronella Technology Group is a Cyber AB Registered Provider Organization, RPO #1449, and we prepare contractors for the CMMC assessment.

00:07:39.045 --> 00:07:40.750
<v Host>What does that preparation look like?

00:07:41.110 --> 00:07:51.617
<v Analyst>We run a 12- to 14-week engagement that starts with discovery, then a gap analysis, a remediation sprint, and ends with a C3PAO readiness handoff.

00:07:51.964 --> 00:07:56.521
<v Host>And how long does it typically take to go from gap assessment to C3PAO readiness?

00:07:56.875 --> 00:08:02.452
<v Analyst>Depending on starting posture and complexity, it can take anywhere from six to eighteen months.

00:08:02.760 --> 00:08:05.917
<v Host>What kind of deliverables does the readiness engagement produce?

00:08:06.409 --> 00:08:29.804
<v Analyst>A system security plan covering all 110 controls with owners and evidence pointers, 14 control-family policies, an incident response plan, acceptable use and media protection policies, a live POA&M, a mock assessment, a baselined SPRS score, and a C3PAO shortlist with warm introductions.

00:08:29.945 --> 00:08:31.020
<v Host>That’s a lot of work.

00:08:31.319 --> 00:08:38.489
<v Analyst>It is, but the cost of not being compliant can be far greater, especially when you consider the enforcement climate.

00:08:38.832 --> 00:08:42.651
<v Host>The article mentioned some settlements from the DOJ Civil Cyber-Fraud Initiative.

00:08:42.947 --> 00:09:01.235
<v Analyst>Yes, Verizon paid 4.09 million in 2023, Penn State 1.25 million in 2024, Raytheon 8.4 million in May 2025, and Georgia Tech 875 k on September 30, 2025.

00:09:01.393 --> 00:09:02.412
<v Host>So the stakes are real.

00:09:02.703 --> 00:09:12.401
<v Analyst>Absolutely. Those settlements show that the DoD takes these requirements seriously and that non-compliance can lead to significant financial penalties.

00:09:12.659 --> 00:09:16.637
<v Host>What about the actual process of scoring in the Supplier Performance Risk System?

00:09:16.994 --> 00:09:38.316
<v Analyst>DFARS 252.204-7019 requires a current NIST 800-171 assessment summary score in SPRS when an offer is submitted. The score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points.

00:09:38.640 --> 00:09:40.897
<v Host>So you have to score honestly before you submit?

00:09:41.315 --> 00:09:51.934
<v Analyst>Yes. The DoD can verify the score through the assessment methodology clause DFARS 252.204-7020.

00:09:52.276 --> 00:09:55.481
<v Host>If you overstate the score, the consequences can be serious.

00:09:55.763 --> 00:10:01.747
<v Analyst>The DOJ settlements illustrate that, and the DoD will enforce the accuracy of the self-assessment.

00:10:02.005 --> 00:10:04.789
<v Host>Now, what should organizations do about all this?

00:10:05.167 --> 00:10:11.764
<v Analyst>You start by confirming whether your contract actually involves CUI or just Federal Contract Information.

00:10:12.100 --> 00:10:16.256
<v Host>That means reading the solicitation and checking the DFARS clauses that appear.

00:10:16.552 --> 00:10:28.195
<v Analyst>If the contract lists DFARS 252.204-7021, you need a valid CMMC certificate at the specified level before award.

00:10:28.483 --> 00:10:38.320
<v Host>And if it references DFARS 252.204-7012, you must implement the 110 NIST controls regardless of certification.

00:10:38.650 --> 00:10:44.494
<v Analyst>So the first concrete step is a scope check-identify the exact data set that is CUI.

00:10:44.825 --> 00:10:48.744
<v Host>Once you know the scope, you can decide where that data will live in your environment.

00:10:49.009 --> 00:10:59.326
<v Analyst>Enclaving CUI into a narrow boundary-like a GCC High tenant or a dedicated cloud landing zone-limits the 110 controls to that slice.

00:10:59.603 --> 00:11:03.141
<v Host>That reduces the assessment surface and the ongoing evidence burden.

00:11:03.443 --> 00:11:13.113
<v Analyst>Next you perform a gap analysis against all 110 NIST SP 800-171 practices across the 14 control families.

00:11:13.377 --> 00:11:17.471
<v Host>The assessment score you produce must match the point-based system the DoD uses.

00:11:17.771 --> 00:11:26.013
<v Analyst>Controls are weighted 1, 3, or 5 points, so you can calculate a score between minus 203 and 110.

00:11:26.337 --> 00:11:30.192
<v Host>That score goes into the Supplier Performance Risk System when you submit an offer.

00:11:30.463 --> 00:11:35.911
<v Analyst>If you overstate that score, the DoD can audit you and the penalties can be severe.

00:11:36.240 --> 00:11:39.641
<v Host>After you have a realistic score, you move to remediation.

00:11:39.907 --> 00:11:47.115
<v Analyst>Prioritize gaps that protect CUI confidentiality first, especially those involving FIPS-validated encryption.

00:11:47.405 --> 00:11:51.431
<v Host>The article notes that strong but non-FIPS encryption does not meet the requirement.

00:11:51.690 --> 00:11:58.984
<v Analyst>Also remember that encrypted CUI in a cloud still requires a FedRAMP Moderate baseline or equivalence.

00:11:59.255 --> 00:12:03.646
<v Host>So choosing a cloud provider is a compliance decision, not just a technical one.

00:12:03.905 --> 00:12:10.475
<v Analyst>You also need to document everything in a System Security Plan covering all 110 controls.

00:12:10.767 --> 00:12:16.393
<v Host>That SSP must include owners, evidence pointers, and a live Plan of Action and Milestones.

00:12:16.734 --> 00:12:26.007
<v Analyst>The Plan of Action and Milestones, or POA&M, is only allowed for not-met requirements and must close within 180 days.

00:12:26.312 --> 00:12:29.583
<v Host>You should review that POA&M at least quarterly to keep it current.

00:12:29.910 --> 00:12:37.498
<v Analyst>For Level 2, you need a C3PAO assessment; only an authorized C3PAO can issue the certificate.

00:12:37.786 --> 00:12:43.224
<v Host>Petronella Technology Group is a Registered Provider Organization but not a C3PAO.

00:12:43.493 --> 00:12:50.190
<v Analyst>They prepare you for the assessment, provide mock assessments, and help you build the SSP and POA&M.

00:12:50.476 --> 00:12:55.885
<v Host>Once you’re ready, you schedule the C3PAO assessment and submit the evidence to eMASS.

00:12:56.176 --> 00:13:03.378
<v Analyst>The C3PAO submits results to eMASS, and the certificate is stored in the Supplier Performance Risk System.

00:13:03.643 --> 00:13:10.011
<v Host>After certification, you still must reassess every three years and keep the senior official affirmation annually.

00:13:10.320 --> 00:13:16.788
<v Analyst>That means the SSP and POA&M remain living documents, not one-time artifacts.

00:13:17.053 --> 00:13:19.626
<v Host>What are the most common mistakes you see in the field?

00:13:20.074 --> 00:13:26.734
<v Analyst>First, guessing at CUI scope-assuming no CUI or assuming everything is in scope.

00:13:27.080 --> 00:13:30.868
<v Host>Second, confusing distribution statements with CUI markings.

00:13:31.206 --> 00:13:42.435
<v Analyst>Distribution statements are governed by DoD Instruction 5230.24, while CUI markings come from 32 CFR 2002.20.

00:13:42.757 --> 00:13:48.434
<v Host>Third, using encryption that’s not FIPS-validated, which the DoD explicitly rejects.

00:13:48.710 --> 00:13:56.182
<v Analyst>Fourth, assuming a cloud provider handles all compliance; you still need FedRAMP Moderate or an equivalence.

00:13:56.445 --> 00:14:04.268
<v Host>Fifth, ignoring the flow-down clause-subcontractors must also meet DFARS 252.204-7012.

00:14:04.546 --> 00:14:11.297
<v Analyst>Sixth, overstating the SPRS score; the DoD will audit you and penalties can follow.

00:14:11.640 --> 00:14:16.583
<v Host>Seventh, treating the SSP as a one-time deliverable rather than a living document.

00:14:16.916 --> 00:14:22.987
<v Analyst>Eighth, waiting for a clear timeline; the acquisition rule and Phase II deadline are separate.

00:14:23.286 --> 00:14:32.459
<v Host>The acquisition rule took effect 2025-11-10, so DFARS 252.204-7021 can appear in contracts today.

00:14:32.712 --> 00:14:40.113
<v Analyst>But the Phase II deadline of 2026-11-10 was suspended, so those later milestones are paused.

00:14:40.387 --> 00:14:46.964
<v Host>So you can still pursue CMMC Level 2 certification, but you don’t need to rush to meet a now-suspended deadline.

00:14:47.304 --> 00:14:53.914
<v Analyst>That gives you time to properly scope, gap-analyze, and remediate before the next reassessment.

00:14:54.247 --> 00:14:57.637
<v Host>What about organizations that only handle Federal Contract Information?

00:14:58.012 --> 00:15:07.635
<v Analyst>They only need to meet FAR 52.204-21, which includes 15 basic safeguarding requirements and an annual self-assessment.

00:15:07.957 --> 00:15:11.012
<v Host>And that level is equivalent to CMMC Level 1, right?

00:15:11.456 --> 00:15:19.925
<v Analyst>Correct. Level 1 covers the 15 basic controls, and the contractor must provide an annual senior official affirmation to DoD.

00:15:20.227 --> 00:15:28.327
<v Host>And for those with CUI, Level 2 is mandatory if DFARS 252.204-7021 is present.

00:15:28.586 --> 00:15:37.028
<v Analyst>Level 3 adds selected NIST 800-172 controls and is assessed by the government, not a C3PAO.

00:15:37.329 --> 00:15:39.582
<v Host>Can a contractor self-assess for Level 2?

00:15:39.938 --> 00:15:46.132
<v Analyst>No. Only a C3PAO can conduct the Level 2 assessment and issue the certificate.

00:15:46.478 --> 00:15:49.601
<v Host>What about the role of a C3PAO-how do we choose one?

00:15:50.041 --> 00:15:58.619
<v Analyst>The DoD maintains a list of authorized C3PAOs on cyberab.org/marketplace; you should review that before scheduling.

00:15:58.926 --> 00:16:03.166
<v Host>Is there a typical timeline from gap assessment to C3PAO readiness?

00:16:03.521 --> 00:16:13.390
<v Analyst>For a mid-size contractor, a readiness engagement runs 12 to 14 weeks: discovery, gap analysis, remediation sprint, and handoff.

00:16:13.735 --> 00:16:17.671
<v Host>And the overall path from assessment to readiness can take 6 to 18 months.

00:16:17.980 --> 00:16:23.305
<v Analyst>That timeline depends on your starting posture and how many systems need to be remediated.

00:16:23.608 --> 00:16:27.015
<v Host>What about the enforcement side-what happens if you’re found non-compliant?

00:16:27.398 --> 00:16:34.222
<v Analyst>The DOJ Civil Cyber-Fraud Initiative has already imposed multi-million-dollar settlements on large firms.

00:16:34.513 --> 00:16:38.708
<v Host>Those settlements show the financial risk, but what about contract termination?

00:16:39.107 --> 00:16:46.015
<v Analyst>Non-compliance can trigger contract termination, loss of future opportunities, and reputational damage.

00:16:46.314 --> 00:16:49.090
<v Host>So the practical takeaway is to get the scope right early.

00:16:49.407 --> 00:17:00.933
<v Analyst>Confirm the data set, decide on an enclave, perform a gap analysis, remediate gaps, document in the SSP, and then schedule a C3PAO assessment.

00:17:01.242 --> 00:17:06.289
<v Host>And keep the SSP and POA&M alive-review them quarterly and refresh evidence annually.

00:17:06.547 --> 00:17:12.458
<v Analyst>Also, treat the SPRS score as a living metric; update it whenever you close a gap.

00:17:12.728 --> 00:17:15.275
<v Host>What about the role of the senior official affirmation?

00:17:15.625 --> 00:17:24.940
<v Analyst>You must submit an annual senior official affirmation to DoD; it confirms that the organization’s security posture meets the required level.

00:17:25.268 --> 00:17:28.349
<v Host>And that affirmation is part of the ongoing compliance cycle.

00:17:28.651 --> 00:17:33.835
<v Analyst>In summary, compliance is a continuous process, not a one-time event.

00:17:34.143 --> 00:17:39.335
<v Host>The key is to build a living framework that you can audit yourself before the C3PAO arrives.

00:17:39.677 --> 00:17:47.501
<v Analyst>That means regular internal reviews, evidence collection, and a culture of security awareness across the organization.

00:17:47.796 --> 00:17:52.293
<v Host>What about the cost implications-how can an organization estimate the investment needed?

00:17:52.731 --> 00:17:58.969
<v Analyst>Start by sizing the enclave: the number of systems, users, and data volumes that will be in scope.

00:17:59.232 --> 00:18:05.798
<v Host>Then estimate remediation effort for each gap-some controls are quick fixes, others require architecture changes.

00:18:06.109 --> 00:18:14.985
<v Analyst>Add the cost of a C3PAO assessment, which varies but typically ranges from 20,000 to 50,000 dollars for a mid-size firm.

00:18:15.276 --> 00:18:22.850
<v Host>Don’t forget ongoing costs-annual evidence refresh, POA&M reviews, and the eventual reassessment every three years.

00:18:23.107 --> 00:18:28.869
<v Analyst>A realistic budget will include personnel time, tooling, and external consulting when needed.

00:18:29.202 --> 00:18:32.252
<v Host>What about small contractors-can they manage all this alone?

00:18:32.673 --> 00:18:42.567
<v Analyst>Many choose a Registered Provider Organization to handle the preparation and mock assessment, then bring in a C3PAO only for the final certification.

00:18:42.915 --> 00:18:46.742
<v Host>Thanks for that deep dive into the practical steps for CUI compliance.
