The FAR CUI Rule Could Put Contractors on Rev. 3 Before DoD Does

The hosts walk through the DoD’s history of grace periods, from the 2013 and 2015 rules (none), to the December 2015 extension (two years, to December 31, 2017), to CMMC’s phased rollouts (which gave the assessment ecosystem time to scale rather than extending implementation time). The FAR CUI proposed rule, which would apply NIST SP 800-171 Rev 3 to all federal contractors, has no phase-in, and the hosts say contractors shouldn’t assume the final rule will add one. Defense contractors with other federal work face a particular problem: Rev 3 on federal contracts right away, but possibly Rev 2 on defense contracts for years.

Key Takeaways

  • No on-ramp in the proposed rule. FAR CUI would apply Rev 3 to new federal contracts as soon as it takes effect, though the final rule could change that.
  • History offers little precedent. The DoD gave no grace period in 2013 or 2015. Industry outcry won a two-year extension, but only after the rule was out.
  • CMMC’s phases weren’t implementation relief. They were meant to scale the assessment ecosystem. The 7012 deadline was December 31, 2017, and the clause hasn’t changed since 2016.
  • Suspension doesn’t suspend requirements. 7012 and 800-171 still apply regardless of CMMC’s status.
  • Dual-baseline risk for defense contractors. Federal contracts could require Rev 3 immediately while DoD contracts stay on Rev 2, and it’s unclear whether other agencies will accept CMMC status.
  • Standard form helps. A standard form will tell contractors exactly what is CUI, reducing guesswork.
  • Plan for the worst case. A Rev 2 implementation is a good starting point, and readiness plans should work even with no phase-in.

Transcript

FAR CUI Has No Proposed Implementation Window

Jacob: All right, folks. It’s the end of October 2026, and everybody is waiting for the transition to NIST SP 800-171 Rev 3 requirements. The FAR CUI rule will impose those cybersecurity requirements on all federal contractors once the final rule takes effect, which we anticipate could be as soon as the end of 2026. There’s just one problem. The rule as written provides no implementation window or phased roll-in. Any new contract would include those requirements all at once. The DoD has granted implementation time and grace periods in the past, but the FAR CUI proposed rule provides no comparable runway. That could change in the final rule, but your readiness plans need to anticipate what to do if it doesn’t. That’s what we’re going to talk about today.

Jason, the CMMC phased rollout: defense contractors know it and love it. Federal contractors may have heard of it. It was a DoD strategy to give the assessment ecosystem time to scale for the number of defense contractors that would need third-party assessment. There’s no phased rollout for implementing the NIST requirements in the FAR CUI rule that we know of. So people have to plan for that, because there’s no four- or five-year on-ramp that we expect in this rule.

Jason: Jacob, this close to Halloween, I didn’t expect such a spooky tale. I didn’t expect you to come across the desk and say, “Trick or treat, here’s a rule with immediate implementation.” But here we are. Part of this episode is going to educate me on the thought that each agency’s adoption of a CUI protection program was at its discretion. The Department of Defense just moved way ahead of the curve, and the phased rollout was part of that. It was like a gift from the DoD to the contracting base saying these requirements aren’t coming to you immediately. As of right now, that gift doesn’t exist anywhere else.

Jacob: We’re going to walk through the DoD’s cybersecurity rulemaking history to show what it has done in the past on implementation grace periods. The FAR CUI rule is used by all federal agencies, and as written there’s no general grace period. Back in the day, the DoD didn’t have implementation grace periods either. So I don’t think it’s guaranteed that people will see long windows of time to get familiar with and implement requirements, because we’re in uncharted territory with the FAR versus the DoD space. That’s important for federal contractors, and it’s super important for defense contractors who also have other federal contracts, because you have multiple things to juggle at once.

Jason: So you’re about to tell us how they started something, realized there was a way to make it better, and instead of stopping completely, made it better and continuously improved?

Jacob: Funny enough, yes. It’s a crazy idea. Let’s look at the quick history of how the DoD has handled this. They had a group of contractors and a set of cybersecurity requirements they wanted implemented right away. What did the DoD do, facing the issue that all the other federal agencies and contractors are about to face very shortly?

2013–2016: When DoD Granted More Time

Jacob: In November 2013, the timeline really starts for DoD cybersecurity requirements in contracts. This is the first time cybersecurity requirements arrive for non-federal systems processing federal data in defense contracting. It was the DoD’s original safeguarding rule for controlled information on contractor networks. It went into effect when it was published. No grace period, no phased rollout, no separate compliance period or on-ramp. This contract clause, which we now know as DFARS 252.204-7012, was originally created then. It required controls from NIST SP 800-53, the master catalog of security controls, and it predates NIST SP 800-171. The DoD said, “Tada, we’ve got a new clause. If you’re processing our data on your system, here are the requirements you need to implement right now. No timeline, no plan of action and milestones, no phased rollout.”

