Latest / CMMC Compliance Guide / CMMC FAQ Update: Timeline, Subcontractor Flowdowns, Enclaves, Cloud Rules, and VDI Scope Explained

Transcript

CMMC FAQ Update: Timeline, Subcontractor Flowdowns, Enclaves, Cloud Rules, and VDI Scope Explained · CMMC Compliance Guide

• 0:21
  Austin: Hey there and welcome to the CMMC Compliance Guide Podcast.
• 0:25
  Austin: I'm Austin.
• 0:26
  Austin: And I'm Brooke from Justice IT Consulting, where we help businesses like yours navigate CMMC and NIST 800-171 compliance.
• 0:34
  Austin: We're hired guns getting companies fast-tracked to compliance.
• 0:37
  Austin: But today, we're here to give you all the secrets for free.
• 0:41
  Austin: So if you want to tackle it yourself, you're equipped to do so.
• 0:44
  Austin: Let's dive into today's episode and keep your business on track.
• 0:48
  Austin: Today's episode is about the CMMC questions that are quietly tripping up DOD contractors right now.
• 0:55
  Austin: We have word from Uncle Sam, the DOD or Department of War.
• 1:01
  Brooke: DOW, yes.
• 1:01
  Brooke: You gotta get that right.
• 1:02
  Austin: Yes, I'm sorry.
• 1:03
  Austin: I'll I'll buy uh and I'm sure I'll get it right here in a couple months.
• 1:08
  Brooke: It's been a couple months, so you know.
• 1:10
  Brooke: I'll get it right by the end of 2026, probably, so you know.
• 1:13
  Austin: I'll say I finally started putting 2026 on things, so DOW is next.
• 1:18
  Austin: So um, but uh we have word from Uncle Sam.
• 1:22
  Austin: Um they have just released um a whole list of uh FAQs facts.
• 1:27
  Austin: They have.
• 1:28
  Austin: Um addressing uh commonly misunderstood or um uh just just items that trip up DOD contractors, and they've come out pretty conclusively and and made decisions on each of them and released facts about them.
• 1:43
  Brooke: Yes.
• 1:43
  Brooke: A lot of these they've addressed before, uh, but they they keep addressing them because they keep being questions.
• 1:50
  Austin: They keep being misconstrued, I guess.
• 1:53
  Austin: So absolutely.
• 1:54
  Austin: So that's what our focus on today.
• 1:56
  Austin: Um we're breaking down uh what the rules actually actually say, uh what they've come out um and uh put in writing on these facts.
• 2:05
  Austin: So today we're breaking down those facts that Uncle Sam came out with, um, what the rules say, what contractors get wrong, um, how to avoid scope and uh vendor mistakes, and ultimately what can derail an assessment sometimes before it even starts.
• 2:21
  Austin: Absolutely.
• 2:21
  Austin: Okay, so first um I want to address timeline.
• 2:25
  Austin: Uh a lot of contractors feel like CMMC is just a problem to address in the future.
• 2:31
  Austin: Um when does it really become real?
• 2:36
  Brooke: I feel like we've addressed this a couple times, but well, on uh you know, to to be fair, I guess it is something to address uh in quote in the future, you know.
• 2:45
  Brooke: Uh you really need to address it now.
• 2:47
  Brooke: But so the um the so let's back up a little bit.
• 2:51
  Brooke: The 32 CFR uh that was published and went into effect uh in December of 2024 was what finalized the what uh the description uh uh defined definition of CMMC.
• 3:05
  Brooke: What what is CMMC?
• 3:06
  Brooke: That's so that uh 32 CFR was uh um published uh in well it went live, I guess, anyway, in uh December of 2024.
• 3:16
  Brooke: So um the uh the 48 CFR is the uh federal rule that puts CMMC on play in place on contracts, CMMC as it is with the level two certification assessments and stuff like that.
• 3:31
  Brooke: So it puts it in effect on contracts.
• 3:33
  Brooke: It went into effect November 10th of 2025.
• 3:37
  Brooke: So it's in effect right now, but there's four phases.
• 3:41
  Brooke: So those four phases, the first one is pretty much what you're doing right now.
• 3:45
  Brooke: They're self uh self-assessments.
• 3:48
  Brooke: Uh there is some more teeth in it, basically.
• 3:50
  Brooke: There's there's a definite timeline now.
• 3:52
  Brooke: There's no question you can't say, you know, I think it's still not coming.
• 3:57
  Brooke: You know, it's because if you still think it's not coming, then you're just not in reality with the rest of us.
• 4:03
  Brooke: So um, but the the each of the phases last a year.
• 4:07
  Brooke: So November 10th, 2025, phase one starts.
• 4:11
  Brooke: That's still the self-assessments.
• 4:13
  Brooke: Uh November 10th of 2026, which now is at this point today when you when we're recording this, uh probably way, way, when as as the time we're recording this, it's about nine and a half months away, I think I counted.
• 4:26
  Brooke: So um so really November 10th, 2026 is not that far away.
• 4:32
  Brooke: That starts phase two.
• 4:33
  Brooke: Phase two says that they will be putting the level two certification requirement on new contracts.
• 4:41
  Brooke: Not necessarily current contracts that you're working on, but new contracts.
• 4:44
  Brooke: Uh so you need to be aware of that.
• 4:46
  Brooke: Uh I assume everybody would need some new contracts to survive, you know, to get business, keep business coming in.
• 4:53
  Brooke: Uh but also the other caveat, the giant caveat to that, uh, is that there's a lot of uh, especially in our neck of the woods, there's a lot of primes.
• 5:02
  Brooke: There's Lockheed, Bell, Raytheon, GD OTS.
• 5:06
  Brooke: I mean, there's there's all sorts of uh primes.
• 5:09
  Brooke: And uh they will be and and are uh starting to push their um suppliers to have get their level two certification.
• 5:19
  Brooke: Um and at some point I'm sure that they will require that ahead of time, ahead of November 10th, 2026, uh to get new contracts because they have to show that they're ready.
• 5:30
  Brooke: They can't wait.
• 5:32
  Brooke: Those primes have so many subcontractors they can't wait till November 10th of 2026 because they'll be behind the eight ball at that point.
• 5:39
  Brooke: And uh when we're talking about uh hundreds of millions or billions of dollars, uh, you know, you probably don't want to wait.
• 5:45
  Brooke: So they don't want to wait.
• 5:47
  Brooke: So uh if you do work for a prime, which in the Dallas-Fort Worth area, there's uh a ton of those.
• 5:54
  Brooke: So uh a ton of subcontractors that do work for primes, uh, you will likely be asked to uh get your level two certification before November 10th, uh or at least show that you have it scheduled before then or something like that.
• 6:06
  Brooke: So it's coming.
