Hello, everyone. This is instructor Gerry Roberts, and this is risk policies and security controls.
First of all, what is risk management?
Well, first, a risk is the likelihood of threat will take advantage of a vulnerability.
So that could be I didn't patch my server
and because I didn't patch my server. Maybe a specific port is open and they can go in and take advantage of it. But how likely is that going to be?
A hybrid situation would be that it's extremely likely, and a low risk would mean that it might happen.
Now risk management is the process of working towards minimizing and eliminating those risks.
You can't get rid of all risk, but you can make it better by minimizing them and some risks you can actually eliminate.
Risk management involves many different people in departments,
and it includes physical and technical controls.
The process of risk management can be a long one.
First, we have risk identification.
What happens usually is you monitor for risks and you do some pen testing and other testing to locate those risks and identify them.
I want to have them identified.
You then do an assessment.
Use that information you gathered in the risk identification phase,
see whether it's quite to impact, what kind of potential impact
and what kind of tasks you're gonna need to do, such as deploying a fireball to mitigate that risk
Once the assessment is done, then you take the action that's been agreed upon during the assessment. So say, for example, we said, Let's deploy some firewall rules.
Well, the action phase. We would go ahead and put those rules in place.
Then we would do continuous monitoring, testing
to ensure that the risk is mitigated. We should monitor
and Penn test again to see if we find any new risks or if the risk is still there.
Sometimes we also do what's called regression testing
to make sure that the action we took, such as the firewall rules,
was implemented properly. And it's working,
signing risk management taxed.
So one of the issues with risk management is assigning tasks
now if it requires a specific task to be completed as far as the action that we agree upon during assessment.
So say the firewall.
We have to assign someone the task
this ensures it is completed
because someone is responsible.
If the task is not assigned, it is very likely the actions not gonna be taken.
Now. This responsibility is so important
because if something does happen,
the task was not completed.
And there's an issue. As a result, we can go back to a specific person
and find out what happened.
So in my example here, this is actually something that happened in a company I worked at.
The firewall rule was not implemented and a breach happened.
The person responsible was tracked down and we talked to that person
and they said, Yeah, I try to put the firewall, you know, in and put those rules in.
But then this application we have tohave which is, you know, critical for business stop functioning because it uses one of those ports to function.
So I asked my manager and he said, Go ahead, take the firewall, rule out.
So the action was not completed because the action would have
changed accessibility. And if we remember with C I A accessibility is important.
what we should have done
as we should have gone back to identification and identify that it was still a risk but the action of putting the firewall rule and was not going to work
and then gone through and see if there was a work around for
methodology for dealing with risk.
Now you're not always going to be able to take an action for a risk.
Sometimes you do different things.
But there are four main ways of dealing with risk
elimination and avoidance.
You can eliminate the risk or avoid the risk completely by resolving vulnerability.
This, obviously is the action we really want to take because that means it goes away. We don't have to deal with it,
but the next thing is mitigation.
You mitigate the likelihood of the risk. So you try to minimize the fact that the risk is gonna happen
and you also mitigate any damage. If the risk were to happen,
that could be things like network isolation, where one part of the network is not connected to the other part of the network. So if one parts affected, the other part is not.
This is usually where we kind of live when it comes to risk management,
transferred so we transfer the risks of someone else. For example, we might have an insurance policy that would cover the cost of data recovery,
new equipment, that kind of thing. In the case of a disaster.
Ah, here, Florida. We get a lot of hurricanes. So some places have those special insurance policies that cover hurricanes, which also have to cover flooding because we are in a floodplain and insurance requires additional coverage for flooding
so they might purchase a insurance plan for the hurricane. And then, when the hurricane comes through,
knocks down the data center. There's really nothing we can do other than maybe building a better building. And in some cases that doesn't even work.
So once that happens, they can then call the insurance company. And the cost and the
risk are now put on the insurance company because the insurance company now is liable for that equipment and for that building
acceptance. Now we rarely like to accept a risk, but acceptance means that we accept the risk and deal with it when it happens
again. This is not something we generally like to d'oh
mainly because again, we wanna live up in at least mitigation. If we can't
some things we can't, and that's why we transfer other things we just can't do anything about. And we kind of have to accept the risk and maybe, you know, have a plan for dealing with the damage when it happens.
All right, we're near the end. So it is once again time for a post assessment question.
An example of a risk mitigation might be
markets a UPS or uninterruptible power supply so that servers can be gracefully shut down in a power outage.
Just buys an insurance plan that covers flooding for the Orlando, Florida, location.
A shod patches the server so the new zero day exploit vulnerability is taken care of.
Tia realizes that there's a fire risk in the Australian location, however. Does that buy insurance or fire controls for the company?
Which one of these is an example of risk mitigation?
As always, I'll give you a few moments to figure that out. You can also pause if you would like, and then we will come back to the answer.
Our answer is, a mark gets a ups to the servers can be gracefully Shut down. Now, the UPS isn't gonna prevent the outage, but it will prevent the servers from shutting off during operation.
Now, if you know anything about servers, you know, if they shut off during operation, it is possible toe have data corruption and other damages to those servers.
So he's mitigating that possibility by making sure he can shut them down gracefully.
Now the other options
just buys an insurance plan. An insurance plan is gonna be transferred.
A shod patches a server.
He's eliminating the rest there because it says it took care of it.
The last one. She's ignoring it, so she's just accepting the risk and allowing it to happen.