WEBVTT

00:00:14.890 --> 00:00:19.739
<v Host>Today we dive into the ISOO CUI registry and why it matters for defense contractors.

00:00:20.002 --> 00:00:25.483
<v Analyst>The registry is the government-wide catalog of Controlled Unclassified Information categories.

00:00:25.830 --> 00:00:29.409
<v Host>So, what exactly does that mean for a company that works with the DoD?

00:00:29.783 --> 00:00:34.917
<v Analyst>It means that the registry tells you which categories of information you hold are CUI.

00:00:35.071 --> 00:00:38.976
<v Analyst>Once you know that, you can see which security baseline applies.

00:00:39.288 --> 00:00:42.919
<v Host>And that baseline is tied to NIST SP 800-171, right?

00:00:43.349 --> 00:00:49.905
<v Analyst>Exactly. The NIST standard has 110 controls that you must implement if you handle CUI.

00:00:50.068 --> 00:00:55.707
<v Analyst>If you only handle Federal Contract Information, you only need 15 basic safeguards.

00:00:55.980 --> 00:00:58.911
<v Host>So the registry distinguishes between those two cases.

00:00:59.208 --> 00:01:08.032
<v Analyst>It does. The registry is governed by 32 CFR Part 2002, which implements Executive Order 13556.

00:01:08.219 --> 00:01:13.664
<v Analyst>That order names the National Archives and Records Administration as the Executive Agent.

00:01:13.820 --> 00:01:15.446
<v Host>What about the connection to CMMC?

00:01:15.843 --> 00:01:25.220
<v Analyst>CMMC Level Two aligns directly with all 110 practices of NIST SP 800-171 Revision 2.

00:01:25.376 --> 00:01:35.910
<v Analyst>Level One covers Federal Contract Information, Level Two covers CUI, and Level Three adds NIST SP 800-172 controls.

00:01:36.171 --> 00:01:43.508
<v Host>So, if a contract says DFARS 252.204-7021, you need a valid CMMC certificate.

00:01:43.856 --> 00:01:49.048
<v Analyst>Exactly. That clause requires a certificate at the specified level before award.

00:01:49.214 --> 00:01:55.250
<v Analyst>The DoD now suspends the Phase II deadline but keeps Phase I self-assessments active.

00:01:55.553 --> 00:01:58.807
<v Host>What about the scoring system in the Supplier Performance Risk System?

00:01:59.175 --> 00:02:11.857
<v Analyst>DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in SPRS.

00:02:12.056 --> 00:02:19.962
<v Analyst>That score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points.

00:02:20.303 --> 00:02:22.320
<v Host>And how does that relate to subcontractors?

00:02:22.686 --> 00:02:33.753
<v Analyst>DFARS 252.204-7012 must flow down to subcontractors when performance involves covered defense information.

00:02:33.979 --> 00:02:40.017
<v Analyst>Each subcontractor reports its own incidents to DoD and passes the report number up the chain.

00:02:40.360 --> 00:02:43.420
<v Host>Speaking of incidents, what are the reporting requirements?

00:02:43.842 --> 00:02:56.221
<v Analyst>DFARS 252.204-7012 requires reporting to DoD within 72 hours of discovery through dibnet.dod.mil.

00:02:56.389 --> 00:03:01.920
<v Analyst>After reporting, you must preserve images of affected systems for at least 90 days.

00:03:02.125 --> 00:03:05.815
<v Analyst>You also need to submit isolated malicious software to the government.

00:03:06.130 --> 00:03:10.598
<v Host>That sounds intense. Are there any examples of companies that faced penalties?

00:03:10.959 --> 00:03:20.794
<v Analyst>Yes. Verizon paid $4.09 million in 2023, Penn State $1.25 million in 2024.

00:03:20.980 --> 00:03:30.649
<v Analyst>Raytheon paid $8.4 million in May 2025, and Georgia Tech paid $875 000 in September 2025.

00:03:30.954 --> 00:03:33.741
<v Host>Those are huge. What caused those settlements?

00:03:34.092 --> 00:03:39.732
<v Analyst>They stem from failures to protect CUI and comply with the Civil Cyber-Fraud Initiative.

