2.1 Selecting Controls

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

1 hour 45 minutes
Video Transcription
Hi and welcome to risk management framework. This is less than 2.1 where we're going to be selecting our controls.
So the learning objectives of this video, um we're really gonna be interested in what the selection step is and how it fits into RMF. What tasks are associated with the selection step as well as how executive leadership can support the proper selection of controls for their environment,
selecting control. So we're gonna go through the definition here from the Nist sp 837.
The purpose of the select step is to select taylor and document the controls necessary to protect the information system and organization commensurate with risk to organizational operations and assets. Individuals and other organizations and the nation. Uh so obviously this is a really important step, making sure that we understand
which controls are important for our systems.
So why is this important? Again, it's making sure that we're selecting the proper controls because without that we don't know if our systems are secured in the way that they should be. It's really about having that full picture and understanding which ones were selecting and why we're selecting them.
So the selection tasks, uh this includes the actual selection of the controls, tailoring them to your system, depending on what kind of system you have or what kind of operating systems and applications you may have,
making sure that you're allocating them properly,
making sure that you're documenting them the documentation, your plan controls. Obviously hugely important to have that documentation to know why you selected them and which ones you selected.
Again, continuous monitoring strategy that we mentioned before is very important when it comes to selecting these. Uh and then of course plan review and approval.
So what we're talking about control selection, we're talking about a top down approach, making sure that,
you know, based on the inputs and outputs. We're categorizing the system properly using the system inventory and any other contractual requirements from vendors or any applications you might be using to bring that output um that you've selected the proper controls for your system or environment depending on which ones you're looking at.
So the primary contact is gonna be your system owner. They're really ultimately going to be the ones to make sure that the controls are selected properly um with supporting roles by the audio. Maybe some security engineers, privacy officers, anyone who may be able to provide technical input for selecting these controls
quiz. So why should you use a top down approach when selecting controls?
You know, it's important to uh what we spoke about earlier brings security from the top down. That really helps people to understand that security should be first or at least integrated into projects. It helps to make sure that when you're selecting controls, again you're balancing security and functionality. So you're saying yes, we need to be secure. But also I need my I need my system to function properly.
So let's make sure that we're selecting controls and make sure that everyone's involved that needs to be involved.
So tailoring the controls uh So we're going to take the inputs from the initial baselines, any risk assessment results, we might have our system inventory and an impact analysis. We're going to take all of those inputs to hopefully create that list of tailored controls for your system or your environment.
Um And that's really getting that whole view of your system to make sure that
you're tailing the controls to your needs. Again, functionality, insecurity balancing.
Uh So again, your primary contacts can be your system owner, they're going to be really heavily involved in this. Um And again, you're supporting roles will be your a. O any security engineers or privacy offers that again, may be able to add some input and help with selecting some of the technical controls.
Okay, so control allocation,
so we're going to take the inputs again from our security categorization, our enterprise or security architecture, uh any list of common controls that might be inherited from the domain or the network as well as any relevant laws depending on your organization or business.
Um with the expected output of a list of security and privacy controls that are allocated to the system.
So your primary contact is going to be your security or privacy architect or officers. So you're gonna want to make sure that anybody that's very familiar with the overall design or anyone who may be dealing with this operationally can help make sure that the controls are allocated properly.
Um And again, you're supporting roles. You're gonna have your Ci or you're authorizing official your A. O helping in this process.
So documentation. So when we're talking about documentation,
we're going to take the inputs from the security categorization, the risk assessment results, your list of selected controls as well as your risk management strategy. So again, you're gonna be taking all this information and you're going to be putting it out into your security and privacy plans. So you're going to grab all this information and try to create a
a great security plan. That's cohesive.
Again, your primary contact is going to be your system owner with supporting roles with your a o any security or privacy engineers or officers that might need to be involved in getting the documentation right
quiz. Who is the main contact when allocating controls?
Again, this is gonna be your system owner. They're really critical throughout this process and I think it's important to note that you want to make sure that your system owners are aware of their responsibilities when it comes to owning a system and really taking responsibility for that system
so that they understand the risks and are able to secure their systems properly.
Okay, So when we're talking about continuous monitoring or conman,
we're talking about taking inputs from the risk management strategy, the organizational conman strategy, because we're talking about the system level now and it's going to be taken into the system common strategy. So you would want to take any of those, like we're talking about inheriting any of those common strategies that would come from the organizational level and apply them at the system level.
So again, your primary contact is going to be your system owner and you're probably going to need some support from uh your risk management executive, see IO security or privacy architect engineers officers. Um You're continuing continuous monitoring strategy
is going to involve a lot of people and it should so that all the teams can work together and make sure that you're monitoring the right things,
so plan review and approval. So here we're talking about the inputs from previous steps, the security and privacy plans, as well as the results from a system level risk assessment,
so that you can then come out with an approved security and privacy plans, which your primary contact is going to be your ale. They're going to need to be the ones that say yes, I sign off on that weather that Ceo Ceo, anyone in the C suite that might be signing off on this uh with supporting roles from your risk management executive
or a chief acquisition officer they may need to be involved in um If you're looking at getting a new product, buying a new application, they might need to be involved in this step.
Okay, So executive are real.
So what are the main takeaways for executives? You know? Again, we're gonna harp on this, this think about using a top down approach, really think about how this how you can help in this step and how you might want to be involved um And also who you want to have involved
to make sure that they're doing the right thing. So, again, your system owners, they have major responsibilities,
making sure that they understand those responsibilities and what it means to their system. Make sure management involves appropriate people for each task that's going to come up again and again. So making sure you've allocated the right people with the right skills to make sure that the tasks are successful.
All right. So for our video summary today, we talked about what the selection step means to the RMF process. We talked about which task correlate to the selection step,
which groups should be involved in each task, so making sure we've got the right people in the right place,
um and how executive leadership should be involved in the selection process when it comes to controls.
Up Next