WEBVTT

00:00:00.000 --> 00:00:03.220 align:middle line:90%


00:00:03.220 --> 00:00:05.950 align:middle line:84%
Hi Welcome to this
INE Video lesson

00:00:05.950 --> 00:00:08.965 align:middle line:84%
on Device Hardening
and Microsoft Defender

00:00:08.965 --> 00:00:10.960 align:middle line:90%
for Identities.

00:00:10.960 --> 00:00:12.280 align:middle line:90%
The agenda is very short.

00:00:12.280 --> 00:00:14.950 align:middle line:84%
We'll start on a high
level of device hardening,

00:00:14.950 --> 00:00:17.920 align:middle line:84%
since this is not a course
on device hardening,

00:00:17.920 --> 00:00:20.470 align:middle line:84%
we just want to
outline the importance

00:00:20.470 --> 00:00:22.360 align:middle line:90%
of doing this action.

00:00:22.360 --> 00:00:25.060 align:middle line:84%
And then we'll move into
discussing Microsoft Defender

00:00:25.060 --> 00:00:29.725 align:middle line:84%
for identity, which is a tool
that you can install locally

00:00:29.725 --> 00:00:31.840 align:middle line:90%
in your active Directory.

00:00:31.840 --> 00:00:37.120 align:middle line:84%
And that tool has the ability
to detect suspicious activity,

00:00:37.120 --> 00:00:40.330 align:middle line:84%
that may point to
compromised identities

00:00:40.330 --> 00:00:43.690 align:middle line:84%
or any other
reconnaissance attacks that

00:00:43.690 --> 00:00:47.200 align:middle line:84%
are towards the identities
in our active directory.

00:00:47.200 --> 00:00:50.598 align:middle line:84%
Now Device hardening is
a very crucial action

00:00:50.598 --> 00:00:52.390 align:middle line:84%
that we need to perform
in our environment.

00:00:52.390 --> 00:00:56.200 align:middle line:84%
For all of the
different concepts

00:00:56.200 --> 00:00:59.530 align:middle line:84%
that we have discussed
in this, in this course,

00:00:59.530 --> 00:01:04.150 align:middle line:84%
to actually be operational and
to provide the security that

00:01:04.150 --> 00:01:07.770 align:middle line:84%
is required or that to
expect from them [INAUDIBLE]

00:01:07.770 --> 00:01:11.640 align:middle line:84%
To harden our devices
what we really try to do

00:01:11.640 --> 00:01:14.070 align:middle line:84%
is we are limiting all
the unused features

00:01:14.070 --> 00:01:18.180 align:middle line:84%
services and everything else can
just disable on the endpoints,

00:01:18.180 --> 00:01:21.840 align:middle line:84%
that you don't require to limit
the attacks surfaced to them.

00:01:21.840 --> 00:01:26.790 align:middle line:84%
We're trying to really
reduce what can execute--

00:01:26.790 --> 00:01:29.740 align:middle line:84%
especially what is coming from
the internet that can execute.

00:01:29.740 --> 00:01:33.400 align:middle line:84%
So that our employees
are not an easy target.

00:01:33.400 --> 00:01:35.680 align:middle line:90%
So to speak.

00:01:35.680 --> 00:01:37.810 align:middle line:84%
What we want to also achieve
with device hardening

00:01:37.810 --> 00:01:41.530 align:middle line:84%
is to limit the
network boundaries

00:01:41.530 --> 00:01:44.740 align:middle line:84%
and by doing so we can try
to prevent lateral movement

00:01:44.740 --> 00:01:45.860 align:middle line:90%
in the environment.

00:01:45.860 --> 00:01:49.150 align:middle line:84%
So even attacker
had compromised--

00:01:49.150 --> 00:01:52.990 align:middle line:84%
or has credentials, that may
have access to remote machine.

00:01:52.990 --> 00:01:55.660 align:middle line:84%
If we have some
method boundaries

00:01:55.660 --> 00:01:57.390 align:middle line:84%
they might not be
able to reach them,

00:01:57.390 --> 00:02:00.690 align:middle line:84%
to reach the other machine to
use those credentials on them.