00:03:39.871 --> 00:03:45.272
<v Analyst>The DOJ settlements highlight that gaps in compliance can lead to significant financial risk.

00:03:45.579 --> 00:03:48.888
<v Host>What about marking and handling rules? How do those work?

00:03:49.291 --> 00:03:57.302
<v Analyst>32 CFR 2002.20 requires a CUI banner marking on every page containing CUI.

00:03:57.488 --> 00:04:02.127
<v Analyst>It also requires a designation indicator naming the designating agency.

00:04:02.411 --> 00:04:04.963
<v Host>Can a distribution statement replace the banner marking?

00:04:05.381 --> 00:04:15.262
<v Analyst>No. DoD Instruction 5230.24 governs distribution statements, but those do not satisfy CUI marking requirements.

00:04:15.456 --> 00:04:18.563
<v Analyst>The two are applied in parallel, not interchangeably.

00:04:18.834 --> 00:04:23.041
<v Host>What about encryption? Does any encryption satisfy the NIST requirement?

00:04:23.437 --> 00:04:31.990
<v Analyst>NIST SP 800-171 requires FIPS-validated cryptography to protect CUI confidentiality.

00:04:32.158 --> 00:04:35.950
<v Analyst>Strong but unvalidated encryption does not meet the requirement.

00:04:36.264 --> 00:04:40.778
<v Host>So, if we use an unvalidated algorithm, we’re still in violation?

00:04:41.132 --> 00:04:48.497
<v Analyst>Correct. The encryption must be FIPS-validated, and if it’s in the cloud, the provider must meet FedRAMP Moderate.

00:04:48.789 --> 00:04:52.077
<v Host>What about the system security plan? How does that fit in?

00:04:52.454 --> 00:04:59.679
<v Analyst>The system security plan, or SSP, covers all 110 controls and assigns owners.

00:04:59.898 --> 00:05:04.048
<v Analyst>It also includes evidence pointers and must be a living document.

00:05:04.193 --> 00:05:05.252
<v Host>And the POA&M?

00:05:05.657 --> 00:05:11.291
<v Analyst>The Plan of Actions and Milestones, or POA&M, tracks gaps that are not met.

00:05:11.428 --> 00:05:20.496
<v Analyst>Under 32 CFR 170.21, POA&Ms are allowed only for not-met requirements with a 180-day closeout.

00:05:20.656 --> 00:05:22.854
<v Host>How often is the POA&M reviewed?

00:05:23.228 --> 00:05:27.101
<v Analyst>At least quarterly, according to the CMMC program rule.

00:05:27.309 --> 00:05:29.084
<v Host>What about the assessment process itself?

00:05:29.497 --> 00:05:36.797
<v Analyst>Only a Certified Third-Party Assessment Organization, or C3PAO, can issue a Level Two certificate.

00:05:37.018 --> 00:05:41.830
<v Analyst>Petronella Technology Group prepares organizations but does not conduct the assessment.

00:05:42.089 --> 00:05:44.027
<v Host>What does a readiness engagement look like?

00:05:44.474 --> 00:05:50.572
<v Analyst>A typical engagement has Discovery in week one, Gap Analysis weeks two to four.

00:05:50.706 --> 00:05:58.575
<v Analyst>Then a Remediation Sprint from week five to twelve, and a C3PAO readiness handoff in weeks thirteen and fourteen.

00:05:58.883 --> 00:06:02.373
<v Host>That’s a lot of work. How long does the entire path take?

00:06:02.745 --> 00:06:09.427
<v Analyst>From gap assessment to C3PAO-ready usually takes six to eighteen months, depending on starting posture.

00:06:09.709 --> 00:06:11.712
<v Host>Is there a way to reduce the audit surface?

00:06:12.112 --> 00:06:20.207
<v Analyst>Enclaving CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone.

00:06:20.431 --> 00:06:25.395
<v Analyst>That keeps the 110 controls from applying across the entire enterprise network.

00:06:25.690 --> 00:06:28.528
<v Host>What about the handling controls for CUI Specified?

00:06:28.927 --> 00:06:35.757
<v Analyst>CUI Specified carries handling controls written into the underlying law, regulation, or policy.

00:06:35.929 --> 00:06:41.270
<v Analyst>Those controls may add additional requirements beyond the 110 NIST controls.

