Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Encrypted Ambition: Where Ambition Meets Encryption - Inside The Minds Of Disruptors.

Encrypted Ambition: Where Ambition Meets Encryption - Inside The Minds Of Disruptors. artwork

When Information May Be CUI in Accordance with Policy

Nov 18, 202623 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Read the full article: https://petronellatech.com/blog/compliance/when-information-may-be-cui-in-accordance-with-policy/ A conversation about "When Information May Be CUI in Accordance with Policy" from the Petronella Technology Group, Inc. blog. Subscribe to Encrypted Ambition and hear every episode: https://petronellatech.com/podcasts/ Questions about AI, cybersecurity, or compliance for your business? Call Petronella Technology Group, Inc. at 919-348-4912.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Chapters

  1. Introduction
  2. When Information May Be CUI in Accordance with Policy
  3. What organizations should do
  4. How to reach us

Transcript

From the show. Tap a time to play from there.

HostToday 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.

AnalystExactly. 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.

HostSo the origin is federal, not just a contractor’s discretion. But what does that mean in practice for a defense contractor?

AnalystWhen 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.

HostThat’s a big jump from the 15 basic safeguards for Federal Contract Information.

AnalystIt 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.

HostLet’s break down the marking requirements. I hear that every page of a CUI document must have a banner.

AnalystUnder 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.

HostAnd if it’s a DoD technical drawing, does a distribution statement replace the banner?

AnalystNo, 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.

HostSo a document can be marked for distribution and still be CUI if it meets those criteria.

AnalystCorrect. The two controls run in parallel. You can have a DoD technical document that is CUI, and you must apply both sets of markings.

HostWhat about the difference between CUI Basic and CUI Specified?

Analyst32 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.

HostSo you first identify the authority that designates the information.

AnalystExactly. 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.

HostAnd then you confirm that the government is the designating source.

AnalystYes. 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.

HostAfter that you need to separate FCI from CUI.

AnalystThat 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.

HostWho bears those responsibilities?

AnalystEvery 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.

HostSpeaking of scope, how do you decide where CUI will live in your environment?

AnalystYou 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.

HostSo the enclave approach is a practical way to keep the 110 controls from bleeding across the entire network.

AnalystExactly. Our consulting team treats the CUI boundary decision as the first major milestone of any engagement for that reason.

HostOnce you know CUI is in scope, what changes for you?

AnalystDFARS 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. 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.

HostAnd after you report, what else do you have to do?

AnalystYou 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.

HostSo encryption alone isn’t enough.

AnalystRight. 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.

HostWhat about the Supplier Performance Risk System, the SPRS?

AnalystDFARS 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.

HostThe SPRS score ranges from minus 203 to 110, right?

AnalystYes, controls are weighted at 1, 3, or 5 points. That score must be current at the time you submit an offer.

HostAnd the CMMC program comes into play when DFARS 252.204-7021 is in the contract.

AnalystExactly. 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.

HostSo there are three levels to consider.

AnalystLevel 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. 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.

HostThat’s a lot of moving parts.

AnalystAnd 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.

HostSo it’s not just a bureaucratic exercise-there are real penalties.

AnalystDefinitely. 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.

HostAnd then you score yourself honestly before anyone else does.

AnalystRight. 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.

HostAnd the full path from gap assessment to C3PAO-ready takes 6 to 18 months depending on starting posture and complexity.

AnalystExactly. And after certification, the SSP remains a living document, the POA&M is reviewed at least quarterly, and re-assessment occurs every three years.

HostWhat about the difference between an RPO and a C3PAO?

AnalystPetronella 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.

HostSo if you’re looking for a readiness engagement, you need to ask the right questions.

AnalystYes. 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.

HostAnd about scope-how do you handle enclave decisions?

AnalystAsk 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.

HostWhat if you’re unsure whether a contract involves CUI?

AnalystTreat 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.

HostSo the next step for an organization is to start that decision process. What should organizations do next? Let’s dive into what the decision process actually looks like in practice, step by step.

AnalystFirst, pull every active DoD contract and subcontract, then identify any DFARS 252.204-7012 clauses.

HostThat clause is the trigger for the 110 NIST controls you’ll need to apply.

AnalystNext, you need to find the cited authority-read the law, regulation, or policy the agency used.

HostOnce you locate that authority, confirm the agency is indeed the designating source.

AnalystThat’s because CUI designation is a government act; the designation indicator on a document must name that agency.

