CUI Hotline: 10.30.26

Brief

Jacob, Daniel, and Scott Edwards recap CS5, where morale was better than expected, and they report that Summit 7 added about forty-five Level 2 certified clients since the pause. They discuss why they expect no DoD announcement before the midterms, the Movers for America pushback on the PPA’s Level 2 proposal, and why FAR CUI’s lack of a phased rollout or scoping guide could leave contractors juggling Rev 2 and Rev 3. Audience questions cover ODPs, GSA’s pulled CUI document, GCC High licensing, ITAR admin access, reassessment triggers, and prime flow-down, and the stream ends with Halloween-themed “scary stories.”

Key Takeaways

  • CS5 morale held up. Attendees stayed motivated, and C3PAOs are still doing gap assessments and certifications during the pause.
  • Many see the pause as a bluff. Daniel says the ecosystem is calling the CIO’s bluff, and companies that understand their liability keep moving toward certification.
  • An announcement likely comes after the midterms. The hosts expect no update before the midterms and see the likeliest window as after them but before Phase 2 on November 10.
  • FAR CUI has no phased rollout and no scoping guide. It is expected near year end, so contractors with both Rev 2 and Rev 3 contracts may face two baselines on one system.
  • DoD’s Rev 3 rule may lag FAR CUI. Jacob says the CMMC Rev 3 rule’s waivers may not survive the delay, which could leave DoD two to three years behind FAR CUI.
  • Primes set the real deadlines. No DoD policy created a November 2026 deadline for everyone, and the hosts expect primes to keep setting their own.
  • Export control is a real gap. Certified companies still give non-US persons access to export-controlled data, and the hosts want DoD and State to align.
  • Own your tenant and put MSP promises in writing. Handshake deals leave customers stranded when providers exit.

Transcript

Welcome

Jacob: All right, everybody, it’s Friday. It’s Halloween Eve, everybody, so I hope everybody’s making plans for that. We’re live on LinkedIn. We’re live on YouTube. You can find us at cuihotline.org. You can call the number, fill out the form, send us DMs, or go to summit7.us and find us over there. You can talk to us in chat over here. Lots of ways to get in contact with us. And we’ve got the whole gang together today. The great and powerful Scott Edwards is here. Fresh off… well, I mean, you’re always traveling these days, Scott. It’s been crazy.

Scott: But I did wear purple. I wore purple today for Halloween.

Jacob: Okay. Very spooky. So, there you go. What’s everybody doing for Halloween? It’s supposed to rain in LA.

Scott: Oh, that will be a nightmare.

Jacob: And it’s been a crisis now for multiple weeks. Everyone’s expecting it to rain only tonight, and it’s in shambles. But anyways, Scott, you’ve been traveling around. We were just at CS5. What’s your thought of the week we can review here?

CS5 takeaways: morale and the ecosystem

Scott: You know, I was actually pretty impressed with the turnout at CS5. The tenor of the conference was significantly higher than I expected it to be, with everything going on with the pause. People were still very motivated to share really good content about what’s going on and how they can meet the security requirements. I sat in a three-and-a-half, four-hour manufacturing session, which I thought was really good. There were a lot of manufacturers in that room, and there was fantastic back and forth between the four individuals running that session and everybody in the audience. Everybody was really trying to figure out how to do the right thing, which is what we want everybody to do, right? How do we manage our security? How do we manage this CUI? So really, really good conversation. I’m really impressed with the resilience of the individuals in the ecosystem who are trying to do the right thing. I was encouraged by what I saw at CS5, and we’ll see where this thing goes.

Jacob: There you go. Daniel, you were hanging out at CS5 for a little while?

Daniel: I was. I got to have some really good conversations. One was with a construction organization. They were like, “Hey, we are kind of new to this. We don’t really know what’s going on, what we should be doing.” It was a great conversation. We talked for about an hour, which I thought was pretty cool. Other conversations were around C3PAOs still being able to do gap assessments and even certifications. People are still actively getting certifications. When you walk in the doors, you expect morale, to Scott’s point, to be really bad, but morale is actually fairly good considering where we are with the pause today. People are just trying to make the best of it, and the people taking advantage of the pause by doing assessments and implementation are thriving right now. Take, for example, our customers. We were talking about this before today.

Jacob: Humble brag. Humble brag coming in.

Daniel: Coming in hot, but we’ve done three assessments a week during the pause. So we’ve added, what, forty-five assessments?

Scott: Since the pause was announced, we’ve hit ten to twelve new Level 2 certified clients a month. We’ve added forty-five since the pause started. So people are still working to do the right thing and working to show that they have put in place all the requirements. That doesn’t mean everybody’s doing it, right? We still have some companies that are waiting to get more clarity. You can’t really blame them for that, because clarity is something we don’t have a lot of right now, and especially smaller businesses are really waiting on additional clarity before they make significant investments. But the larger and medium-sized companies are continuing forward as if nothing happened, for the most part. I think it’s really good to see that. Oh, what’s up, Dan?

Daniel: No, go ahead.

Scott: Go ahead.

Is the CIO bluffing?

Daniel: I would phrase my take on the ecosystem at CS5, since July 13th, through the eyes of a degenerate gambler who has won poker tournaments before. If we’re playing a game of poker, the vibe I’m getting from the ecosystem is they think the CIO is bluffing. The language that was used around the suspension back in July has not stuck around in terms of how the ecosystem is reacting. Things have slowed down for C3PAOs, but they certainly haven’t stopped. That’s not what we saw at CS5, and that’s not what we’ve seen in our portfolio of customers since then. The way I’ve told people is, the biggest shift we’ve seen is that companies that understand their liability against current requirements are still doing everything, up to and including getting a certification, for liability reasons. That can range in company size. It’s more a maturity of understanding their risk and liability. Most of the companies that have backed off are those that either feel comfortable taking the gamble, not recommended, or would have easily been knocked off their pursuit of compliance for any number of reasons, let alone this one.