00:06:41.527 --> 00:06:44.256
<v Host>So you need to check each category for those extra rules.

00:06:44.514 --> 00:06:48.932
<v Analyst>Exactly. The registry lists each category and its designation.

00:06:49.257 --> 00:06:51.514
<v Host>How do you evaluate your own CUI exposure?

00:06:51.932 --> 00:06:56.719
<v Analyst>Step one: inventory what you hold, go contract by contract.

00:06:56.941 --> 00:07:01.405
<v Analyst>Step two: decide whether to enclave, which limits the scope.

00:07:01.567 --> 00:07:07.054
<v Analyst>Step three: build the program the registry demands, starting with the SSP.

00:07:07.312 --> 00:07:09.812
<v Host>What about the supplier performance risk system score?

00:07:10.190 --> 00:07:20.268
<v Analyst>You need to score yourself and post it, because DFARS 252.204-7019 requires a current score.

00:07:20.484 --> 00:07:24.999
<v Analyst>The score is used to assess risk in the Supplier Performance Risk System.

00:07:25.154 --> 00:07:27.255
<v Host>Does the score impact contract awards?

00:07:27.642 --> 00:07:33.723
<v Analyst>Yes, a higher score can improve your competitiveness, while a lower score may raise concerns.

00:07:33.913 --> 00:07:36.117
<v Host>What about the 72-hour reporting window?

00:07:36.548 --> 00:07:41.857
<v Analyst>You must report any incident affecting covered defense information within 72 hours.

00:07:42.002 --> 00:07:49.161
<v Analyst>That includes submitting the incident to DoD via the reporting portal at dibnet.dod.mil.

00:07:49.439 --> 00:07:52.586
<v Host>And after reporting, you preserve evidence for 90 days.

00:07:52.887 --> 00:07:56.567
<v Analyst>Correct. That includes system images and monitoring data.

00:07:56.832 --> 00:07:59.068
<v Host>What about the FOIA and privacy aspects?

00:07:59.469 --> 00:08:04.783
<v Analyst>The CUI registry is separate from FOIA, but both involve controlled information.

00:08:04.986 --> 00:08:11.725
<v Analyst>FOIA deals with public records, while CUI is about protecting sensitive but unclassified data.

00:08:11.995 --> 00:08:14.976
<v Host>How does the CUI registry drive security obligations?

00:08:15.406 --> 00:08:21.430
<v Analyst>The registry determines whether you need to meet the full NIST SP 800-171 baseline.

00:08:21.575 --> 00:08:27.756
<v Analyst>If you handle CUI Basic, you need the uniform controls at a moderate confidentiality baseline.

00:08:27.926 --> 00:08:33.015
<v Analyst>If you handle CUI Specified, you also need the specified handling controls.

00:08:33.273 --> 00:08:34.986
<v Host>That sounds like a lot of nuance.

00:08:35.256 --> 00:08:39.911
<v Analyst>It is, but the registry provides a clear taxonomy to avoid confusion.

00:08:40.170 --> 00:08:42.644
<v Host>What about the difference between the DFARS clauses?

00:08:43.037 --> 00:08:51.698
<v Analyst>DFARS 252.204-7012 covers the 110 NIST controls for CUI.

00:08:51.919 --> 00:09:00.151
<v Analyst>DFARS 252.204-7019 covers the SPRS score requirement.

00:09:00.336 --> 00:09:10.691
<v Analyst>DFARS 252.204-7020 governs how the assessment is conducted and allows DoD verification.

00:09:11.017 --> 00:09:14.109
<v Host>So you need to satisfy all three if you’re a defense contractor?

00:09:14.497 --> 00:09:19.045
<v Analyst>Yes, if you handle CUI and are subject to those clauses.

00:09:19.314 --> 00:09:21.509
<v Host>What about the role of the National Archives?

00:09:21.895 --> 00:09:29.848
<v Analyst>The National Archives is the Executive Agent for the CUI Program, implementing 32 CFR Part 2002.

00:09:30.019 --> 00:09:34.787
<v Analyst>They oversee the designation of CUI categories and the marking requirements.

00:09:34.912 --> 00:09:38.639
<v Host>And the DoD Instruction 5200.48?