HostAfter that, distinguish Federal Contract Information from CUI-it’s the fork that determines the regulatory regime.

AnalystFCI triggers the 15 basic safeguarding requirements of FAR 52.204-21, while CUI triggers the full 110 controls of NIST SP 800-171.

HostIf a contract contains DFARS 252.204-7012, you’re looking at the full NIST set regardless of whether you think the data is FCI.

AnalystThe next step is to trace where the CUI will live-identify the systems that will store, process, or transmit it.

HostDFARS 252.204-7012 requires adequate security on every covered contractor information system, so that mapping is critical.

AnalystYou 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.

HostEnclaving reduces audit surface, shortens timelines, and lowers ongoing cost, but it’s a design decision that must be documented in your System Security Plan.

AnalystOnce you know the boundaries, perform a self-assessment against NIST SP 800-171 Revision 2, recording a score that reflects the weighted controls.

HostDFARS 252.204-7019 requires that you post that current assessment summary score in the Supplier Performance Risk System when you submit an offer.

AnalystThe score ranges from minus 203 to 110, with controls weighted at 1, 3, or 5 points, so precision matters.

HostAfter you submit that score, the contracting officer can verify it under DFARS 252.204-7020, which gives DoD a path to audit your evidence.

AnalystIf your contract also includes DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award.

HostCMMC Level One covers FCI with the 15 basic safeguards, a self-assessment, and a senior official affirmation each year.

AnalystLevel 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.

HostThen you must go through a triennial reassessment and an annual senior official affirmation to keep the certificate valid.

AnalystThe process from gap assessment to C3PAO readiness can take 6 to 18 months, depending on how mature your controls already are.

HostCommon mistakes often start with the assumption that unmarked documents are uncontrolled.

AnalystBut 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.

HostAnother frequent error is confusing DoD distribution statements with CUI markings.

AnalystDoD Instruction 5230.24 governs distribution statements, but those statements do not satisfy the CUI banner requirement; they run in parallel.

HostEncryption is another area where many think they’re covered, but NIST SP 800-171 requires FIPS-validated cryptography to protect confidentiality.

AnalystStrong but unvalidated encryption does not meet the requirement, and DoD CIO FAQ clarifies that encrypted CUI is still CUI.

HostIf you’re working in a cloud, the data still needs a FedRAMP Moderate baseline or an equivalent certification.

AnalystScope sprawl is another common mistake-if you leave CUI across the entire enterprise, you’ll be required to apply the 110 controls everywhere.

HostThe enclave approach keeps the controls confined, but it also requires you to clearly document the boundary in your SSP and POA&M.

AnalystWhen 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.

HostThat verification step is part of the overall flow-down requirement; it ensures subcontractors also meet the same controls.

AnalystSpeaking of subcontractors, DFARS 252.204-7012 requires you to flow down the 110 controls to any subcontractor that handles covered defense information.

HostThey must report incidents to you, give you the report number, and keep images of affected systems for at least 90 days.

AnalystIncident response duties also include submitting isolated malicious software to the government and holding your cloud provider to a FedRAMP Moderate baseline.

HostRemember, NIST SP 800-171 requires FIPS-validated cryptography; strong but unvalidated encryption does not meet the requirement.

AnalystThe CMMC program rule, published on October 15, 2024, took effect December 16, 2024, and it introduced the three levels of certification.

HostIf your contract includes DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award.

AnalystThe DoD CIO announced on July 13, 2026, that the Phase II deadline was suspended, but Phase I self-assessments remain in force.

HostThat means you still need to submit a current assessment summary score for any offer, but you can pause the later milestones.

AnalystThe enforcement side is real; the DOJ’s Civil Cyber-Fraud Initiative has settled cases against contractors for misrepresenting their security posture.

HostRecent 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.

AnalystThese cases remind contractors that accurate self-assessment and honest reporting are not optional; they are legal obligations.

HostSo what do you do if you’re unsure whether a contract involves CUI?

AnalystStart with a contract inventory: pull every active DoD contract and subcontract, and note which clauses actually appear.

HostThen walk your teams through the data they receive, generate, and store for each contract, asking where it lives and who touches it.

AnalystIf you find a document with a CUI banner or a designation indicator, you’ve identified a CUI instance that triggers the NIST safeguards.

HostIf the marking is absent but the underlying law suggests control, flag it for a determination rather than guessing.

AnalystThe 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.

