To Rev 5 & Beyond
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
so welcome to less than 1.6 where we're gonna go from two revision five and beyond. And just talk about the current revision, and then I should look at anything passes you understand how to assess it for your organization.
So for this lesson, we're gonna look at some of the major changes for red five. Describe the reasons why we needed a new revision. Interpret how an organization should implement red five. So just give some high level of idea of how it should be done
and then kind of talk about how we address rapidly changing technology as we've seen, and how this life cycle of the document may not always keep up with the technology.
So think about how much has changed since ready for in 2013. So at this time six years ago, ever since then, everything's connected your refrigerator, your smoke detectors as doorbells. Now everything has an embedded processor. Code is open, sores start moving to virtualization.
And my bullet, I just said, is not already
not up the technology because we started moving away from virtual ization into container, like why do we need virtualized a whole system when I could just spit up a doctor, a doctor instance, And it just does what I want. It's it's up for a couple minutes and then it goes away and, like, How do we
this contract? We take these controls? How do you even apply to assistant? That's Onley online for, say, three minutes. You may be expecting your
ah virtualized instance to come up and install ages to take five or 10 minutes. And if you waited for all that that could, the system would already been offline. So we need to again figure out ways to address this technology. And then, of course, the cloud. And where is your data? Even store? We say it's in.
We have a system. But what does that mean? Is it replicated outside your country?
Does that matter to you?
There's a lot of really going on that needs to be addressed.
Azi mentioned for red five. It's gonna take the privacy controls and said, keeping them separate. They're actually gonna integrate them in because they thought that was important enough.
And they're gonna transition away from information system to system because again, information system doesn't doesn't always make sense. Now. I have this Internet of things device. It doesn't store any data. It just processes it. So is an information system. Not really, because there's no information. It's sending it on somewhere else
on there, also incorporating the cyber security framework, which is a whole nother topic we can't go into. But if you go out and search on that, there's a lot to discuss it now.
So the other topics they incorporated they mentioned is the Internet of things. That's all these diet devices, the camera to smoke detectors, the doorbell, things like that, or but within the organization might be environmental controls any of that
cloud computing mobile devices again, the physical systems. We didn't think about that for the longest for the longest time. That's important. These industrial control systems, these embedded controls or these modules that you may not be able to update. They may not have the security feature that you need, and you have these
requirements that say, you must do this. How do I do this on the system that I can't even update or
performed these functions? How doe I mitigate those controls?
They also wanted you to start relations to look at state of the practice involving threat intelligence like I mentioned before, is what other threats out there specific to my organization and my financial Am I
health care, anything like that? What? What are what are these threats out there? What these threat actors that really are going to infect our sorry affect my system
and then going beyond red five, the in red five and really everyone of the revisions save the controls have been in hands. Sometimes they've withdrawn them something added new ones. They change the supplemental guidance. That language changed a little bit,
they said. There's this couple year life cycle where they're with it, where they come out with a new revision.
Andi, it's difficult. They mentioned to really capture the technology. So what does this say you should do? The best way is to tailor your controls to address the technology. We'll talk a little bit later about it, but they've in all a lot a lot of the controls. There is these organs organization to find variables. What they call it
They give you the chance to say what it means, so they'll give you the framework of it. But allow you to make it specific. So this is
the best way to work on new revisions. Or, I said, within revision changes as well. And miss, give it a
suggested methodology. It's very high level, but they're really when they want to do is say, take a look at the new revision. Are the new controls, they added, applicable to your system? If they are, maybe you want to roll them in or, you know, add some of them without one do you want, or the ones that are that makes sense. Then take a look at the supplemental guidance
changes applicable if they are
decide what is the risk of not including that in there, because there's always the balance of redoing everything. Redoing your accreditation for this new revision isn't worth what you're actually doing. Time in the money you're spending in that. Are you really getting in war Secure system? It's back to their idea about compliance vs
security, which balance and find what's really the best
effort that you're gonna put into securing your system.
And what they suggest is integrate to changes into your continuous monitoring strategy. So maybe you don't have to put it into your document are your security plan. You might not have to actually implement the controls, but you have if you have ah, really good continuous monitoring strategy out there and you have a way of testing the controls implemented into that
and then spend time looking through the revision
to see how it's applicable
claims that there's a lot
to that. It takes two.
Go to a new revision, especially if you're using software for keeping the controls. For a manager of your poems like that, that all that has to be updated.
And then everybody has to understand the new controls. It's a lot to go through.
Module 1 Summary
Module 2 Overview
Anatomy of a Control