WEBVTT

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


00:00:03.030 --> 00:00:04.030 align:middle line:90%
Hi.

00:00:04.030 --> 00:00:07.830 align:middle line:84%
Welcome to this video
lesson on BloodHound.

00:00:07.830 --> 00:00:10.470 align:middle line:84%
Now we'll begin looking
into different tools that

00:00:10.470 --> 00:00:14.220 align:middle line:84%
can unleash Active Directory
and find misconfigurations which

00:00:14.220 --> 00:00:17.730 align:middle line:84%
we can go and fix before
a potential adversary can

00:00:17.730 --> 00:00:19.500 align:middle line:90%
discover them.

00:00:19.500 --> 00:00:22.200 align:middle line:84%
BloodHound is a
really famous tool

00:00:22.200 --> 00:00:26.640 align:middle line:84%
which can reveal hidden and
often unintended relationships

00:00:26.640 --> 00:00:28.050 align:middle line:90%
in Active Directory.

00:00:28.050 --> 00:00:31.650 align:middle line:84%
And by relationships,
what we really mean is,

00:00:31.650 --> 00:00:37.030 align:middle line:84%
imagine a path where a user
can have forced change password

00:00:37.030 --> 00:00:40.650 align:middle line:84%
to another user who is member
of a privileged group that

00:00:40.650 --> 00:00:42.510 align:middle line:90%
can log into a server.

00:00:42.510 --> 00:00:46.020 align:middle line:84%
The entire chain of
sequence is something

00:00:46.020 --> 00:00:49.170 align:middle line:84%
that BloodHound is really
good at can discover and then

00:00:49.170 --> 00:00:54.760 align:middle line:84%
showcase back to us in a
very easy to understand form.

00:00:54.760 --> 00:00:58.570 align:middle line:84%
With BloodHound we can
go scan our environment

00:00:58.570 --> 00:01:01.840 align:middle line:84%
and identify those
paths because,

00:01:01.840 --> 00:01:05.260 align:middle line:84%
in a large organization it's
very often the case when

00:01:05.260 --> 00:01:08.950 align:middle line:84%
one administrator
might leave delegations

00:01:08.950 --> 00:01:12.070 align:middle line:84%
or add groups to be
members of groups

00:01:12.070 --> 00:01:18.190 align:middle line:84%
to get a very big list of merged
groups or nested membership

00:01:18.190 --> 00:01:21.460 align:middle line:84%
that you completely lose track
of who is a member of what.

00:01:21.460 --> 00:01:25.750 align:middle line:84%
I have seen environments where
the main users in five or six

00:01:25.750 --> 00:01:29.770 align:middle line:84%
layers nested grouping was
member of Domain Admins,

00:01:29.770 --> 00:01:33.400 align:middle line:84%
simply because administrators
had no easy way

00:01:33.400 --> 00:01:37.750 align:middle line:84%
to identify the entire chain,
or follow who is member of what.

00:01:37.750 --> 00:01:39.850 align:middle line:84%
And this is where
BloodHound comes in handy.

00:01:39.850 --> 00:01:41.530 align:middle line:84%
For attackers that
could be great

00:01:41.530 --> 00:01:45.130 align:middle line:84%
because they can see if
a compromised user has

00:01:45.130 --> 00:01:48.340 align:middle line:84%
any rights across the
rest of the network just

00:01:48.340 --> 00:01:49.630 align:middle line:90%
in one simple view.

00:01:49.630 --> 00:01:54.460 align:middle line:84%
While for defenders, they can
go and see those exact paths

00:01:54.460 --> 00:01:55.160 align:middle line:90%
as well.

00:01:55.160 --> 00:01:58.690 align:middle line:84%
But instead of forbidding
them, we can fix them.

00:01:58.690 --> 00:02:01.280 align:middle line:84%
BloodHound consists of
two different parts.

00:02:01.280 --> 00:02:03.250 align:middle line:90%
The first part is an ingestor.

00:02:03.250 --> 00:02:08.500 align:middle line:84%
The ingestor, you would use to
go and scan your environment,

00:02:08.500 --> 00:02:09.910 align:middle line:90%
collect data.

00:02:09.910 --> 00:02:13.370 align:middle line:84%
And that data will contain
a lot of information.

00:02:13.370 --> 00:02:15.190 align:middle line:84%
For example, it will
extract information

00:02:15.190 --> 00:02:21.900 align:middle line:84%
about every group, every user,
the relationship between them,

00:02:21.900 --> 00:02:26.590 align:middle line:84%
what group is a user a
member of, what group

00:02:26.590 --> 00:02:27.950 align:middle line:90%
is a member of another group.

00:02:27.950 --> 00:02:30.010 align:middle line:84%
You have the entire
information of everything

00:02:30.010 --> 00:02:31.240 align:middle line:90%
from Active Directory.

00:02:31.240 --> 00:02:34.120 align:middle line:84%
You'll also see what
access control list

00:02:34.120 --> 00:02:36.010 align:middle line:90%
objects have on each other.

00:02:36.010 --> 00:02:37.900 align:middle line:84%
And one example
would be a group that

00:02:37.900 --> 00:02:39.910 align:middle line:84%
can change passwords
of every user,

