Make Defensive Recommendations
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
2 hours 24 minutes
This is module for lesson for make defensive recommendations.
You've got three objectives in this lesson
going to get into some of the different types of defensive recommendations.
Talk a little bit about how to prioritize recommendations, and we're going to have you go through an exercise where you're actually making defensive recommendations.
So we're now at Step five. We're in the homestretch
of actually making defensive recommendations.
So it's important to consider through all of this
that you don't just think about technical. Think about new sensors
that recommendations can be strategic. They can be policy related, operational, tactical
or even making a decision to accept risk.
Who the recommendations are for is going to vary based on your organization's. So it's very important to think about
who is your audience for your recommendations. Is it management? Is your your security operations center? Is that information technology or are you the cyber Threat Intelligence shop and you're making recommendations to all of the above.
So we've gone through a bunch of different defensive options where you're getting them from ways to to take a look at them. Look at some of the pros and cons,
and so some of the potential recommendation types that are coming out of this and may come from your own research.
So the sort of obvious is the technical.
This could be collecting new data source.
Write a detection or an analytic from existing data,
change it configure, make an engineering change
or potentially implementing new tool. And we've talked about a little bit of some specific ways of doing. Each one of those over the course is module.
but there are options definitely beyond the technical.
So there are things like policy changes. Some examples we've gone through in terms of requiring more training are more of a policy change. Or it could be policy change on terms of what's allowed in a given organization.
There's always the possibility that the correct answer is accept risk. So we've determined that a technique is a priority for us.
We've looked at the pros and cons. We've looked at our options, we've weighed them,
and our final answer may be that
it is either undetectable, unmitigated ble or it's not worth the trade off
that all of the options we have on the table are are beyond what we're willing to accept and that we we've decided to accept the risk of that technique happening,
So to give some specific example. So we've We've talked about user execution throughout this. So maybe we we come down to a policy recommendation, so we'll tackle them via user training. You know, we've we've got this highly technical workforce
will work with them, will help make them into better sensors against malicious emails.
But so there are other types of techniques and attack or that may come up in your prioritization. So, for example, if we're working from supply chain compromise and pos boot component firmware,
these can be really hard techniques, really expensive techniques to potentially mitigate and detect.
And so maybe we have stuff that is a priority to us.
But after we take a look, it's beyond our capability or beyond our resources
to stop or detect. And so we have to accept the risk that, you know, we're going to move on with our lives, and it might happen.
So we've given this example. We've gone through and taking a look at user execution.
So we can now take what we've weighed as our pros and cons what we've come up with
of how it works with are given organization. And so these are some of the defensive recommendations we might make from
what we've worked through the rest of the module.
So everything we said around having a technical workforce
is that you know, so one new user training geared around, not clicking on attachments and how to identify social engineering.
There are some downsides in terms of training fatigue, but it looks like this may be very well matched with our organization.
Continued use of antivirus. Why not we? We already have it. It's already there, no additional resource requirements. And so there's there's no reason to stop using anti virus.
And lastly, so we've got this email detonation appliance. Maybe we try to make sure that our email is taking an unencrypted path past it so that we can make use of our existing tools.
These are example recommendations coming out of the pros and cons we've worked up through and the options we've worked through up to this point.
So now it's your turn
in the resources tab
on your exercise. For there should be a text file called making Defensive recommendations guided exercise.
Download this worksheet
and it will walk you through the same recommendation process. We've just done
with some guidance. So instead of asking you to fill in your own organization, it's going to give you some different decision points and suggests some particular places to look
rather than just having sort of full, open scope.
So you're going to be working through this process of determining priority techniques,
researching how the techniques are being used.
Research defensive options related to those techniques.
Research, organizational capabilities and constraints.
Determine what trade offs are for your notional organization on specific options
and then make recommendations based on what you've gathered in that process.
So please pause the video now, and we're just giving yourself 15 minutes for this exercise and when you come back and then pause will go over the exercise.
Okay, So as you went through this exercise,
what resources did you end up using? So we gave some particular suggestions, but were there
others that you decided to pull in other things that you found useful?
What kinds of recommendations did you end up making? Were they technical? Were they policy?
Were they risk acceptance? And did you consider doing nothing and just accepting the risk.
Were there any options that came up as you gathered options here that looked like they would be completely inappropriate for you.
So to start with, uh, step zero determined priority techniques,
we gave you a scheduled task job as the priority technique coming from the same list that we're working with from our threat reporting
Step one. How is that technique being used in the reporting we gave you?
So let's take a look at the Cobalt Kitty report.
So we're seeing it being used coming from a spearfish. Were being seeing it being used from a word macro. And so it's being run on the command line. In both cases,
how did you take a look at data sources? So take a look at some of the defensive options related to the technique or sub technique, so you should have come up with data sources, file monitoring process, command line parameters, process monitoring Windows, event logs,
I said, you take a look at detection,
so this gives you a couple different options of things you might be able to do. Taking a look at scheduled tasks being run.
We gave you some of the organizational capabilities and constraints
just so that you aren't having to take this from your own organization, give you something notional to work with. So for this exercise, we had to assume that you have a Windows event log collection going to assume, but no ability to collect. Process execution. Logging, which will narrow your ability a little bit.
So given where we had you go through and take a look.
These are some of the specific trade offs you might have come up with for your enterprise.
So monitor scheduled task creation from common utilities using command line in vacation
pros might have been would allow us to collect detailed information on how the task is added. It would give us some great visibility,
but we said the organization has no ability to collect process execution. Logging system is probably off the table.
Configure event. Logging for scheduled task creation and changes
fits well into our Windows event. Log collection will get it up to our SIM. Probably be the easiest to implement enterprise wide.
This will increase collected log volumes.
There are the tools that are suggested along the course of the way that may be able to use assist internals. Auto runs will see these scheduled tasks being used.
Uh, some of the pros. This would let us see other persistence techniques as well. So other
ways that things are being added to the system to run at boot
auto runs free.
But it frees not necessarily free. It's not currently installed. You need to be pushed out to all systems, and we need to build up the data collection in analytics around it for it to actually be useful.
Another defensive option that came up was to monitor processing command line arguments
again. This would last collect detailed information,
but we gave us a constraint that the organization has no ability to collect this information.
So we we've guided your path and your steps a little bit where we think you might have come up with a couple of different options that look like this. But you're your answers may differ depending on how you actually reading and processing the information that you're going through.
So we think you might have come up with an option of enabling Microsoft Windows Task Scheduler operational setting within the event logging service and creating analytics around event I. D. One oh six, an event I. D. 1 40.
These are things that come from the defensive options and the detection options that are within the technique and sub technique.
Another option might have come up with is to use auto runs to watch for changes that could be attempts of persistence. Maybe you decided that
the additional logging infrastructure and pulling it together would be worth it, based on the constraints that we gave.
So in this final lesson, we've examined the different types of defensive recommendations
you've looked at, how to prioritize recommendations would you might need to accept risk.
And we've given you some practice making customized defensive recommendations,
considering the elements contributing to your individual approach.
This is now the end of our attack for cyber threat Intelligence Journey
Now work through five different modules, getting into different aspects of first understanding how attack is useful for cyber threat intelligence, how to map narrative and raw data to attack, how to work with that intelligence and then how to do something with that intelligence.
And this is the end of module four and thank you for joining us for this training