00:09:39.048 --> 00:09:43.882
<v Analyst>That instruction implements the CUI program inside the Department of Defense.

00:09:44.027 --> 00:09:46.610
<v Analyst>It is the most relevant for defense contractors.

00:09:46.819 --> 00:09:48.916
<v Host>What about the impact on subcontractors?

00:09:49.362 --> 00:10:02.307
<v Analyst>Subcontractors must flow down DFARS 252.204-7012 and DFARS 252.204-7019.

00:10:02.526 --> 00:10:06.984
<v Analyst>They also need to report incidents and provide their own SPRS score.

00:10:07.306 --> 00:10:11.152
<v Host>Do you have any examples of how a company might handle a CUI category?

00:10:11.527 --> 00:10:20.373
<v Analyst>If a company receives a contract that designates a specific CUI category, it must mark every page with the banner and designation indicator.

00:10:20.516 --> 00:10:29.198
<v Analyst>For example, a document marked as "CUI - DoD - SHIP" would include the banner and the agency indicator.

00:10:29.477 --> 00:10:32.170
<v Host>And if the document also has a distribution statement?

00:10:32.613 --> 00:10:37.574
<v Analyst>The distribution statement does not replace the banner; both must be present.

00:10:37.908 --> 00:10:39.908
<v Host>What about the impact on cloud providers?

00:10:40.307 --> 00:10:46.667
<v Analyst>If you store CUI in the cloud, the provider must meet FedRAMP Moderate or an equivalency.

00:10:46.801 --> 00:10:50.426
<v Analyst>That ensures the encryption and controls are FIPS-validated.

00:10:50.560 --> 00:10:52.468
<v Host>What about the timeline for compliance?

00:10:52.909 --> 00:10:59.555
<v Analyst>The DoD CIO announced a suspension of the 2026-11-10 Phase II deadline.

00:10:59.768 --> 00:11:04.871
<v Analyst>Phase I self-assessments remain in force, while later milestones are paused.

00:11:05.146 --> 00:11:08.474
<v Host>So contractors still need to do the self-assessment before the award?

00:11:08.895 --> 00:11:14.747
<v Analyst>Yes, the self-assessment and senior official affirmation remain required for Level One.

00:11:14.951 --> 00:11:15.778
<v Host>And for Level Two?

00:11:16.179 --> 00:11:24.148
<v Analyst>Level Two requires a C3PAO assessment, triennial reassessment, and annual senior official affirmation.

00:11:24.408 --> 00:11:27.142
<v Host>What about the benefits of going through a readiness engagement?

00:11:27.544 --> 00:11:31.749
<v Analyst>It helps map your controls to the NIST framework and identify gaps.

00:11:31.884 --> 00:11:38.964
<v Analyst>It also produces a live POA&M and a mock assessment to prepare for the real C3PAO.

00:11:39.171 --> 00:11:39.884
<v Host>And the cost?

00:11:40.325 --> 00:11:46.386
<v Analyst>A typical Level Two readiness engagement for a mid-size contractor runs 12 to 14 weeks.

00:11:46.574 --> 00:11:52.373
<v Analyst>The full path from gap assessment to C3PAO-ready can take 6 to 18 months.

00:11:52.628 --> 00:11:54.620
<v Host>What are the most common mistakes companies make?

00:11:54.824 --> 00:11:57.667
<v Analyst>Assuming encryption alone solves everything.

00:11:57.856 --> 00:12:05.788
<v Analyst>NIST SP 800-171 requires FIPS-validated cryptography, not just strong encryption.

00:12:05.950 --> 00:12:06.649
<v Host>Another mistake?

00:12:06.792 --> 00:12:10.250
<v Analyst>Confusing distribution statements with CUI markings.

00:12:10.422 --> 00:12:13.164
<v Analyst>They are applied in parallel, not interchangeably.

00:12:13.323 --> 00:12:15.170
<v Host>What about subcontractor flow-down?

00:12:15.569 --> 00:12:26.829
<v Analyst>DFARS 252.204-7012 must flow down to subcontractors when performance involves covered defense information.

00:12:27.026 --> 00:12:29.395
<v Analyst>Failure to do so can lead to penalties.

