so kind of moving on from this slide. We have another visual here That kind of lays out that certain team composition again, Depending on your organization. It may or may not very from this, but at the center of that, you're gonna have that team leader.
Uh, then you'll have that incident manager, your forensics person
Local I t support I t administrators. Maybe that your system spans many geographical regions. And then your incident response team members
also kind of included in this incident Response team is going to be a dispatcher and dispatchers air going to essentially man that incident response hot
so they may or may not be actual part of that team. But if you have ah, ticketing system similar to maybe Ark site, they might be the person who receives that initial call and put the ticket in the system that says, Hey, we've had some incidents.
So essentially their responsibilities Heir to receive distress calls from clients are employees and they provide general information about the various incident Response service is
we'll fill out. The reports will essentially assign a tracking numbers, even keep track of that incident, and they'll connect clients with the appropriate incident response team personnel for further assistance. And then typically this function is going to be conducted around a clock. A cz Many organizations have 24 7 up time,
especially if they're large
So kind of another aspect are looking at this incident response,
incident response Totality is the awareness of something occurring.
So that's going to be the first level of incident response that something happened
and that we may or may not know what happened, but we want to know, how do we know that this occurred? And then we're looking for these indicators, so indicators may come in various forms. Could be something from IGs. Maybe you've got a ping or something that someone has tried to
who do something to your network
and you need to go investigate that. Forget exactly what that waas.
Maybe you've had someone who was cruising along the Internet or they've opened up some type of file on their email on all of a sudden, you have this
virus skinner alert pop up and say that your system is either infected and door that your buyer scanner has quarantines,
and that would warrant some type of incident response.
The next indication you might have is a violation of acceptable use policies. So if you're monitoring traffic on your network and you're seeing boys go thio certain websites that they're not supposed to if you see them using a computer for other than its intended purpose.
But that might be something that you want to investigate. Figure up
further what exactly happened, why they're doing what they're doing.
And they also have firewall notifications that something's happening. Are someone's trying to get into your network or something is trying to escape your network. Shouldn't you could also have self reporting. So maybe a user has opened up that email attachment
and they noticed that they're now infected with Ransomware. Or maybe they've lost the laptop with mobile devices connected to you
network, and they're calling the dispatcher to report that.
And then lastly, hopefully this doesn't occur. But it has, in fact, to several organizations is that you get a report on the news that you've been hacked and you don't know about it. Are you having to now respond to this? This reported back in the news so you're definitely behind the power curve,
so moving on after the awareness state essentially have to question that. Now that we know something happened, how do we know?
So we're going to identify what happened. The who? What, When, where? How will we asked ourselves the question. Is this actually an incident?
Often times of this may happen, and they may not may not rise to the level of something being an incident. So does the event violate any principle of that? See a triad of that confidentiality integrity, your availability of data on your network,
and hopefully those things will be laid out in your incident. Response.
Pause. But if not, it's important to ask those questions.
And then what? You determined that it is an incident that it does violate some principle of that CIA triad.
You have to ask yourself how serious of a problem is that incident? So if it's fishing with no data loss, it may just war. Essentially blocking that sender's email address.
AARP. It's Adidas attack that shuts down your network. You're obviously gonna have to spend up a lot more of your incident spots
personnel to essentially deal with that, and you'll probably calling your I S P provided to essentially have some assistance in blocking that large amount of traffic that's coming into your network.
And then, obviously, once you're starting to respond to these incidents, it's important to follow your organizational procedures and policies as required.
So after we've kind of figured out that plan of action, the next thing that we're gonna have to do is to react to that incident. So been reacting to that incident with kind of proven that down into simple, easy to remember
process is the first step that are is to review the policies and procedures. Keep hammering on that
policy and procedures, and that just shows the necessity and the importance of having good policies and procedures in place. So after you've done that, we're going to evaluate the situation determined. Given what we talked about, who, what, when, where, why, how
The next step is to avoid panic so often times with when something happened such a very serious incident. Ah, lot of people want to panic and make rash rash decisions. Eso avoiding panic thinking through the process. Logically, coming up with a good solution
Collecting information is obviously going to help us come up with that solution to the problems, just like G I, Joe said. Knowing is half the battle, the Maur information that you've been collecting them, or information that you know about an incidental help. Taylor that response to the incident.
after you collect that information and you haven't understanding of the exact situation it's occurring. You'll want to take the appropriate action.
But obviously, if you don't follow the aforementioned steps and reviewing your policies and procedures, knowing and understanding the situation, not panicking and not collecting any information about the incident, it's very difficult to come up with the appropriate action and take. So it's very important to follow that react
in that step action that's out.
So looking at the reactor principle a little more in depth.
Don't talk about the first process, which is reviewing the policies and procedures.
So any time that there is an incident,
you want to locate the policy that addresses incident response
and then you wanna look at the incident response procedures.
So in those different procedures,
it should stay what is and what is not allowed. It should kind of get the playbook. Who to call or not to call, especially if you've got a large enterprise. So maybe if you're in the United States, you've got someone in Mongolia. Are you got someone in China?
There may be other individuals that you're gonna have to call in a part of that incident response
plan of reaction. So knowing who to call, knowing what what policies and procedures toe access are very important
on. And then the question is, what if you don't have any incident response policies and procedures? What do you do at that point in time? And who you calling who can make make some type of decision in order to start beginning to work this incident on remediated?