Transcript of https://www.youtube.com/watch?v=j15muxOg5Po, published 2025-05-20. Auto-generated captions, lightly corrected; the video is the canonical version.
There are spreadsheets you can download from the DoD and other private companies that give you a little gap assessment and you can set your status on each item and uh you know chart it out and do all those good things that you do in any other gap assessment. So do that now and at least start prepping for closing gaps. Regulations and compliance efforts are tied. They all overlap significantly. Gather around as we spill the tea on cyber security. We're talking about the topic in a way that everyone can understand. I'm your host, Gerald Row, giving you just what you need. This is the tea on cyber security, a podcast from [Music] Trava. Hey friend, you
know on the tea on cyber security, we really like to break down these confusing cyber security topics. So, on this episode, we're going to dive into something that's especially critical if you would like to work with the federal government, CMMC. Is this something you've heard of before? If not, or even if you have, we are definitely going to dive into that on this episode. We'll talk about what CMMC actually means for your business, how to get prepared, and why waiting may potentially cost you. So let's dive into it with our expert Tom. Thanks Jara. Hi everybody. Yeah, Tom Greco. I've been in infosac cyber security for a long time, 20 plus years. Interestingly, we were
here today talking about CMMC, which is a DoD regulation. And I I started with the DoD actually way back in the mid '90s working for the Department of the Navy uh and information warfare center in Norol. So it was fun times back then. The '90s were a little bit more wild and have a lot of regulation on these things back then and nobody knew a whole lot about it tell you the truth. Uh so it's interesting to see how far we've come. But over the years I've had the the fortune or misfortune to work in several regulated industries obviously the government. I've worked also in financial services, healthcare, uh, and just, you know, public companies
in general. So being in regulatory environments is not foreign to me. And this is the new frontier with CMMC. Yeah, I'm so excited. So I'm assuming everyone here has heard CMMC at some way, shape, or form, but for those that are new to this topic, what does CMMC stand for and why was it created? Well, CMMC. So, we got to go back. Let's do some history. There's this concept of or the framework called the NIST 800-171, which is about protecting controlled and classified information in non-federal systems. So, contractors that has been enforcable, compliance with the NIST 800171 has been enforceable actually since December of 2017. And it's evolved over time. So, first it was compliance,
then around 2020 they added the requirement that you had to self assess and put your assessment scores into uh the SPRS. So, that was like 2020ish. And now we fast forward now we have CMMC which is a cyber security maturity model capability model. It's really putting teeth behind the NIST 8001 171 compliance by upping the the compliance requirements and the tatisation requirements. And so the various levels, there's different assessments that you have to do as well as you have to get thirdparty audits on top of that. So it's it's not just self assessment anymore. The evolution is natural, right, with the the evolution of the threats and risks that we face today, especially in cyber
security. It's certainly not going backwards. It's an arms race. It's just going to keep getting worse and worse, I think. So CMMC was developed for that reason. CMMC is the cyber security maturity model certification. Okay. though it's the NIST 8001 171 into a program that bolsters the compliance by not only requiring the spurs um assessment and uh score but the third party attestations. Okay, perfect. All right, so let's go ahead and move into trying to clear the confusion a little bit more. So, I know you were mentioning how like CMMC is definitely buzzworthy right now, but what are some common misconceptions about CMMC that you encounter or how do you address them? Well, I don't
call them misconceptions. I think the attitude towards CMMC has been up until now a wait and see. I think there were a lot of folks who thought it wasn't going to come to fruition or it was going to be watered down because how could they really do this and pass all these laws and have everybody do all these things but completely losing their entire supply chain, right? But it's it's not it's there now. And also I think compliance with the NIST 800 171 has been enforceable since 2017 is something that people didn't I think take seriously because there was no there's no teeth behind it. I think that's one way to look at it. you
people have to look at it from two perspectives. One is so in June when it's when the requirements are going to go down to the contracts. It's not going to require certification at that point. But you need to be prepared for that. I think don't pump the brakes on going for certification even now because one, it's going to come up quicker than you think. It always does, right? because there's always everybody has conflicting priorities and getting through the your own self assessment as well as certification audit time and effort and money. But also the other thing is you could actually have a certification requirement flow down to you if you're a subcontractor to a higher
level contractor and they could require you to become certified earlier than what the government says, you know, because that's their business. They're a private business. They can do whatever they want. They can require from their their subcontractors. So, you know, make sure you understand those contracts you have, relationships, especially if you're a subcontractor, but don't wait. If a company is starting from scratch, what's a realistic timeline for like getting ready? It all depends on scope. So, let me let me say it this way. The very first thing you need to do is go through a scoping assessment. And there's a scoping guide that's available that will allow you to understand what your requirements could be.
And this is true for any any regulation or any compliance effort, right? Because you don't want to over scope because you don't want to have apply controls and spend effort time and money in areas that you don't need to, but you also don't want to under scope because that has its own risks. So if you go through your scoping exercise, especially with CMMC, you know, you're going to identify all your data flows. you're going to identify there are several asset types that are you know defined in specifically with CMMC scope and you'll start looking at how that how that lays out in your current environment and I think in most cases people realize they need
to do some kind of minimization kind of segmentation so they can contain the blast contain the scope to adjust a certain area of their infrastructure and of their operations so scoping is key and once you do that then you know if you've sufficiently designed behind your uh they call the buzz term is enclave. So this area where you're going to do all your CMMC COI work the effort could be a lot less if that's something that you know there there are companies that you can outsource that to these days if you're going to build your own you know build versus buy is your decision point there. So that when you go back to what's the
effort it's tough to say unless you know your scope. Okay. So when it comes to scoping though, how should a business approach this and are there any tips that you would have for them to make it feel like less daunting? If you don't know what you're doing, I would definitely get help. Definitely bring in a subject matter expert. Sculpting itself it's not highly complex but there are definitely nuances that you have to understand especially when you start talking about not just the specific assets and uh you know systems and networks that are going to be uh processing storing and transmit cui but getting in and out of those areas also has some implication to your
scope for example there's this concept of the contractor riskmanaged asset that's an asset type and it's an asset a type that isn't intended to process store or transmit CUI but isn't prevented from doing so. So it's somehow tangentially connected to the rest of the scope that is going to be fully assessed. And the way the rules are written is that the controls around those assets still need to be documented in your system security plan, but they aren't going to necessarily be directly assessed when the C2PAO comes in to do the audit unless they don't like how you documented the controls. Then they can start doing some limited examination of those assets. It's those kinds of
things that if you don't really understand what those are and what the implications are that you could underscope I see in this case and maybe leave something out and then you get to the finish line and you get your audit done and they you realize there's a whole class of things that you didn't consider. So just one example why I say get help if you don't know what you're doing. This isn't one that you want to get wrong. Things like HIPPA for example for the most part unless you're going to get a letter of attestation from a third party no one's going to come and audit you unless something bad happens. Now, that's certainly a
time where you don't want to find out that you didn't do something correctly, right? But with CMMC, if you don't get it right, you don't make money, right? You're not going to be awarded contracts. Yeah. So, I think that's why I'd say scoping is the most important thing. Perfect. So, you mentioned CUI a couple times. Then, what is that exactly? It's an acronym for controlled unclassified information. So it's information of in various types and there's a catalog of the different types but it's information that the government doesn't deem classified. So in the actual federal classification system, you know, secret, top secret, etc. But sensitive enough that it warrants specific control. You mentioned earlier about there
being different levels of CMMC. You went through one, two, and three, but does scoping have anything to do with levels? Yeah, in your scoping exercise you can determine your level, but also the DoD contract will also specify exactly what level you will need to be compliant at based on the contract. Perfect. Okay, so let's talk a little bit more about like the preparation and everyone's favorite topic, budgeting. So for companies on a tight budget, is there a secret sauce, if you will, to prepping for their required level? if you're on a tight budget and I don't know if that correlates it shouldn't correlate to the size of your organization but it's a tough one because
again because this is tied directly to contract award you know or if you're a sub for a prime that's direct to the DoD contract there's no shortcut if you're a smaller company and you're just getting into this and maybe your level of maturity overall on your security program is low because you just haven't been forced yet to build those kinds of capabil ilities. There are ways that you can phase through gap assessments and prioritization of remediation. There are ways you can phase the controls in. And that's really a decision for organizations to say, well, depending on my budget, I'm going to have these phases over these this timeline. And you may push your your ability
to to be awarded contracts down the road simply because you can't do it all the same time. I mean, even if you have all the money in the world, it doesn't mean you can suddenly implement all the controls and close all the gaps that you need to close in a certain amount of time, unless you're really, really super focused on it and that's all you're doing. I think it's really tough in this case because it is it depends on how quickly you need it. If it wasn't tied to being awarded contracts, those are different things. is if you're trying to meet PCI compliance or HIPPA compliance those kinds of things but you know otherwise you're
more free to set your own timeline and that then defines budget right right so you have already given us a few tips and everything about prepping and things like that but is there anything that you would have someone do right now to get ahead of this do the gap assessment against the uh the 800171 the 80071 is very prescriptive there are you know assessment tools and spreadsheets you can if you're using a GRC uh everybody has this framework in the GRC or if you're using a Secureframe or carbide right you can pull it into your your GRC tool and use that as a guide there spreadsheets you can download from the DoD and other private
companies that give you a little gap assessment and you can set your status on each item and you know chart it out and do all those good things that you do in any other gap assessment. So do that now and at least start prepping for closing gaps. Forget about CMMC at this point. Just close gaps. And if you have a an existing certification, you know, if you have a an ISO 27,01 certification or if you have a SOC 2 certification, those things will help because you map those controls over to the NIST 80071. I mean, and that's the other thing about all these frameworks that regulations and compliance efforts are tied. they all overlap significantly.
And they go a step further. If you're using a GRC tool to manage that compliance, most of them you can copy those controls over when you when you add the ISO or then this framework or the CMMC framework, copy those controls over and that'll help spit out gaps really quickly as well. But work on gaps. So speaking of assessment, you did talk a little bit more about self assessments and third party assessment a little bit ago, but what is the difference between the two? So, self- assessments and thirdparty assessments. And then when are each of those required? The self assessment specifically against the NIST 800171 is required at level two and up. And what it
means is that you are formally assessing your yourself against those 320 assessment objectives that I had mentioned before. And so if you pull down one of these gap assessment tools, spreadsheets, whatever, it'll show you explicitly or if you just download the specification itself, right, it'll say this is the control and in this control there may be 2 3 4 5 six assessment objectives for that control. So your self assessment is literally you going through and testing that you cover every one of those objectives and that results. So there's the SPRS which calculates a score. you have to achieve a score of 110 because that's equal to the number of controls the top level controls that
are in the NIST 800 171. But as you go through and you do your self assessment, you'll strive to achieve that score and it starts out at a minus 202 and it goes up and up and up and up and eventually positive and then it goes up to let's say 110 when you've achieved compliance against all those things. And then a a senior executive of your organization has to then go to the SPRS and make their attestation. Okay. Say we attest that we are compliant. That's very important because you know management needs to take ownership of that. That helps drive prioritization as well. So that's the self assessment and then yeah I mean in most
cases level two you're going to have to engage one of these third party assessors to come in and do the independent audit. and they're essentially going to do the same thing. Go through every one of those assessment objectives and they're going to test you. They're not they don't typically do full operational audit, but they're definitely going to do operational testing of walkthroughs. So, it's not just a documentation review, right? They're actually going to validate that the controls are operating effectively. Depending on the result of that is how you either get your certification or you don't. Right. Right. And then you also mentioned the C3PO. I don't know if we gave what that stood for. So
I know it's another acronym. What does that stand for? They are certified third party assessed organizations. So they're organizations who have achieved the certification by DoD to go out and do these these certifications. So you can't just hire anybody. There's an organization, independent organization that manages all the directories of all the different certified people that have anything to do with CMMC or the C3POS are part of that. So there's cyberavab.org. They have a directory of all those folks who are accredited and as well as individuals who may be just considered like I'm considered a registered practitioner. That doesn't mean I can do certifications, but it means that as a consultant, I would help organizations perform
their gap assessments, help them create system security plans, help them, you know, facilitate their self- assessments. And I could even sit in on the audit meetings when the CBO comes in to test it, right? if they wanted. It's not like that that designation is the only one or that you have to have it for those things, but the organization at least would I think you more higher level of trust with the organization. So there's a there's a registry of the registered practitioners as well as the C3PAO out there and a lot of other information as well. You said that was cyberab.org. Yeah. Okay. All right. I know how important it is for like maintaining compliance
and continuous cyber security. So once someone is CMMC certified, how can organizations maintain their compliance with CMMC over time? I mean I I'll say this is and this is really independent of CMMC. You have to have a compliance program. You have to have folks that are not necessarily dedicated but are focused on making sure that you do understand all things that you have to do and in what timeline you have to do them. If you're not implementing, you know, in management control assessments throughout the year, they have to be at least some folks that are there making sure that things are operating and that you're maintaining the evidence of their operation. GRC tool can help
a lot in that respect. sort of talking about before because it not only gives you a framework within which to do that you know but it'll help trigger you when certain things the actions have to be performed and in a lot of cases there are integrations between the GRC tool and the other tools like your identity tools or your endpoint security tools etc that will monitor those things for compliance and so you'll have the evidence of compliance and also it'll help alert you if things are going south all right so another thing that I have learned about cyber security and compliance is that it truly is a team effort and it kind of is top
down. But achieving compliance isn't just about checking boxes, but how can organizations foster collaboration across departments to succeed in CMMC or any other framework that they would be going after? I mean, it's a cliche, but the most effective tool is the one at the top. Making sure that senior leadership understands requirements. And in this case when we're talking about regulatory requirement the legal department is the first line there right they need to understand an organization's regulatory requirements and obligations and they should be flowing that through the organization through senior leadership to make sure that all that need to happen are happening. Now with the CMFC there's that extra kick that cos are going to care
about because if they don't have their certification they don't get contracts. So that's another motivator, but still it's tone at the top and making sure that that flows down so people have the right prioritization, budgets, etc. to do the things that they need to do. And I mean, I've been in organizations and I've been in the specific position myself too where you feel as though we're working really hard to do this because we know it's important. You're trying to manage your own priorities and it's tough for folks to do that, especially when you get down to the, you know, the engineering level. I I think just assuring that your organization has that right senior leadership
direction, understanding and direction and keeping them informed. You always need to lead up because those are the types of things that will help you if you do need priority to get something done. If you do need that collaboration, if you need money specifically or anything else, don't hesitate to lead up either. That's very true. So, one of the tips you gave us a little bit ago was to find someone to help you get an expert. So, I think it would be a miss if we did not talk about ourselves. So, how can Trava assist an organization from a compliance standpoint with CMMC or anything else? Yeah. Well, specifically with CMMC, we help our clients with
first and foremost that scoping engagement. So we help them navigate the complexities of scoping and then identify those opportunities for them to limit that scope, right? Options on how we can make it easier and faster and cheaper for you. And then we we go right into gap assessment. So we'll perform the gap assessment for you. We'll create a remediation plan with recommendations. We will assist you in developing. There's some requirements. You know, you have to have your system security plan. And that's that's a fairly comprehensive document. So we'll assist in creating systems of security plans in managing what they call plans of action and milestones or PAMS. You'll see that term thrown out there. You
know, managing that and making sure that that those things are closed as well. So helping you track monitor those and basically everything up to getting you through your self assessment for the first time, right? And then coordinating with the C3PAO if that is part of your requirement so you can get that audit performed. that's really on the the advisory consulting side, but Trava also has a great offering called compliance to service and that's really a an augmented compliance department for you with a GRC thrown in. Yeah, that's fantastic. Okay, Tom, we've covered a lot of information. I've taken um a page and a half worth of notes here, but if there is anything else that
you would like to hit home or stress, what would it be? Don't wait. Get your sculping done and start those gap assessments. Even if you're not ready to engage third parties or if you need to, there's no downside to it, right? NIST 800 171 is a nice comprehensive framework against which to to define and measure your security program. And it doesn't matter if you need to get CMMC certified or not. I mean there are other frameworks obviously as well but it's good one. So use it and it it does apply in in a lot of cases. It applies for obviously for CMMC but it also applies for example in the joint certification program. So JCP
is another DoD program that and for folks who aren't necessarily working on DoD contracts but they want to have access to DoD unclassified technical data like blueprints and specifications those kinds of things. Maybe you're doing pre-cont contract work on something that you're developing for the Department of Defense and so you you need some information or do prototyping and to collaborate with other folks. You have to do a NIST 8001 171 self assessment for that and put it in spurs and plus you're already required to do it anyway. If you are handling COI already, it's already enforcable, right, that you do your self assessment and get it in spurs. So, so do that. Tom, thank you
so much for joining me and your time and expertise are really valuable. I appreciate it. Fun stuff. Thank you. [Music] Now that we've spilled the tea on CMMC, it's time to go over the receipts. It looks like CMMC has been a bit of a mystery or like a wait until now, just until recently, maybe the last end of 2024. So let's go ahead and get into what I took away from the conversation. Receipt one is what does CMMC even stand for? And it stands for the cyber security maturity model certification and CMMC is a department of defense framework that is based off of the NIST 8001 171 framework. Another main thing that I took away
is that CMMC has different levels. So there's level one, level two, and level three. With level one that focuses on the protection of federal contract information, level two protects controlled and classified info along with everything that level one does. And level three protects the info that has impact on national security. So, there are different businesses that may need different levels and Tom also said that you figure out what level makes the most sense from you during a scoping exercise. Another receipt that I have is actually a resource that Tom talked about which is cyberab.org. So, they have a lot of different information including important things and downloads for CMMC. So, if this is something you
are looking into, I would start with cyberab.org. And the final receipt from this episode, Tom's advice is to start now. If you want to work with the DoD, CMMC is not optional. It's mandatory and it's something that you have to do. So, it's important to go ahead and get all of your ducks in a row, find someone that can help you, and get things rolling. And that wraps another episode of the tea on cyber security. Thank you. And that's the tea on cyber security. If you like what you listen to, please leave a review. If you need anything else from me, head on over to Trava Security. Follow wherever you get your podcasts.