I was just talking to a defense contractor who lives in my neighborhood last night, as we were walking around looking at Halloween decorations, and his biggest gripe was, “When is Rev 3 required?” He’s like, “I’m buying stuff right now in order to meet my obligation. Are you going to give me a year? Are you going to give me six months? Are you going to come out and say do it now? What is the plan?” He was like, “It doesn’t really matter to me whether I have to get certified or not. That’s not really the problem. The problem is which baseline do I comply with?” It was literally nine o’clock at night, and there’s a guy down the street who’s like, “What baseline do I use?” I’m like, “I don’t know, man. We’ve got to wait until they tell us.” Jacob, do you have people knocking on your door in your neighborhood asking you CMMC questions? (laughter)

Jacob: Yeah. Listen, the number of defense contractors in Southern California is pretty dense. There’s a lot of stuff in the greater Long Beach, South LA area, so they’ve got to live somewhere. And yeah, I was out there looking at pumpkins and he was like, “Which baseline do I use?” Because I’m like, “I’m just trying to get some candy, man.” (laughter)

Daniel: That’s fantastic.

Jacob: Yeah. So I can’t wait to see the announcement, because people are calling the bluff. They think it’s a bluff. What do you guys think in chat? You think they’re bluffing? I don’t know. Daniel, managed services.

Export control and CMMC

Daniel: Yeah. I had an interesting conversation this week with somebody. They were like, “We can’t find export control regulated service providers.” They said, “We just got CMMC certified, but we realized that we’re actually not meeting export requirements with the vendors that we have. We have an SRM, but nowhere in the SRM does it talk about…”

Jacob: Did you raise your hand?

Daniel: I did. I said, “As a matter of fact, we are one of these.” (laughter) It’s me. It’s me. It was just kind of an interesting conversation where we had people getting CMMC certified. This is real out there. This is a certified company that was in violation of export control because they were giving non-US persons access to unencrypted technical data. I just thought it was a fascinating thing, and I’m really hoping the DoD and the Department of State get on the same page and start having some better conversations around this.

Jacob: Gosh.

Daniel: I would love, at some point, incorporation of export control requirements into CMMC for applicable specified CUI types. Go ahead and just roll it in there and make it a requirement for somebody to be able to validate US persons of external service providers and internal, or the appropriate licenses in place. So it’d be great.

Scott: It would be. I mean, getting the Department of State and DoD to talk about these topics, and then let everybody know what they’re talking about, right? Is impossible.

Daniel: Scott, that’s not very harmonious. (laughter) I thought we were harmonizing.

Scott: Yeah, I wish we were harmonizing. I really do.

Jacob: What do they say? Culture eats strategy for breakfast. You’re talking about big entrenched cultures, and this wouldn’t be the first time people have been talking big game. This is a long-term culture shift thing you have to manage. It isn’t as simple as rolling in and being like, “We’re going to do XYZ,” because we’ve all been talking about harmonization for a long time. Shout out to the CUI program, which was harmonization before it was cool. Tell your friends.

Movers for America and the PPA proposed rule

Jacob: Speaking of fun things that are going on. Shout out to chat here on the hotline, because we’ve had people bring this up to us before. We’re always learning about new stuff together on the hotline. That’s why I love this show. But this moving industry versus CMMC thing is really coming to a head. Among other very interesting articles on Federal News Network recently, which you should check out, there was an article that came out a couple of days ago about industry pushback on DoD’s proposed rules for their moving program.

As you can imagine, service members move a lot, and PCS moves are a global logistics problem. It’s a big deal. If you’re working in that space as a large moving company, you have access to a lot of privacy information, logistics information, timing and movement information. You have a lot of stuff that you have access to, and that’s potentially an issue. Apparently, and I’m still learning about this space, the way bills of lading and these moving contracts work is not actually governed by standard DFARS clauses in this world. I’m still learning the details, but there’s some other type of agreement that happens that isn’t just “you have DFARS 7012 or you don’t.”

Apparently, back in January, the DoD created the Personal Property Activity, the PPA, which now manages all of the permanent change of station moves. This is a subpart of the Defense Personal Property Program. If any of you were or are in the military, you’re very familiar with DITY moves and PCS moves and all this stuff. Anyways, the PPA published its proposed rules. Everybody loves a good alliteration. In these rules, they say you’ve got to achieve CMMC Level 2. And so the president of Movers for America, Katie McMichael, and multiple other people in charge of these moving companies are writing op-eds saying we shouldn’t have to comply with these requirements.

I was commenting to them yesterday, being like, you’re putting the cart before the horse here. Do you handle CUI or not? Because if you don’t handle CUI, you don’t have an obligation to protect CUI. And if you don’t have obligations to protect CUI, there’s nothing to verify through the CMMC program. If the premise is wrong, don’t concede the premise and then debate the method of verification. You have to go upstream to a different program and a different data flow to figure out if it’s already there. There are other people commenting, former government officials, people who are in government, being like, there have been issues in the past with service members’ privacy information getting compromised and aggregated logistics information, and does this fit into a CUI category? It’s a very fluid space right now.

The Movers for America article and their response was, “We don’t think that we should have to do Level 2. We think we should only have to do Level 1.” My question to them is, have you traditionally had FAR 52.204-21? Have you traditionally had DFARS 252.204-7012? If yes, then you’re in the same situation that all the DIB manufacturers are in. If no, then you’ve got another sequence of problems to debate and figure out. But the PPA is very new. This is as of January. This is like a SECDEF initiative, and they came out and said Level 2. So it’s very interesting.

Daniel: Did you get any feedback from any of these individuals at Movers for America on whether they’re handling CUI or not?

Jacob: They have not responded to my line of inquiry yet, but hopes are high. We’re trying to help. We’re here to help.

Daniel: So I know a guy, Ryan Bonner, who could probably help him out with that very quickly, right? (laughter)

