Transcript
A (0:02)
Guess what, Joy? We're back. We're back. We are back. It is you and me, and we are going to talk to Cyber AB Town Hall. More specifically, what's happening in the ecosystem. The things that everybody needs to know. And they've been busy since last month, Joy. And I feel like I haven't seen you since last month. Last month. What have you been up to?
B (0:22)
Well, I'm in our office now. I got all moved in, settled into Tennessee.
A (0:27)
Okay.
B (0:27)
I do want to say, when Matt Travis opened the town hall last night, he was funny. He always. It cracks me up. He was so funny about, you know, wanted to spend 85 minutes for the State of the Union address and, and. But he didn't have his jacket, so.
A (0:42)
He didn't have the jacket. So funny. As somebody that likes to, like, layer the jokes in with current events, I appreciate that. The opening where you, you throw out the funny. The dad jokes as it is. And so I 100 appreciate it. Maybe we're rubbing off, maybe we're not. He didn't just have jokes, though, Joy. Actually, everything else that he had to say wasn't technically funny. It was actually really good news. He was the good news fairy in, in this month's town hall. And it started with, like, a bit of good news that I know. This week I learned, uh, that everybody else probably should know. And it has to do with Tier three background checks. Now, we know that the delays sometimes can be a bit cumbersome for a lot of people. Takes a lot longer, me especially, but I did not know up until now. The only thing that I thought was after six months, then you can reach out to the people that they've listed and you can ask them, hey, what's going on My status for my tier three. But if you are an organization that has an FSO facility security officer, did you know that if you have submitted a Tier 3 background check, you can actually reach out to that person and say, hey, can you see what's going on with this? It's taking a little bit longer than I think it should. Did you know that?
B (2:01)
I didn't. And that's awesome because I think a lot of folks in this ecosystem actually are organizations that have an fso.
A (2:08)
Yeah. So it's like something that's already, for the most part, readily available. Now, I don't know how that works. Maybe if you have an outsourced fso, if that agreement goes there, obviously there's the variables and the wrinkles that go into things, but just to have another avenue for people to reach out for a process that does take right now a little bit longer than usual, although improving and getting better. I think that that's a great start. So that was the first bit of good news that he delivered to us in this month's meeting. So this one, not necessarily great news, good news, but significant changes, obviously a topic, a hot topic of discussion, who can determine it or what can we do from, you know, the significant changes, what to do if there is a significant change. And so he just wanted to say first and foremost that there is formal guidance that's in the works, right? In the backgrounds. We know the Department of War and we. He said specifically the C3PAO subcommittees, the advisory subcommittees that they formed. There may be some discussions on the back end about how significant change is being handled and at some point there's going to be some formal guidance issued. But he wanted to point people back to the formal guidance that already exist, right? And so that formal guidance obviously was to refer to the rule and to the 32 CFR rule and to page 9 of the CMMC Level 2 Scoping Guide that basically can a look essentially at kind of the basis of what it says. And then, you know, in the preamble of 32 CFR Part 170, it addresses significant changes specifically and it says if an OSA makes significant changes within the CMMC assessment scope, a new assessment and affirmation are required. Case in point, you make a change to something that's been certified, we're gonna have to certify that again to make sure it's good enough to hold cui. And everybody's like, well, what's a change? Right? So then it goes into there. The required assessment frequency is every, you know, for organizations, every three years, they have to get a new CMMC assessment. Every year the affirming official has to affirm. And when changes occur within the CMMC assessment scope, that invalidates that system, invalidates that boundary. So in page nine of the CMMC Level two scoping guide, every CMMC ecosystem participant, every assessor has to know this pretty, pretty well, says new assessment is required if there's a significant architectural or boundary or boundary changes to the previous CMMC assessment scope readings are today, apparently. Examples include, but are not limited to expansions of networks or mergers and acquisitions. Huge parts questions that we answer all the time. Operational changes within a CMMC assessment scope, such as adding or subtracting resources within the existing assessment boundary that follow the existing ssp, do not require a new assessment, but rather may Be covered by annual affirmation to continuing compliance with requirements. So that's a lot of words. Essentially significant changes to your architectural, to your architecture, the things that are within your architecture or to the boundary of your architecture, where it goes, how big your yard is, right. What's within your yard or what's how big the yard is going to be. You want to purchase more land, right. And if you purchase another organization that's going to constitute the significant change. So adding or subtracting resources like endpoints and things of that nature within the existing assessment boundary. So if it's in your SSP called out that way, it's a one for one switch. We're saying that's not a significant change. Am I understanding that correctly, Joy?