HostOnce you’ve made that determination, map the systems that will host the data-whether it’s an on-prem server or a cloud tenant.

AnalystApply the 110 controls only within that enclave; the rest of your network can remain at the baseline level required for FCI.

HostAfter that, run a self-assessment against NIST SP 800-171 Revision 2, record a score, and post it to SPRS.

AnalystThe score must include the weighted points-controls are worth 1, 3, or 5-so do the math carefully.

HostIn the System Security Plan you’ll document the boundary, the controls you’re applying, and the owners responsible for each.

AnalystThe POA&M should be live, with owners assigned to each gap and a deadline for remediation; review it quarterly.

HostRemember that POA&Ms are only allowed for ‘not met’ requirements within the limits of 32 CFR 170.21, with a 180-day closeout.

AnalystOnce you submit your score, the contracting officer can verify it under DFARS 252.204-7020, which gives DoD a path to audit your evidence.

HostIf you’re subcontracting, remember that the 110 controls must flow down, and your subcontractors must report incidents to you.

AnalystThey 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.

HostIncident response is a big part of DFARS 252.204-7012; you must report within 72 hours to the DoD portal at dibnet.dod.mil.

AnalystThat portal requires a DoD-approved medium assurance certificate, which you must obtain in advance of any incident.

HostAfter reporting, you must preserve evidence for 90 days and provide isolated malware to the government.

AnalystThe CMMC assessment also requires a baseline score in SPRS, so you need to maintain a current score that reflects any changes you make.

HostYour System Security Plan and POA&M should be living documents, updated at least quarterly to reflect new controls or gaps.

AnalystThe reassessment for Level Two occurs every three years, but you still need an annual senior official affirmation to keep the certificate.

HostA typical Level Two readiness engagement takes 12 to 14 weeks for discovery, gap analysis, remediation sprint, and C3PAO readiness handoff.

AnalystThe 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.

HostCommon questions from listeners include: how do I know which clause is relevant?

AnalystThe answer is to look for DFARS 252.204-7012, 7019, 7021, and FAR 52.204-21; those are the clauses that trigger the controls.

HostAnother question: what if my data is marked with a DoD distribution statement but no CUI banner?

AnalystA distribution statement does not satisfy the CUI banner requirement; you still need to apply the CUI banner if the data is CUI.

HostListeners also ask whether encrypted CUI is exempt from the 110 controls.

AnalystNo, encrypted CUI is still CUI; it still requires the 110 controls and, in a cloud, a FedRAMP Moderate baseline.

HostThank you for that.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Cairn Zero Day Attack Shows Ai Agents Exploited In The Wild

    Nov 21, 202623 minAudio

    Read the full article: https://petronella.ai/blog/cairn-zero-day-attack-shows-ai-agents-exploited-in-the-wild/ A conversation about "Cairn Zero Day Attack Shows Ai Agents Exploited In The Wild" from the Petronella...

    Credit the people on this episode

  2. Zero Trust for Software Supply Chains When Cloud Fails

    Nov 21, 202620 minAudio

    Read the full article: https://petronellatech.com/blog/zero-trust-for-software-supply-chains-when-cloud-fails/ A conversation about "Zero Trust for Software Supply Chains When Cloud Fails" from the Petronella Technology...

    Credit the people on this episode

  3. Qwen Self Hosted Ai Models Need Stronger Steering

    Nov 20, 202617 minAudio

    Read the full article: https://petronella.ai/blog/qwen-self-hosted-ai-models-need-stronger-steering/ A conversation about "Qwen Self Hosted Ai Models Need Stronger Steering" from the Petronella Technology Group, Inc....

    Credit the people on this episode

  4. Java4Shell Exploitation Attempts Begin as Advisories Grow

    Nov 20, 202618 minAudio

    Read the full article: https://petronellatech.com/blog/cybersecurity/java4shell-exploitation-attempts-begin-as-advisories-grow/ A conversation about "Java4Shell Exploitation Attempts Begin as Advisories Grow" from the...

    Credit the people on this episode

  5. Edge Lockdown Mode Disables Gpu Apis To Cut Attack Surface

    Nov 19, 202621 minAudio

    Read the full article: https://petronella.ai/blog/edge-lockdown-mode-disables-gpu-apis-to-cut-attack-surface/ A conversation about "Edge Lockdown Mode Disables Gpu Apis To Cut Attack Surface" from the Petronella...

    Credit the people on this episode