Video: CUI Compliance: The Rules, the Risks, and the Road Ahead | Duration: 2660s | Summary: CUI Compliance: The Rules, the Risks, and the Road Ahead | Chapters: Welcome To Webinar (2.72s), CUI Compliance Challenges (122.78s), Federal Regulation Standardization (252.82501s), NIST and FAR (383.46s), Compliance Penalties (561.815s), CUI Regulations Impact (914.175s), Compliance Preparation (1478.76s), Compliance Challenges (1590.63s), Incident Reporting (1797.75s), Compliance Frameworks (1880.395s), Compliance Integration (2009.735s), Public Comment Impact (2172.675s), DFARS vs FAR (2275.3699s), Final Questions (2339.345s), CMMC Oversight (2462.19s), Final Thoughts (2563.7551s)
Transcript for "CUI Compliance: The Rules, the Risks, and the Road Ahead":
Alright. And we are live. So, hello, everyone. I am Tarek Wiley of Apptega, and welcome to our webinar on, CUI compliance, the rules, the risks, and the road ahead. I am joined today by Thomas Allen, principal consultant and chief information security officer at Foresite Cybersecurity. And he's here to share his expertise and answer our questions about, CUI compliance. So, Thomas, do you want to introduce yourself, tell us a little bit about Foresight? Sure. So Foresight is a pure cybersecurity company. We don't do anything but cybersecurity. We have multiple lines. We're a Google SecOps partner, for MSSP. We, manage a lot of people's security in a lot of ways, using various products. But we also have a GRC platform, that we use use app using Activia's platform. But we have a practice where we help people meet their requirements and go through their various frameworks such as NIST eight hundred one seventy one, which we'll talk about today, but lots of others too. Great. Thank you. And, we appreciate you joining us today. Quick note before we dive into, the real conversation, but, I'll be moderating and asking some questions, but we we really want this to be a discussion. So, audience, we welcome your participation. If you have any questions or comments, please chime in through the chat, or the q and a that's up in the right hand side of your screen, and we will prioritize your questions. So this is really your chance to help us lead the discussion and, you know, know, chime in with anything that you want to ask. Final thing, an on demand recording will be available after the webinar. So, you know, please feel free to, check this out if you wanna watch it again or send it to anybody within your organization who didn't get a chance to, attend it live. That being said, we'll go ahead and jump right into the topic. So, to set the stage, controlled unclassified information, or CUI or CUI is sensitive government information that requires safeguarding. So if you're a government contractor, you likely have CUI that requires you to take certain steps to ensure compliance with federal regulations. So that's a a very broad definition of, of CUI, but in reality, identifying it within your organization can be very difficult and confusing, you know, finding out, well, what really classifies as as COE. So, it's also very difficult to implement the right way, you know, how you're gonna protect that. So as the government rolls out stricter COI regulations like the new far COI, FARCOE rule, which we're gonna go over today, organizations are facing new challenges protecting that sensitive data and legal consequences for failing to do so. So that's why we're here today. We have Tom here as our expert, to walk us through everything. So let's go ahead and get started again. Feel free to ask your questions in the chat. But, Tom, can you, please tell us a little bit more about the current state of federal COE regulations? Yeah. So the current state is pretty much an amalgam of a lot of different, standards by different departments. Currently, it's basically per department. They tell you what the rules are if you're going to supply them with a product or service. They get in either in the contract or as a side note. They give you a list of the rules for handling that data, and that's pretty much it. So if you work with DHS, you might have one set of standards. If you work with DOE, you might have another and so forth. So, that's really the current state. Most most of them require cybersecurity requirements, although maybe not as prescriptive as the future holds. Great. And, we mentioned before the the new FAR, Kui rule. Can you tell us, more about what that is and, how it's gonna impact businesses and other organizations? Yeah. So it's a a rule proposed. Well, first, let's talk about how we get to a rule. So who manages, the FAR, the federal acquisition regulations? Well, it's a panel of three groups for groups made up of NASA, the GSA, and the DOD. So the this panel gets together, and they decide on what the federal regulations are going to be. As we discussed in the last question, up till now, it's been, hey. Federal agencies, you decide. Do it yourself. We're seeing more standardization. They're seeing the threat actors and especially nation states and things becoming more and more interested in that data. So, they're they're gonna hand down this standard. So I think that is important to know where it comes from, because you can kind of get an idea of where this is going when you look at the DOD being heavily involved and you look at regulations they're providing to defense contractors. So I think that's why it's important to know that. Great. Thank you. And how does this, this new rule change existing, COE compliance requirements for contractors, subcontractors, and other entities? Yeah. So, again, it it's standardizing things. It has it's it's going to have broad applicability. So in other words, all federal contractors now. That may not or federal agencies. That may not sound like a lot. I think what there's 13 at the most federal agencies. However, then there's subcontractors of contractors who are bidding on these contracts. When you extrapolate it out, it comes to the an impact of lots and lots of organizations. So and even some higher ed and so forth. We'll get into that a little later. But, so it's really important to understand that this is gonna be a standardized approach. So if you want to do business with the federal government and you're going to have data in that contract that measures up to CUI, then you're going to have to abide by this. Okay. Thank you. And you you had mentioned, NIST eight hundred one seventy one, I believe, before. Can you can you tell us about the role that, that has as well as FedRAMP, in this new, FAR rule? Yeah. So, again, we kinda have to go back to, the how does this come about? What's the genesis of it? So the the national registry, NARA, the national archives, they, were asked to be responsible for managing CUI and what is CUI. So they have a registry. You can go online, find the registry, and say, what data is actually CUI? So then you can say, well, in the contract that I have, does it measure up does any of this stuff measure up to that now? The interesting thing about the new FAR, which is better than the defense, the d DFARS, they call it, the defense contractors is in the FAR rule, they have to supply you with a standard form that's going to tell you all the stuff we're giving you that's KuoE. And it might even tell you stuff that you create might be KuoE too. Because that's always been the biggest problem is what is CUI? What what CUI do I have? Where does it travel on my network? You know? And for a large part, even though DFARS says that they should tell you what the query is, they don't. So this is gonna standardize that. So at least the query they hand you will be identified. The problem is you may create query in the process of doing this project or the service or whatever. And how do you make sure you identify it and label it as the rules? And that's that's always been the trick. So, again, we start with NARA. NARA says, well, here's what the categories of Kuie are. So then the government went to NIST, the National Institute of Standards and Technology, and said, can you create us a framework for protecting this Kuie? So they did, and it's called eight hundred one seventy one. It is derived from, NIST eight hundred fifty three, which is for actual federal systems. It's a subset of the controls for federal systems that now you're a non federal system, but you're gonna handle, non federal data. So we're gonna transfer these controls from 53 to one seventy one, in a subset as appropriate. There are many people who argue that basically, one seventy one and fifty three are very, very much the same. However, doesn't really matter. Point is they created one seventy one, and they said, okay. This is how we expect non federal systems or people with non federal systems to handle and protect this controlled unclassified information. Great. And, do you know anything about the penalties for noncompliance with this, FAR COE rule, or, you know, other COE regulations in general? Yeah. So it's not super clear. So there the penalty is obviously you could lose the contract. That's one penalty, one potential financial penalty. This the FARCUI rule, the one thing they didn't go as far as the Department of Defense and say you must have a third party that validates that you're meeting this, they said you can self assess. However, the trick there, is that NIST eight hundred one seventy one doesn't stand alone. So, in other words, there's another document called NIST eight hundred one seventy one a. And that document has so one seventy one has a 10 controls. So you might think, well, that's not so bad, a 10. Well, the the one seventy one a, which is the guide for auditing or assessing one seventy one, has what they call control objectives. So you're gonna have 320 control objectives to satisfy a 10 controls. So I always like to use the example of access. So, you know, we're gonna control access to this QE. Well, okay. That's one control. However, the the control objectives say, okay. How do you do this for users? That's easy, usually. With active directory, we use some sort of system. But then it says, how about devices? Oh, okay. Well, maybe we do that. Maybe we don't. And how about processes acting on behalf of users or of accounts? So, you know, we break that down into many parts, and it's not quite as simple as it seems. So, but then so we do the self assessment, and we tell the government, yes. We're compliant. And, usually, it's not some big formal thing. It's we if we accept this contract and we start working on it, we're in the contract notes somewhere. It says, by accepting this contract, you're saying you're compliant with the state hundred one seventy one. So where would the enforcement be? The enforcement would be say you had a breach, say something went wrong. We could wind up with what what what's been happening recently in the DOD world is that, the FTC has been bringing false claims act actions against companies that claimed that they were compliant, that then something bad happened turned out they weren't compliant. In a couple of those cases, it was an action to claw back every dollar that they ever got from the federal government for, federal contracts. In other cases, it was just a blanket fine, so forth. So, I I don't believe it's gone as far as criminal litigation yet. But could it? It certainly could in the future. And I again, I had said earlier, I think the way we look at this is we look at it the way the DOD handled it. So the DOD started with you can do self assessments, started figuring out people were basically very cavalier about their answers and how they were dealing with the self assessment, and claiming that they were compliant. And so eventually we got CMMC, which is, now we have to go out and pay someone to give an opinion that we are compliant instead of just being able to say we are compliant. So I think you can look at it and say, if if this doesn't go well, that's looming over the head. And I think most people involved in the federal procurement system kind of feel like it's coming anyway. Sooner or later, all these other if CMMC goes well because it's pretty new, then you're gonna see it transferred to other departments. I know the DHS has already publicly said they're watching what the DOD is doing very closely. So you may eventually wind up with a CMMC like rule for all CUI throughout all federal agencies, but that's remains to be seen. Okay. And, you know, you're talking about CMMC. Can you kind of expand on, what, what the relationship is between far, KUI, and CMMC? You know, are the places where they intersect or where they can complement each other? Just can you go into a little bit more about that? Sure. So a lot of people mistake, CMMC. They think it's another framework. It's really not. It is a certification methodology to certify that people are living up to what one seventy one says or are compliant with it. If you get into level three, it has some of its own controls that go beyond one seventy one. But most people are gonna fall in level two, and level two is really just NIST eight hundred one seventy one. So, yeah, so it's a certification requirement. It's not a framework in and of itself, to certify by a third party that you are compliant in in the way you're handling this query. So it's it's again, it doesn't have anything to do with far query today. So that's what I would say is but, you know, because if you're if you're getting a DFARS clause in your contract, that's Department of Defense, and that's the one that's gonna require COOE or require CMMC. I apologize. But if you're doing a contract that has far clauses, you will not have the CMMC requirement right now. Okay. Got it. Thank you. And so the far Kui rule, it, it not only bronze its reach beyond just defense contracts to all federal contracts. Right? But can you talk about how the FAR CUI rule could impact other entities? You had mentioned at the top of the, the call higher education institutions, for example, who might have federal research grants or funding, you know, rather than, you know, direct contract? Yeah. So, I mean, CUI is CUI. So if if if you have a federal contract that has CUI, you're expected to protect it. The DOE had decided to do their own FAR kind of COE rule or their own COE rule, and they've that's kind of been put on hold because the fate of the DOE is kind of a little sketchy. But the other thing is that a lot of people feel like they already have it because GLBA, they is required. And GLBA, they how do you GLBA is very vague and basic. It says you must secure stuff, basically. It doesn't get into how or why. So most of the clients I work with, have decided that we're just gonna use one seventy one as our means of proving GLBA. So, you know, it's it they're very tied together. I I think if you have federal, data that might be CUI, you should be thinking about January. So Right. Clarification question from the audience. What is GLBA, and which agency is pushing it? Yeah. So GLBA is already a law. So it's the Gramm Leach Bliley Act. And it basically was a a law that was passed to protect, they call it NPI, non public private information. I think that's what it stood for. So and that information also leaks down into the higher ed world because of FAFSA. So if you take FAFSA money, you fall under GLBA. So, you have to make sure that the data you're getting on all your all the private financial information of your students going through FASFA, that is now federal money or federal data is now CUI. So the two tie together right there. So, yeah. The and so that's what it is, and it flows down from the the one seventy one is not a requirement. Let me be clear about that. It is a way to meet g bit GLBA. So, and it's the way that most commonly we see used. And you could use anything. You could use, 853. You could use, ISO. You maybe not. But you can use lots of other ways to get to GLBA compliance. But the one seventy one makes the most sense because the data that you're concerned with is COE, is classified as CUI. So Thank you. Yeah. Another question from the audience. How much risk is mitigated by transferring the requirement from self assessment to assessment by a c three p a o? And, when will we see the effectiveness of CMMC in the flow down? So I think that you're not really mitigating any risk. You're really just getting a third party to say, yes. We agree that you're compliant. So does that third party take on some liability or litigation potential if you're not compliant? Possible. When we look at other things that have are similar, I'd I'd like to look at PCI. So PCI has auditors called QSAs. So they go in and they audit credit for the credit card brands that you're handling credit card data correctly. And if you get breached and they don't think you were handling it correctly, The interesting thing is that QSA companies have been sued a few times and not one time successfully. So the courts have found that it's really your responsibility, and I think that's how this will have work with CMMC. You know, they're they're not gonna say because what could happen, right, is I could come in there as your three CPAO, and you could show me all these controls that are great. And then tomorrow, I walk away, and you could change them all back to make your workflows easier. Right? So, you know, it's kind of a point in time thing. So until we get to some automated way where the government can just watch you daily and go back and look, I don't think you're ever gonna see a three c a three PAO or a an audit firm become part of the liability of a breach or something like that? As far as the flow down, it's a great question. I I mean, I hope we start seeing it soon. The problem right now is that not a lot of companies have even been able to get their audits and get certified. So the contracts, we won't have CMMC on all contracts till 2027. So it's gonna be hard to sort of cherry pick the data and figure out what the overall metric to it. How how is this affecting the security of the data? Sure. Great. And thank you for the, questions from the audience. Please keep them coming. Like I said, we will prioritize them. So going back to what you're saying, Thomas, you'd mentioned, a rule specific to higher education that was proposed. Are there any other current or proposed rules that could impose stricter data protections on CUI? And and, you know, can you go into a little more detail about that rule that you had mentioned? Yeah. So the the DOE was just going to have their own rule to say all the student information that you have should be protected like CUI. I think it would only apply to federal to publicly, funded institutions, not private institutions, unless they're getting, you know, federal funds from FASFA for student, you know, monies and things like that. But, so anyway but I think that, again, you know, there there's a lot of debate about, don't they already fall under that? Is this just a redundant rule on top of rules we already have? Sure. I think it's a valid argument. You know? So I would say that and other than that, you you know, the big thing is CMMC right now. So that's kind of taking up a lot of the oxygen in the room as far as new regulations. So I'm not sure that it really kinda caught most of us off guard that this rule popped out. It was like, well, that's yeah. We know they're working on it. That's gonna be down the road aways, and it just kinda occurred. So the far one, I mean. So, yeah, I think those are those are the two big impactful ones right now. But I I I think, you know, you could read the tea leaves. We all could. Cybersecurity is becoming more and more important. They're coming up with more and more data types that we have to protect. It's just sort of a common thing in the world in general of being stricter with cybersecurity regulations around data. Great. Another question around CMMC. We heard about CMMC two being required for some contracts with the DOD. Is it actually required? If not, what's the timeline, for when it will be required? Yeah. So I had said earlier, I think by 2027, they want all contracts that come out of the DOD, as far as they're gonna do a slow ramp up, they claim. So I think in May or June, they're planning you're you're gonna see the first few contracts come with the CMMC requirement, And then you're gonna see more and more after that slowly. You know, they kinda it's a whole ecosystem they're building. So they have to get three CPAOs onboard, and then we have to get companies assessed. So, like, if they put out a contract yesterday that said you must be CMMC certified, there'd probably only be two companies. Yeah. That's that's a exaggeration. There's 20 to a hundred companies that are CMMC two certified now. So who's gonna do it? Right? So it's gonna be a slow ramp up as more and more companies. The place where we see a lot more pressure today is coming down from subcontractors. So, General Dynamics or Raytheon or whatever, they're saying, no. We don't care about the contract. We want you to prove that you're CMMC ready now before we make you allow you to use subcontract work. So a lot of pressure is coming from them rather than even the DOD on the subcontractors and downstream folks. Great. Thank you. And, anyone who wants to know more about CMMC, we have an upcoming webinar, you know, in just a few weeks on CMMC. Link is is right there in the chat. But, if you're interested in more on CMMC, you know, feel free to sign up for that. Alright. So diving back in, Thomas, can you tell us a bit about the steps that organizations should take, to prepare for compliance with the FRQUE rule, you know, once it's finalized, assuming that's finalized. Yes. You should go back in time about two years. No. I'm just kidding. I'm I'm only kinda kidding. But, seriously, I mean, the first thing you need to do is you need to assess yourself. So you need to sort of try to figure out what CUI do we have, what systems does it flow through, and how are we protecting it today. I would download the NIST eight hundred one seventy one a, and I would start walking through those control objectives and, you know, putting together the idea of, so, hey. Do we do this? How do we think we do it? Is that good enough? That's gonna require some research or some expertise if that's good enough, question. So then, you know, obviously, it's going to be very helpful to have a platform like an AppTIGA or any any way to to keep this organized. Because what we find, as GRC consultants is where most people's compliance process breaks down is in project management, more so than necessarily not doing the right things. It's just managing the project to keep everything straight, make sure everything's all i's are dotted, all t's are crossed, and that's where a platform is super helpful. But you don't have to have one. Like I said, you could download the one seventy one a right off of NIST's website, and you could start going through it, and sort of managing your own self assessment and then saying, okay. Where are gaps, and what will it take to fill those gaps? So, that's that's where I would suggest everybody start. You can certainly look for a consultancy like Foresite or others that use a tool like Apptega. But it really comes down to where do we stand today, what are our gaps, and how do we fill those gaps, in short order. Great. Thank you. And, what would you say are the biggest challenges that organizations face when managing Kooi compliance programs, and what strategies would you recommend for, for overcoming them? So the biggest challenge starts with what is KUI and where is it in our systems. So it's it's very hard to know how to how you're protecting something if you don't know where it is. Right? So we've gotta have an inventory of that and figure out where it is. We often, tell people, and and we get debates about this, but we often tell people is just follow the contract. If you you are creating data on behalf of a contract that has a query clause, I would just consider it and leave it at that. Now the reason we get some pushback on that is because people talk about the the risks of over labeling I mean yeah. So you're overprotecting things maybe that you don't have to. The that's the risk. The risk of underprotecting it is far greater and far potentially more dangerous. So I would lean on the side of overprotecting it, and not underprotecting it. So that's that's one challenge is just identifying the COE. I think, the other challenge is that a lot of people feel like, okay, you know, take a control that says you must have antivirus. Well, we got antivirus, so we're all set. But if you look at it, there's really, like, multiple things that make this a process, a repeatable process that can be audited. And it starts with a policy. Do you have a policy that says, hey, the business says we must have antivirus on all machines that are commonly commonly get malware. Then you need a process or a procedure. How do we do that? Okay. Well, we use CrowdStrike, and we make sure that it's on all these machines, and here's our process for how we put it on and how we make sure it's on and and all of that. Then we have the practice, which we've already discussed. So they're doing that already. And then how do we verify and validate? That's the fourth pillar. Verify and validate and audit that the process is effective. And then finally, we come to how do we make sure that the process how do we update it and make sure that the process continues to be effective as technology and the world changes. So I always say there's five pillars to it. And most people are doing one pillar pretty well, which is the practice, which is great because it's better than not. But they're they're missing some of the other things that an auditor is going to look for. Great. And, I mean, you you're talking about the importance of of having a a process policy. With that in mind, can you, can you talk about the role of incident reporting, in, Kuwei compliance? And Glad you brought that up, especially the FarCUI rule because the FarCUI rule has a crazy short amount of time that you have to let the government know that you've had an incident. So it's eight hours. Eight hours. I would argue that in eight hours, you may not even know if you had an incident or not. So, that's that's a challenge for sure. I think, when we look at everything everything in the far query rule makes mostly makes sense, but that one stands out as almost too onerous and too difficult. So we'll see. We're in the comment period. So, basically, the public has a right to go comment on this rule and say, you know, we think this this or that is not reasonable, and make those comments. And then, generally, after the comment period ends, which is March 17, so not long from now, sixty days after that, the rule becomes final, and it becomes the real deal. Perfect. Thank you. Quick question from the audience. If you're starting in on a compliance certification initiative, what standard would you recommend pursuing? So I usually recommend, NIST cybersecurity framework to begin with, because it's really more of a program around putting together the pieces you need. Now there isn't a compliance audit for it, so you're not gonna get a certification for it. But it's a great framework to build around. So, and it's fairly simple and fairly easy to understand. So we start with that, and then we expand out from there. So you might want to take your CSF and use it as the base for moving on to a SOC two or an ISO, which are then kind of the next step of rigor. Then there's another step to, like, a HITRUST. Might be a takes a little more rigor and a little more intensity to get there. And then on the end of that, you've got the NIST eight hundred fifty three and the federal standards, which are the most rigorous, including one seventy one, frankly. So if you're really just trying to start out, to then build up and you don't have this regulation breathing down your neck, then I would start with NIST CSF. And the other thing about CSF, ISO, SOC two, so these are general frameworks for your entire security program. They are not so this, Cooey, is one specific type of data with one specific way of protecting it, as laid out in January. Whereas that's more of those are more of general controls over your whole cybersecurity practice. So you you'd want to be able to do those for everything, whereas you wanna focus on the CUI or if it's PCI credit card data or HIPAA, you know, patient data. Those specific ones get a little more detailed and a little more prescriptive in how you handle that data rather than your overall program. Great. Thank you. And that leads into my next question. I think you you touched on this a little bit. But, can you talk about how, you know, with all these different frameworks that you you, you know, you just went over and, you know, some organizations are dealing with multiples, some are, you know, building up from from one to another. Can you talk about how organizations can effectively integrate their Kooi compliance with, with some of these existing compliance frameworks, you know, like the ISOs, the SOX, etcetera? Sure. Like I said, you have to realize that these are not gonna be soup they're you're gonna have gaps. So you're you can't say because we're ISO twenty seven zero one certified, we we protect KUI. So you're probably gonna get about 80% of the way there. Because I anticipated this question, I went through the one seventy one and the ISO mappings to map them together, and there were about, of of the 320 going to one seventy one a, there were about 60 to 65, no direct mapping. So you're gonna have about 60 to 65 of those 320 that are not gonna be covered by the ISO. So, you know, you want also, you wanna be careful too because, some businesses get in the idea, and I understand why, of saying, well, we're just gonna do everything to one seventy one level for all our data for our entire program, and then we're covered. And and that's why it's, you know, in enticing because you're covered now. The problem is you're gonna spend way too much money on your program. You're gonna break some workflows. You're gonna make your life really difficult to do that. So you really do want to focus it. You wanna have a scope where you say, okay. The Kui is over here. We protect that this way, and then the rest of this stuff, we protect differently in a in a little more easier way that doesn't require as much rigor. Great. And you had, you had mentioned that the, the Farooqooi, rule comment period is coming to an end. I know it ends in a couple weeks on March 17. So what should our audience know leading up to that date? Yeah. So, I mean, usually, we we don't see a lot of public comments on these things, which is disappointing because then after the fact, there's generally after the fact, there's always gonna be a lot of complaining. But there's you know, when you when you got no comments and then you get complaints, it's a little more. But you wanna be careful too. You know? You don't want to go on there and say, you know, my public comment is this is ridiculous, and it's very expensive. And, you know, that's just gonna get discarded. They're not even gonna give it any attention. But you if you say eight hours is ridiculous or eight I wouldn't even use the word ridiculous. Eight hours is challenging, to report an incident when, you know, oftentimes, we're still trying to determine if we even had an incident within eight hours of discovery or something like that. That that has a little more weight. So just make sure your comments are well thought out, articulated. And remember, your goal here is to persuade the reader, the board, to say, well, maybe we did push this a little too far. Maybe we should back it off. Then if if that's your goal. I'm sure they'd be happy to get, you know, a comment that's like, you know, you guys are great. This is perfect. But I I doubt anyone's gonna take the time to do that. Yeah. Not likely. But then again, you know, if you want to, you know, or you want us to say something a little less glowing, we left a a link there in the chat for anyone who does wanna leave a comment before the period is up. Again, that last date will be March 17. So, you know, if you wanna if you want anything to say, you should do it, pretty soon. And let me say, they do read those. They took a lot of that into consideration before they released the CMMC rule just recently. So the actual rule that came out, there were a number of areas that were dialed back from the original rule pre public comment. And you could actually trace them to public comments if you took the time. So, you know, it it does make a difference. So Yeah. Absolutely. We are coming up on the end. Oh, great. Another question. So why is the FAR rule for instant response eight hours while the DFARS, seven or twelve rule is seventy two hours? What is the difference? I wish I could tell you. I don't know. The well, you know, the seventy twelve rule came from 2012, and now it's, you know, 2025. Maybe that's the difference. I don't know. And they just feel like it needs to be faster. It's hard to know. That is the head scratcher that a lot of people are out there wondering about. So, you know, we're gonna have a in in theory, the DFARS rule should be more strict because it's around Department of Defense data that, in theory, has a higher level of confidentiality. But, you know, this this came out that like I said, eight hours just shocked everybody I know, that it was that short a duration. Yeah. Absolutely. Any any additional questions? Final questions, really, before we wrap things up here with Tom? If you have any final questions, please, feel free to leave those in the chat. We'll try to get to them, quickly. Excuse me. If not and, Tom, thank you so much. We appreciate you joining us today. You know, this was very interesting, very insightful learning more about this, the FARS CUI rule. Here's another question here. We can we can keep this going a little bit longer. Question is, what would be your advice for a medium sized business, about 200 employees, that plan to be CMMC certified? For example, separate servers for c for, Kui contracts. And, how about engineering data in, PLM solution that handles both, and not Yeah. So Sounds like bugs. A lot of people, a lot of businesses now are are kind of touting the idea of an enclave, secure enclave for all your query data, which would be the kind of what you're describing. You have your query over here and then your systems that are non query over here. In some cases, that may make sense. A lot of it has to do with the workflow, what what are you doing and how are you doing it. So, for example, if you have a machine shop with a bunch of CNN, c n c machines that are getting fed CUI data to make parts, how do you bifurcate that? I don't I don't know. Can you? And then it's the same sort of deal with the PLM solution. It's, you know, you could have two, one that's more secure and one that's not. But, you know, in general, I think at that point, you're dealing with the system that has to meet CUI standards because it has both. If it has both, it's gonna require that it meet. Great. And, see if say oh, sorry. No. No. Please. Get a yeah. No. You can read that question. I'll just taking an active oversight of COVID audits? I I would say it's it it might happen. I've I've worked on with clients that were under those audits from them. They were interesting. What I was actually surprised that they they didn't level up to the rigor I expected out of them. So that was good, I guess, in the long run for the client. So it's hard for me to foresee anything, honestly. Nothing surprises me anymore. I I do think the people who think that some of this stuff might go away there were a lot of people that with the change of administration in Washington thought, well, maybe this will loosen some of this. And I think if you had any hopes of that, when they made Katie Arrington the CISO of the DOD, those all went away because she's the one who she was on the team that built CMMC from the beginning. She's been a champion of that. So and then, you know, you think about, again, the DOD sits on the board that decides the far regulations. I I wouldn't hold my breath and think anything's backing off. But now, having DCSA oversee it, that could happen. I think that'll happen if the CMMC ecosystem breaks down, and doesn't do its job. But I'd they'd have to expand DCSA so much that I don't know that they could do it. Great. Thank you. I just answered in the chat, but any transcription of the presentation will be will any transcription of the presentation be available, as I said in chat? I believe so. I think with the recording, you can view the transcript as well. If that ends up not being the case, please reach out to us. We can definitely get you one, but, I I do believe, that will be available. Any final questions before we wrap up? No? Alright. Well, in that case, we will end there. Thomas, appreciate your time. Thanks for joining us. This was really great. To our audience, thank you so much. We appreciate the participation. Always enjoy getting some of your questions, so, thank you for that. If you enjoyed this webinar, if you wanna see more, like I mentioned, we have the upcoming CMMC webinar if you wanna learn more about that. We also have an upcoming product launch event. So, providing links to both of those in the chat. Please feel free to join. We'd love to see you at, either one. Until then, thanks again. I hope, this was valuable, for you. And, Thomas, again, appreciate your time. Thanks for joining us, and we'll see you on the next one. Do it. Thanks. Thanks, everyone. Appreciate it.