Jacob: If you don’t have the data, then you shouldn’t need to safeguard the data, and so you shouldn’t need the verification. Like I was telling Ms. McMichael in the messages and in the comments, is it the DoD misunderstanding their own program? Would it be the first time? You know what I’m saying? They’re just slamming this out there. If you don’t have the data, you can dismantle this pretty easily through your comments. Or is the DoD being like, “Holy crap, this is a big issue, we’re just going to make them do it anyways,” which is also very interesting? Or have they had the data all along, and the protections haven’t been the best, and so on and so forth, and then we all know how that song and dance goes. So it’s very, very interesting to see what’s happening in this space. It’s a big space. These are big contracts. This is a global data flow issue. I don’t know, but it’s making news on Federal News Network, so go check that out and click around. There’s a lot of interesting things on Federal News Network.

Scott: Lots of interesting news on FNN this week. (laughter)

Live chat and queue questions

Jacob: All right, let’s get into chat here and see. People celebrating Halloween, which is always fun. Spooky ghosts, which is always fun.

Shadow: Let’s hear some GRC horror stories.

Jacob: I don’t know. Maybe you guys will have something to think about through the show. What’s the scariest story you’ve heard over the last few weeks or months from people you’ve talked to? Maybe we can bring that up in a little bit. Before we get to that, or while you’re thinking of one…

Shadow Stick: I think there was zero chance of the CIO coming back with information before the midterms.

Jacob: I think at this point it’s pretty much guaranteed we’re not going to hear an update before the midterms. Which, I don’t know, if the news was so great, it’s kind of odd that you wouldn’t announce it before the midterms. That might just be me rationalizing things. The question, though, is will they announce something before November 10th, because the regulation still says that Phase 2 kicks in November 10th. I know you pulled your memo out of your back pocket that says “I can do whatever I want,” but the regulation is still in black and white, and memos sometimes don’t percolate all the way through the vast acquisition ecosystem. So after the midterms but before Phase 2 is probably the best guess at this point. What do you guys think?

Scott: Listen, from day one, I have said post-midterms. I just don’t think they have any better news than what they’ve already been able to show with helping small business by suspending the program. I could be wrong, but there just isn’t a lot that I can see happening. Certain articles that have come out on Federal News Network have kind of just shown the hand: there’s not a lot, without significant rulemaking and changes, that could even happen even if they wanted to. It’s just really difficult. And the fact that their only cybersecurity reporting measure, in the sense of knowing the state of their supply chain, in CMMC is gone… You can’t have your cake and eat it too. You can’t pause the program and then terminate it unless you have at least something to supplement the cyber posture of your supply chain. It would be absolutely crazy to do that. Anyways, we will see what happens, but it’s definitely post-midterms, I think.

Jacob: Yeah. I mean, Scott, you know how I feel about this, but the mashup montage is going to absolutely slap, as the kids might say, of “We’re cutting bureaucracy and red tape,” and then right after the midterms they go, “Do Rev 3.” (laughter) And “Do Rev 3, and here’s our plan for PQC, and here’s our plan for phishing-resistant MFA, and all the things.” Like I said, we will never complain about the requirements being better and bigger and more expansive and better for security, but when you frame it as a cost reduction, that’s your problem.

Megan: Rev 3 is a concern of mine in terms of timing. The Summit 7 podcast yesterday hit all of my open questions.

Jacob: That’s awesome. Although they seem open because there is no guidance. Yeah. So if you missed the podcast yesterday, you’ve got to be aware the FAR CUI rule is right around the corner as part of the Revolutionary FAR Overhaul, and the FAR CUI rule does not have a phased rollout. The FAR CUI rule does not have a phased implementation plan. The FAR CUI rule is just like previous DFARS rules. When the original DFARS 7012 rule came out in 2013, no implementation timeline, no on-ramp period. It shows up in a new solicitation, and that’s the requirement. When they updated the rule in 2015, no implementation window, no on-ramp, no phased rollout. Industry pushed back in 2015, and they said, “You’ve got two years.” And then it was in place, and it’s been that way ever since, for the last ten years. There is no phased rollout, on-ramp, or implementation window in the proposed FAR CUI rule.

That’s a big problem, because if you have defense contracts on Rev 2 and federal contracts on Rev 3 and there isn’t an implementation window, I hope you know how to juggle, because you’ve got two different baselines that are probably going to apply to the same system. And this is a big deal because if the DoD comes out with their plan after the midterms and says we’re going to move to Rev 3, when are you going to make people move to Rev 3? A year from now? Two years from now? When is the FAR CUI rule going to make people move to Rev 3? As soon as it goes into effect, in December or January. It’ll be before the DoD plan, because the DoD has to go through rulemaking in order to fix it.

What really ended up happening, as a result of the many things that happened as a result of the suspension, is it threw the rulemaking timelines off. Those rulemaking timelines were synced up at the beginning of the year. Whoopsie daisy. So if you’re a federal contractor and this is all news to you, just know there is no phased rollout. If you’re a defense contractor with both, which we’ve talked to many companies in that situation, we’ve got a real problem on our hands for what they’re going to do, because they could easily be asked to be assessed against Rev 2 but to comply with Rev 3, and managing that compatibility is just another thing to manage.

Daniel: Another burden. And so what are you thinking right now from a timing standpoint? I’ve been thinking for a long time it’s going to be this year.

Jacob: So for the FAR CUI rule and for CIRCIA, CIRCIA will almost certainly, definitely be before the end of the year. FAR CUI rule, all indications point to the end of the year. Here’s the problem, right? Not to get too deep into the rulemaking. When the 32 CFR 170 CMMC program rule went into effect at the end of 2024, that was what we called, if you remember, the market rollout, in the sense that you could go get a C3PAO certification, but the DoD didn’t have a contract clause to make you go get a certification. We had to wait for the second rule to go into effect. That didn’t happen until October of 2025, which is why the phased rollout started in November of 2025.