00:02:39.910 --> 00:02:43.900 align:middle line:84%
or a group that can write
certain properties of a user,

00:02:43.900 --> 00:02:46.840 align:middle line:84%
or a user who can
read LAPS passwords.

00:02:46.840 --> 00:02:49.270 align:middle line:84%
This can be really, really
many different things.

00:02:49.270 --> 00:02:50.980 align:middle line:84%
And the great thing
about BloodHound

00:02:50.980 --> 00:02:53.200 align:middle line:84%
is that it will
extract all of it--

00:02:53.200 --> 00:02:58.120 align:middle line:84%
will have it in one really
easy overview at the end.

00:02:58.120 --> 00:03:01.990 align:middle line:84%
And the ingestor initially
it was a PowerShell script,

00:03:01.990 --> 00:03:06.110 align:middle line:84%
but performance wise
it was really slow.

00:03:06.110 --> 00:03:09.250 align:middle line:84%
So what the developers did is
they re-implemented the tool

00:03:09.250 --> 00:03:13.450 align:middle line:84%
in C# that significantly
improved the speed of gathering

00:03:13.450 --> 00:03:14.470 align:middle line:90%
this data.

00:03:14.470 --> 00:03:19.600 align:middle line:84%
And the tool rebranded now in
C#, the ingestor part of it,

00:03:19.600 --> 00:03:21.020 align:middle line:90%
is called SharpHound.

00:03:21.020 --> 00:03:23.440 align:middle line:84%
You can download
BloodHound and SharpHound

00:03:23.440 --> 00:03:25.840 align:middle line:84%
from the links which are
provided on the slide

00:03:25.840 --> 00:03:26.680 align:middle line:90%
currently.

00:03:26.680 --> 00:03:27.950 align:middle line:90%
They are free for use.

00:03:27.950 --> 00:03:30.530 align:middle line:90%
They are available on GitHub.

00:03:30.530 --> 00:03:32.780 align:middle line:84%
Now the second
part of BloodHound

00:03:32.780 --> 00:03:36.230 align:middle line:84%
is essentially a
database with a nice GUI.

00:03:36.230 --> 00:03:39.890 align:middle line:84%
And that GUI is the part
which would display back

00:03:39.890 --> 00:03:43.850 align:middle line:84%
to us the results
that were collected.

00:03:43.850 --> 00:03:45.860 align:middle line:84%
Essentially, it's
just a visualization

00:03:45.860 --> 00:03:49.100 align:middle line:84%
of all the relationships
which were discovered.

00:03:49.100 --> 00:03:51.980 align:middle line:84%
And we can also do
custom searches.

00:03:51.980 --> 00:03:54.912 align:middle line:84%
One such example would be if we
take a user in our environment

00:03:54.912 --> 00:03:58.070 align:middle line:84%
called Slavi, and search
if Slavi has a way

00:03:58.070 --> 00:03:59.870 align:middle line:90%
to become Domain Administrator.

00:03:59.870 --> 00:04:03.920 align:middle line:84%
That could be because Slavi
has access to server 01,

00:04:03.920 --> 00:04:06.830 align:middle line:84%
where a domain administrator
is also logged into.

00:04:06.830 --> 00:04:09.350 align:middle line:84%
Then if Slavi logs
into server 01,

00:04:09.350 --> 00:04:12.890 align:middle line:84%
he can perform a credential
theft attack, for example,

00:04:12.890 --> 00:04:16.640 align:middle line:84%
dumping credentials from the
LSASS process and obtaining

00:04:16.640 --> 00:04:19.250 align:middle line:84%
the password or the
password hash of the domain

00:04:19.250 --> 00:04:21.170 align:middle line:84%
administrator account
logged in there.

00:04:21.170 --> 00:04:23.510 align:middle line:84%
Then Slavi can
essentially escalate

00:04:23.510 --> 00:04:26.270 align:middle line:84%
to become a domain administrator
by abusing credential

00:04:26.270 --> 00:04:28.340 align:middle line:84%
theft and the domain
administrator account that's

00:04:28.340 --> 00:04:30.450 align:middle line:90%
logged into the server.

00:04:30.450 --> 00:04:33.070 align:middle line:90%
Now let's take a graphical view.

00:04:33.070 --> 00:04:35.220 align:middle line:84%
We have executed BloodHound
into the environment

00:04:35.220 --> 00:04:37.470 align:middle line:90%
and we extracted all of data.

00:04:37.470 --> 00:04:41.910 align:middle line:84%
What we did a search
of is, can Johnny

00:04:41.910 --> 00:04:44.130 align:middle line:90%
become a domain administrator.

00:04:44.130 --> 00:04:45.920 align:middle line:84%
So what we can see
here in the diagram

00:04:45.920 --> 00:04:51.450 align:middle line:84%
is that Johnny has generic
right access over the account

00:04:51.450 --> 00:04:56.030 align:middle line:90%
exchange ADM, or the EXCH_ADM.

00:04:56.030 --> 00:05:00.860 align:middle line:84%
Generic right access will
give the ability for Johnny