• 6:07
  Brooke: There's no question that's the timeline.
• 6:09
  Brooke: So they one of the FAQs was what's the timeline?
• 6:12
  Brooke: And that that's that's what the timeline is.
• 6:15
  Brooke: It's fairly obvious from the uh federal rule that came out, but that was one of the FAQs that was answered.
• 6:21
  Austin: Yeah, so uh I to jump on what you're saying there, um you know I don't think it is apparent that the primes don't um uh care to uh manage things by the details, you know, and exactly, you know, um who has the contracts and and whatnot.
• 6:39
  Austin: They as you kind of mentioned, they want to just get everyone on board so that way they're in just in a good position and they're just gonna ask everyone that is doing work for them whether you have an immediate contract need for it or not, to get we have seen instances of that, yes.
• 6:55
  Austin: Seen many instances of that.
• 6:57
  Brooke: We've told them, you know, politely push back and politely see what you can do and make sure that, you know, that they're responding to you and not just a form email, you know.
• 7:07
  Brooke: Uh and some of them have been told, yep, sorry, uh they we want you to be level two.
• 7:13
  Brooke: And when when they know they're really not supposed to be level two for what they have right now, but again, they want to be able to show the numbers.
• 7:21
  Brooke: We have 75 percent or whatever of our subcontractors are level two.
• 7:26
  Brooke: Great.
• 7:27
  Brooke: I don't know that it'll be level two or 75 percent by uh November.
• 7:31
  Brooke: That's a tall order.
• 7:32
  Brooke: But you get my point.
• 7:33
  Brooke: Though they want to be able to say, you know, hey, we're better than the other prime over there because we have X number of subcontractors, X percent of subcontractors ready to go.
• 7:42
  Austin: Yeah.
• 7:43
  Austin: Yeah, we uh and to be clear, we always recommend pushing back gently, nicely.
• 7:48
  Austin: Yes.
• 7:48
  Austin: Um checking your contract.
• 7:49
  Brooke: Don't want to bite the hand that feeds you.
• 7:51
  Brooke: I understand that.
• 7:52
  Brooke: Absolutely.
• 7:52
  Austin: They are a customer, you know.
• 7:54
  Austin: Uh you know, auditing your contracts, making sure that the link proper language is in there.
• 7:59
  Austin: So don't just go spending money that you don't need um and and doing things that you aren't necessary, but just as a general rule, we're seeing we're seeing that happen, right?
• 8:10
  Brooke: Absolutely we are.
• 8:11
  Austin: So one of the uh reliably um confusing or frustrating or um just pro problem prone areas as a flow down rule.
• 8:22
  Austin: Um uh, you know, it it has its issues across industries for different you know things.
• 8:29
  Austin: Absolutely it does.
• 8:30
  Austin: Um and so uh and it's it's also misunderstood, um, highly misunderstood.
• 8:35
  Austin: So uh do CMMC requirements really apply to subcontractors, you know, you know, from the perspective of, you know, if if you're at home being a sub a subcontractor and you also have subcontractors that may be working on this work with you or on your behalf?
• 8:56
  Brooke: Yeah, uh yeah, there's been flowdown rules in it from uh from the get-go, uh, but they've they've been made more clear and now uh they've been made more clear more than once, and now there's another FAQ about it that says, hey, you know, the flow down we talked about, we're serious, you know.
• 9:14
  Brooke: So um they are serious.
• 9:17
  Brooke: Uh you have to make you have to make have some level of effort to make sure that uh your subcontractors, the ones that are helping you with your CUI, uh or that maybe not helping you with your CUI, but they get CUI in the process of doing business for you, um they need to be the same level of uh CMMC as you are.
• 9:39
  Brooke: So if it's level two C through PAO assessed uh or you know, L2 certified, uh then they need to be L2 certified too, as long as that's CUI you're you're handing down to them.
• 9:52
  Brooke: I don't uh off the top of my head I can't think of a reason for this, but if you're just sending them FCI and there's no CUI with it, uh FCI is federal contract information, anyway.
• 10:03
  Brooke: If you're sending them FCI with no CUI, then no, they don't necessarily they don't have to be level two.
• 10:08
  Brooke: They do have to be level one.
• 10:10
  Brooke: So it depends on what information you send you send them.
• 10:13
  Brooke: But if you do send them that CUI that you have so they can do whatever work it is for you, finishing, deburring, that might be a dumb one, but you know, it's whatever they may be doing for you.
• 10:26
  Brooke: Uh painting, um anyway, they if they get that CUI, then they need to, uh they need to be the same level as you.
• 10:34
  Brooke: And you have to have some process to say, yes, here's our process.
• 10:38
  Brooke: We checked, we've verified that they are CMC level two certified.
• 10:44
  Brooke: You can't go look uh and look for their level two certification, but they can show it to you.
• 10:49
  Brooke: Or they can, you know, Scouts Honor, however that is, Scouts Honor.
• 10:54
  Brooke: Uh they can uh it's the peace sign.
• 10:57
  Brooke: I know I just did the peace sign.
• 10:59
  Brooke: Sorry.
• 11:00
  Brooke: Oh, three fingers?
• 11:00
  Brooke: Yeah, there you go.
• 11:01
  Brooke: Okay.
• 11:02
  Brooke: So I keep getting it wrong.
• 11:03
  Brooke: I don't remember.
• 11:03
  Brooke: But anyway.
• 11:04
  Brooke: Um the uh you can't just say, I promise we did it.
• 11:09
  Brooke: You have to have you have to be able to prove, show what process you have, so show how you and show proof that you actually did it, right?
• 11:16
  Brooke: And so uh there has to be some level of effort to verify your level two or your your subcontractors.
• 11:24
  Brooke: So whether they're level one, level two self-assess self-assessed, or level two certified, they there has to be proof.
• 11:31
  Brooke: Uh you have to have a process and proof that you did it.
• 11:34
  Austin: Yeah.
• 11:34
  Austin: Yeah.
• 11:35
  Austin: So and it has to be um defensible.
• 11:39
  Austin: Yes.
• 11:39
  Austin: Right.
• 11:39
  Austin: Yeah.
• 11:40
  Austin: Yeah.
• 11:40
  Brooke: Yeah.
• 11:40
  Austin: This is one of my favorite ones.
• 11:42
  Brooke: Me too.
• 11:43
  Brooke: It's been around for a long time.
• 11:44
  Brooke: Yeah.
• 11:45
  Brooke: I don't know why the question is still around, but go ahead.
• 11:47
  Austin: I mean, I I guess I get the I get it in you know why someone might arrive to that conclusion, um, although I don't agree.
• 11:56
  Austin: Um so the question uh to clue in the audience, because they haven't seen our cards, yeah.