However, when that program rule was done at the end of 2024, the CMMC PMO immediately started working on the next revision of the program regulation to transition the DIB from Rev 2 to Rev 3. As a result of the change in the administration and various executive orders, that was a very tough process, because there’s an executive order that says for every new regulation you want to issue, you have to rescind ten regulations. The DoD doesn’t have a lot of regulations compared to other agencies, so there aren’t ten regulations to repeal. And so you have to ask for waivers to the circumstance. You have to go through this very, very, very time-consuming and bureaucratic process for what is otherwise a very simple update: you’re on Rev 2, we need to go to Rev 3. Here are the ODPs. Here’s the new scoring system. There you go. It’s basically an iteration on the existing program. It’s not a new regulation.

So that team got their waiver for that executive order. They got their ten-for-one waiver. On top of that, we know, as a result of what’s been published in the Unified Agenda, they also got an interim final rule waiver, which is very, very rare. If you know anything about our coverage of rulemaking in this space over the years, you know that’s exceptionally difficult to do. Very bureaucratic process. What that means is that when the rule is published, it goes into effect immediately. You don’t have to get public comments, go back and adjudicate the public comments, and republish the rule again, a process that can take eighteen to twenty-four-plus months. So they got all their waivers in place. That rule was ready to go in January of this year, and the new leadership team did not execute that rule.

History tells us, when they did this in 2020, when they issued the rule and then stopped it in order to do the review and then restarted the rulemaking process, they did not get their interim waivers reissued. That’s what head-faked everybody. DoD said, “We’re doing our review in 2021.” At the end of 2021, they said, “We’re doing 2.0, and it’s going to be done in like eight or nine months,” because they were expecting that their interim final rule waiver would be granted after this long delay. OMB said, “No, no, no. We gave you an emergency waiver, and then you took almost a year to get back to us. You’ve got to go through the regular process,” which is what ended up taking all that extra time. Well, now the question is, they had their waivers in January, and now we’re not going to hear anything until November. So they go back to OMB and go, “Hey, we would like to use these year-old emergency waivers.” OMB is probably going to tell them to pound sand and start a regular rulemaking process. If that happens, that means the FAR CUI rule would be requiring Rev 3, and DoD’s updated CMMC program wouldn’t move to Rev 3 for two years, eighteen months to two or three years. At that point, we’re talking about Rev 3 being, what, almost five years old.

Daniel: Rev 4 would almost certainly be out by that point, right?

Jacob: Yeah. And this was 100% avoidable. We don’t know the timing, but the FAR CUI rule is certainly not going to take two or three years to get done. And if the DoD doesn’t pull a rabbit out of their hat and get the old waivers respected, they are going to take a long time to get the program updated. It’s a freaking mess, and it was 100% avoidable. So I don’t know, maybe they’ve got a plan.

Who should define the ODPs for Rev 3 and FAR CUI?

Daniel: The question I still have is Rev 3, and specifically, FAR CUI has the ODPs from the DoD baked into the rule, and those ODPs aren’t published anymore officially. You can still get them from the Wayback Machine and things like that, but I don’t know. That’s another question I have: FAR CUI comes out referencing what ODPs?

Jacob: Well, listen, we don’t like to deal in a lot of rumors. We try to substantiate them. I’m going to caveat this: there are a lot of rumors flying around the rumor mill about what’s going on. But one of the most discouraging things I heard about the task force, take this with a grain of salt because I have no proof that this is true, but I believe the person who told me, is that the people in charge of the task force didn’t like that the DoD was defining ODPs. They thought it would be too much work for the department to do, which is an argument. So they pulled the ODPs down and said NIST needs to define the ODPs. What do we know, class, about NIST defining ODPs? They will never define ODPs. They’re not the data owner. The data owner has to define the ODPs.

So all of a sudden, we’ve heard lots of things like that, where they go, “The DoD shouldn’t do this, somebody else should do it,” only for them to turn around and be told, “Actually, you have to do this. No one else will do this.” And then they got stuck, which is why we think they’re taking so long to give us an answer. In my opinion, NARA should be the one defining the ODPs for 800-171.

Daniel: Oh, interesting.

Jacob: Because they’re the executive agent for the entire federal CUI program.

Daniel: Well, I can see that. If they own the CUI program, they own all CUI, effectively. They would define what would be considered ODP basic, if you will: if you have nothing defined for the protection of CUI at all, the minimum requirements are the 171 baseline with these ODPs. If you want to specify additional ones or different ones, you can specify whatever you want, because if you only specify the empty Mad Libs in 171 and all of the agencies define different ODPs, you don’t really have a common baseline, do you?

Jacob: Pro tip, everybody: I emailed the folks at NARA recently. They’re very nice. I don’t know if they took my feedback, but I said, “This is a massive problem, and you guys should do something about it.” But we’ll see. I know that the process for defining the 171 Rev 3 ODPs was a process where the DoD invited industry representatives from primes. It was a lot of NDIA and DIB ISAC people. They invited primes, they invited small defense contractors, and they all got together in a drum circle and came up with what they thought the ODPs should be. This was not some bureaucrat in the DoD spinning a wheel and saying, “Back in 1985, this is what we did, so that’s going to be the value.” This was a collaborative, industry-led process. And so if you come out and make those ODPs more stringent, shame on you, because that’s not how those were made. Anyways, let’s get to some more questions here.

Ian: Any update around GSA’s CUI update from earlier this year? Are people starting to see it in force?

Jacob: No. Daniel, we did an episode on this when it came out. They pulled it down.

Daniel: They pulled it down. Somebody asked me about this the other day, and I went to look it up again. It wasn’t there. I was like, it’s crazy. They pulled it down. I’m assuming because A, it didn’t go through rulemaking. It was just a “Hey, FYI, this is our new IT security policy as it relates to CUI.” And GSA is likely part of the FAR CUI representation.

Jacob: They sit on the council.

Daniel: They do.

Jacob: Yeah. The guy in charge of the FAR CUI rule is a GSA employee. So I have a feeling that they were like, “Hey, why are you doing that when we have this coming out?” And they pulled it.

Daniel: Haven’t seen it.