Jason: Before I make my comments, as any wholehearted cyber nerd would do, all praise be to 800-53. But what you just described sounds like the same boat we’re in 13 years later.

Jacob: It bears a lot of similarities. The 2013 rule said do these requirements, and by accepting the contract terms you’re telling us you’re doing them. There was no third-party audit mechanism, which is a big problem if you know the history of why CMMC was created. Fast forward to August 2015. Sure enough, there’s a national security crisis with the hack of the OPM system. Non-federal systems were processing federal information in the cloud, and there was no provision in the 7012 clause about FedRAMP, cloud protections, or incident reporting. So they jammed out an emergency rule modifying 7012 in August 2015. They said don’t do those 800-53 requirements. We have a smaller set for you to focus on, which we’re calling NIST SP 800-171, derived from 800-53. According to the DoD at the time, it was a 20 to 30 percent reduction in what contractors were required to do compared with 2013.

It required implementing the new version at contract award. No grace period, no phased roll-in, no on-ramp, no 30-, 60-, or 90-day window to get familiar. If you’re bidding on a contract, the requirements are due at the time of award. The DoD emphasized the national security impact and urgency of protecting controlled defense information and reporting incidents. This is the DoD, folks. About ten years ago, they said, “Here are your requirements, do them right now.”

Jason: What they did was narrow the requirements. They took a selection of 800-53 controls from that massive catalog, and if I remember correctly, a majority were the confidentiality baseline, the predecessor to the 800-171 we live in today.

Jacob: So we’re two rules in, several years into the department prescribing requirements, with no phased roll-ins. The reaction to the August 2015 rule was intense, to say it in a word. Industry went to the DoD and said we need time to implement. The DoD’s reaction was basically, “What do you mean you need time to implement a smaller set of requirements than what you’ve been doing for the last two years?” But whatever, we’re all friends here, we had to issue this rule because of a national security emergency. Then in December 2015 they issued a follow-up rule that gave industry an explicit extension: until December 31, 2017 to implement the 110 requirements in NIST SP 800-171. Two years to implement a smaller baseline than the one they’d supposedly been implementing since 2013. The DoD acknowledged the concerns and said, “Okay, maybe some contractors can’t comply with these existing terms. Water under the bridge. Here are two years.” You can’t fight city hall. This was the first time the DoD gave an on-ramp of time to get ready.

Jason: The DoD acknowledged the risk and eventually acknowledged the time needed to mitigate it. What wasn’t acknowledged was industry’s acknowledgment that it now had requirements, because, as history tells us, this didn’t spin up immediately. Not everybody rushed to implement 800-171. It led to more stalling until closer to that deadline.

Jacob: Then another follow-up rule came out in October 2016, and the DoD preserved the December 2017 deadline. That was the final tweak to DFARS clause 252.204-7012, and it hasn’t changed since. The 7012 clause in your contracts today went into effect in October 2016 and hasn’t changed in ten years. All your FedRAMP requirements, incident reporting requirements, and the requirement to implement 800-171 are in it, and you can still see the language saying the deadline for compliance is December 31, 2017. If you’ve been a defense contractor since at least 2017, that’s the problem that eventually led to the CMMC program. So that’s how we ended up with the clause we have now. We started in 2013 with the original baseline, an emergency happened in 2015, industry said it needed more time, the DoD gave two extra years, and then it put a period on the sentence: “Yes, 2017 is the deadline. Thanks for playing.” And still no third-party requirement to prove you were implementing and complying, which sure enough leads to yet another problem.

Jason: Still no mention of a phased rollout or third-party validation. And we have to mention that it doesn’t bother us one bit that the clause hasn’t been updated since it was first published.

Jacob: It’s pretty crazy, because that clause holds a lot of weight. It’s the source of the cost and burden on contractors. It imposes the requirements, and the requirements are what cost money to comply with.

CMMC: Phasing Assessments, Not Safeguards

Jacob: Fast forward to 2020, and there’s yet another national security crisis, directly the result of unclassified contractor systems being compromised and sensitive data exfiltrated. If we know anything about history, when these things happen, other things happen to compensate for what should have been happening.

Jason: There you go. Give him a PhD, folks.