00:02:00.690 --> 00:02:03.570 align:middle line:84%
We should also look into
implementing the Disk

00:02:03.570 --> 00:02:06.780 align:middle line:90%
encryption that can prevent--

00:02:06.780 --> 00:02:09.120 align:middle line:84%
stolen devices from
our environment,

00:02:09.120 --> 00:02:12.750 align:middle line:84%
from providing access to
attackers to our environment.

00:02:12.750 --> 00:02:17.310 align:middle line:84%
Or giving attackers information
about our environment. .

00:02:17.310 --> 00:02:21.540 align:middle line:84%
Because if we have the physical
device without Disk encryption,

00:02:21.540 --> 00:02:24.990 align:middle line:84%
it is trivial to
log into that device

00:02:24.990 --> 00:02:27.000 align:middle line:90%
as administrative privileges.

00:02:27.000 --> 00:02:29.850 align:middle line:84%
So all the data which is
local, will most likely

00:02:29.850 --> 00:02:30.960 align:middle line:90%
be compromised.

00:02:30.960 --> 00:02:32.640 align:middle line:84%
And depending on
what VPN solution

00:02:32.640 --> 00:02:36.420 align:middle line:84%
you have towards your network,
if you have one of course.

00:02:36.420 --> 00:02:38.790 align:middle line:84%
That log-in may
allow an attacker

00:02:38.790 --> 00:02:41.550 align:middle line:84%
to get into our network
by stealing device.

00:02:41.550 --> 00:02:44.460 align:middle line:84%
So device encryption is
important to prevent this

00:02:44.460 --> 00:02:48.700 align:middle line:84%
from occurring and depending
on how it's implemented.

00:02:48.700 --> 00:02:53.410 align:middle line:84%
It may or may not allow
for certain access

00:02:53.410 --> 00:02:58.010 align:middle line:84%
to data or to at
least query who is--

00:02:58.010 --> 00:02:59.950 align:middle line:90%
the account in a machine.

00:02:59.950 --> 00:03:02.810 align:middle line:84%
But by having this
encryption you can really

00:03:02.810 --> 00:03:06.440 align:middle line:84%
limit big parts of
the risks, that can--

00:03:06.440 --> 00:03:09.190 align:middle line:84%
that's not having
this encryption

00:03:09.190 --> 00:03:12.270 align:middle line:90%
will bring to the environment.

00:03:12.270 --> 00:03:17.660 align:middle line:84%
But also want to do is to,
install, or to implement,

00:03:17.660 --> 00:03:20.540 align:middle line:84%
enforce application
white listing.

00:03:20.540 --> 00:03:23.740 align:middle line:84%
Which will only allow
software that we are aware of

00:03:23.740 --> 00:03:26.480 align:middle line:84%
or that we want to allow
execution, execution

00:03:26.480 --> 00:03:28.740 align:middle line:90%
of in our environment.

00:03:28.740 --> 00:03:32.290 align:middle line:84%
And finally we need
to focus on logging,

00:03:32.290 --> 00:03:35.850 align:middle line:84%
monitoring and then alerting
of suspicious activity.

00:03:35.850 --> 00:03:38.110 align:middle line:84%
We need to not just
enable default,

00:03:38.110 --> 00:03:40.560 align:middle line:84%
when window slacks have
to go a step further

00:03:40.560 --> 00:03:44.520 align:middle line:84%
and ensure that we have
tools such a Sismon

00:03:44.520 --> 00:03:47.430 align:middle line:84%
or any other logging
capability that you

00:03:47.430 --> 00:03:50.280 align:middle line:84%
can introduce in an environment
because they'll capture locks.

00:03:50.280 --> 00:03:53.970 align:middle line:84%
That will really aid us
into identifying attacks,

00:03:53.970 --> 00:03:58.540 align:middle line:90%
at very early stage executing.

00:03:58.540 --> 00:04:02.560 align:middle line:84%
One way to introduce
or to perform

00:04:02.560 --> 00:04:05.800 align:middle line:84%
hardening is by following
some of the guidelines that