Jacob: But we hear this a lot, because essentially what that GSA document said was, “We’re going to do RMF for contractor systems on a case-by-case basis.” And it’s like, you and what army? It was a Rev 3 implementation with C3PAO verification plus a review by their own internal team.

If you didn’t catch our episode with Eric Crusius on the recent protests around CMMC status and bonus points, definitely go check that out. But you want to know a really great way to get a lot of contract protests? Give a variable risk acceptance for minimum baselines on different federal contracts, contract to contract. The DoD got on stage in 2018 and told everyone, “We cannot do RMF for the DIB,” first of all because we don’t own their systems. The RMF doesn’t apply to a nonfederal system. They can’t tell you what to do on your system. The only connective tissue, and I’m somewhat talking to the folks inside the DoD, hopefully you’re watching, who are rumored to have thought of this idea, the only connection you have to my nonfederal system is the fact that your data is on my system. If your data is not on my system, get off my lawn, because it’s a nonfederal system. Go away. You’re the federal government, and you don’t have an authority to regulate it.

Go ask the EPA how successful they were trying to interpret a very open-ended authority to regulate nonfederal systems in a critical infrastructure sector. When they released their memo that said they were going to apply assessments and cyber requirements to water and wastewater systems that are privately owned, literally twelve hours later, like fourteen states’ attorneys general sued them into oblivion. You can’t do RMF on nonfederal systems. It doesn’t work. All right, let’s see here. Bunch of stuff in the queue.

Does Summit 7 have a minimum seat count for GCC High licensing-only engagements and procurement?

Daniel: Yep. One. (laughter) That’s the minimum seat count.

Jacob: Probably get zero these days, let me tell you.

Daniel: Actually, we can do zero. People go to the eligibility validation website and check the GCC provision, basically a test environment box, and just FYI, you cannot provision a test GCC High instance. They just don’t have that option. For those out there, because people come to the door all the time saying, “I already have a tenant, I filled out the form,” you actually have the wrong type of tenant for what you need. So just be aware of that. But outside of that, one and done. Send them this way, or zero if you just want Azure Gov.

Jacob: This isn’t a question we hear as often these days, but this is an issue that people run into where they’re going licensing only and there are minimum counts that some vendors enforce. Am I understanding that?

Daniel: Yeah. A lot of times other vendors will have their own thresholds, but Microsoft EA is at 500 seats. What we’ve seen a lot of is larger enterprises still coming to us for licensing, because the contract addendum and the time it takes to enable the purchase of Gov licenses is sometimes sixty to ninety days. It’s got to go through their LSP, then it’s got to clear Microsoft, then it’s got to be added to the contract. So the timeline is very, very long, and usually when people call us, they’re calling with a sense of urgency: “I’ve got to have this environment yesterday.” We don’t get a lot of people who call and say, “You know what, I’ve got all the time in the world.”

Jacob: Yeah. “Two years from now, please. I’m good. Get to it when you get to it.”

Scott: They’re like, “Just put it on the maybe board.”

Jacob: Yeah. (laughter)

Follow-up: FAR CUI has no scoping guide

Jacob: This reminded me, I meant to bring it up earlier. Tell your friends, folks, we’re going to have a podcast coming on it pretty soon. Not only does the FAR CUI rule not have a phased rollout, there is no scoping guide that comes with the FAR CUI rule. There is no such thing as a specialized asset. There is no such thing as a contractor risk-managed asset. There is no such thing as an out-of-scope asset. The only scoping guidance you’ve got is the single-sentence scoping line in NIST SP 800-171, and we all know how well that worked out over the years. So, good luck, man. (laughter) There’s an interesting story for this week.

Scott: Do what? I’m still here. Interesting story for this week: I talked to a client, certified, wanting to look at Rev 3, but they’re having to scope Rev 3 for their enterprise boundary because their enclave isn’t sufficient, because of the scoping guidance.

Jacob: Well, I mean, talk about those rulemaking timelines where you get different contracts at different baselines. You’ve got different contracts, different scoping guidance. Heaven forbid that GSA or NASA or the Department of Energy wakes up and comes up with their own scoping guidance for CUI as a result.

Scott: Oh boy. You know, DoD did so much work to really limit cost and burden by putting together very extensive scoping guidance. I mean, years went into developing that, right? And now all of these additional federal rules that are coming out have none. FAR CUI has none. It’s just what’s in NIST. CIRCIA has none. I mean, it’s everything. It’s your enterprise. It’s the whole thing. And DoD did so much work to try and control the scope of what the impact was going to be. And man…

Jacob: Well, and this is the paradox we talked about, right? Because people see the scoping guidance and they go, “Oh my God, I don’t want to read all this red tape and bureaucracy.” And you’re like, “No, no, no, no. You had a single sentence that put everything in scope.” This is what happens when you try to interpret scoping guidance: you end up with more information that you have to interpret and understand and deal with. So yeah, it’s a burden and it’s red tape, but as we’ve said probably more than anything on this channel, scoping is the number one way that you save money. If you rip up the scoping guide under the guise of “this is all just wasteful, stupid red tape and we’ve got to get back to the real work of real security,” I mean, sure, we don’t do enclaves anymore. I guess everybody just scopes everything. That isn’t a better solution. Now, there are ways to improve the scoping guide. Make it more readable. Make it shorter, more concise. There are always ways to improve it. But is every agency going to agree with the idea that contractor risk-managed assets can just exist within the boundary of the system that processes their data without having requirements applied to them? That’s crazy talk. And the DoD was like, “Yeah, do it. Sure.” (laughter)

Scott: Yeah. Over and over and over again, over a decade, DoD bent over backwards to try and help the industrial base, to help make it more palatable, and the FAR is not doing that. The worst possible timeline is you get three different scoping guides for three different agencies, and you have to do two different baselines, and it’s all for the same minimum data standard, and you only have one system in operation. That is a nightmare scenario. So, Daniel’s back. Daniel, if you missed it, I was saying the worst possible scenario you could have is three different agencies come out with three different scoping guides. You end up with two different requirements baselines, and you’re a contractor that only has a single system in operation. That’s probably the worst possible…