• 12:01
  Austin: Is um uh if CUI is encrypted, um is it still considered CUI?
• 12:07
  Brooke: Aaron Powell If a tree falls in the forest.
• 12:09
  Brooke: Uh so yes, it is CUI.
• 12:13
  Brooke: Just because it's encrypted does not mean it's uh not CUI anymore.
• 12:17
  Brooke: There's probably a million reasons by well, probably a few reasons behind that.
• 12:21
  Brooke: One off the top of my head that I can think of is is quantum computing.
• 12:25
  Brooke: So at some point there's gonna be uh you know, there's gonna be quantum computing that can break a lot of the encryption or maybe all the encryption that we currently have.
• 12:35
  Brooke: So if people steal that stuff, if you know China or Russia steals that information uh and they hang on to it, and later on they can decrypt it.
• 12:43
  Brooke: So the point is not to just protect that with encryption, but protect that uh information with other all the other controls that are in there um uh for the for CMMC.
• 12:55
  Brooke: So yes, uh if it is encrypted, it is still considered CUI and it needs to be protected as such.
• 13:01
  Austin: Yeah.
• 13:01
  Austin: So my question here would be if if you have uh if you mine gold um and you got it put in a safe and a thief comes in your house and steals a safe and walks away with it, is the gold still in there?
• 13:14
  Austin: The answer is yes.
• 13:15
  Austin: Yeah.
• 13:16
  Brooke: Can they get to it?
• 13:17
  Brooke: Who knows?
• 13:18
  Brooke: Yeah.
• 13:18
  Brooke: Right.
• 13:19
  Brooke: You know, after a while they probably will be able to, you know.
• 13:21
  Brooke: With enough effort, the gold is still there.
• 13:24
  Brooke: Is that safe heavy?
• 13:25
  Brooke: Probably so.
• 13:25
  Brooke: Is it, you know, uh, but you know, if you put a bunch of gold in your safe and you're, you know, uh you might want to figure out a good place to put it in your house, in a secure place in your house.
• 13:36
  Brooke: You don't want to just stick it outside in your driveway, right?
• 13:38
  Brooke: Right.
• 13:39
  Austin: Yeah, yeah, exactly.
• 13:40
  Austin: You wouldn't you wouldn't be like, well, it's um, you know, it's in a safe, so you know, it's not gold anymore.
• 13:45
  Austin: So I'm gonna just, you know, uh keep it on my front porch.
• 13:49
  Austin: You know.
• 13:49
  Brooke: Oh my gosh, my safe is gone.
• 13:50
  Brooke: What happened?
• 13:51
  Brooke: I can't believe it.
• 13:52
  Austin: Right.
• 13:52
  Austin: So that that's more or less, you know, the concept simplified for why um they consider um it still to be C UI because the data still is there and it still is C UI.
• 14:03
  Austin: It's just it's just protected better.
• 14:05
  Austin: Yes.
• 14:06
  Austin: Yeah.
• 14:06
  Austin: So um and and uh the the important piece of clarity here is that um this is an argument that when you're going to an assessor that you just cannot make because it's coming out it's come out you know in the facts on and the DOD has addressed it very specifically um that uh you know it you're you're just not gonna it's not a winning argument when you go to an assessor.
• 14:34
  Austin: So if you're trying to figure out what you know what hills to fight on, that's probably not gonna be one of them if if that's part of your strategy, um, your CMMC strategy and uh and and scope and everything else.
• 14:48
  Brooke: So to uh dive into that just a tad more or give some examples on it, it's also not enough to say my COI is encrypted on this little drive and we're just not gonna lock it up because you know it's encrypted and it's safe.
• 15:04
  Brooke: No.
• 15:05
  Brooke: You still have to follow all the other controls.
• 15:07
  Brooke: That little thumb drive still has to be locked up, you still have to, you know, inventory it and all that kind of fun stuff.
• 15:12
  Brooke: So um so that it's not just the fact of any CUI being out on some unprotected system or some lightly protected system.
• 15:21
  Brooke: It's also, you know, you can't just say, you know, in your environment, you know, I have this uh encrypted drive and it's okay, we don't have to do anything else with it.
• 15:29
  Brooke: It's still CUI.
• 15:30
  Brooke: It still falls under the other controls.
• 15:33
  Austin: Yep.
• 15:33
  Austin: Yeah.
• 15:34
  Austin: It's uh all 110 controls uh should be applied if at all possible is typically the the well it is the rule, I guess not typically the rule, but it is yeah.
• 15:45
  Austin: So um it's uh it's not fun, but it's it's what we're supposed to do, you know?
• 15:49
  Austin: So yeah.
• 15:51
  Austin: Um and uh that'll keep you from from failing assessment or um or having problems later if you just build the right system in.
• 16:00
  Austin: Right.
• 16:01
  Brooke: Exactly.
• 16:03
  Austin: So uh next question for you is are CMMC assessment results public information?
• 16:10
  Brooke: They are not, and they won't be.
• 16:11
  Brooke: Uh you can share them with uh a customer and your primes will likely ask for them, but um but uh they're not public.
• 16:20
  Brooke: They don't at this point, the way I understand it, uh they that is not a consideration to make a searchable database because I know I know a few people uh you know in the in the DIB, the defense industrial base, that say, hey, you know, we want cy Cyber A B, we want a place where we can search for all these level two certified companies so we can choose the the vendors that we want to work with and uh so we don't have to guess and it's not so much work.
• 16:51
  Brooke: And the and the DOD has said, nope, not doing it because we don't want to make it we don't want to make it make it that easy for our adversaries to go, oh, here's all of the uh here's all the level two certified uh businesses so far.
• 17:06
  Brooke: Uh you know, they're gonna get contracts, so let's go after them.
• 17:10
  Brooke: Because when you're specifically targeted by uh nation state, uh it is a lot harder to defend against than than just being a general target.
• 17:20
  Brooke: So uh you don't want that target on your back, if at all possible.
• 17:23
  Brooke: Um you know, they've got cyber ninjas just like we do, although I'm you know hopefully ours are better.
• 17:31
  Brooke: But uh anyway, so uh but yeah, that they're not gonna make a public database, or at least from what we've been told so far, uh they they're not gonna make any kind of public database to look for uh level two certifications.
• 17:47
  Austin: So uh operational poems and just regular old poams.
• 17:53
  Austin: That's right.
• 17:54
  Austin: Uh there's a lot of talk about that.
• 17:56
  Austin: They addressed it in one of the facts.
• 17:58
  Austin: Um so why does that distinction matter?
• 18:02
  Brooke: Uh well sorry, I can't get this out of my mind, but I they so the POAMs are plan of action and milestone, they call a POAM, but the operational plan of action and milestones is not a OPOAM, it's a OPA.