00:04:05.800 --> 00:04:10.180 align:middle line:84%
are out there and the most
famous known guidelines

00:04:10.180 --> 00:04:14.000 align:middle line:84%
are those from CIS and
from Microsoft, which are

00:04:14.000 --> 00:04:15.820 align:middle line:90%
the Microsoft security baseline

00:04:15.820 --> 00:04:19.890 align:middle line:90%
CIS is a complete set it comes--

00:04:19.890 --> 00:04:21.640 align:middle line:84%
of course, you can
purchase it pre-defined

00:04:21.640 --> 00:04:23.140 align:middle line:84%
or you can just get
the free version

00:04:23.140 --> 00:04:26.140 align:middle line:84%
which is a PDF with, all the
settings and the recommended

00:04:26.140 --> 00:04:26.980 align:middle line:90%
values.

00:04:26.980 --> 00:04:29.920 align:middle line:84%
And that PDF is more than 1,000
pages so it's quite massive,

00:04:29.920 --> 00:04:31.210 align:middle line:90%
it's quite descriptive.

00:04:31.210 --> 00:04:34.360 align:middle line:84%
And I urge you to go
in and look into this

00:04:34.360 --> 00:04:37.800 align:middle line:90%
if you haven't done so yet.

00:04:37.800 --> 00:04:41.220 align:middle line:84%
Now let's move into Microsoft
Defender for identity.

00:04:41.220 --> 00:04:43.600 align:middle line:84%
The tool is a cloud
based solution,

00:04:43.600 --> 00:04:49.080 align:middle line:84%
which attempts to
identify any relation

00:04:49.080 --> 00:04:52.455 align:middle line:84%
toward suspicious activity
with produced identities

00:04:52.455 --> 00:04:55.630 align:middle line:84%
send to detect
threats to warn them.

00:04:55.630 --> 00:04:58.530 align:middle line:84%
It can identify
reconnaissance tools

00:04:58.530 --> 00:05:02.880 align:middle line:84%
in our environment such
as, someone executing

00:05:02.880 --> 00:05:05.470 align:middle line:84%
Chuck hunt which is
sent to extracting

00:05:05.470 --> 00:05:07.370 align:middle line:90%
data of Active Directory.

00:05:07.370 --> 00:05:11.040 align:middle line:84%
It can also identify other
threats in the environment,

00:05:11.040 --> 00:05:13.630 align:middle line:84%
because it's creating
profiles for the users.

00:05:13.630 --> 00:05:16.950 align:middle line:84%
So if suddenly an
administrative account

00:05:16.950 --> 00:05:21.000 align:middle line:84%
logs into a server, that,
that has not logged into,

00:05:21.000 --> 00:05:23.550 align:middle line:84%
in the past one year
this tool has the ability

00:05:23.550 --> 00:05:26.610 align:middle line:84%
to detect that and notify
us that, something weird is

00:05:26.610 --> 00:05:29.130 align:middle line:84%
happening, something
that is not aware of.

00:05:29.130 --> 00:05:31.200 align:middle line:84%
And it could be
suspicious so maybe it's

00:05:31.200 --> 00:05:34.240 align:middle line:90%
something we want to look into.

00:05:34.240 --> 00:05:37.600 align:middle line:84%
And because it's looking
to quite a few things

00:05:37.600 --> 00:05:39.010 align:middle line:90%
by creating this profile.

00:05:39.010 --> 00:05:42.730 align:middle line:84%
It can identify attacks in
the entire cyber kill chain

00:05:42.730 --> 00:05:45.380 align:middle line:84%
from the entire, from the
initial reconnaissance

00:05:45.380 --> 00:05:51.790 align:middle line:84%
in the network to using
closed identities to laterally

00:05:51.790 --> 00:05:54.880 align:middle line:84%
move between devices, or
to extract credentials.

00:05:54.880 --> 00:05:57.610 align:middle line:84%
So tools sorry,
attacks such as DC sync

00:05:57.610 --> 00:06:00.220 align:middle line:84%
will also be on the
radar of this tool,