00:05:00.860 --> 00:05:04.950 align:middle line:84%
to change quite a few
properties of EXCH_ADM

00:05:04.950 --> 00:05:06.740 align:middle line:90%
including the password.

00:05:06.740 --> 00:05:08.330 align:middle line:84%
But as an attacker,
you'd probably not

00:05:08.330 --> 00:05:10.430 align:middle line:84%
go over to go and
change their password

00:05:10.430 --> 00:05:13.820 align:middle line:84%
because you'll make a user
aware that something's wrong.

00:05:13.820 --> 00:05:17.450 align:middle line:84%
Another way to approach this is,
Johnny with his generic right

00:05:17.450 --> 00:05:22.880 align:middle line:84%
access can add an SPN value
to the EXCH_ADM account.

00:05:22.880 --> 00:05:25.130 align:middle line:84%
And by doing so,
this account will

00:05:25.130 --> 00:05:28.803 align:middle line:84%
be potentially vulnerable
towards Kerberoasting

00:05:28.803 --> 00:05:30.470 align:middle line:84%
which was one of the
first attacks which

00:05:30.470 --> 00:05:32.550 align:middle line:90%
we discussed in this course.

00:05:32.550 --> 00:05:34.850 align:middle line:84%
So if Kerberoasting
is now in play,

00:05:34.850 --> 00:05:39.710 align:middle line:84%
we can extract a Kerberos
ticket that we can crack offline

00:05:39.710 --> 00:05:42.650 align:middle line:84%
with our password
cracking tools.

00:05:42.650 --> 00:05:46.760 align:middle line:84%
By doing so, if we successfully
crack the password of EXCH_ADM,

00:05:46.760 --> 00:05:49.040 align:middle line:90%
we can log in as that account.

00:05:49.040 --> 00:05:51.680 align:middle line:84%
And then going forward on
the diagram of BloodHound,

00:05:51.680 --> 00:05:55.130 align:middle line:84%
when we have compromised
EXCH_ADM, that account

00:05:55.130 --> 00:05:59.960 align:middle line:90%
is member of SG_AZURESYNC.

00:05:59.960 --> 00:06:04.610 align:middle line:84%
And this group, SG_AZURESYNC
in Active Directory,

00:06:04.610 --> 00:06:07.010 align:middle line:84%
you can actually
see that users are

00:06:07.010 --> 00:06:11.460 align:middle line:84%
shown as a green single
user identity, while groups

00:06:11.460 --> 00:06:15.120 align:middle line:84%
in the diagram are multiple
identities shown in yellow.

00:06:15.120 --> 00:06:17.390 align:middle line:90%
So SG_AZURESYNC is a group.

00:06:17.390 --> 00:06:21.980 align:middle line:84%
And that group has certain
rights on the domain object.

00:06:21.980 --> 00:06:24.710 align:middle line:84%
And these rights will give
the ability for this group

00:06:24.710 --> 00:06:28.430 align:middle line:84%
to add replication changes
permissions to any user

00:06:28.430 --> 00:06:30.000 align:middle line:90%
that this group desires.

00:06:30.000 --> 00:06:32.770 align:middle line:84%
So if Johnny
compromises EXCH_ADM

00:06:32.770 --> 00:06:39.530 align:middle line:84%
through Kerberoasting he can
provide himself the ability

00:06:39.530 --> 00:06:43.475 align:middle line:84%
to perform this sync by
modifying the domain object

00:06:43.475 --> 00:06:44.870 align:middle line:90%
ELS.BANK

00:06:44.870 --> 00:06:46.910 align:middle line:84%
With the [INAUDIBLE]
rights, then

00:06:46.910 --> 00:06:50.774 align:middle line:84%
Johnny can obtain the password
hash of any of the domain

00:06:50.774 --> 00:06:51.732 align:middle line:90%
administrator accounts.

00:06:51.732 --> 00:06:54.140 align:middle line:84%
And in this case,
BloodHound shows

00:06:54.140 --> 00:06:56.030 align:middle line:84%
that one of those
accounts could be,

00:06:56.030 --> 00:06:59.040 align:middle line:84%
as an example, the administrator
account of the domain.

00:06:59.040 --> 00:07:01.610 align:middle line:84%
So essentially, yes,
to answer the question,

00:07:01.610 --> 00:07:05.120 align:middle line:84%
Johnny has a path
to escalate himself

00:07:05.120 --> 00:07:06.770 align:middle line:90%
to domain administrators.

00:07:06.770 --> 00:07:12.170 align:middle line:84%
And that path goes through
changing the password,

00:07:12.170 --> 00:07:14.630 align:middle line:84%
or cracking the
password EXCH_ADM

00:07:14.630 --> 00:07:19.810 align:middle line:84%
and performing certain
changes in ELS.BANK.

00:07:19.810 --> 00:07:22.060 align:middle line:84%
Now let's go into
the environment

00:07:22.060 --> 00:07:25.210 align:middle line:84%
and go through
the entire process

00:07:25.210 --> 00:07:27.505 align:middle line:84%
of executing the
ingestor of BloodHound

00:07:27.505 --> 00:07:30.430 align:middle line:84%
and then analyzing data
so you can get a better