• 18:18
  Brooke: So I don't know why they call this one an OPA and the other one a POAM, but you know, it's either neither here nor there.
• 18:24
  Brooke: It just it bugs me.
• 18:26
  Austin: So isn't OPA like a grandpa or something?
• 18:29
  Brooke: Yeah, that's like a it's like a yes, that's a grandfather or grandmother or something.
• 18:33
  Brooke: Uh I think from Germany, something like that.
• 18:36
  Brooke: I'm not sure.
• 18:37
  Brooke: Maybe you can tell us.
• 18:40
  Brooke: Because we're obviously not looking it up right now.
• 18:42
  Brooke: Uh but nevertheless, so uh a plan of action of milestones is the formal plan of action of milestones or POAM uh for your CMMC assessment.
• 18:51
  Brooke: Those you have to have all of those closed, complete, done, finished, finae, done done, anyway, for your to be able to get your level two certification.
• 19:02
  Brooke: The um the OPA, the operational plan of action of milestones, OPA that they're calling it, is um plan you put together for things that you may have had covered.
• 19:15
  Brooke: Um for instance, and I go back to this one all the time because it's kind of easy to use, but if you have a firewall, you've got it in FIPS mode, you it you've covered all the other controls, it's all good.
• 19:28
  Brooke: Uh but the latest firmware comes out for it, and uh, of course the firmware generally has security patches in it, so you need to uh load that uh firmware update on it for those security patches, but yet that's gonna take it out of FIPS compliance.
• 19:44
  Brooke: So what do you do?
• 19:45
  Brooke: Well, they would much rather you have uh latest security updates than FIPS validated uh cryptography.
• 19:53
  Brooke: So it doesn't mean things won't be encrypted, just means they won't be encrypted with FIPS validated cryptography.
• 19:59
  Brooke: So they would rather you put that on an operational POAM and have a process to fix it when it comes out, whatever it may be.
• 20:08
  Brooke: Um they would rather you do that than keep it unpatched, for instance, because then at that point you fall out of compliance anyway, and that's the that's the higher level of uh that's a more important need is the Is the uh you know, stay in patch with security patches.
• 20:24
  Brooke: So that's what an operational poem is.
• 20:26
  Brooke: Those things that may need to come out of compliance, but there's a very valid reason for it.
• 20:30
  Brooke: Um and you put those on an operational poem.
• 20:33
  Brooke: They specifically mention uh FIPS validated encryption because that's such a common one that like for instance, there's no supported versions of Windows 11 right now that have uh that have FIP that are FIPS validated, uh that have FIPS validated modules in them.
• 20:51
  Brooke: So you're just kind of out of luck there on servers.
• 20:54
  Brooke: You do have uh Windows Server, uh as far as Windows servers go, Windows Server 2019, uh 2016, 2019.
• 21:03
  Brooke: And there I know there are some modules for 2022.
• 21:06
  Brooke: 2025, you're out of luck.
• 21:08
  Brooke: So uh I would suggest not deploying any 2025.
• 21:12
  Brooke: 2020, you can if you have a license, you can downgrade to 22 or 19, or even 16 because they're still in support.
• 21:19
  Brooke: So um, and actually I have to look up 16.
• 21:22
  Brooke: I don't know how long 2016 is in support for, so that may not be one you want to downgrade to.
• 21:28
  Brooke: Uh, but in any case, uh generally you can downgrade on those Windows servers to a supported version.
• 21:35
  Brooke: Um, and I would highly suggest that rather than just putting 2025 in and saying, sorry, because you have to show that you know you you've at least tried to be compliant.
• 21:45
  Brooke: So uh but that's what that is, an operational poem or an OPA.
• 21:49
  Brooke: Uh is uh, or I guess that's OPA.
• 21:52
  Brooke: Uh anyway, I need a beer in my hand.
• 21:55
  Brooke: So, you know, opa.
• 21:57
  Brooke: Um we need to look that up and see what that really is.
• 22:01
  Brooke: You know, make sure we're not saying something uh something we're not supposed to be saying.
• 22:05
  Brooke: Uh but the uh so the op the operational.
• 22:07
  Austin: Jokes on you, we've already been banned.
• 22:09
  Brooke: We've already been banned, I know.
• 22:11
  Brooke: Uh so the uh the operational plan of action, the OPA, OPA is uh for those items that were in compliance, but you've had to pull them back out of compliance for for some reason, like the FIPS validated encryption I told you, the the actual the formal POAM plan of action and milestones is the main one for your CMMC uh assessment.
• 22:34
  Brooke: And all those items on that uh main official POAM have to be cleared before you can get a level two certification or before you can do your level two self-assessment.
• 22:44
  Brooke: Or say that you're you know uh that you've got 110.
• 22:49
  Brooke: They all have to be cleared.
• 22:50
  Austin: So dream scenario, I think, uh, for all the defense contractors out there that um I guess applies to some people.
• 23:00
  Austin: Um but uh certainly not the majority.
• 23:05
  Austin: The question is uh what if a company only handles hard copy only CUI?
• 23:12
  Austin: Hard copy being you know paper.
• 23:15
  Brooke: Yeah.
• 23:15
  Brooke: Uh so if if it's only hard copy, truly, truly only hard copy.
• 23:23
  Brooke: Uh so maybe you think about a construction company where they give um a contractor a paper copy of the plans and that they just keep them in paper and they open them up, they roll them up, they stick them in a little tube, you know, all that kind of fun stuff.
• 23:38
  Brooke: Um actually I have no idea if they still do that.
• 23:40
  Brooke: I assume they do because it protects it.
• 23:42
  Austin: Uh but um this includes no Xerox copying, no No Xerox copying, no electronic anything.
• 23:50
  Brooke: It's just paper CUI, right?
• 23:52
  Brooke: So if it's just paper CUI and they're just handling that paper CUI, uh then no, they don't have to have a level two certification.
• 23:59
  Brooke: They don't that flow down does not apply the same way.
• 24:03
  Brooke: Um so uh you know, all the construction people are out there going, yay, you know, but you gotta make sure you follow it right.
• 24:11
  Brooke: Um, they can't take it and uh not necessarily gonna scan in big blueprints, but you know, you can't take a piece of paper and go scan it in somewhere and say, uh, you know, it's just a hard copy.
• 24:22
  Brooke: Well, once you scan it in, it is no longer just a hard copy.
• 24:25
  Brooke: So um if it hits any sort of information system at all, CUI applies.
• 24:32
  Brooke: So but the caveat to that is that if you handle hard copy CUI, so paper CUI, uh you still have to protect it as per uh DODI 5200.48.
• 24:43
  Brooke: So there's still some I believe that's what it is.
• 24:46
  Brooke: I believe I got that right.