00:12:29.563 --> 00:12:31.617
<v Host>What about the incident reporting timeline?

00:12:31.974 --> 00:12:35.184
<v Analyst>You must report within 72 hours of discovery.

00:12:35.334 --> 00:12:38.035
<v Analyst>Then preserve evidence for at least 90 days.

00:12:38.286 --> 00:12:41.425
<v Host>So the registry really drives the entire compliance framework.

00:12:41.752 --> 00:12:46.409
<v Analyst>Yes, it determines what baseline you need and what controls to implement.

00:12:46.712 --> 00:12:50.649
<v Host>What about the difference between CUI Basic and CUI Specified?

00:12:51.057 --> 00:12:56.028
<v Analyst>CUI Basic has uniform controls at a moderate confidentiality baseline.

00:12:56.249 --> 00:13:01.727
<v Analyst>CUI Specified carries handling controls written into the underlying law or policy.

00:13:01.882 --> 00:13:03.738
<v Host>Does that affect the marking requirements?

00:13:04.176 --> 00:13:07.894
<v Analyst>The banner marking and designation indicator apply to both types.

00:13:08.038 --> 00:13:11.925
<v Analyst>But CUI Specified may require additional handling rules.

00:13:12.237 --> 00:13:15.570
<v Host>So the key takeaway is that the registry tells you what you need to do.

00:13:15.741 --> 00:13:18.680
<v Host>Now, what should organizations do about this?

00:13:19.037 --> 00:13:27.178
<v Analyst>The first thing you need to do is inventory every contract you hold and identify which ones contain Controlled Unclassified Information.

00:13:27.511 --> 00:13:31.240
<v Host>So you’re looking at a list of contracts, not just a list of systems?

00:13:31.662 --> 00:13:48.319
<v Analyst>Exactly. DFARS 252.204-7012 requires that any system receiving or generating CUI be covered by the full set of 110 NIST SP 800-171 controls.

00:13:48.667 --> 00:13:52.790
<v Host>And if you only have Federal Contract Information, you’re looking at a different baseline?

00:13:53.239 --> 00:14:09.058
<v Analyst>Right. For FCI only, the FAR 52.204-21 baseline of 15 basic safeguarding requirements applies, plus an annual self-assessment and a senior official affirmation for CMMC Level One.

00:14:09.329 --> 00:14:14.360
<v Host>So the registry is essentially a mapping between the type of information and the security controls you must have?

00:14:14.768 --> 00:14:26.858
<v Analyst>That’s correct. The registry tells you whether your environment is subject to the 110 controls or the 15 basic safeguards, and it also tells you which marking and handling rules apply.

00:14:27.158 --> 00:14:31.146
<v Host>What about the actual marking? Do we need to put a banner on every page?

00:14:31.557 --> 00:14:45.236
<v Analyst>Yes, 32 CFR 2002.20 requires a CUI banner marking on every page that contains CUI, along with a designation indicator naming the agency that designated the information.

00:14:45.414 --> 00:14:47.784
<v Host>And distribution statements don’t replace that?

00:14:48.173 --> 00:15:01.017
<v Analyst>Correct. Distribution statements governed by DoDI 5230.24 run in parallel; they do not satisfy the CUI marking requirement, so you must still add the banner.

00:15:01.279 --> 00:15:08.713
<v Host>Moving on to encryption, the article says FIPS-validated cryptography is required. What does that mean in practice?

00:15:09.115 --> 00:15:22.755
<v Analyst>NIST SP 800-171 requires that any encryption used to protect CUI be FIPS-validated. A strong algorithm that isn’t validated against the FIPS standard does not meet the requirement.

00:15:23.011 --> 00:15:25.783
<v Host>So a commercial encryption tool could still be insufficient?

00:15:26.187 --> 00:15:35.525
<v Analyst>Exactly. You need to verify that the encryption suite you deploy is FIPS-validated, or you must use a vendor that offers a validated solution.

00:15:35.785 --> 00:15:41.057
<v Host>Now, what about incident reporting? The article mentioned a 72-hour window.

00:15:41.310 --> 00:15:59.628
<v Analyst>DFARS 252.204-7012 requires you to report any cyber incident that affects covered defense information within 72 hours of discovery via the DoD reporting portal at dibnet.dod.mil.

