2 hours 24 minutes
this is module. One lesson to attack. Mapping, process, finding and researching the behavior.
This lesson. We have three objectives
going to discover how to find behaviors. That's step one of the attack mapping process I gave in the previous lesson.
We're going to learn how to research behaviors. That's step two of the mapping process I gave.
And finally, I'm going to go into some narrative reporting so that we can see some example behaviors.
So step one of our process, finding the behavior
you're going to want to look in your reporting for what the adversary or software does during the steps of the compromise.
As you look through your reporting, you're going to want to focus on pre compromise initial compromise and pros compromise details.
So you're going to want to take a look at how the adversary actually behaved through different parts of their intrusion.
So things like how they gained their initial access to a system, how they moved around between systems and how they actually did the compromise of the victim network systems.
Oftentimes, this is going to be verbs
so used create installed
things that are narrative reporting that describe a behavior in things that the adversary actually did.
This isn't going to be absolutely everything. In a report, there's information and reporting that may not be useful for attack mapping
information that doesn't describe details about adversary behavior.
Oftentimes that's found in places like static malware analysis. So talking about hashes or very specific details of how about a piece of Mao was compiled
infrastructure registration information. So what I. P address an adversary used is not going to be an attack behavior
industry victim targeting information.
So the fact that an adversary went after power, utilities or educational institutions
that exact who is the targeting is not a attack behavior.
So let's take an example report. This comes from a fire I report called Operation Double Tap. It's a couple of years old now, but it's still useful for looking at behaviors.
So the first thing we're going to be doing here is starting to look for those verbs looking for those descriptions of the things that the adversary is doing for.
We're talking about successful exploitation
we're talking about, uses the Windows Command command at Eggs E. So I see who am I?
We're talking about creates persistence by creating the following scheduled task
establishes a socks five connection to 192157198.1 oh three
sends the socks five connection request. And so each of these are behaviors. There are things that the adversary is doing,
and they're starting places for us to be able to look for attack tactics and techniques.
Some of these might even be multiple behaviors, at least as we get towards the language of attack.
So we don't just have establishes a connection.
We also have using TCP port. And each of these are things that, as we go through our process, will be able to turn into attack tactics and techniques.
So once we have identified the behaviors we've gone through, we figured out where those verbs are where those things that our adversary actions,
we need to research the behavior we want to understand what is the adversary is doing now? This may be something that you can skip. You can cheat this maybe activity that you already understand. You understand? You know what the adversary was trying to do.
But if there are unfamiliar adversary software behaviors,
you need to get into and look at a little bit more of what the adversary was doing.
So, for example, you may want to examine details about network protocols that were used. Some of attack is leveraging OSC models. So looking at things like application layer
looking at capabilities that things have, uh, what's the assigned port number? Is it a common services in an uncommon service?
What is it normally used for?
Is the adversary going up against a specific tool? So things like samba or remote desktop
as you go through this, collaborate with your own organization? Different people are going to have understanding of different behaviors.
People are just going to have different skill sets
and absolutely leverage external resources. Search engines are your friend.
Understanding core behaviors will help you with these next steps. But not just that. It also enhances analytic skills. It will make you a better analyst.
So let's take a couple of the behaviors we identified in that original report.
We said the adversary used socks proxy.
Okay, so maybe we aren't familiar with socks.
Uh, we google it, we find it in Wikipedia
and we find this information here.
Socks is an Internet protocol.
go through it socks performs layer five of the EC model. The session layer
that's a little bit unusual. So layer five is not a layer that most things run on.
Okay, so we see it's a proxy. We see it's layer five. So we've got at least a little bit more information on what Socks is.
So similarly, we said that they were using Port 1913.
Well, you know, we think we you know, we know ports. We know TCP IP, but
maybe we haven't heard of 1913 before.
So maybe this is not a port that we've come through another analysis
so we can hunt for this as well. So this is a database out there of common ports with different services called speed Guide. We look up Port 1913 and we find that it's for service called arm ADP.
I've never heard of arm ADP and you know, when we created this, I talked to my other instructor, Katy. She had never heard of arm ADP.
And so, you know, this is not this is not a common service. This is not a common port.
And that's going to be useful knowledge for us as we go forward.
So in summary, I've covered a couple of things going through this lesson.
I've talked a little bit about what some of the guidelines are for places where you're likely to be able to do useful mapping and looked at tips for finding behaviors.
I talked about why it's a little bit important to understand these behaviors and and some of how you can start doing research on behaviors themselves.
We also took a look at a narrative report
and some of the behaviors that are coming out of even just a small piece of text.