00:07:30.430 --> 00:07:34.320 align:middle line:90%
view of how to use the tool.

00:07:34.320 --> 00:07:36.250 align:middle line:84%
I'm now currently
in the environment,

00:07:36.250 --> 00:07:38.605 align:middle line:84%
and we're going
to simulate that--

00:07:38.605 --> 00:07:41.105 align:middle line:84%
let's say we don't know anything
about this Active Directory

00:07:41.105 --> 00:07:42.240 align:middle line:90%
at all.

00:07:42.240 --> 00:07:46.110 align:middle line:84%
So what we want to do is, from
the perspective of an attacker,

00:07:46.110 --> 00:07:49.390 align:middle line:84%
although we're morally
defending in this case,

00:07:49.390 --> 00:07:51.690 align:middle line:84%
let's just take the
perspective of an attacker.

00:07:51.690 --> 00:07:57.630 align:middle line:84%
Let's compromise this user
called Slavi or just do whoami.

00:07:57.630 --> 00:08:02.160 align:middle line:84%
User Slavi in the domain
production or prod.

00:08:02.160 --> 00:08:04.590 align:middle line:84%
So I went forward and
I downloaded SharpHound

00:08:04.590 --> 00:08:08.250 align:middle line:84%
just so that we don't have to go
through that process together.

00:08:08.250 --> 00:08:10.200 align:middle line:84%
But everything from
now onwards, we'll

00:08:10.200 --> 00:08:12.600 align:middle line:84%
go through and do
it step-by-step.

00:08:12.600 --> 00:08:14.760 align:middle line:84%
So I have downloaded
SharpHound and I'll

00:08:14.760 --> 00:08:19.700 align:middle line:90%
execute it to get a Help menu.

00:08:19.700 --> 00:08:21.740 align:middle line:84%
Now, we're not going
to go through each

00:08:21.740 --> 00:08:23.790 align:middle line:90%
of these different options.

00:08:23.790 --> 00:08:26.480 align:middle line:84%
The one that I really
want to outline

00:08:26.480 --> 00:08:31.520 align:middle line:84%
is the CollectionMethod,
or you can specify just, c.

00:08:31.520 --> 00:08:34.820 align:middle line:84%
The Collection Method
tells SharpHound

00:08:34.820 --> 00:08:38.289 align:middle line:84%
what exactly do we want to
obtain from the Directory.

00:08:38.289 --> 00:08:42.820 align:middle line:84%
And my really common
recommendation

00:08:42.820 --> 00:08:45.340 align:middle line:84%
here is that we should
go for everything.

00:08:45.340 --> 00:08:47.590 align:middle line:84%
We want to obtain
all the information

00:08:47.590 --> 00:08:52.610 align:middle line:84%
that these two can get, because
we want to identify all paths.

00:08:52.610 --> 00:08:55.985 align:middle line:84%
Now, getting this data
and not being stealth--

00:08:55.985 --> 00:08:58.680 align:middle line:90%


00:08:58.680 --> 00:09:00.500 align:middle line:84%
getting this data
and not being stealth

00:09:00.500 --> 00:09:03.410 align:middle line:84%
will produce a lot of
noise into the environment.

00:09:03.410 --> 00:09:06.230 align:middle line:84%
And that's also a good thing
from the defending point

00:09:06.230 --> 00:09:11.240 align:middle line:84%
of view because, if you have
monitoring in your environment

00:09:11.240 --> 00:09:15.650 align:middle line:84%
you will be able to detect
this SharpHound tool requesting

00:09:15.650 --> 00:09:18.230 align:middle line:90%
a lot of LDAP queries.

00:09:18.230 --> 00:09:23.810 align:middle line:84%
One way to detect it is by
using a tool, Azure ATP,

00:09:23.810 --> 00:09:26.240 align:middle line:84%
which we're going to
discuss later in the module.

00:09:26.240 --> 00:09:29.630 align:middle line:84%
Or, you can set up
additional logging

00:09:29.630 --> 00:09:33.080 align:middle line:84%
at the endpoint, which can
detect LDAP queries being

00:09:33.080 --> 00:09:36.740 align:middle line:84%
created from the endpoint
towards some of the servers.

00:09:36.740 --> 00:09:39.470 align:middle line:84%
For example, some of these
queries with SharpHound

00:09:39.470 --> 00:09:43.730 align:middle line:84%
is also going to create our
core members of the group domain

00:09:43.730 --> 00:09:45.020 align:middle line:90%
administrators.

00:09:45.020 --> 00:09:48.563 align:middle line:84%
And that LDAP query is
not normal occurrence,

00:09:48.563 --> 00:09:50.480 align:middle line:84%
or it's not something
normal that you'd expect

00:09:50.480 --> 00:09:52.200 align:middle line:90%
from a endpoint to create.

00:09:52.200 --> 00:09:55.910 align:middle line:84%
If you see someone from an HR
or Marketing department making

00:09:55.910 --> 00:09:59.510 align:middle line:84%
an LDAP query, asking who
is member of domain admins,

00:09:59.510 --> 00:10:01.960 align:middle line:90%
that is really suspicious.

00:10:01.960 --> 00:10:04.550 align:middle line:84%
So we're not really going to
attack anything in this case.