00:06:00.220 --> 00:06:04.210 align:middle line:84%
it will have the
ability to detect them.

00:06:04.210 --> 00:06:07.780 align:middle line:90%
And the tool itself it's--

00:06:07.780 --> 00:06:10.930 align:middle line:84%
a simple installation tool
that you to install locally

00:06:10.930 --> 00:06:14.080 align:middle line:84%
on your environment
you can do it

00:06:14.080 --> 00:06:15.850 align:middle line:84%
on a domain
[INAUDIBLE] controller,

00:06:15.850 --> 00:06:17.770 align:middle line:90%
or on a separate server.

00:06:17.770 --> 00:06:21.670 align:middle line:84%
And what it does is it
collects all the data

00:06:21.670 --> 00:06:23.710 align:middle line:90%
and send it to Azure.

00:06:23.710 --> 00:06:26.860 align:middle line:84%
So Azure is a central
management for this tool where

00:06:26.860 --> 00:06:29.890 align:middle line:84%
you can see all the alerts
and everything, configuration

00:06:29.890 --> 00:06:33.040 align:middle line:90%
wise for the tool itself.

00:06:33.040 --> 00:06:35.530 align:middle line:84%
But I want to do this,
I want to go to Azure

00:06:35.530 --> 00:06:37.810 align:middle line:84%
and I want to show you
the different attacks

00:06:37.810 --> 00:06:41.120 align:middle line:90%
that this tool can detect.

00:06:41.120 --> 00:06:42.860 align:middle line:90%
I have not connected to Azure.

00:06:42.860 --> 00:06:48.212 align:middle line:84%
To access this tool you need
to go to portal.atp.azure.com

00:06:48.212 --> 00:06:50.850 align:middle line:84%
And I have connected
to the tool,

00:06:50.850 --> 00:06:55.430 align:middle line:84%
and what you can see in here is
where my sensor is installed,

00:06:55.430 --> 00:06:58.010 align:middle line:84%
but I can see that it's
installed on a machine called

00:06:58.010 --> 00:07:00.550 align:middle line:90%
this is zero one.

00:07:00.550 --> 00:07:03.730 align:middle line:84%
What I want to do is I'll go
into the exclusion list just

00:07:03.730 --> 00:07:06.490 align:middle line:84%
to show you what
exclusions you can do off

00:07:06.490 --> 00:07:08.890 align:middle line:84%
and that will also list
the different attacks

00:07:08.890 --> 00:07:11.350 align:middle line:90%
that this tool can detect.

00:07:11.350 --> 00:07:16.690 align:middle line:84%
So if you look into here, we'll
see that it can detect overpass

00:07:16.690 --> 00:07:20.380 align:middle line:84%
the hash, NTLM
authentication tampering,

00:07:20.380 --> 00:07:25.180 align:middle line:84%
It can detect DC sync attacks,
it can recall or can also

00:07:25.180 --> 00:07:27.190 align:middle line:84%
detects some type
of reconnaissances

00:07:27.190 --> 00:07:29.740 align:middle line:84%
in the environment remote
codes execution DNS,

00:07:29.740 --> 00:07:32.620 align:middle line:84%
and a large number
of different attacks.

00:07:32.620 --> 00:07:34.413 align:middle line:90%
As well as golden tickets.

00:07:34.413 --> 00:07:36.580 align:middle line:84%
And these are the attacks
that we're discussing also

00:07:36.580 --> 00:07:39.190 align:middle line:90%
in the beginning of the course.

00:07:39.190 --> 00:07:40.840 align:middle line:84%
So having this
tool in the network

00:07:40.840 --> 00:07:43.820 align:middle line:84%
will be really beneficial,
just to listen and try

00:07:43.820 --> 00:07:47.440 align:middle line:84%
to see if it can correlate
anything that is suspicious,

00:07:47.440 --> 00:07:50.410 align:middle line:84%
that points to-- any of
our previous accounts

00:07:50.410 --> 00:07:52.500 align:middle line:90%
being compromised.

00:07:52.500 --> 00:07:53.000 align:middle line:90%