Daniel: Doctor Strange. I analyzed thirteen thousand different rulemaking timelines, and they all end up with you having to do the guides. At that point, you just have to high-watermark everything and do the whole system. You do everything at high watermark.

Jacob: Yeah, that’s the only option you have at that point. Yeah, absolutely.

Do you track the Canadian CPCSC program?

Jacob: Oh, this is the Canadian one. Somebody was asking, do you guys track the Canadian CPCSC program? We have a little bit in the past, but we haven’t heard too much about it recently. Someone was saying it’s basically in a holding pattern. PSPC’s last update was basically a response to the CMMC pause, and the tone was them going back to square one.

Scott: There are a lot of things in holding patterns. There are a lot of things in the government that aren’t really governmenting right now. White-collar crime enforcement is at a forty-year low. So this might be the rubber band getting pulled further and further back, and then once things get back in action, the pendulum just whips back in the other direction and we all have to deal with it. But I haven’t heard anything about the Canadian program recently.

Jacob: Have you guys?

Daniel: No, I haven’t.

How will the DIB improve its cybersecurity posture if CMMC loses steam? What’s the next likely forcing function?

Jacob: Well, there isn’t one. CMMC is the forcing function.

Scott: Well, FAR CUI, I mean, yeah, that’ll be it. But what do you think, Dan?

Daniel: I agree that FAR CUI will definitely take the requirements wider, but without a certification or verification mechanism, I think we’re still another five years out from another level of enforcement, a CMMC-ish at a top-level federal perspective.

Jacob: Maybe. We were just talking about this yesterday. I’m sure a lot of people in this audience have heard my history of the rulemaking timeline. Every time the DoD has turned the screws, even slightly, on defense cybersecurity requirements, it’s been on the heels of a major national security crisis as a result of cybersecurity breaches. You could do CloudHopper in 2011, which led to the creation of 7012 in 2013. You talk about the OPM hack, which led to the revision of 7012 in 2016. You talk about Cadragon and the F-35 and F-22, which led to the creation of CMMC in 2020. And now, as we’re out here watching Harry the hamster educate everybody on the CIO’s LinkedIn page for Cybersecurity Awareness Month, we just read the Lumen Technologies report about Volt Typhoon yesterday. All the public reporting about Volt Typhoon was saying they’re going after power, energy, water, critical infrastructure. Lumen’s analysis, over the course of three years, said that the sector that got hacked the most, second only to the federal government itself, was the DIB, followed by universities, followed by MSPs. So here we go again, another national security crisis facing the DIB. I don’t think it’s going to lose steam.

Daniel: Well, combine that with, we were talking about this in the green room right beforehand, 4% of all CVEs ever released have happened in the last thirty days. It’s crazy. Over 18,000 CVEs in the last thirty days. You add that to this Lumen report and the cybersecurity status of the DIB, and it’s an absolute disaster waiting. It just doesn’t lead you to think that the answer we get will be “actually, do fewer things now.” There is a case to be made, as the CIO has said, as the DoD has said, that assessments every three years are not frequent enough and human-run assessments are too expensive and take too long. Great. Then automate them. Fire up a hundred thousand clanker assessors to go out and run free automated assessments against the DIB. And then all of a sudden, you’ve solved that problem and you’ve created another one, because we know that implementation is the real barrier, not passing the assessment. People who are implemented generally pass their assessments just fine. So you’re not going to reduce the requirements. You might have a way of magically automating the assessments, but that doesn’t really solve your problem. It just makes the problem worse, really. So, we’ll see. But yeah, with all the things going on in the world, it’s not really a time to go back to the Armed Services Committee and be like, “Yeah, you know, that old thing you asked us to do? We’re going to ask people to not do that.” And on top of that, the requirements they’ve had for ten years: do less. We’re going to do less. (laughter) Probably not a good answer.

Jacob: All right. “We stumble into World War III without making the DIB pay their tech debts, and lose information at speed.” Already happening, my man. Already been happening for a long time. We’ve been losing that war for a long, long time. All righty. On other cheerier notes. (laughter)

For ITAR data controls, can we revoke delegated admin privileges after a GCC High tenant is spun up so an internal team maintains exclusive access?

Scott: Daniel, we work with tons of companies that have internal teams. They don’t outsource 100% of their work to us.

Daniel: Sure. We augment internal teams all the time. Yes. The short answer is yes. You can revoke access to those individuals. Some organizations will have an environment stood up with their internal non-US IT team involved in the deployment of the technical controls, and then they immediately exit once the data migration is underway, because they can’t access a lot of that data set. So yes, very common approach, global large enterprises. Scott, we’ve seen it for years and years and years. So yeah, you can remove the access. They can be involved in the implementation and technical controls. There’s no rule stating that they can’t be involved in the design of it. They just can’t be involved in the sense of having access to unencrypted technical data. That’s export control. So that’s the access, or my favorite, the ability to access credentials.

Jacob: That’s right. So you can’t have either of those fun things.

Jacob: You know, I was just thinking, as you were talking about that, it’s unrelated. We were talking about the movers issue with CMMC and all those things. Flag officers have to PCS too. SES members have to move. Very important, high-level people have to move all the time, and it’s not always just base to base, but their movements and stuff are tracked. Sorry, I’m just thinking about this in terms of, is it a CUI category? Should it be a CUI category? Are they going to require it even though it’s not a CUI category? If anybody knows anything about this space, hit us up, because I’m very interested to see how this develops. It’s related, but it’s its own thing. It’s not necessarily controlled technical information. It’s a different type of information.

Daniel: Well, as long as they have all their CUI printed out and it’s just in paper form, it’s not a problem. (laughter)

Jacob: Hey, right, you found it. There you go. “Don’t worry, sir, we’ve got it right here on paper. Don’t worry about it. I know you’re moving over to Fifth Fleet or CENTCOM. Not to worry, I printed it out.” (laughter) “Oh, sorry, were these all your family members’ names? Don’t worry, sir. Have a nice day, Admiral.” Gosh.