00:15:59.897 --> 00:16:01.943
<v Host>What happens after you file the report?

00:16:02.317 --> 00:16:16.001
<v Analyst>After filing, you must preserve images of affected systems and monitoring data for at least 90 days, submit isolated malicious software to the government, and hold any cloud providers to a FedRAMP Moderate baseline.

00:16:16.186 --> 00:16:18.005
<v Host>That’s a lot of post-incident work.

00:16:18.281 --> 00:16:29.512
<v Analyst>Yes, and remember the 180-day POA&M closeout requirement for any ‘not met’ controls under 32 CFR 170.21.

00:16:29.842 --> 00:16:35.255
<v Host>Speaking of POA&Ms, what is the difference between a gap analysis and a live POA&M?

00:16:35.684 --> 00:16:49.209
<v Analyst>A gap analysis identifies the gaps between your current controls and the required 110 controls, while a live POA&M tracks remediation actions, owners, and timelines for each identified gap.

00:16:49.495 --> 00:16:54.322
<v Host>How long does it typically take to get from a gap analysis to a C3PAO-ready state?

00:16:54.704 --> 00:17:07.150
<v Analyst>For a mid-size contractor, the path from gap assessment to C3PAO readiness usually takes between six and eighteen months, depending on starting posture and CUI environment complexity.

00:17:07.481 --> 00:17:13.273
<v Host>What about the actual assessment itself? Do you need to do anything special before the C3PAO comes?

00:17:13.668 --> 00:17:26.706
<v Analyst>You need a live, validated System Security Plan covering all 110 controls, a POA&M with evidence pointers, the 14 control-family policies, and an incident response plan.

00:17:26.960 --> 00:17:29.599
<v Host>And the scoring for the Supplier Performance Risk System?

00:17:30.046 --> 00:17:52.178
<v Analyst>DFARS 252.204-7019 requires you to submit a current NIST SP 800-171 assessment summary score in SPRS when you submit an offer. The score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points.

00:17:52.523 --> 00:17:53.968
<v Host>That seems like a lot of paperwork.

00:17:54.308 --> 00:18:04.385
<v Analyst>It is paperwork, but it’s a single, repeatable process. Once you have a baseline score, you can use it to track progress and demonstrate compliance to DoD.

00:18:04.649 --> 00:18:08.348
<v Host>What are some common mistakes that contractors make when dealing with CUI?

00:18:08.757 --> 00:18:16.413
<v Analyst>One major mistake is assuming encryption alone satisfies the requirement; you must use FIPS-validated cryptography.

00:18:16.568 --> 00:18:17.007
<v Host>Another?

00:18:17.368 --> 00:18:25.252
<v Analyst>Confusing distribution statements with CUI markings is another frequent error; the two are separate and must both be applied.

00:18:25.390 --> 00:18:27.548
<v Host>What about flow-downs to subcontractors?

00:18:27.989 --> 00:18:44.284
<v Analyst>DFARS 252.204-7012 must be flowed down to all subcontractors working on covered defense information. They must also report incidents to DoD and provide the report number up the chain.

00:18:44.568 --> 00:18:49.134
<v Host>So a subcontractor who discovers an incident must report it within 72 hours too?

00:18:49.519 --> 00:18:56.361
<v Analyst>Yes, the same 72-hour requirement applies to any subcontractor handling covered defense information.

00:18:56.690 --> 00:18:58.842
<v Host>What if a subcontractor fails to report?

00:18:59.241 --> 00:19:10.190
<v Analyst>Failure to report can lead to penalties under DFARS and may result in loss of contract or future opportunities, as well as legal liability if the incident causes data loss.

00:19:10.308 --> 00:19:11.748
<v Host>That’s a serious risk.

00:19:12.075 --> 00:19:26.618
<v Analyst>Indeed. The DOJ Civil Cyber-Fraud Initiative has already imposed settlements on major firms, including Verizon, Penn State, Raytheon, and Georgia Tech, for failures related to CUI handling.

00:19:26.905 --> 00:19:28.595
<v Host>How can a company minimize that risk?