Jacob: A big investigation follows. The DoD Inspector General finds that all these contractors said they were implementing the requirements, and they weren’t. So we need a mechanism for holding them accountable. The Armed Services Committees read that report and say great idea. They put a provision in the FY20 NDAA telling the DoD to create a mechanism holding contractors accountable to prove they’re implementing the requirements they said they’d been implementing since at least 2016, really since 2013. What they came up with was the CMMC program, what we now call CMMC 1.0. That rule came out in 2020, and the DoD established a five-year phased rollout. Remember, that wasn’t an implementation rollout for the 7012 requirements. That deadline ended in 2017. It was a phased rollout for the assessment program to come online slowly over five years. The wink and nod from the department was, “You need to get ready to go under assessment. We know you haven’t implemented the requirements. We’ll take five years to cycle everybody into third-party assessments, so make sure you implement the requirements that were due in 2017.” If you read the rule, they say they assume everybody has implemented all the requirements in NIST SP 800-171 and 7012, but the entire reason for the CMMC rule is that they know people hadn’t. So the concession to industry was time to scale up the assessment ecosystem, and the second benefit was time to catch up on implementation.

Jason: The first benefit of this history lesson is for people to understand this was a directive of the Armed Services Committees, not a group of people sitting in some office trying to find ways to make more money for consultants.

Jacob: If this was anybody’s individual idea, it was Secretary of Defense James Mattis’s. It wasn’t some random bureaucrat low down in the DoD CIO’s office or the acquisition and sustainment office. This was a real national security problem with major impacts on the lethality of the joint force. There were task forces and Armed Services hearings, and there’s a statute in place. This wasn’t an accidental thing somebody thought of one day.

Jason: And it still exists for that same reason. The other lesson is that small business was thought about, and the burden on it, from the get-go, from the Armed Services Committees through the government.

Jacob: The phased rollout had a lot of benefits. Rewind to 2018 or 2019, when this crisis was unfolding. Even with evidence that contractors weren’t complying with requirements the DoD had already given a two-year extension to implement after the previous crisis, the DoD still said it would take five years before fully implementing the assessment program. The original requirements came out in 2013, and full third-party assessment wasn’t supposed to be done until 2025. Even in the wake of a national security emergency, there were many concessions, and one explicit one was impact on small business. Nevertheless, the reaction to the CMMC rule was swift and mostly uninformed, because people were learning that they’d had requirements in their contracts since 2016 or 2013 when they heard about CMMC for the first time. To this day, people associate their requirements with CMMC. We hear it at shows, at conferences, on the phone every day: “CMMC is suspended, therefore my cybersecurity requirements are suspended.” They’re different things. The 7012 clause went into effect in 2016 with a 2017 deadline and hasn’t changed in ten years, regardless of what’s going on in the CMMC program. In the pause, the only thing we’ve paused is validation of things you still have to do. These are all still your responsibilities.

Jason: I just thought of something crazy. The CMMC 1.0 phased rollout was 2020, and we’re about to enter 2027. Imagine you fell into a seven-year coma and woke up knowing about CMMC in 2020: “Yeah, phased rollout, everything’s going to be secure.” Now it’s about to be 2027, and you ask, “So CUI’s secure, right?”

Jacob: I’ve said it a million times: the further you zoom out from the current debate, and the more context you have about the evolution of DoD cyber requirements over time, the more obvious it becomes that allowing self-attestation hasn’t worked. It does not work. They’re going to have to get people to prove it somehow. Human-powered assessments, AI-powered, who knows what the solution is, but the status quo of the last ten years doesn’t work.

Jason: Are you using facts to defend your argument?

CMMC 2.0 and the Contractual Rollout

Jacob: Nevertheless, the reaction to the 2020 rule was that it felt like a new burden, new burden costs money, I don’t like it, get rid of it. Then there was an election, an administration change, and rulemaking started again. It wasn’t until 2024 that we got the CMMC 2.0 final rule outlining the program: everything about CMMC you know and love, the three levels, the roles and responsibilities, the assessment guide, the scoring and POA&M guidance. All of it was codified in the rule at the end of 2024. It also had a phased rollout, four phases instead of the five in the 1.0 rule, and that rollout would start when the corresponding contract clause rule went into effect. Under 2.0, CMMC is one program made up of two rules: a program rule, with roles, responsibilities, how assessments are run, how waivers are issued, and a contract clause rule to implement it in contracts. We didn’t get the contract clause rule until 2025, which is why Phase 1 started in November 2025, even though the program was created in 2024. DFARS 252.204-7021 is the contract clause where people fill out whether they need Level 1, Level 2 self-assessment, Level 3, and so on. You can only have contract clauses if they’re created or modified by a regulation, and those have to go through rulemaking.