If an MSP changes its servicing stack (RMM, SIEM), would that trigger a reassessment for the customer?

Jacob: Alrighty. Daniel, your favorite question.

Daniel: I have seen people spin this every which way, so I’m going to give you both ways and let you decide to your own volition. It’s a lot easier now that there’s language in the CMMC FAQs in the CIO’s office, where it talks about how if you go from a not-met control to now meeting a control, that’s a triggering event for reassessment, self or certification. However, if you scroll down a little bit to Q&A number three around that same question, it talks about how if you’re introducing new technical items to your environment, it’s at the discretion of the affirming official whether or not a triggering event has occurred. So it really just depends on the lens you’re looking through, quite honestly.

But there are some MSPs, I’ll give you an example: if you’re moving from a VDI SaaS-based solution and now you’re moving into an enclave environment because you want the ability to do on-prem work, right? That’s VDI driven, but also connections to on-prem. Well, in that move to a different provider, you’re likely going to switch from not-met controls to met controls. So there are simple things like that that can easily flip it over and would be a triggering event for a new assessment.

Jacob: There you go. It’s been a while since we had an FAQ update. Maybe we’ll get one coming up, and we’ll get an answer to what a significant change really means.

Daniel: I would love it if significant change were defined in rulemaking, but I’ll take an FAQ update. I don’t think we’ve had one since before the suspension.

Jacob: So yeah, it’s been a minute.

Does Summit 7 support state or local CJIS customers in addition to defense contractors?

Jacob: This is, what, criminal justice information? Yeah, CJIS.

Daniel: Yeah. I actually had this question this week. Microsoft has three platforms, you’re probably aware at this point: Commercial, GCC, and GCC High. GCC can do state-level CJIS. GCC High does federal-level CJIS, criminal justice information. So, long story short, we have sold Microsoft Gov tenants to organizations needing those requirements. The latest conversation this week was with a state agency, but in support of the DOJ and federal records. So it was a little bit of an interesting mashup there, but yeah, we do.

Jacob: The interesting point about that is, at least, I haven’t looked at CJIS coverage with Microsoft in a minute, but if I remember correctly, it was exclusive. So GCC High only did federal. GCC only did state. So if you had both state and federal, you had a problem.

Daniel: Yeah. Two tenants, man.

Jacob: It’s almost like a CMMC and FAR CUI situation a little bit. You’re going to have to duplicate your effort there.

Daniel: I mean, we have StateRAMP, so why not… see state now? I think they switched it all. They switched it all. I think it’s a rebrand.

Jacob: Did Texas do it too? Because I know we had TX-RAMP.

Daniel: Oh, yeah.

Jacob: So yeah, municipality RAMP, and you know what? Everybody join in. What’s the worst that could happen here?

Jerry: Can you review the prime stance on requiring subcontractors to be CMMC Level 2 C3PAO certified to be eligible as an approved sub on the prime’s contract? Any stories?

Jacob: All right. First off, we got to meet Jerry at CS5.

Scott: That’s right.

Jacob: Our first international viewer, from Greece. I was watching while he was on vacation. He said he was in a hot tub in Santorini watching the hotline. You’re like, buddy, that’s commitment. (laughter) There’s got to be something better to do if you’re in a hot tub in Santorini. Come on. (laughter) But no, we always appreciate the views. We’ll take them. So, yeah. What have you been seeing, Daniel?

Daniel: Yeah. Outside of that, I’ve seen primes get more and more heavy-handed with this whole minimum score of 88. I’ve not seen enforcement of certification, although they are definitely very happy when they see subs and suppliers that are certified. But from a mandate requirement, they’re thrusting down this 88. A couple of weeks ago, somebody forwarded me an email that an organization in the construction space decided to no-bid work. That wasn’t because they weren’t compliant. That was because they couldn’t find enough suppliers that could actually fulfill the work, because those suppliers couldn’t meet minimum requirements like the self-assessment of 88. Not because of the certification assessment.

Jacob: It’s not because of the certification assessment. They suspended the certification assessments, which means no one anywhere, technically, under any circumstance, no matter what kind of data they’re dealing with, can be required in a DoD contract to get a third-party certification. Just let that sink in. Just think about some of the super cool, high-speed, kick-ass stuff that defense contractors are working on. Not all of them, but some of them. And we will not require a third-party certification assessment, any proof whatsoever at all. So in lieu of that, elsewhere in the big wide world of the DIB, you have companies that do not have the requirement to pass a third-party assessment still cannot find eligible suppliers, because the assessments weren’t the problem. Meeting the requirements was the problem.

Daniel: Meeting the requirements was the problem. So, like you said, we’ve seen the minimum scoring. The worst stories that I’m hearing are people saying, “Tell us your minimum score and send us proof.” So you don’t have a cert to show them to reciprocate the proof of the fact that you implemented everything.

Jacob: The nice part about having the cert to hold up is it’s third-party proof that we did it. So they can just take that, right? When you don’t have a third-party cert, whether it’s the current structure or an automated structure, whatever, when you don’t have your permit that says you can do what you want, every customer is going to ask for the data over and over and over again, in different formats, different things.

Daniel: It’s like insurance questionnaires, right? You don’t have a universal key to unlock this work because you don’t have the CMMC cert. Now you go out and get the cert, and hopefully that works. But I know that’s not a better system, having all the primes and all the customers ask for the same data over and over and over again instead of showing a single cert that was required. It’s way more work and time.

Halloween scary stories

Jacob: Did you guys think of any scary stories? I don’t know if this would be the scariest story, but like you’ve heard recently, phone calls or people coming up to us while we were traveling. It is Halloween Eve.

