welcome to Lesson three module to within the attack based stock assessments training course.
In this lesson, we're going to close out the previous lesson by providing a couple of walk through examples of how to analyze different data source strategies
to determine what potential attack coverage they might have.
So kick off this lesson. We're going to start with the following exercise.
We're giving you a kind of informal, freeform paragraph describing a sock that's deploying
a defensive strategy, and your task is to try to figure out what data sources this sock might be keying off of.
So feel free to pause the video, get out a piece of paper and a pad it
trying to think about what data sources this
the sock might be looking at.
So and when you come back and then pause the video, we'll walk through how we look at this and what data sources we think this sock might be able to pick up on.
Okay, we're not gonna walk through our solution, and this is going to follow a similar processes to walk through. Example. In less than 2.2,
we're basically going to take each sentence in the strategy and
decompose it to look at those sentences and figure out what data sources
they might be keying off of,
so to kick it off, the first sentence is that the sock is implementing a multi tiered defensive architecture.
They're going to have Dems galore,
and this is interesting. But from an attack perspective there, there's no real relevant information there.
The next statement is short and simple antivirus. On each end point,
this one's pretty clear. It says it in just right there. Antivirus. That's the attack data source, and so we can immediately add that one to the list now.
There is, of course, some nuance between whether or not they're deploying antivirus or whether or not they're collecting logs from their antivirus.
But for this very informal example, we're going to give the sock the benefit of the doubt and assume that they are indeed collecting those longs as well.
This next sentence is pretty interesting.
A perimeter firewall that's guaranteed to block zero days,
a Web proxy to do deep packet SSL inspection and a next gen detonation chamber that will throw everything into.
There's a lot to unpack there, and when you get to it. There's two big things that stick out.
Ssl slash TLS inspection and then detonation chamber.
Want to bypass our firewall and email us? No way. We're deploying the latest and email Gateway Protection software.
This one's a little bit less common from a data first perspective, but if you kind of go through it, you'll see email. Gateway
is a pretty good attack data source.
This is a fun 11 of our engineers is going to even dockerized power shell to prevent crypto mining.
That's a very fun statement, Um, empowers. You certainly relevant from an attack perspective.
But from a data source strategy perspective there, there's nothing really relevant to key off of there.
Oh, and don't forget our SIM platform. We're forwarding logs from all of our defenses as well as every single packet. Yeah,
all of them into our system.
Our analytics are top notch. There's no way anyone is getting in here.
There's a lot in this statement. Of course, it's a little it's got a little bit of flavor to it,
but really, the key thing is that they're forwarding all of the packets, which which says to us, Hey, that's probably gonna gonna tie into packet capture
and then the last one. Our analytics are top notch. There's no way anyone is getting in here.
This one is, of course, great. It's good to have analytics, But from a data source perspective, we're not really looking at the analytic side yet.
So now, having identified these five data sources, what we can do is kind of put them together and come up with the following heat map
showing all the different techniques that this sock might be able to detect.
And here you can see, it's kind of a little bit of coverage throughout the framework, mainly, just strong under command and control and
maybe a little bit of strength under exfiltration.
So now we're gonna move on to the next exercise. This one is a little bit shorter. It's a little bit maybe more direct.
Um, you know, kind of the same same thing as before. Feel free to pause the video, see what you think. And then when you come back, we'll walk through how we look at this strategy.
Okay. Welcome back. We're not going to walk through it again. It's gonna be the same process as before.
We'll start out with kind of the first statement, We're going to be looking at all the standard stuff Net flows, packet capture, intel feeds you name it.
This is a good statement. Right away. You can see net flows, slash enclave net flow and packet capture. Those stick out.
What's interesting is that, you know, we'd really like to see what the other standard stuff is just because, you know,
they're they're kind of doing and etcetera here by saying you name it, so there could be more there, But just from this statement, we can really only get those two.
is our endpoint in SIM deployment.
This is a good good thing to have. Great to have, you know, endpoint monitoring. Great to have, you know, some deployment, but there's no real data sources highlighted there.
Each endpoint is going to be running in. Sussman pulling an event. I ds 468846574732 and 51 42.
This is a great statement. Um, it's a little confusing just because they do reference like Sussman as well as Windows event ideas, you know, of course, there's
different numbering there. But you know, we can give them the benefit of the doubt. And we can do is say Okay,
these are looking at Windows event logs just because we noticed the event log numbers there. And then when you look up those four event logs, you can find that they match two process monitoring and Windows registry
and then lastly, in case we were breached, we'll also have some disk forensics capabilities. We've gotta crack reverse engineering team to handle any of that tough a PT Malware.
flavorful statement of of this strategy.
And when you look through it, you'll find that that really kind of two things stick out.
Disk forensics actually maps to an attack data source and then malware. Reverse engineering is another potential one.
What's cool is that these data sources now map too much, much, much more coverage.
Now, of course, the sock isn't necessarily going to detect all of these techniques,
but these are the ones that might be visible, given what they're pulling in,
I'd add that you know, a big part of this heat map is really the process monitoring that they're doing
just because they're ingesting all those different, you know, process events. They have the potential to detect a lot. But of course there's always nuanced and what they will detect
in that. You know, it's really the analytics that they deploy to pick up on the anomalous process events.
So just to close out this this lesson one primary kind of summer and take away
analyzing data source strategies can provide insight into sock coverage.
That's really the main lesson learned here. We're kind of closing out the previous lesson as well.
The big thing to take away is that, you know, even just a paragraph of an informal description of what the sock is doing can be enough to help you understand what potential coverage the sock might have.