• 24:48
  Brooke: Anyway, but you still have to protect it.
• 24:49
  Brooke: They still have to protect that paper CUI, that hard copy CUI.
• 24:53
  Brooke: Uh but the Army, I think at first the first time I heard of it was an Army statement.
• 24:58
  Brooke: Uh talked to one of my clients about it.
• 25:00
  Brooke: I said, don't get too excited.
• 25:01
  Brooke: I wouldn't trust just the Army.
• 25:03
  Brooke: It's gotta come from the DOD, not just the Army, you know.
• 25:06
  Brooke: And uh so now we've heard or have seen in a uh FAQ from the DOD that, you know, yes, that's right.
• 25:13
  Brooke: If it's just paper, uh it's not CUI, uh they still have to protect it, but not the same, not under the same controls because it's not an information system.
• 25:22
  Austin: And I know we already said it, but we I'm very familiar with um, you know, the the questions that typically come up out of this.
• 25:30
  Austin: So that means if you're emailed something and then you print it out, that's not hard copy only, right?
• 25:37
  Brooke: Aaron Powell No, that's not a hard copy only.
• 25:39
  Brooke: It's in an information system.
• 25:40
  Austin: So it came to you over email.
• 25:42
  Brooke: That that one was hopefully it did not come to you over email.
• 25:45
  Brooke: But uh but however it came to you, email or whatever.
• 25:48
  Brooke: Yes.
• 25:48
  Brooke: If it gets if it comes to you that way and then you print it out, it's still in an information system.
• 25:53
  Brooke: It was still on your computer.
• 25:54
  Austin: Even if you delete it afterwards.
• 25:55
  Austin: Even if you delete it afterwards, yes.
• 25:57
  Austin: So you physically have to receive the physical copy, whether it's by uh going there or having it mailed or dropped off to you.
• 26:07
  Brooke: I'm sure it could be by carrier pigeon.
• 26:08
  Brooke: Yeah.
• 26:08
  Brooke: You know, they don't really that's not electronic.
• 26:10
  Brooke: So you know, if you want to send a carrier pigeon with CUI, or excuse me, hard copy CUI.
• 26:16
  Brooke: I'm just kidding.
• 26:17
  Brooke: I wouldn't try that.
• 26:18
  Austin: Who knows what'll happen with that pigeon, but so yes, it it it has to res you have to be received, you have to receive it physically, and it has to leave you physically, um, and you have to store it physically.
• 26:31
  Austin: Um and so like think of the 40s and 50s before any photocopying existed.
• 26:38
  Austin: That is the system you would have to have, right?
• 26:41
  Austin: Yes.
• 26:41
  Brooke: Okay.
• 26:42
  Austin: Yeah.
• 26:43
  Austin: Cool.
• 26:43
  Austin: Thank you.
• 26:44
  Brooke: Absolutely.
• 26:45
  Brooke: Yeah.
• 26:45
  Brooke: That's uh that was actually kind of a surprise.
• 26:48
  Brooke: Um, but you know, they they did say that.
• 26:51
  Brooke: So it's it it allow it it helps out construction companies a lot.
• 26:56
  Brooke: Uh and I'm sure it helps out manufacturers in some instances and whatnot, but um that really is a is an area of concern uh for for a lot of people, especially in construction.
• 27:08
  Austin: So next question for you is can encryption alone create logical separation in a network?
• 27:15
  Brooke: Uh good question.
• 27:16
  Brooke: I didn't and actually I didn't even really think that was a question.
• 27:19
  Brooke: I mean, you know.
• 27:20
  Brooke: Uh but no, it c it cannot provide logical separation.
• 27:24
  Brooke: It encryption provides confidentiality.
• 27:27
  Brooke: In other words, it it encrypts that uh that data so uh the wrong people can't read it, right?
• 27:34
  Brooke: Or people don't have that decryption key, can't read it.
• 27:37
  Brooke: That's great.
• 27:37
  Brooke: That's confidentiality.
• 27:39
  Brooke: It does not prevent that file from being moved around.
• 27:43
  Brooke: Uh so you need to have some logical separation in there, you know, like uh like uh through networks, a subnet or a VLAN, uh through ACLs, access control lists, stuff like that.
• 27:56
  Brooke: You need to divide up that access and restrict access to it.
• 28:00
  Brooke: Uh because again, we go back to the whole uh is encrypted CUI, CUI still.
• 28:05
  Brooke: Right.
• 28:06
  Brooke: Uh and yes, it is.
• 28:07
  Brooke: And yes, it still has to be um protected with all 110 controls, right?
• 28:13
  Brooke: Uh so no encryption does not provide any sort of logical separation on a server or anything else.
• 28:21
  Brooke: It simply provides the uh confidentiality of the data.
• 28:26
  Austin: So this is why we say all roads lead back to scope.
• 28:29
  Brooke: So because I thought you were gonna say something else, but uh go right.
• 28:33
  Austin: Well, I'm sure it would apply.
• 28:35
  Austin: Uh no, all roads lead back to scope.
• 28:37
  Austin: They do.
• 28:37
  Austin: Um and so if if you had properly scoped, um, this wouldn't be a question to begin with.
• 28:42
  Austin: And that's why we always start with scope.
• 28:45
  Austin: Um and you have to map that journey of CUI, how it flows through your business, um, and every system it touches needs to be within scope and then segmented from the rest of your network, basically.
• 28:58
  Austin: Um and so uh encrypting or password protecting a file um doesn't do that job for you because you've never addressed scope, right?
• 29:08
  Austin: So um that's why that that is a a problem, or why or why it doesn't create logical separation, right?
• 29:15
  Austin: Yeah, yeah, exactly.
• 29:16
  Austin: Yeah, this is another uh technical in the weeds question, um, but uh is one that's asked a lot nonetheless.
• 29:24
  Austin: What about enclaves that rely on enterprise networking components?
• 29:30
  Brooke: Yeah, I mean, uh it uh it does not pull the rest of your uh enterprise network into scope.
• 29:36
  Brooke: Uh so if you can show that you're separating out through the use of secure VLANs, uh stuff like that, uh, or untrusted subnets, uh, or you know, untrust no trust between the two.
• 29:49
  Brooke: Um or I should say no trust between your enclave and whatever else is out there.
• 29:55
  Brooke: It may not be just two.
• 29:56
  Brooke: Um but uh you need to be able to show how you're separating it and all the logical separations through secure VLANs, firewall rules, all that kind of fun stuff, whatever it may be.
• 30:07
  Brooke: If you can show that and prove it and uh it makes sense and you it's not uh I mean uh that's pretty uh that's pretty common, so I don't see what would be controversial about uh some setup.
• 30:20
  Brooke: I'm sure somebody could dream up a setup that isn't that they think is secure, but it's really not.