So we’re in the phased rollout of CMMC 2.0, and we’re supposed to move to Phase 2 in November 2026. But as of this conversation, we’re in a suspension while they review the program yet again to tell us the new direction. There will almost certainly be a phased rollout of sorts, as there has always been with CMMC, even though they have plenty of assessment capacity to spare. That begs the question of why you need more phases when your ecosystem is already scaled and the phases weren’t for implementation. But I’m certain they’ll keep it.

To summarize: the December 2015 extension bought everyone two years to implement safeguarding requirements for DoD data on non-federal contractor systems. CMMC’s phased rollout was designed to give the assessment ecosystem time to scale so there’d be enough assessment capacity for everybody to prove they implemented their requirements. Those are different forms of relief. One extension was granted in 2015, and the phased rollout is an element of the program. The secondary benefit was giving people more time to implement, but that wasn’t the purpose.

Jason: What I just heard is a journey of a CUI program that started in 2013, took almost 14 years, still isn’t completed, and is at a pause. The path started at the same point as a rule that’s about to pass, with the same characteristics. So if history repeats itself, by 2038 we’ll be pausing all CUI implementations.

Jacob: In all seriousness, it took so many revisions and rules to arrive at a place where there was relief for all parties while the risk was being mitigated.

Jason: So will we learn from the mistakes? Is this the canary in the coal mine?

What Contractors Can, and Can’t, Assume

Jacob: Maybe. Here’s where it gets relevant. Depending on what they decide, you could have a lot of time or no time to implement these requirements, a potentially massive difference, and you won’t know until the rule comes out. Business is about taking risk, but understand the dice you’re rolling before you roll them if you decide to bet there will be relief.

Jason: Are grace periods par for the course, common courtesy, or just sometimes?

Jacob: The only precedent is the DoD’s rules from 2013 and 2015. In 2013, when the DoD said you have cyber requirements, there was no grace period. In 2015, when it said you have updated requirements, no grace period. Then it responded to industry and said you have two years, not a grace period, just a new deadline. Once that deadline passed, it hasn’t changed implementation periods in ten years. All the other phased implementations are for assessment programs spinning up and scaling.

Now we come to the FAR CUI rule, which will take this DoD rule and expand it to the rest of the federal ecosystem. When you’re processing CUI from any federal agency on your contractor-owned non-federal system, you must comply with NIST SP 800-171 Rev 3. As of June 2026, the last time we saw the draft proposed regulation, there’s no grace period, no phased rollout, and no on-ramp. It just says here’s the contract clause that goes into effect when the rule does. If you’re going after new awards after that effective date, those are the requirements. To be clear, this doesn’t mean existing federal contracts will change. It means new federal opportunities will have these requirements, without a grace period. If you aren’t familiar with how 800-171 works, the documentation, and how to prove you’re implementing it, you’re attesting to the government that you’re doing these things. This isn’t ISO. It’s not SOC 2. There’s a lot involved. As of now, we have no indication of a phased rollout.

Jason: Given the way government works, there’ll be no indication that the rule’s coming out until it’s published in the Federal Register and some dude with a beard hops on LinkedIn: “Boop boop. Alert!” That’s the warning organizations get for the assumed requirement that you already have basic fundamental cybersecurity practices in place to do contract work with the federal government.

Jacob: The rulemaking for the FAR CUI rule has had very few public comments, and most have come from defense contractors, because they’re aware of what’s going on after being stuck in this terrible journey for over ten years. Most federal contractors have no idea this is coming. So if you’re a federal contractor, build your readiness around the proposed rule’s requirements, because we won’t know what the final rule says until it’s published, and we won’t know when it’s published until a couple of days before it goes up. Follow us on LinkedIn, because we constantly monitor this obscure world of rulemaking for any hint of what’s happening. But even for people who live and breathe it, it’s an opaque process, and sometimes you only get a day or two of indication that something is going to happen.

Unlike the DoD, contrary to popular belief, the federal group in charge of the FAR CUI rule doesn’t have conferences, press releases, videos, or websites around this stuff. They don’t communicate about these requirements at all. The DoD, in comparison, hasn’t stopped yapping about these requirements for 15 years: town halls, conferences, websites, press releases, videos, all telling everybody about the requirements. Pop quiz: tell us in the comments who’s in charge of the FAR CUI rule. What’s their name? You have no idea, because they don’t go outside. They don’t feel obligated to tell federal contractors what these requirements are, but they’re certainly going to put them in your contracts pretty soon. So don’t assume you’ll get a future grace period. You can take that risk. In the past, the DoD responded to contractor outcry and gave an extension, but only after the rule had come out. Will the people in charge of the FAR CUI rule respond to a more disconnected group of contractors, who aren’t as tuned in as the defense sector was in 2015? If you believe they’ll make a concession, plan accordingly. If you don’t, plan accordingly.