Daniel: I’ll just very much generalize this. I think my latest uptick is people who know they have CUI and export data in their enterprise try and buy a ten-dollar-a-month enclave to check the box to meet compliance, knowing in reality they’re absolutely not. We’re seeing this whole “get me compliant fast because my prime has a deadline of X date with a minimum score of 88 or a full 110.” And there are people who are doing the thing but just not doing the right thing. They have non-US persons around this export control data, external non-US-person support through MSPs globally. They have basically all of this just, honestly, non-compliant and potentially illegal access to information that they just shouldn’t have. And I think the scariest part is they are more and more aware of this risk. CMMC brought a lot of this to light, and they’re still at times deciding to not do the right thing but just to do the something that checks the box.

Scott: Yeah, and this is rampant. This is everywhere. I’ve heard of data being exfiltrated on a weekly basis, and it’s just scary because it’s all very real. This is an active and real threat. I used to have so much empathy for the DIB because of DFARS 7012 obligations. It’s just hard to understand for a small business. At this point, I still get it and understand it’s a cost, but we are seeing the side effects of not protecting national security information, controlled unclassified information, and export control data.

Daniel: And we only know one percent of one percent of what’s going on, right? I mean, those are the people who call us.

Scott: Yeah. These are the people who actually talk about what’s going on, and there are way more companies that are not that.

Daniel: I was thinking not at all.

Jacob: It’s Halloween season. It’s zombie season. And my favorite zombie story is Night of the Living Deadline, because there is no DoD policy that makes November of 2026 a deadline for everyone to achieve a Level 2 certification. It ain’t in the regulation. It’s not in the rule. It’s not in the preamble. It’s not in the memo. It has never once, ever, ever, ever existed. So where did the November 2026 deadline come from? It came from the primes. The phone call was coming from inside the house, because they took the start of Phase 2 and said, “The DoD is going to start inserting these requirements in new contracts, so all of you subcontractors need to be ready by that date.” And there is nothing the DoD can do to stop the primes from saying do it in July, or do it in November, or whenever they want to set their deadline.

So I have a prediction that if the DoD comes out and says, “We’re extending the deadline,” or “We’re extending Phase 1 to November of 2027,” we’re going to be right back in the same boat we were in before, where the primes are going to say they’re going to start certification assessments in November of 2027, so you need to go get a cert right now. Our deadline is November of 2027. And then whoever the new DoD CIO is in November of 2027 will be right back in the same situation. I mean, that’s my zombie story that I think is going to happen for Halloween. I don’t know. Scott, you got any scary stories?

Scott: I don’t have any recently. We’ve talked about a lot of them before, but…

Last queue questions

How much will this change with 171 Rev 3?

Jacob: I got one. I’ll just cue this one up as we walk out: how much is this going to change with 171 Rev 3?

Daniel: It’s significant. It’s, what, about a 30%, 34% increase? 320 to 510 assessment objectives, I think, is the number. So it is not insignificant at all.

Jacob: Yeah. We were talking earlier, before we went online, you’re beating the drum for application whitelisting.

Scott: Oh yeah. Application whitelisting is a big deal. It isn’t going to stop everything, but we just saw the report about the Accenture contractor that had a personal AI agent running within the DoD. It was running on a system inside the DoD infrastructure and accessing data for two months before it was caught.

Jacob: That settlement is going to be expensive. Before I even finished reading the article, I was like, I can hear the DOJ licking their chops right now, because that’s not good.

Smith: Our SIEM management firm is ending our contract early, getting out of the SOC business. Now trying to shop replacements, having challenges finding a whole new service provider. Found one in Canada. We’ll now have to redo our entire document set. I’m so glad I didn’t proceed with Level 2 certification three months ago when originally planned.

Scott: Daniel, we’ve had people call us being like, “Our MSP is terminating our agreement because they’re getting out of this space.” Which is crazy, because typically that happens with people who had a wink and a handshake from their MSP that said, “We’ve got your back for all this DoD stuff.” And then as the deadline started to show up, they started to just leave them on the side of the road.

Daniel: Yep. I’ve seen one example of one MSP becoming insolvent and just terminating everything. Every other example I’ve seen was a handshake deal that they were going to walk them through the assessment, and they had no contractual fallback to pursue damages. So they literally had to eat the cost of the managed contract or pray to the president of that company and say, “Please let us out, do the right thing.” It’s hard. It is very, very difficult. Get things in writing when it comes to this stuff. Put it in contracts and agreements. And by the way, Smith, give us a call.

Jacob: Yeah, absolutely. And on that note, talking about MSPs going insolvent, this is something we should probably lead with and talk about more. People own their tenants when they work with us. If a jet engine falls on Summit 7 headquarters tomorrow and takes out the building, you still own your stuff. If Scott puts on a nose-and-glasses disguise and flees to Southeast Asia or whatever and just shuts the lights off on the way out, he doesn’t take the tenants with him.

Scott: No, that’s super important for us. Customers own their tenants, customers own their data. Obviously, customers have administrative accounts in the environment, and if Summit 7 just disappears, none of our customers lose access to their environments. That is really important, and we design all of our service offerings around that kind of structure, because we’ve seen what’s happened in other cases where a company goes upside down and customers are left in a lurch.

Jacob: Yeah. Absolutely.

Wrap-up

Jacob: All righty, everybody. That’s been an hour. It always flies by. If you find this after it’s done, you can leave your questions and comments down below and we’ll add them to the queue. You can always send us a DM. You can find us at cuihotline.org. Call and leave a message. You can fill out the form over there. You can find us at summit7.us. Lots of ways to get a hold of us.

Make sure you like and subscribe, because any day now we’re going to have, hopefully, a big announcement about CMMC, CIRCIA, FAR CUI, all kinds of fun things in store for everybody that’s going on in the world. Everybody go trick-or-treating. Everybody celebrate Halloween. It’s the last Saturday Halloween for eleven years, everybody, so get out there and do it. If your kids are like seven, eight, nine years old, this is the last Saturday Halloween you’ve got. Public service announcement. Anyways, thanks for watching, and we’ll see you next week. See y’all. Happy Halloween.

Contact

Speak With Our Team

Scroll to Top