• 30:25
  Brooke: So I guess you really need to have a reality check with yourself.
• 30:27
  Brooke: But as long as you're uh creating a secure enclave, secure subnet or VLAN, and you have the proper separation, proper logical separation, proper ACLs in place, uh you should be good and it should not pull the rest of your uh enterprise network into it.
• 30:44
  Austin: Yeah.
• 30:45
  Austin: So in other words, if you've properly scoped things.
• 30:49
  Brooke: You know, I think you said all real roads lead back to scope, so yes, that would be if you properly scope things.
• 30:56
  Austin: And I'm gonna say something really controversial here in terms of uh so get ready.
• 31:01
  Brooke: If we're not banned already, here it comes.
• 31:02
  Brooke: Yeah.
• 31:06
  Austin: But enclave's a buzzword.
• 31:08
  Austin: In my personal opinion.
• 31:10
  Austin: It is a buzzword.
• 31:11
  Austin: Yes.
• 31:12
  Austin: And so uh it's like the cloud.
• 31:14
  Brooke: Yeah, it's like the cloud.
• 31:15
  Brooke: It's in the cloud.
• 31:16
  Brooke: Okay, well, what do you mean it's in the cloud?
• 31:18
  Austin: Right, exactly.
• 31:18
  Austin: All enclave means, in my personal opinion, a controversial one at that, is that you've properly scoped things and CUI stays in there.
• 31:29
  Austin: And scope means you map that journey out, and all those computers and come uh and servers that that uh process, store, or transmit CUI are properly protected and follow all 110 controls.
• 31:43
  Austin: That's all it means.
• 31:44
  Austin: Right.
• 31:45
  Austin: Yeah.
• 31:45
  Austin: And so if you're trying to just get an enclave and keep everything in the enclave, that's great.
• 31:51
  Austin: That's what you should be doing.
• 31:53
  Austin: That is the whole purpose of scoping things and and uh and and following uh the rules set forth and uh you know by the CMMC whole regime of you know regulation and everything else.
• 32:07
  Austin: So um, you know, and you can you can put everything in an enclave box and and buy enclave off the shelf or as a service or something.
• 32:17
  Austin: Um and that certainly uh works as well if it works, um, but it's still the same exact thing that we had just talked about.
• 32:25
  Austin: It's just a network that you're only keeping your COI in that follows all Hunterton controls, and you can do the same thing at your local office um to solve all the same problems.
• 32:38
  Austin: So I'm sorry, my my soapbox there, um uh, but it's uh it's a it's a buzzword at the end of the day, and it causes a lot of confusion for people um because uh they hear Enclave and then uh it it has this feeling like it means something more than it is, just like cloud.
• 33:02
  Austin: Um, but in the day, cloud is just utilizing someone else's server somewhere else.
• 33:06
  Austin: Yeah.
• 33:07
  Austin: Exactly.
• 33:07
  Austin: Um and so it's just important, you know.
• 33:09
  Austin: I don't have a a problem with Enclave.
• 33:12
  Austin: It's just important to know what it means.
• 33:14
  Brooke: It is, and really it's just a a logical separate logical secure separation uh that follows the boundary you've defined, right?
• 33:22
  Brooke: So um that's really what it is.
• 33:25
  Brooke: Uh so if you can set up your enclave within your network with logical separations properly in place, uh properly defined, and you can prove it uh and and it actually works, uh then you're good to go.
• 33:38
  Brooke: Yep.
• 33:39
  Austin: Absolutely.
• 33:41
  Austin: Absolutely.
• 33:41
  Austin: And I'll uh I could talk about that one for a while, but I'll uh save our listeners and we'll move on to the next question.
• 33:47
  Brooke: That's right.
• 33:49
  Austin: Um so the next question is do program managers have to require CMMC level two C3PAO assessments right away?
• 34:00
  Brooke: Uh they do not.
• 34:01
  Brooke: So that is uh part of one of our earlier questions, maybe our second question or so, uh that um this is phase one, and phase one uh is uh self-assessments.
• 34:13
  Brooke: Uh phase one will be uh over, and phase two will start November 10th of uh 2026, so this year.
• 34:20
  Brooke: So a little less than uh somewhere around nine and a half months away.
• 34:24
  Brooke: You know, just seems like just yesterday we said it's you know a little more than a year away, but now you know the holidays just speed by.
• 34:32
  Brooke: So now it's uh less than nine and a half months away, or somewhere around nine and a half months.
• 34:36
  Austin: So can a cloud?
• 34:41
  Austin: Speaking of cloud, we just talked about cloud.
• 34:44
  Austin: We did, absolutely.
• 34:45
  Austin: Again, cloud just being someone else's servers that you're utilizing, right?
• 34:50
  Austin: Um so can a non-fed ramp cloud uh store encrypted CUI?
• 34:57
  Brooke: No.
• 34:58
  Brooke: Uh short answer is no.
• 34:59
  Brooke: The longer answer is that uh uh CUI uh to be in the cloud to for to utilize a CSP, a cloud service provider.
• 35:09
  Austin: So not on your servers in your office or your computers in your office.
• 35:14
  Brooke: Uh and not to muddy the waters too much.
• 35:16
  Brooke: I think we might have this question coming up in a second, but that does not include your uh your MSP that may be hosting your backups or something like that.
• 35:26
  Brooke: So uh that's a different story, uh but they don't have to be um they don't have to be FedRamp unless unless they're providing a true uh CSP service, a cloud service provider type service like Microsoft 365, Commvault, you know, stuff like that.
• 35:44
  Austin: So what if they have a vendor for backup that they uh that hosts the data for them on their behalf?
• 35:51
  Brooke: That is that that does muddy the water a little bit.
• 35:54
  Brooke: So that uh that vendor, if it's if if a uh CSP is in the picture somewhere, that CSP that that uh handles CUI does have to be FedRAMP, moderate or higher, um authorized or equivalent.
• 36:12
  Brooke: And equivalency uh has a very specific meaning in the DOD uh and they have to they defined it and they have to go through a uh a whole equivalency equivalency uh assessment with um with a C through PAO um uh C through PO or maybe through PO anyway, they have to go through a whole uh equivalency uh assessment and uh they have to uh be declared and and approved by the DOD that they are in fact uh equivalent.
• 36:44
  Brooke: So for instance, ProVel uh is one of those, they were in fact the first one.
• 36:49
  Brooke: And to tell you the truth, I don't know who else is actually uh you know has achieved that, but I do know Pravel kind of early on uh achieved that FedRAMP equivalency.
• 36:59
  Brooke: They're not FedRAMP uh authorized, but they are FedRAMP equivalent.