Jason: The only positive the FAR CUI rule has going for it that the CMMC rule didn’t is the standard form. A lot of the confusion with the DoD CMMC rule was what’s CUI, especially in contracts where people attached these clauses. Now there’s no questioning it, no searching, no migrations on things you think might be it. It’s: this is what we need you to protect, sign here saying you’ll protect it.

Jacob: There will be a standard form with a checkbox where the contracting officer says, “You do have CUI pursuant to this contract. Please comply with these requirements accordingly. Have a nice day.” Pretty cut and dry.

Defense Contractors: One System, Two Baselines

Jacob: Okay, defense contractors, thanks for watching to the end. Everyone gather around. If you’re a federal contractor, keep scrolling. Defense contractors, family meeting. You have a pretty complicated problem, and we don’t know what the answer will be, because we’re still in the middle of the CMMC suspension. The inadvertent consequence of this suspension is that it could easily make things a lot harder for you, which is not how it was advertised. Your existing 800-171 implementation and CMMC prep work are a great foundation. The transition to Rev 3 from a full Rev 2 implementation isn’t that crazy a project. The transition to full Rev 3 from zero is a big, big project. So if you’re unsure what’s going on with Rev 3, your existing Rev 2 focus is a perfectly good starting point. Lots of people will have uplift and transition programs, especially if you’re working with us. We have all that planned out.

However, we don’t know the DoD’s timeline for its transition to Rev 3. The FAR CUI rule is expected by the end of this year, and we don’t expect a phased rollout for implementation. That means starting in early 2027, if you have federal contracts, you must comply with Rev 3. But if you also have defense contracts, you must comply with Rev 2. So what are you supposed to do? We did a previous episode on this. The DoD in 2024 explicitly anticipated this and put provisions in place to avoid it, and those provisions are now nullified by the Phase 2 suspension. If the DoD comes out of this suspension and says, “We’ll do rulemaking to transition everybody to Rev 3, and here’s the transition timeline,” that could be one, two, or three years before Rev 3 is fully required. Meanwhile, you’ve got one, two, or three years of federal contracts that say do Rev 3 right now.

What we don’t know is whether federal agencies other than the DoD will respect your CMMC status. If you have a Level 2 status that says you’ve proven you’ve implemented 800-171, will they accept that as evidence of complying with the FAR CUI rule, even though it verifies a different baseline? We don’t know the DoD’s policy. We don’t know whether it will ask other agencies to accept it, or whether other agencies will ask for their own proof of Rev 3 while the DoD asks for proof of Rev 2. It’s a mess, and the DoD hasn’t given us any answers. So if you’re a defense contractor with federal contracts, pay attention, because you might have to move to Rev 3 a lot faster than the DoD says.

Jason: I think this gives the wider contracting base much more forewarning than the DoD’s requirements gave. So organizations hopefully aren’t as blindsided. They’re more modernized, and with the standard form, this might be a less painful process.

Jacob: If you only do defense contracts and the DoD says, “We’ll give you three years to transition from Rev 2 to Rev 3,” awesome. You have a ton of time for not many deltas. But if you also have a federal contract, you must satisfy Rev 3 immediately after the FAR CUI rule, not on the DoD’s schedule. And if you have one contractor system where all your CUI lives, you now have a big problem juggling two baselines for the same system. It will take a lot of overhead, management, and thought, and we haven’t heard what the DoD’s answer will be. I wouldn’t bet the farm there will be one.

Jason: There’s a possible situation where an organization was three-quarters of the way through Rev 2 implementation for CMMC Level 2, heard of the pause, hit pause, and when they hit resume, it’s full speed to Rev 3.

Jacob: That could easily happen. It’s not how I’d do it if I were in charge, but they didn’t ask me. We’ll all find out together what the plan will be from the DoD and, if any, in the FAR CUI rule.

Plan for a Rule Without an On-Ramp

Jacob: The primary takeaway is that the final FAR CUI rule could provide an on-ramp or transition window, but your readiness plan, as a federal or defense contractor, needs to work if there isn’t one. At this point, we just don’t know, and if you’re wrong, it could be very painful. Like and subscribe for all the updates coming around the corner on these rules and requirements, and we’ll see you next week.

Jason: See you next week.

Contact

Speak With Our Team

Scroll to Top