00:10:04.550 --> 00:10:06.873 align:middle line:84%
We'll just go forward
and extract data.

00:10:06.873 --> 00:10:08.290 align:middle line:84%
What we're going
to do is, we will

00:10:08.290 --> 00:10:10.930 align:middle line:84%
specify that we want the
collection method to be All,

00:10:10.930 --> 00:10:13.100 align:middle line:84%
simply because we have
a small environment.

00:10:13.100 --> 00:10:15.148 align:middle line:84%
But in a big
enterprise environment,

00:10:15.148 --> 00:10:16.690 align:middle line:84%
you should specify
collection method,

00:10:16.690 --> 00:10:19.090 align:middle line:84%
All, and separately,
you should also

00:10:19.090 --> 00:10:23.990 align:middle line:84%
define SessionLoop that will
enumerate sessions over time.

00:10:23.990 --> 00:10:27.280 align:middle line:84%
So for example, you can
extract all the data as of now

00:10:27.280 --> 00:10:28.640 align:middle line:90%
at this moment.

00:10:28.640 --> 00:10:33.200 align:middle line:84%
But let the Session
Loop run for another day

00:10:33.200 --> 00:10:35.680 align:middle line:84%
to extract sessions
in different servers

00:10:35.680 --> 00:10:38.080 align:middle line:84%
that users are connecting to
throughout the entire day,

00:10:38.080 --> 00:10:41.660 align:middle line:84%
and not just at that
specific moment.

00:10:41.660 --> 00:10:45.820 align:middle line:84%
So we'll just execute
SharpHound with dash c, All,

00:10:45.820 --> 00:10:47.880 align:middle line:90%
for all collection methods.

00:10:47.880 --> 00:10:52.870 align:middle line:90%
And I'm getting a network error.

00:10:52.870 --> 00:10:56.242 align:middle line:84%
I'll debug the
network right now.

00:10:56.242 --> 00:10:57.700 align:middle line:84%
I'll pause the
video, and then I'll

00:10:57.700 --> 00:11:02.250 align:middle line:84%
resume when I have figured out
what is causing this issue.

00:11:02.250 --> 00:11:05.700 align:middle line:84%
So I looked around and it
seems that there was not really

00:11:05.700 --> 00:11:06.420 align:middle line:90%
any issue.

00:11:06.420 --> 00:11:10.140 align:middle line:84%
At the point, something
was wrong with the DNS.

00:11:10.140 --> 00:11:14.010 align:middle line:84%
But if we run it now,
we'll see that SharpHound

00:11:14.010 --> 00:11:15.750 align:middle line:90%
starts collecting data.

00:11:15.750 --> 00:11:17.720 align:middle line:90%
And it's really that fast.

00:11:17.720 --> 00:11:19.640 align:middle line:90%
All the data is now collected.

00:11:19.640 --> 00:11:22.140 align:middle line:84%
That is because of course, we
have a very small environment.

00:11:22.140 --> 00:11:25.230 align:middle line:84%
If your environment is
10,000 or more objects,

00:11:25.230 --> 00:11:28.350 align:middle line:84%
you would expect it
to take a longer time.

00:11:28.350 --> 00:11:32.070 align:middle line:84%
When BloodHound finishes, it
will create this zip file.

00:11:32.070 --> 00:11:35.340 align:middle line:84%
And this zip file is now
all the extracted data

00:11:35.340 --> 00:11:42.840 align:middle line:84%
that we need to move into the
second tool of BloodHound,

00:11:42.840 --> 00:11:44.850 align:middle line:84%
or the virtualization
side of it.

00:11:44.850 --> 00:11:46.920 align:middle line:84%
This was the ingestor
collecting the data.

00:11:46.920 --> 00:11:50.640 align:middle line:84%
Now we'll move the zip
file into the other tool

00:11:50.640 --> 00:11:52.170 align:middle line:90%
that can visualize it to us.

00:11:52.170 --> 00:11:54.180 align:middle line:84%
I have the second
part of BloodHound

00:11:54.180 --> 00:11:56.290 align:middle line:90%
installed on our Linux machine.

00:11:56.290 --> 00:11:59.143 align:middle line:84%
So I'll switch to the Linux
machine and move the file.

00:11:59.143 --> 00:12:00.810 align:middle line:84%
I'll pause the video
when I'm switching,

00:12:00.810 --> 00:12:05.080 align:middle line:84%
and then resume it when
I'm at the next machine.

00:12:05.080 --> 00:12:05.590 align:middle line:90%
All right.

00:12:05.590 --> 00:12:07.257 align:middle line:84%
Now we're connected
to the Linux machine

00:12:07.257 --> 00:12:09.640 align:middle line:84%
and I have already
started BloodHound.

00:12:09.640 --> 00:12:12.070 align:middle line:84%
This is the GUI and
you're going to become

00:12:12.070 --> 00:12:16.000 align:middle line:84%
very familiar with it once you
start working with the tool

00:12:16.000 --> 00:12:17.080 align:middle line:90%
yourself.

00:12:17.080 --> 00:12:21.500 align:middle line:84%
The first thing we have to
do is go and upload data.