• 37:04
  Brooke: So um so it you have to so if there's a cloud service that you put CUI in, it either has to be FedRAMP moderate or higher uh authorized or FedRAMP moderate or higher equivalent.
• 37:17
  Brooke: Okay.
• 37:17
  Austin: So if you have CUI in your office, you're good.
• 37:20
  Austin: Yep.
• 37:21
  Austin: If you have CUI backed up to your IT provider's office and it only goes to their office and on their own servers, you're good.
• 37:30
  Austin: With some caveats.
• 37:31
  Brooke: I think we have that question in a minute, but yes.
• 37:33
  Brooke: Yeah.
• 37:33
  Austin: And then but if you're using a backup provider that stores it somewhere else that's not your IT provider, or if they are and they're just reselling it to you, it needs to be a FedRAMP.
• 37:45
  Brooke: If a CSP comes in the picture anywhere, doesn't matter where, then yes, it has to be FedRAMP.
• 37:51
  Brooke: Yep.
• 37:51
  Brooke: Authorizer equivalent.
• 37:53
  Brooke: And you're we'll get to it in a minute, I think, but your uh NSP isn't necessarily uh a uh a CSP.
• 38:02
  Austin: So uh let's go ahead and get to that.
• 38:05
  Austin: So do m MSPs need their own CMMC certification?
• 38:08
  Brooke: They do not.
• 38:09
  Brooke: So uh the the minimum that an MSP needs to provide uh for uh for their client, for you, the OSC, the organization seeking certification, um the minimum they need to uh supply is a uh responsibility matrix.
• 38:28
  Brooke: It's called the DOD and their infinite wisdom decided to change the term from shared responsibility matrix to customer responsibility matrix.
• 38:37
  Brooke: So it's a CRM, which confuses with another very common uh uh term we use in the in the whole IT world, but uh but that it's okay.
• 38:48
  Brooke: You know, federal government can do that.
• 38:50
  Brooke: Uh so this uh you have to provide the IT provider, the MSP, has to provide a CRM uh to you that explains what their responsibility is and they do for you uh as it's laid out by controls, uh preferably assessment objectives, but controls, uh and uh and what your responsibility is.
• 39:11
  Brooke: So uh that's called a you know, like I said, customer or shared responsibility matrix.
• 39:15
  Brooke: And that's what it defines is who takes care of what as it applies to uh CMMC.
• 39:21
  Brooke: Uh so as long as you have that CRM in place, it's clear to clearly defined, um that's great.
• 39:28
  Brooke: Uh you'll know what flows down, what does not uh to you.
• 39:32
  Brooke: Um the if they are, if if your MSP does get a level two certification, uh that does it's not promised, but it does it should lighten the load some uh for your assessments.
• 39:46
  Brooke: It will certainly lighten the load uh for the um MSPs uh assessments if they have multiple clients.
• 39:54
  Brooke: If an MSP has multiple clients, then uh they really just have to go through a uh I can't r think of a polite term to call it uh uh but an assessment.
• 40:05
  Brooke: They only have to go through an assessment, uh uh a full assessment once.
• 40:09
  Brooke: They will spot check and verify, uh, but they go through that full assessment once.
• 40:15
  Brooke: They say, here's our certification, uh, here's our CRM, and uh the assessors should Be pretty good with that.
• 40:22
  Brooke: They'll like I said, they'll spot check some of it, but they won't go through the full assessment on each one of those controls that they provide you.
• 40:29
  Austin: If your MSP has a CMMC level two certification, it uh lowers the risk um that they carry to you during your assessment because uh you're likely just they're just likely gonna be spot checked more or less uh by the your C3PAO.
• 40:49
  Austin: But if they're not, then it's gonna be a much more intimate exam.
• 40:54
  Brooke: Intimate exam.
• 40:54
  Brooke: That's what I was looking for.
• 40:56
  Brooke: Gotcha.
• 40:56
  Brooke: Uh the word intimate couldn't come to me, but I was thinking of something else.
• 41:00
  Brooke: But yes, the uh it will be a much more intimate exam for that MSP.
• 41:04
  Brooke: Uh and the um you know I don't know how this would translate for future uh for future assessments, you know, maybe it'll matter a little bit more, um, but right now the the cost is a cost, and it does they don't they don't take any of that cost off if your MSP has a has a certification.
• 41:23
  Brooke: So uh could be that they do that later, but the burden certainly is a little bit lighter on the assessment and on you, the OSC, uh uh the risk to you, uh your uh burden that you shoulder, the weight you feel on your shoulders, you know, that that's lighter.
• 41:41
  Brooke: Um so yes, so level two certification will help a lot, um but it's not a it is not a panacea, you know.
• 41:50
  Austin: Let's a hedge your bets.
• 41:52
  Austin: Yes.
• 41:52
  Austin: Yeah.
• 41:53
  Austin: What if your IT support and your security tools are not handled by the same company, but instead different vendors?
• 42:01
  Brooke: Aaron Powell Sure.
• 42:02
  Brooke: This would be like if you had an MSP to take care of the normal support, the care and feeding of your system, but you also outsource some MSSP services.
• 42:11
  Brooke: Uh MSP is managed services provider and MSSP is managed security services provider.
• 42:18
  Brooke: So for instance, a lot of people will uh outsource their SIM or or MDR to a different company.
• 42:24
  Brooke: Um firewall, stuff like that.
• 42:26
  Brooke: Yeah, something like that.
• 42:27
  Brooke: So uh so it can it's okay if they are you know provided by different companies, no big deal, but they will be assessed uh for whatever controls that they uh uh cover for you.
• 42:41
  Brooke: So for instance, if I mean well whatever they uh whatever services they may provide uh to protect CUI, uh they're gonna cover antivirus uh you know uh firewalls, uh anyway, they're they're gonna be assessed for those controls.
• 43:01
  Brooke: Not all of them.
• 43:02
  Brooke: Not all the controls, not all 110, just the controls that they provide you uh service for.
• 43:07
  Austin: Well, fortunately we were uh uh provided uh easy question this last time, but this next one also will be a pain.
• 43:16
  Austin: So uh are endpoints in scope when using VDI?
• 43:21
  Brooke: So VDI is virtual desktop infrastructure, and uh it has a pretty specific meaning.
• 43:28
  Brooke: Um and the uh Department of Defen Department of War has uh uh defined it, defined what they're talking about.
• 43:36
  Brooke: So um a VDI system can be out of uh the endpoint connecting to VDI can be out of scope as long as you meet certain parameters.
• 43:45
  Brooke: Those certain parameters are gonna be, for instance, uh no USB passed through, no uh map drives pass through, no uh or local drive, no no drives pass through, uh no copy and paste ability, um uh screenshots, uh no screenshots.
