Hello. My name is the adviser
and welcome to incident response steps.
Hello again. Welcome back to larger to where we're talking about It's your response Steps re laid the groundwork in our last episode together on talked about incident response being a
yes process. We talked about the need to
so that you aren't missing steps so that you have adequate resource is at hand. Whole host of things come into plan in preparation Now, sad to say in, uh, these episodes, we won't be able to dig too far into preparation step
of the incident response process. But you'll hear me bring it up again and again and again because I find it to be the most important step in the entire incident. Response arena s so to speak. And if you don't plan and prepare properly,
you're not going to be able to respond properly.
So I do want to kind of make that clear, because I'm a firm believer in number one here. Feeling to plan is planning to fake those are words to live by in the field in which you're you're either entering or are currently working on. And,
uh, from my own experience in and I did my intro in our last episode together. But I want to tell you I didn't come into this out of the I t world.
Uh, I'm actually rather old,
and I grew up in a world before the, uh when the phone was still attached to the wall. So I had to come into this out from outside the world of I t
*** what I've learned. It's kind of like the picture there, which I love this picture.
Um, because it's kind of like networks and incident response in cyber security in the world today, the sandwich was made.
They realized they needed cheese on the sandwich. So what do you do? Slap it easily outside? It's kind of what the cyber security response has been.
The network's revealed,
um, programs were instituted. Data was aggregated all those good things, and then
they began to realize they needed cyber security and a slap things onto the outside. And unfortunately,
that is the reality of the world, as you'll find it in
the cyber security slash incident response
But you're here, which is great because you want to start doing things the right way, right?
Yes. You don't wanna fail. Nor can we afford to deal with so much data floating around out there on the Internet.
Our job, our responsibility,
is to protect that data. An incident response is one of the first places that this comes into play. One of the most important ones. Actually,
put together a little chore for you here on. As you can see, it's kind of wide ranging, but it should look kind of familiar to you if you saw that one.
So in the broad arena out there in the world, you see the preparations
and again it ISS because when that incident occurs at the bright red explosion, sign all of your preparations going to come into play because you're going to go into the incident response process.
You're gonna make that first step, which is detection and identification. And don't think too far ahead. You're We are going to delve into these steps deeper as we go through our episodes together. But right now it's just an introduction, so to speak.
Then you go to containment,
then hopefully you're able to contain the that actor, the attacker, once they get access to your network
pray that they don't get access. But unfortunately, in today's day and age, there are multiple holes.
Uh, that if you fail to prepare properly, are gonna be there, and the Attackers will find in the mistake about it
on. Then, after your containment, uh, you moved to eradication where you try to get the attacker out of your network. You try to remove their tools. You look for backdoors. It may have been a soldier open and close those shutters down on and hopefully, uh,
out of the network, or at least restricted somewhat in what they can actually do within the network. Now,
in some incidents and some networks environments, there's kind of a running dialogue, a running study as to whether you want to immediately move to containment and eradication, where if you want to allow the attacker,
just think that they that they are on exams and allow them to
do what they came to do on and then hopefully
catch them in the act, so to speak that that is dangerous
on. Unless you guys talk to your team. Unless you've got a lot of preparation in place, you can actually cause yourself a lot more damage. If you allow that kind of thing happen,
then it Finally we move over to recover where trying to get your programs back up, drank its data restored. Say it's a ransom or attack or something like that on get your network back one day to day putting on activity. And then
you've got the aftermath,
which is often times as much of remote, is the preparation stage. But is almost, if not just as important,
do the entire incident response process. Now, there are two major styles
when it comes to answer response. I mentioned this. People work sands in this. These were kind of major ones. There are others like F f I C a p C I. D. S s.
They all deal with incident response. But sands in this kind of break it down and you can see Sands breaks it down into six steps in This breaks down into four.
I can't say I'm a proponent of either one being better than the other one, because, really, they're quite similar to each other. You got preparation, but
detection analysis. You've got under identification percent. Just sort of a
name change really? On, then containment eradication recovery nest
are taken by Sands and broken out into individual steps
which is viable is something to consider.
Ah, and as an incident response player,
you need to be able Thio, identify each of these steps, discuss it
and make recommendations as to whether we should go with Sands with nets. Now, some companies mandate
we are going to use the new standards for all of our processes, procedures, others. They allow the team, the members of the team to make a decision and more democratic manner.
I not sure what you're going to deal with, but
you're going to be a subject matter expert. So you need to know these steps, be able to identify them, articulate them and make recommendations regarding,
uh, moving on. N'est talks about post incident activity,
whereas sands cause it lessens work again. It's a issue of semantics here.
convey the idea that you're trying. They cover the steps that need to be covered.
It just depends on yeah, uh,
the social mei loo in which we're working when it comes to incident response. Really? Um, those are adequate. Are complete.
Both can provide you with what you need in order to conduct good instant response process. Now, this is coming straight from the NIST special Publications. The link there is at the bottom of the screen. It will also be included in the resource is
document with this module.
Now, with preparation again, you want in depth ***.
Um, which is a wide range. We're not going to hit it here.
Are moving into detection analysis again. You need to be able to identify different attack vectors. Be able to identify signs of the pack, Um, in order to respond to them, which is incident responds.
Then you need to move into the next step, which is containment eradication, uncovered about good strategy. Identify different types of threats and attacks and crafted getting coverage plan. And finally, again, your post incident activity, which covers a whole host of areas that we will strike into more in depth.
For now, this is from Sands
pulling out of their documentation. You've got preparation
got identification containment flowing into eradication, blowing into recovery flowing in the lessons learned. Now I kind of have to apologize with multitude collars here, but I kind of hoped that it wakes you up and grabs your attention, Posey n this is sans This is next
only slight variations, only slight differences
You need to make the determination on which one you're going to adopt and stick with it so that you have a good standard on which to rely.
Now, now we've gone over the sands and then this morning, death will continue to go down this learning avenue that we're on, uh,
to learn more about the individual steps. What you can do is an instant response an analyst to institute and work within.