00:12:21.500 --> 00:12:23.320 align:middle line:84%
So we're going to
upload the zip file.

00:12:23.320 --> 00:12:25.630 align:middle line:84%
You had select
just the zip code.

00:12:25.630 --> 00:12:29.560 align:middle line:84%
And the tool automatically unzip
it and take the different text

00:12:29.560 --> 00:12:31.300 align:middle line:90%
documents which were inside.

00:12:31.300 --> 00:12:34.420 align:middle line:84%
So it will go, unzip the
files, process the data

00:12:34.420 --> 00:12:40.060 align:middle line:84%
and then just show us
the output or the summary

00:12:40.060 --> 00:12:41.360 align:middle line:90%
of what it found.

00:12:41.360 --> 00:12:45.490 align:middle line:84%
So there are seven users in our
environment, three computers,

00:12:45.490 --> 00:12:49.360 align:middle line:84%
65 groups, two active
sessions where users

00:12:49.360 --> 00:12:51.340 align:middle line:90%
are logged into computers.

00:12:51.340 --> 00:12:55.270 align:middle line:84%
There are certain access
control lists between objects

00:12:55.270 --> 00:12:57.640 align:middle line:90%
and some relationships.

00:12:57.640 --> 00:13:01.300 align:middle line:84%
We can start and search for
a computer or user in here.

00:13:01.300 --> 00:13:05.470 align:middle line:84%
Or, we can also go into the
Queries section which comes

00:13:05.470 --> 00:13:07.270 align:middle line:90%
with some pre-built queries.

00:13:07.270 --> 00:13:09.610 align:middle line:84%
For example, we
can state or just

00:13:09.610 --> 00:13:12.620 align:middle line:84%
click on the one that says,
Find all Domain Admins.

00:13:12.620 --> 00:13:15.580 align:middle line:84%
And it will visualize
the domain admins group

00:13:15.580 --> 00:13:19.250 align:middle line:84%
to the right, and everyone
who is a member of it.

00:13:19.250 --> 00:13:21.890 align:middle line:84%
So what we're going to see here
is that we have two members.

00:13:21.890 --> 00:13:25.630 align:middle line:84%
One of them is the account
called Administrator, and also

00:13:25.630 --> 00:13:26.930 align:middle line:90%
the domain controller.

00:13:26.930 --> 00:13:28.930 align:middle line:84%
And it's really weird
that the domain controller

00:13:28.930 --> 00:13:30.100 align:middle line:90%
is a member of this group.

00:13:30.100 --> 00:13:31.900 align:middle line:90%
This is not something custom.

00:13:31.900 --> 00:13:34.270 align:middle line:84%
And actually this would
be a misconfiguration

00:13:34.270 --> 00:13:36.520 align:middle line:84%
that we need to look
into and potentially

00:13:36.520 --> 00:13:39.790 align:middle line:84%
mitigate by removing the
domain controller from being

00:13:39.790 --> 00:13:41.830 align:middle line:90%
a member of this group.

00:13:41.830 --> 00:13:46.400 align:middle line:84%
But aside from that, we have
the administrator account,

00:13:46.400 --> 00:13:49.160 align:middle line:90%
which is a domain controller--

00:13:49.160 --> 00:13:52.060 align:middle line:90%
sorry it's domain admin.

00:13:52.060 --> 00:13:55.850 align:middle line:84%
The built in queries can
also identify certain paths.

00:13:55.850 --> 00:13:58.180 align:middle line:84%
So for example, show us
all the different paths

00:13:58.180 --> 00:14:01.480 align:middle line:84%
from user or computer to
become a domain administrator,

00:14:01.480 --> 00:14:04.370 align:middle line:84%
if there's any
relationship between them.

00:14:04.370 --> 00:14:06.940 align:middle line:84%
To use any of these
queries, we can

00:14:06.940 --> 00:14:10.040 align:middle line:84%
specify what edges we
want to be part of that.

00:14:10.040 --> 00:14:11.800 align:middle line:84%
So do we want to
consider the fact

00:14:11.800 --> 00:14:16.330 align:middle line:84%
that the user can RDP to a
server as a jumping spot,

00:14:16.330 --> 00:14:19.560 align:middle line:84%
or BloodHound to detect
that relationship or not?

00:14:19.560 --> 00:14:22.660 align:middle line:84%
In this case, I don't
want to see points

00:14:22.660 --> 00:14:25.520 align:middle line:84%
where a user has the
RDP ability but is not

00:14:25.520 --> 00:14:28.160 align:middle line:84%
a local administrator
of that machine.

00:14:28.160 --> 00:14:30.850 align:middle line:84%
And I want to see all the
different access control

00:14:30.850 --> 00:14:34.105 align:middle line:84%
list edges that BloodHound
can detect, such as as

00:14:34.105 --> 00:14:37.240 align:middle line:90%
the rights, or generic rights.

00:14:37.240 --> 00:14:40.007 align:middle line:84%
If certain users
own objects, that

00:14:40.007 --> 00:14:41.590 align:middle line:84%
is something I would
like to discover.

00:14:41.590 --> 00:14:43.870 align:middle line:84%
Or, if they're member
of-- if they session tool,

