Hello. My name is the adviser.
And welcome to incident response steps
Brief over. You
getting into it here. We're gonna talk about some of the steps involved in the incident response process. But before we get there, let's talk about me.
I don't know about you, but talking about yourselves, never the most comfortable thing in the world to do. But because we are going to be learning together, it helps for you to know a little bit about me. A name? Just a visor on me Day, David. Hey, you or what? Your name doesn't matter. I am currently an instant response engineer in
private industry deal.
In the past, I've been a penetration tester,
and I've conducted malware analysts analysis over the years, but officially and unofficially, I love being outdoors. I love to do things, which is kind of what led me into this field in the first place. Um,
and anyone that's worked in cyber Security or I d is aware of that
I spent in my prior life 10 years is a criminal investigator, which got me into the realm of cyber security cyber crime.
I hunted tal pornographers for a while on and and as the Internet grew and criminals expanding their enterprises, I got into thefts and frauds and investigating, Reaches testified in court.
A multiple level state Opal in federal also
now retired on And I Spent two years, is an instant response consultant
for a managed security service's provider and mess. SP. And I left that field and got into the private industry as its response engineer on. That's a little bit about me. Hopefully, we can learn together as we go on. Cheers. Knowledge.
So what do we want to talk about? Incident. Response?
Um, it's glamorous. It's on build. It's exciting.
But in order to do it properly, you need to have what's known as a plan.
Uh, if you don't have a plan, things can go very much a rock.
Ah, and unfortunately, when I spent time as a cyber security or incident response consultant, I got to see that on many levels in many different industry, that
so hopefully part of what we'll learn. Going through these modules on incident response is
the need for plan. How did to document your plan, how to put it in place I tested and all those happy accompaniments that go along with it. You don't want to be missing step story, and it's in that response. Just do a little bit of reading a little bit of searching out on the Internet.
Read up on some large breaches that occurred,
uh, in which many hind steps were missed
during the response process which led Thio further damage or alleged missed evidence off school.
uh, all kinds of things that can go wrong. So we in this module here are going to take a look at something steps that could help you out in that. Now,
excuse me, As we get through this, you're going to see that there are a lot of resource is out there available. Thio um, there's n'est there. Sands of the f f I C. There's hip, amongst others
but govern and regulate cyber security across a broad range of industries. Our focus just so you're aware will be on this standards and incorporating some of the sands processes as well in order to
but word and gives a practical guidance into how to implement these kinds of
things into your incident response program.
if you, uh
oh are working as a consultant or in a company that's just starting this process. This will hopefully get you started down that road as well.
Now I mentioned before Did you process? It has steps.
This is a little diagram put together from the mist standards to kind of lay that out for you. And this basically follows these four steps preparation,
action and analysis,
containment, eradication and recovery and then post incident activity.
As a consultant, we pushed
the post incident activity
working internally. Oftentimes that post incident activity can be overlooked and it shouldn't be. And I just want to stress that here, you hear me say it again as we get through. Um,
in some cases, these are expanded and set into separate categories, which you get to see is Well, um,
preparation is extremely important. And when I hit that here just shortly as well, because sometimes it's overlooked.
Ah, and preparation leads to a failure in every step after.
This is kind of where the robbers gonna meet the road, eh? So you need to really be prepared. Um
always be systematic and organized across the board. You have to act quickly. Of course, if you have an active intrusion. You don't wantem lurking in your network doing all times of nastiness. Of course, you've got to fix the problem which falls into containment, eradication of recovery and then a worse.
You want to learn from your mistakes or learn from the lessons that you learned Hopefully
not too many mistakes in there and then make improvements on the entire process As you go.
Sands has, uh, connection with the critical security controls, which is a good resource that you couldn't go out to on the Sands website as well, both for preparation and also for working through on. I just pulled a quick screen shot out from your incident response advantage Mint article Night King
in There's Control Siris.
And as you can see, you need a written incident response procedure that is encompassing. You need to have everybody sure of what they're doing. Their jobs, their sign duties, management personnel need to be identified a cz well, and then across the organization.
Aah! These standards need to be in place, trained up
two and then imposed from the top down
in order for them to provide proper and adequate standards that you need in order to conduct a good incident response
you need thio. Make sure that in your preparation you've identified this third party contacts that can help, whether it's an M S, S p, whether it's saying antivirus company, it could be a law enforcement agency, the FBI, our homeland security and here in the United States overseas.
It could be
Interpol or someone like that. Whoever whoever you have contacts with should be clearly identified then that contact information needs to be kept up to date.
Publish it again. Make sure that everybody knows that you haven't answered response plan, conduct at least annual training zone. It's everybody's aware of what they have to do. Unfortunately, AA lot of companies like that slide they look at the bottom line, which is the almighty dollar
here in us again, I could be any
other denominations overseas on. And
unfortunately, cybersecurity sometimes gets the axe instead of the sport in the way that it should be.
And that is just a kn introduction. Clearly steps process that we are going to be going through together. Um, play late. A little bit of a foundation for you here, talking about Mr Sands
profiles for incident response. You could see more of that in Episode two as we move along here. In the process. Have any questions? I am outside Very well for you to reach out to me, baby. 135 Happy to talk to you. Exchange information exchange knowledge. Get contacts extremely important this field. Have a great day talk use.
Kali Linux Fundamentals
If you’re interested in penetration testing and ethical hacking, then this Kali Linux course is ...
1 CEU/CPE Hours Available
Certificate of Completion Offered
Performing Incident Response in a Windows Environment
Take on the role of the lead incident responder on a sysadmin team, and use ...