• 44:03
  Brooke: Uh as long as you cover all those controls, uh and I'm off the top of my head I can't think if that's all of them or not, but uh anyway, if you configure it properly and make sure that you know those things can't be done, uh then your endpoint connecting to VDI is is out of scope.
• 44:19
  Brooke: But if you can't do all those items, so you can do everything, you know.
• 44:23
  Brooke: I can cover all those controls except for uh disabling screenshots.
• 44:28
  Brooke: I can't disable screenshots, you know, um, but we tell people not to.
• 44:33
  Brooke: Sorry, doesn't work.
• 44:35
  Brooke: Uh that that means your endpoint is in scope.
• 44:38
  Brooke: You know, are you actually yes you can do that, uh absolutely, but that puts that endpoint that's connecting in scope.
• 44:46
  Brooke: So um uh they have defined that very uh very well, and everybody knows if you read uh the clarification on that, you know how you have to configure it, and you know that you have to put some sort of VDI infrastructure in place, you know.
• 45:02
  Brooke: Whatever it may be.
• 45:03
  Brooke: Parallels is a is a good one to go with if you if you want to look.
• 45:07
  Brooke: So short answer is as long as it's configured properly, that endpoint is out of scope.
• 45:12
  Brooke: If it's not configured properly, uh like the DOD defines, DOW defines, I'm s it's gonna take me a whole year to get it used to that.
• 45:20
  Brooke: Uh you know, if it's not uh configured properly, then yes, your endpoint that you connect with is gonna be in scope.
• 45:27
  Austin: Yeah, this is one that causes a lot of confusion because uh you know it a lot of the off-the-shelf um VDI solutions, what uh is nice and fortunate about them is that most of those are already solved for you.
• 45:39
  Austin: Right.
• 45:40
  Austin: Um and so uh I remember at maybe it was last year um in Vegas at CS whatever East, uh I don't know, the names changed and I think CS5.
• 45:51
  Austin: CS5, but no, it was before it was CS5.
• 45:54
  Austin: Um Seek East, I think.
• 45:57
  Austin: Yeah, Seek West and Seg Western.
• 45:59
  Austin: Yeah, whatever, one of those things.
• 46:01
  Austin: Um there was a lot of confusion about it.
• 46:05
  Austin: Um and uh uh anyway, uh it it seemed like at the time the prevailing thought was you couldn't provide your own VDI solution to yourself.
• 46:15
  Austin: Um uh you could only really source it, you know, from a VDI vendor.
• 46:22
  Austin: Um, but that's not necessarily true.
• 46:24
  Austin: You can do it if you have everything configured correctly.
• 46:27
  Brooke: Correct, yeah.
• 46:28
  Austin: Right.
• 46:28
  Austin: So but some of those things are hard to configure.
• 46:32
  Austin: Um and uh to do it, you might as well just make some things in scope.
• 46:37
  Austin: Um uh because the cost to get the proper solutions to do it easily and properly is um, you know, you know, if you're if you're a smaller company, um, you know, uh it's just not always worth it.
• 46:51
  Austin: So but if you're a larger company making your own VDI solution for yourself, um very much um could be worth the the money spent to get a specific solution to to solve some of the things like the screenshots and and other things that are um uh are to do just you know with uh your off-the-shelf remote desktop and terminal services from Microsoft or whatever.
• 47:16
  Brooke: So absolutely.
• 47:18
  Brooke: Yeah, it's you know it depends on the the scenario.
• 47:21
  Brooke: You have to do a cost-benefit analysis and see.
• 47:25
  Brooke: Uh, but you're right, the uh VDI solutions that cover all the bases here, uh they're they're not inexpensive, you know.
• 47:34
  Brooke: So there may be some open source uh VDI that you can use, uh, but you know, there's always a trade-off, you know.
• 47:40
  Brooke: Uh there's uh the open source and commercial arguments all the time.
• 47:44
  Brooke: Uh so typically, you know, commercial, you pay for you know somebody else figuring everything out for the support.
• 47:51
  Brooke: And uh uh for open source, you know, it's the time invested uh to figure it out.
• 47:59
  Brooke: Uh search through all the news groups and whatever else for uh you know for support.
• 48:03
  Brooke: Uh so there's there's an investment either way.
• 48:06
  Brooke: It depends on how you want to invest.
• 48:07
  Brooke: Either one uh is not gonna be inexpensive, however you want to look at that.
• 48:12
  Brooke: Um so for smaller companies, depending on your environment, manufacturers, it's hard to make a uh VDI solution be the end-all be all for them.
• 48:24
  Brooke: So same thing for construction companies, uh, although there's some things that fit in a little bit better for construction companies.
• 48:30
  Brooke: But in any case, uh it can work for you.
• 48:32
  Brooke: You just gotta do the benefit cost-benefit analysis and see uh because they are not inexpensive solutions to put in.
• 48:38
  Austin: So I think that about rounds out all of the uh FAQs, the facts.
• 48:42
  Austin: Um so what would you say the biggest takeaway uh from all of this today is, Brooke?
• 48:49
  Brooke: Uh well the biggest take really the biggest takeaway from all from these FAQs, uh there were only a couple of them that were um that were truly new, uh at least new to me, you know.
• 49:01
  Brooke: Uh uh but the rest of them, they were uh stuff that they've just reiterated and reiterated and reiterated.
• 49:09
  Brooke: So if you're if you're in the ecosystem, you're paying attention to it, um you know, they're not necessarily uh some of them are very technical, like we just talked about, the VDI and uh, you know encryption and stuff like that.
• 49:25
  Brooke: But uh the gist of most of them are not highly technical, uh and it's just revolves around, for instance, you know, is uh encrypted CUI still CUI?
• 49:34
  Brooke: You know, that's not technical, that's just uh I was gonna say philosophy, but that's not even philosophy, but that's just a argument some people try to make to to uh ease their burden of uh scoping things out properly, I guess.
• 49:47
  Brooke: But uh anyway, most of them are not highly technical.
• 49:50
  Brooke: Most of them uh have to do with understanding the controls and understanding everything properly, um, you know, what they're asking for, the processes and stuff like that.
• 49:59
  Brooke: So really it's you know about understanding all the controls and making sure you have the proper documentation in place, making sure everything's scoped properly, you know, all that kind of fun stuff.
• 50:10
  Austin: I think that's it for us today.
• 50:11
  Austin: Uh, if you have questions about what we covered, reach out to us.
• 50:15
  Austin: We're here to help fast track your compliance journey.
• 50:18
  Austin: Text, email, or call in your questions, and we'll answer them for free here on the podcast.
• 50:24
  Austin: You can find our contact information at cmccomplianceguide.com.
• 50:30
  Austin: Stay tuned for our next episode.
• 50:31
  Austin: Until then, stay compliant, stay secure, and make sure to subscribe.