00:14:43.870 --> 00:14:46.930 align:middle line:84%
the administrator
tool, and so on.

00:14:46.930 --> 00:14:49.660 align:middle line:84%
I'll let you play with
the different built

00:14:49.660 --> 00:14:53.110 align:middle line:84%
in queries yourself so you can
see how valuable they can be.

00:14:53.110 --> 00:14:54.970 align:middle line:84%
But instead, what
I'm going to do

00:14:54.970 --> 00:14:59.890 align:middle line:84%
is I'll specify a path that
I want to look for myself.

00:14:59.890 --> 00:15:02.740 align:middle line:84%
And the path is, if we could
start from the compromised

00:15:02.740 --> 00:15:07.510 align:middle line:84%
user called Slavi, and
can I use that user

00:15:07.510 --> 00:15:09.370 align:middle line:84%
to become a domain
administrator.

00:15:09.370 --> 00:15:11.120 align:middle line:90%
Is there a path?

00:15:11.120 --> 00:15:13.790 align:middle line:84%
So running that query
returns an output,

00:15:13.790 --> 00:15:18.700 align:middle line:84%
which means that BloodHound
has indeed detected a path.

00:15:18.700 --> 00:15:20.840 align:middle line:90%
So let's look into that.

00:15:20.840 --> 00:15:23.770 align:middle line:84%
What we're going to discover
here is that the account,

00:15:23.770 --> 00:15:29.620 align:middle line:84%
Slavi is administrator to Server
01 where currently the account

00:15:29.620 --> 00:15:32.650 align:middle line:90%
administrator is logged into.

00:15:32.650 --> 00:15:34.510 align:middle line:84%
And the administrator
account is the account

00:15:34.510 --> 00:15:38.990 align:middle line:84%
that we discovered has
domain admin rights.

00:15:38.990 --> 00:15:41.440 align:middle line:84%
So if Slavi, my
compromised user--

00:15:41.440 --> 00:15:44.470 align:middle line:84%
if I could [INAUDIBLE] that
user to go to Server 01,

00:15:44.470 --> 00:15:48.070 align:middle line:84%
I can perform credential
theft and compromise this

00:15:48.070 --> 00:15:50.860 align:middle line:90%
administrator account.

00:15:50.860 --> 00:15:54.640 align:middle line:84%
By doing that, I will
escalate my privileges

00:15:54.640 --> 00:15:56.350 align:middle line:84%
to those of domain
administrator.

00:15:56.350 --> 00:15:58.840 align:middle line:90%


00:15:58.840 --> 00:16:01.340 align:middle line:84%
Now, there is something really
interesting about BloodHound,

00:16:01.340 --> 00:16:03.750 align:middle line:84%
because since it
has all the data

00:16:03.750 --> 00:16:08.030 align:middle line:84%
about all users in all groups
it can also visualize it to us.

00:16:08.030 --> 00:16:13.430 align:middle line:84%
For example, if I press
on the account, Slavi,

00:16:13.430 --> 00:16:16.530 align:middle line:84%
on the left hand side I'll
see all the information

00:16:16.530 --> 00:16:21.080 align:middle line:84%
that BloodHound extracted
about this user.

00:16:21.080 --> 00:16:25.460 align:middle line:84%
And that would include the Sid
value, when the password was

00:16:25.460 --> 00:16:28.640 align:middle line:84%
last changed, when the
user last logged on,

00:16:28.640 --> 00:16:30.500 align:middle line:84%
whether the user is
enabled or disabled,

00:16:30.500 --> 00:16:31.890 align:middle line:90%
the description filed.

00:16:31.890 --> 00:16:33.890 align:middle line:84%
What is interesting here
is that you'll see that

00:16:33.890 --> 00:16:37.707 align:middle line:84%
in the description field,
it contains pass:Welcome1.

00:16:37.707 --> 00:16:39.290 align:middle line:84%
That could potentially
be the password

00:16:39.290 --> 00:16:42.470 align:middle line:84%
of the user which is another
misconfiguration that might

00:16:42.470 --> 00:16:45.350 align:middle line:90%
exist an Active Directory.

00:16:45.350 --> 00:16:47.780 align:middle line:90%
But there's much more than this.

00:16:47.780 --> 00:16:51.590 align:middle line:84%
Because it will also
create a summary

00:16:51.590 --> 00:16:54.800 align:middle line:84%
of the groups that
the user is member of,

00:16:54.800 --> 00:16:57.535 align:middle line:84%
and you can directly
press on this number.

00:16:57.535 --> 00:16:59.160 align:middle line:84%
So you can see that,
for example, Slavi

00:16:59.160 --> 00:17:02.690 align:middle line:84%
is a member of the group
Domain Users directly.

00:17:02.690 --> 00:17:06.390 align:middle line:84%
But indirectly, he's a
member of five groups.

00:17:06.390 --> 00:17:08.180 align:middle line:84%
So if you press
on five, we'll see

00:17:08.180 --> 00:17:11.000 align:middle line:84%
that the direct membership
into Domain Users

00:17:11.000 --> 00:17:14.480 align:middle line:84%
starts to expand into
other groups as well.