00:19:29.002 --> 00:19:46.457
<v Analyst>By following the steps we just outlined: inventory contracts, identify CUI, enclave the CUI boundary, build a live SSP, maintain a POA&M, obtain a validated encryption solution, and ensure timely incident reporting.

00:19:46.789 --> 00:19:49.907
<v Host>What about the timeline for getting a CMMC Level Two certificate?

00:19:50.317 --> 00:20:02.921
<v Analyst>The assessment itself is a C3PAO-only activity; once you’re ready, the C3PAO will conduct the assessment, submit results to eMASS, and the certificate will be stored in SPRS.

00:20:03.237 --> 00:20:05.810
<v Host>So the certificate is not issued by Petronella, right?

00:20:06.215 --> 00:20:14.201
<v Analyst>Correct. Petronella is a Registered Provider Organization; we prepare you for the assessment but do not conduct the certification.

00:20:14.456 --> 00:20:17.615
<v Host>What are the key questions a business should ask a potential provider?

00:20:17.999 --> 00:20:31.385
<v Analyst>Ask whether the provider is an RPO or a C3PAO, what credentials the team holds, what deliverables are included, how they scope the CUI boundary, and what the realistic timeline and cost are.

00:20:31.641 --> 00:20:33.195
<v Host>Do you have a checklist we can use?

00:20:33.553 --> 00:20:48.211
<v Analyst>Yes, we provide a readiness engagement checklist that covers discovery, gap analysis, remediation sprint, and C3PAO readiness handoff, along with a live POA&M and a mock assessment.

00:20:48.397 --> 00:20:49.711
<v Host>That sounds comprehensive.

00:20:49.970 --> 00:21:02.323
<v Analyst>It also includes a baseline SPRS score, the 14 control-family policies, and an incident response plan, ensuring you meet Level Two requirements before the C3PAO assessment.

00:21:02.473 --> 00:21:05.360
<v Host>What about ongoing compliance after certification?

00:21:05.753 --> 00:21:18.411
<v Analyst>Compliance is continuous. You must keep your SSP updated, review the POA&M quarterly, refresh policies regularly, conduct training, and maintain incident response capacity.

00:21:18.662 --> 00:21:22.238
<v Host>So the CMMC assessment isn’t a one-time event.

00:21:22.539 --> 00:21:34.459
<v Analyst>Exactly. The NIST SP 800-171 controls must be maintained, and the CMMC Program rule requires a triennial reassessment for Level Two contractors.

00:21:34.738 --> 00:21:38.309
<v Host>What about the new DoD CIO announcement about the Phase II deadline?

00:21:38.715 --> 00:21:53.861
<v Analyst>On July 13, 2026, the DoD CIO announced the suspension of the 2026-11-10 Phase II deadline, so Phase I self-assessments remain in force but later milestones are paused until further notice.

00:21:54.149 --> 00:21:57.266
<v Host>Does that change anything for contractors currently in Level Two?

00:21:57.672 --> 00:22:06.353
<v Analyst>Not for the self-assessments you already completed; they still count, but you’ll need to stay prepared for the next reassessment cycle when the deadlines resume.

00:22:06.643 --> 00:22:12.090
<v Host>What about the Supplier Performance Risk System scores? How do they affect contract awards?

00:22:12.455 --> 00:22:33.387
<v Analyst>DFARS 252.204-7019 requires a current NIST SP 800-171 assessment summary score in SPRS when submitting an offer. A higher score demonstrates better security posture and can be a differentiator in the evaluation process.

00:22:33.689 --> 00:22:36.323
<v Host>What are the most common questions we hear from listeners?

00:22:36.677 --> 00:22:49.948
<v Analyst>We often get asked about the difference between CUI and FCI, how to handle marking, whether encryption alone is enough, how to set up a POA&M, and what the timeline looks like from assessment to certification.

00:22:50.284 --> 00:22:51.847
<v Host>Any final tips before we wrap up?

00:22:52.414 --> 00:23:09.825
<v Analyst>Make sure you treat the System Security Plan as a living document, keep the POA&M under 180-day closeout, validate your encryption, and flow down all DFARS clauses to every subcontractor. That will keep you compliant and reduce the risk of costly settlements.

00:23:10.105 --> 00:23:13.784
<v Host>Thank you for breaking down the CUI registry and its implications.