00:17:14.480 --> 00:17:19.910 align:middle line:84%
Then the account has local
admin rights into one computer,

00:17:19.910 --> 00:17:23.359 align:middle line:84%
and we can see which
computer that is immediately.

00:17:23.359 --> 00:17:27.020 align:middle line:84%
If we do, Derivative
Local Admin Rights,

00:17:27.020 --> 00:17:30.290 align:middle line:84%
we'll see that there's
a path for this user

00:17:30.290 --> 00:17:34.410 align:middle line:84%
to escalate their privileges to
essentially derive local admin

00:17:34.410 --> 00:17:36.050 align:middle line:90%
rights on three machines.

00:17:36.050 --> 00:17:39.290 align:middle line:84%
And if you remember, the
three machines were--

00:17:39.290 --> 00:17:43.240 align:middle line:84%
all of the machines will
have in our environment.

00:17:43.240 --> 00:17:46.270 align:middle line:84%
And there's much more that
can be shown here, really.

00:17:46.270 --> 00:17:48.160 align:middle line:84%
It's just a matter of
identifying a bigger--

00:17:48.160 --> 00:17:51.170 align:middle line:84%
or having a better environment
to have these populated

00:17:51.170 --> 00:17:54.110 align:middle line:84%
so we can see how
valuable they can be.

00:17:54.110 --> 00:17:55.660 align:middle line:84%
And one thing of
the queries which

00:17:55.660 --> 00:17:58.810 align:middle line:84%
I mentioned before earlier
was that the pre-built ones

00:17:58.810 --> 00:18:01.840 align:middle line:84%
can detect and showcase
quite a few things.

00:18:01.840 --> 00:18:04.120 align:middle line:84%
You can also create
custom queries

00:18:04.120 --> 00:18:06.910 align:middle line:84%
into the language
of this database.

00:18:06.910 --> 00:18:08.890 align:middle line:90%
It's using [INAUDIBLE] backend.

00:18:08.890 --> 00:18:12.820 align:middle line:84%
So if you're more familiar with
the language-- or there is also

00:18:12.820 --> 00:18:16.990 align:middle line:84%
cheat sheets of the
most common queries

00:18:16.990 --> 00:18:19.760 align:middle line:84%
that you can have already
pre-made in a cheat sheet,

00:18:19.760 --> 00:18:22.740 align:middle line:84%
which you can just
plug in using here.

00:18:22.740 --> 00:18:24.945 align:middle line:84%
But if we run the
pre-built one called,

00:18:24.945 --> 00:18:26.820 align:middle line:84%
Find Shortest Path
to Domain Admins,

00:18:26.820 --> 00:18:28.650 align:middle line:84%
it will essentially
identify all paths

00:18:28.650 --> 00:18:34.273 align:middle line:84%
that exist towards domain
admins without a starting point.

00:18:34.273 --> 00:18:35.690 align:middle line:84%
The one that's
interesting here is

00:18:35.690 --> 00:18:39.180 align:middle line:84%
that if we go all
the way to the left,

00:18:39.180 --> 00:18:42.350 align:middle line:84%
we'll see that there's a path
from Slavi, who we already

00:18:42.350 --> 00:18:45.170 align:middle line:84%
discussed earlier,
to the administrator.

00:18:45.170 --> 00:18:47.840 align:middle line:84%
There's also a path
for account operators,

00:18:47.840 --> 00:18:51.320 align:middle line:84%
because account operators
have generic All rights

00:18:51.320 --> 00:18:52.790 align:middle line:90%
on computer objects.

00:18:52.790 --> 00:18:54.720 align:middle line:90%
So a member of this group--

00:18:54.720 --> 00:18:55.970 align:middle line:90%
right now, there's no members.

00:18:55.970 --> 00:18:57.428 align:middle line:84%
If you click on
the group we'll see

00:18:57.428 --> 00:19:00.880 align:middle line:84%
that there's no direct or
indirect members of the group.

00:19:00.880 --> 00:19:03.910 align:middle line:84%
So if there was a member
of this group, who

00:19:03.910 --> 00:19:08.230 align:middle line:84%
he'll have the ability
to alter the computer

00:19:08.230 --> 00:19:10.990 align:middle line:84%
object and escalate
the right domain admin

00:19:10.990 --> 00:19:15.490 align:middle line:84%
again through the same path
that the Slavi user can.

00:19:15.490 --> 00:19:18.340 align:middle line:84%
I really hope that this
short video and demonstration

00:19:18.340 --> 00:19:23.500 align:middle line:84%
of BloodHound can showcase
how valuable this tool can

00:19:23.500 --> 00:19:26.380 align:middle line:84%
be, and not just for attackers
but also for defenders

00:19:26.380 --> 00:19:28.690 align:middle line:84%
to identify these
escalation paths

00:19:28.690 --> 00:19:32.110 align:middle line:90%
and essentially stop them.

00:19:32.110 --> 00:19:33.850 align:middle line:84%
Implement something
that mitigates

00:19:33.850 --> 00:19:36.450 align:middle line:90%
the escalation for these users.

00:19:36.450 --> 00:19:37.320 align:middle line:90%