WEBVTT

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


00:00:03.020 --> 00:00:03.690 align:middle line:90%
Hi.

00:00:03.690 --> 00:00:05.780 align:middle line:84%
Welcome to this
video lesson in which

00:00:05.780 --> 00:00:07.580 align:middle line:84%
we're going to be
talking about passwords

00:00:07.580 --> 00:00:10.280 align:middle line:90%
and different password policies.

00:00:10.280 --> 00:00:13.260 align:middle line:84%
Let's begin by
looking at the agenda.

00:00:13.260 --> 00:00:17.510 align:middle line:84%
First, we will look into
general what passwords are

00:00:17.510 --> 00:00:20.210 align:middle line:84%
and common passwords
We'll talk a little bit

00:00:20.210 --> 00:00:22.760 align:middle line:84%
about different password
policies that we can create

00:00:22.760 --> 00:00:24.560 align:middle line:84%
and the ones that
we should definitely

00:00:24.560 --> 00:00:26.150 align:middle line:90%
have in our environment.

00:00:26.150 --> 00:00:29.270 align:middle line:84%
We'll move into fine-grained
password policies

00:00:29.270 --> 00:00:31.460 align:middle line:84%
or how we can
implement, practically,

00:00:31.460 --> 00:00:35.270 align:middle line:84%
the different policies that we
can create in our environment.

00:00:35.270 --> 00:00:37.010 align:middle line:84%
We'll demonstrate
how to create one

00:00:37.010 --> 00:00:39.260 align:middle line:84%
of those fine-grained
password policies.

00:00:39.260 --> 00:00:43.400 align:middle line:84%
Then we will look into a
tool called Get-bADpassword.

00:00:43.400 --> 00:00:48.320 align:middle line:84%
Or B, the naming convention
is rather interesting.

00:00:48.320 --> 00:00:53.450 align:middle line:84%
Which can scan the environment
and showcase weak passwords,

00:00:53.450 --> 00:00:57.350 align:middle line:84%
leaked passwords, and also
users who share passwords,

00:00:57.350 --> 00:01:00.380 align:middle line:84%
and a lot of different
information about passwords.

00:01:00.380 --> 00:01:04.670 align:middle line:84%
And that is purely based on the
password hashes in our AD DS,

00:01:04.670 --> 00:01:06.740 align:middle line:90%
in our Active Directory.

00:01:06.740 --> 00:01:10.590 align:middle line:84%
We'll also demonstrate
how this tool works.

00:01:10.590 --> 00:01:16.370 align:middle line:84%
So let's look at the top
10 passwords for 2020.

00:01:16.370 --> 00:01:18.800 align:middle line:84%
What we can see here
is absolutely shocking

00:01:18.800 --> 00:01:22.100 align:middle line:90%
because we're based in 2020.

00:01:22.100 --> 00:01:24.020 align:middle line:90%
We're at the end of 2020.

00:01:24.020 --> 00:01:26.060 align:middle line:84%
And the most common
passwords haven't really

00:01:26.060 --> 00:01:27.780 align:middle line:90%
changed over the years.

00:01:27.780 --> 00:01:30.830 align:middle line:84%
The most common password
being the numbers,

00:01:30.830 --> 00:01:33.650 align:middle line:90%
sequentially, 1 to 6.

00:01:33.650 --> 00:01:38.600 align:middle line:84%
Well, it's rather crazy that
even passwords that are six

00:01:38.600 --> 00:01:40.340 align:middle line:90%
characters are still allowed.

00:01:40.340 --> 00:01:44.450 align:middle line:84%
And the fact that
it's six characters

00:01:44.450 --> 00:01:47.900 align:middle line:84%
is just crazy because six
characters, breaking it,

00:01:47.900 --> 00:01:49.670 align:middle line:84%
from a password
protection perspective,

00:01:49.670 --> 00:01:52.580 align:middle line:90%
takes a fraction of a second.

00:01:52.580 --> 00:01:55.120 align:middle line:84%
So this list is
really shocking to me

00:01:55.120 --> 00:01:58.600 align:middle line:84%
and we really need to find a
way to move away from this.

00:01:58.600 --> 00:02:00.880 align:middle line:84%
You can see some of
them are numbers.

00:02:00.880 --> 00:02:05.110 align:middle line:84%
The other ones are
only lowercase letters.

00:02:05.110 --> 00:02:08.199 align:middle line:84%
But the important part
here is that they're all

00:02:08.199 --> 00:02:11.370 align:middle line:90%
very short passwords.

00:02:11.370 --> 00:02:15.910 align:middle line:84%
So let's define the
different password types.

00:02:15.910 --> 00:02:17.460 align:middle line:90%
We have weak passwords.

00:02:17.460 --> 00:02:21.930 align:middle line:84%
And that would be a
password that you can guess,

00:02:21.930 --> 00:02:23.760 align:middle line:84%
or it's also a
password that doesn't

00:02:23.760 --> 00:02:25.740 align:middle line:90%
have any complexity enabled.

00:02:25.740 --> 00:02:27.970 align:middle line:84%
As you can see in
the example here.

00:02:27.970 --> 00:02:31.440 align:middle line:84%
We have only a password that's
only a number or only lowercase

00:02:31.440 --> 00:02:32.670 align:middle line:90%
letters.

00:02:32.670 --> 00:02:33.450 align:middle line:90%
There's no mix.

00:02:33.450 --> 00:02:37.310 align:middle line:84%
There's no uppercase,
lowercase, numbers and so on.

00:02:37.310 --> 00:02:40.030 align:middle line:84%
And that brings us to
the next definition

00:02:40.030 --> 00:02:43.420 align:middle line:84%
that a password can actually
be complex but at the same time

00:02:43.420 --> 00:02:44.990 align:middle line:90%
still weak.

00:02:44.990 --> 00:02:48.100 align:middle line:84%
An example of that
is "Password1"

00:02:48.100 --> 00:02:51.190 align:middle line:84%
which contains uppercase
lowercase and a number.

00:02:51.190 --> 00:02:53.020 align:middle line:84%
But again, it's
very easy to guess.

00:02:53.020 --> 00:02:54.460 align:middle line:90%
It's a weak password.

00:02:54.460 --> 00:02:56.830 align:middle line:84%
Same thing with
"Winter2020", that

00:02:56.830 --> 00:02:58.810 align:middle line:84%
would be one of the first
passwords an attacker

00:02:58.810 --> 00:02:59.890 align:middle line:90%
is going to try to guess.

00:02:59.890 --> 00:03:02.230 align:middle line:90%
It exists in every dictionary.

00:03:02.230 --> 00:03:04.430 align:middle line:84%
There's no protection
against these passwords.

00:03:04.430 --> 00:03:06.700 align:middle line:84%
And if you look
into "Winter2020",

00:03:06.700 --> 00:03:08.890 align:middle line:84%
that password is
nine characters.

00:03:08.890 --> 00:03:11.530 align:middle line:84%
It's complex, but
again, it's weak.

00:03:11.530 --> 00:03:13.000 align:middle line:90%
It's guessable.

00:03:13.000 --> 00:03:16.480 align:middle line:84%
So we really need to move
from creating passwords

00:03:16.480 --> 00:03:19.450 align:middle line:90%
into creating password phrases.

00:03:19.450 --> 00:03:23.980 align:middle line:84%
And that is something that
will have increased length

00:03:23.980 --> 00:03:29.880 align:middle line:84%
because more length makes
cracking significantly harder.

00:03:29.880 --> 00:03:33.680 align:middle line:84%
And as an example, I added
a complex phrase in here.

00:03:33.680 --> 00:03:36.860 align:middle line:84%
In which I have uppercase,
lowercase letters, and also

00:03:36.860 --> 00:03:37.790 align:middle line:90%
numbers.

00:03:37.790 --> 00:03:40.850 align:middle line:84%
And the phrase in here is
something that would be easy

00:03:40.850 --> 00:03:42.230 align:middle line:90%
for me to remember.

00:03:42.230 --> 00:03:46.370 align:middle line:84%
And I don't need to put
effort into coming up

00:03:46.370 --> 00:03:48.530 align:middle line:90%
with something that is random.

00:03:48.530 --> 00:03:50.510 align:middle line:84%
So coming up with a
phrase of something common

00:03:50.510 --> 00:03:52.730 align:middle line:84%
in your daily life
could actually

00:03:52.730 --> 00:03:54.800 align:middle line:84%
be much better than
creating a password, which

00:03:54.800 --> 00:03:56.120 align:middle line:90%
is just "password".

00:03:56.120 --> 00:03:56.780 align:middle line:90%
Right?

00:03:56.780 --> 00:03:59.330 align:middle line:84%
So in this example, I have
given a password, which

00:03:59.330 --> 00:04:02.540 align:middle line:90%
is "DailyCoffee4EarlYbirdz".

00:04:02.540 --> 00:04:04.910 align:middle line:84%
And if you're a
coffee person this

00:04:04.910 --> 00:04:06.800 align:middle line:84%
could be just a great
password for you.

00:04:06.800 --> 00:04:09.650 align:middle line:84%
And of course, you like
waking up in the morning.

00:04:09.650 --> 00:04:13.610 align:middle line:84%
But the idea here is that it's
easy to remember, the phrase.

00:04:13.610 --> 00:04:16.140 align:middle line:90%
It's long and it's even complex.

00:04:16.140 --> 00:04:17.990 align:middle line:84%
And when we talk
about long passwords.

00:04:17.990 --> 00:04:19.700 align:middle line:90%
Complex is not necessary.

00:04:19.700 --> 00:04:22.710 align:middle line:90%
It's just good to have.

00:04:22.710 --> 00:04:27.170 align:middle line:84%
So our goal is to
get users to think

00:04:27.170 --> 00:04:33.440 align:middle line:84%
into creating a passphrase
compared to having a password.

00:04:33.440 --> 00:04:38.030 align:middle line:84%
And we have really failed to
ensure that our users have

00:04:38.030 --> 00:04:39.260 align:middle line:90%
good passwords.

00:04:39.260 --> 00:04:42.860 align:middle line:84%
So passphrase is
really the way forward.

00:04:42.860 --> 00:04:45.680 align:middle line:84%
Now why are we talking
about policies?

00:04:45.680 --> 00:04:47.790 align:middle line:84%
Is there something
much more here?

00:04:47.790 --> 00:04:50.240 align:middle line:84%
Well yes, because we
have different users

00:04:50.240 --> 00:04:51.050 align:middle line:90%
in our environment.

00:04:51.050 --> 00:04:53.750 align:middle line:84%
And we need to
categorize those users

00:04:53.750 --> 00:04:56.120 align:middle line:84%
and create different
policies based

00:04:56.120 --> 00:05:00.440 align:middle line:84%
on what these users have access
to or what they can manage.

00:05:00.440 --> 00:05:02.540 align:middle line:84%
So regular users
are the first group.

00:05:02.540 --> 00:05:06.020 align:middle line:84%
That will be the most normal
employees with normal accounts

00:05:06.020 --> 00:05:07.580 align:middle line:90%
with no privileges at all.

00:05:07.580 --> 00:05:11.000 align:middle line:84%
They only have access to email,
to their workstations, and very

00:05:11.000 --> 00:05:12.590 align:middle line:84%
few business
applications, that they

00:05:12.590 --> 00:05:16.430 align:middle line:90%
need to work during the day.

00:05:16.430 --> 00:05:20.240 align:middle line:84%
So an example password policy
in here is shown on the slide

00:05:20.240 --> 00:05:21.380 align:middle line:90%
currently.

00:05:21.380 --> 00:05:23.630 align:middle line:84%
Where we define that,
we want to remember

00:05:23.630 --> 00:05:26.150 align:middle line:90%
24 the previous passwords.

00:05:26.150 --> 00:05:30.210 align:middle line:84%
And the choice of 24 here is
because this is the maximum.

00:05:30.210 --> 00:05:32.960 align:middle line:84%
We don't want users to
repeat the same password.

00:05:32.960 --> 00:05:37.640 align:middle line:84%
Then we have increased the
password age to 180 days,

00:05:37.640 --> 00:05:43.080 align:middle line:84%
as opposed to the 90 days which
used to exist in the old audit

00:05:43.080 --> 00:05:43.580 align:middle line:90%
scripts.

00:05:43.580 --> 00:05:46.580 align:middle line:84%
And audit companies
were checking for that.

00:05:46.580 --> 00:05:49.700 align:middle line:84%
There really isn't any need to
change your password every 90

00:05:49.700 --> 00:05:53.030 align:middle line:90%
days, maybe not even 180 days.

00:05:53.030 --> 00:05:57.560 align:middle line:84%
Maybe 360 days, once a year,
would be a good indication.

00:05:57.560 --> 00:05:59.780 align:middle line:84%
Once we come at the
point where we're

00:05:59.780 --> 00:06:03.290 align:middle line:84%
looking into pass phrases,
unless there's a reason

00:06:03.290 --> 00:06:05.240 align:middle line:84%
to believe that the
password is compromised,

00:06:05.240 --> 00:06:08.780 align:middle line:84%
there should really be no reason
for changing that password.

00:06:08.780 --> 00:06:11.000 align:middle line:84%
So increasing the
password age, not

00:06:11.000 --> 00:06:12.980 align:middle line:84%
making it an infinite
as some companies

00:06:12.980 --> 00:06:18.350 align:middle line:84%
have recommended recently,
but expanding this,

00:06:18.350 --> 00:06:21.650 align:middle line:84%
giving some buffer
space for users,

00:06:21.650 --> 00:06:25.640 align:middle line:84%
because we're increasing their
complexity and length so we

00:06:25.640 --> 00:06:28.878 align:middle line:84%
can actually increase
the days for which they

00:06:28.878 --> 00:06:30.170 align:middle line:90%
have to remember that password.

00:06:30.170 --> 00:06:33.110 align:middle line:84%
It's a good trade-off for us,
as security professionals,

00:06:33.110 --> 00:06:35.900 align:middle line:84%
but also for the users as
well that they don't have

00:06:35.900 --> 00:06:38.060 align:middle line:90%
to change the password at all.

00:06:38.060 --> 00:06:40.760 align:middle line:84%
What we have also defined here
is the minimum password age

00:06:40.760 --> 00:06:41.800 align:middle line:90%
of 1 day.

00:06:41.800 --> 00:06:46.260 align:middle line:84%
The reason why we define this is
because if this is not defined,

00:06:46.260 --> 00:06:50.810 align:middle line:84%
a user will be able to go and
change their password 24 times

00:06:50.810 --> 00:06:54.015 align:middle line:84%
consecutively, in 24
seconds, and they'll

00:06:54.015 --> 00:06:55.640 align:middle line:84%
end up with the same
password that they

00:06:55.640 --> 00:06:57.470 align:middle line:90%
used to have before that.

00:06:57.470 --> 00:06:59.540 align:middle line:84%
And we don't want
passwords to be repeated.

00:06:59.540 --> 00:07:03.230 align:middle line:84%
With having 1-day
password minimum age

00:07:03.230 --> 00:07:06.920 align:middle line:84%
we really prevent a user
having the same password again.

00:07:06.920 --> 00:07:08.780 align:middle line:84%
Unless they change their
password every day,

00:07:08.780 --> 00:07:12.530 align:middle line:84%
but that would be
just absolutely crazy.

00:07:12.530 --> 00:07:14.570 align:middle line:84%
And even if they
were doing that,

00:07:14.570 --> 00:07:18.260 align:middle line:84%
the password would still
be a massive passphrase

00:07:18.260 --> 00:07:19.940 align:middle line:84%
that they would
hopefully create.

00:07:19.940 --> 00:07:22.220 align:middle line:84%
We also said the
minimum password length

00:07:22.220 --> 00:07:23.940 align:middle line:90%
of 14 characters.

00:07:23.940 --> 00:07:27.770 align:middle line:84%
And 14 is a really good
number here because it

00:07:27.770 --> 00:07:31.010 align:middle line:84%
will, just by default, get rid
of all these weak passwords,

00:07:31.010 --> 00:07:34.970 align:middle line:84%
such as Password1,
summer2020, Winter2020.

00:07:34.970 --> 00:07:37.640 align:middle line:84%
A user will not have the
ability to set those passwords.

00:07:37.640 --> 00:07:39.200 align:middle line:90%
So they need to think big.

00:07:39.200 --> 00:07:43.190 align:middle line:84%
Of course they have the
option to do summer20202020

00:07:43.190 --> 00:07:47.300 align:middle line:84%
or summersummer2020,
but we will have this,

00:07:47.300 --> 00:07:50.330 align:middle line:84%
you'll see in a little bit,
ability to actually take

00:07:50.330 --> 00:07:53.840 align:middle line:84%
these passwords and either force
users to change their passwords

00:07:53.840 --> 00:07:57.290 align:middle line:84%
again, or at least
notify them that,

00:07:57.290 --> 00:08:01.250 align:middle line:84%
give them a crash course on
how to create a passphrase.

00:08:01.250 --> 00:08:04.010 align:middle line:84%
And you have the
knowledge that users

00:08:04.010 --> 00:08:05.780 align:middle line:90%
will have these bad passwords.

00:08:05.780 --> 00:08:09.590 align:middle line:84%
And the amount of them is going
to be significantly less, as

00:08:09.590 --> 00:08:12.080 align:middle line:84%
opposed to having a
password policy which

00:08:12.080 --> 00:08:14.490 align:middle line:90%
is eight characters.

00:08:14.490 --> 00:08:17.250 align:middle line:84%
In this password policy we will
also enable the complexity.

00:08:17.250 --> 00:08:21.330 align:middle line:84%
And we do not store passwords
with reversible encryption.

00:08:21.330 --> 00:08:23.133 align:middle line:84%
We want to store only
the password hash.

00:08:23.133 --> 00:08:25.050 align:middle line:84%
Of course, we don't want
to be able to reverse

00:08:25.050 --> 00:08:28.590 align:middle line:84%
the original
password of the user.

00:08:28.590 --> 00:08:31.260 align:middle line:84%
So that brings us
to the next policy

00:08:31.260 --> 00:08:33.539 align:middle line:84%
and that would be
administrative accounts.

00:08:33.539 --> 00:08:35.880 align:middle line:84%
Should administrative
accounts have the same policy

00:08:35.880 --> 00:08:37.320 align:middle line:90%
as regular users?

00:08:37.320 --> 00:08:39.929 align:middle line:84%
I mean, by definition
this doesn't make sense,

00:08:39.929 --> 00:08:42.840 align:middle line:84%
because regular users are
not administrative accounts

00:08:42.840 --> 00:08:45.900 align:middle line:84%
and administrative accounts
have way more access.

00:08:45.900 --> 00:08:48.930 align:middle line:84%
Some of them will have complete
access for our environment.

00:08:48.930 --> 00:08:51.780 align:middle line:84%
We need to protect
these accounts better.

00:08:51.780 --> 00:08:54.970 align:middle line:84%
And one way to do it is to
have a different password

00:08:54.970 --> 00:08:59.100 align:middle line:84%
policy for them and require
them to have a password length

00:08:59.100 --> 00:09:01.530 align:middle line:90%
of at least 20 characters.

00:09:01.530 --> 00:09:04.750 align:middle line:84%
Then we'll have a service
accounts in our environment.

00:09:04.750 --> 00:09:08.190 align:middle line:84%
So should we have these special
policies for service accounts?

00:09:08.190 --> 00:09:09.810 align:middle line:84%
Should they apply
it as they are?

00:09:09.810 --> 00:09:11.040 align:middle line:90%
Well, not really.

00:09:11.040 --> 00:09:13.497 align:middle line:84%
The thing about service
accounts is that, first of all,

00:09:13.497 --> 00:09:15.330 align:middle line:84%
if you can use group
Managed Service Account

00:09:15.330 --> 00:09:16.372 align:middle line:90%
you should totally do it.

00:09:16.372 --> 00:09:19.260 align:middle line:84%
The password is meant
going to be 127 characters.

00:09:19.260 --> 00:09:20.260 align:middle line:90%
It's going to be random.

00:09:20.260 --> 00:09:23.685 align:middle line:84%
And it's going to
be changed regularly

00:09:23.685 --> 00:09:24.810 align:middle line:90%
by Active Directory itself.

00:09:24.810 --> 00:09:27.573 align:middle line:84%
So if you need to
create an account

00:09:27.573 --> 00:09:30.240 align:middle line:84%
to start a service, which is not
supported group Managed Service

00:09:30.240 --> 00:09:34.050 align:middle line:84%
Account, and we need to
create our normal service user

00:09:34.050 --> 00:09:37.800 align:middle line:84%
accounts, then the
password of these accounts,

00:09:37.800 --> 00:09:40.410 align:middle line:84%
we should really increase
it significantly.

00:09:40.410 --> 00:09:44.220 align:middle line:84%
Because in most cases, this is
a password which you enter once

00:09:44.220 --> 00:09:47.370 align:middle line:84%
and you don't have to
ever use it again, nearly,

00:09:47.370 --> 00:09:48.630 align:middle line:90%
in your lifetime.

00:09:48.630 --> 00:09:52.860 align:middle line:84%
Or in the lifetime of
rotating service account

00:09:52.860 --> 00:09:56.670 align:middle line:84%
passwords, which might be a
year or two years in the future.

00:09:56.670 --> 00:09:59.142 align:middle line:84%
It's not something that
you'll be typing every day.

00:09:59.142 --> 00:10:00.600 align:middle line:84%
So the recommendation
here would be

00:10:00.600 --> 00:10:02.730 align:middle line:84%
that you need to set
a password, which is

00:10:02.730 --> 00:10:05.100 align:middle line:90%
at least 100 characters long.

00:10:05.100 --> 00:10:07.860 align:middle line:84%
The maximum password which
can have in active directory

00:10:07.860 --> 00:10:10.140 align:middle line:90%
is 127 characters.

00:10:10.140 --> 00:10:14.940 align:middle line:84%
So I'm leaving you a buffer
zone between 100 and 127

00:10:14.940 --> 00:10:18.490 align:middle line:84%
so you can choose the
exact length yourself.

00:10:18.490 --> 00:10:20.760 align:middle line:84%
And in that way we
don't have an attack

00:10:20.760 --> 00:10:23.670 align:middle line:84%
that you have a password
length of certain size.

00:10:23.670 --> 00:10:27.030 align:middle line:84%
If I tell you that your password
length should be 100 exactly,

00:10:27.030 --> 00:10:31.140 align:middle line:84%
then attackers will be cracking
passwords exactly 100 size.

00:10:31.140 --> 00:10:35.610 align:middle line:84%
While that might be impractical,
they might still try to do it.

00:10:35.610 --> 00:10:39.813 align:middle line:84%
And that is impractical with
the current computing power

00:10:39.813 --> 00:10:41.480 align:middle line:84%
but it might be
practical in the future.

00:10:41.480 --> 00:10:42.360 align:middle line:90%
You never know.

00:10:42.360 --> 00:10:45.420 align:middle line:84%
Although it sounds crazy if you
look into the cryptography part

00:10:45.420 --> 00:10:46.840 align:middle line:90%
of that.

00:10:46.840 --> 00:10:48.900 align:middle line:84%
Now there is an issue
with service accounts

00:10:48.900 --> 00:10:52.020 align:middle line:84%
in hundreds or more characters
passwords, because some of them

00:10:52.020 --> 00:10:55.860 align:middle line:84%
are used in services
which do not support,

00:10:55.860 --> 00:10:58.530 align:middle line:84%
themselves, that
long a password.

00:10:58.530 --> 00:11:00.360 align:middle line:84%
And in that case,
I would normally

00:11:00.360 --> 00:11:04.620 align:middle line:84%
suggest that you can have a
second service account password

00:11:04.620 --> 00:11:07.110 align:middle line:90%
policy which is 32 characters.

00:11:07.110 --> 00:11:09.360 align:middle line:84%
So you default for
hundreds or more.

00:11:09.360 --> 00:11:11.963 align:middle line:84%
If you need a service
account for services

00:11:11.963 --> 00:11:14.130 align:middle line:84%
that doesn't support the
hundreds or more characters

00:11:14.130 --> 00:11:19.570 align:middle line:84%
password then you can
create it with 32 or more,

00:11:19.570 --> 00:11:22.200 align:middle line:84%
depending on what
the service supports.

00:11:22.200 --> 00:11:25.620 align:middle line:84%
Then we can also have different
password policies for VIP,

00:11:25.620 --> 00:11:27.630 align:middle line:90%
management, executives.

00:11:27.630 --> 00:11:30.380 align:middle line:84%
It depends on your
own organization,

00:11:30.380 --> 00:11:33.418 align:middle line:90%
how you want to approach this.

00:11:33.418 --> 00:11:35.460 align:middle line:84%
Usually, I would recommend
at least 20 characters

00:11:35.460 --> 00:11:38.100 align:middle line:84%
for these accounts as well,
similar to the administrative

00:11:38.100 --> 00:11:41.578 align:middle line:84%
accounts So this is a
different password policy

00:11:41.578 --> 00:11:42.370 align:middle line:90%
that we can create.

00:11:42.370 --> 00:11:44.710 align:middle line:84%
And you can expand the
list as much as you want,

00:11:44.710 --> 00:11:47.050 align:middle line:84%
but these are the ones
that you really have

00:11:47.050 --> 00:11:50.010 align:middle line:90%
to have in your environment.

00:11:50.010 --> 00:11:52.340 align:middle line:84%
Now fine-grained
password policies,

00:11:52.340 --> 00:11:55.590 align:middle line:84%
it's a way to create
multiple password policies

00:11:55.590 --> 00:11:57.890 align:middle line:90%
within the same domain.

00:11:57.890 --> 00:12:02.600 align:middle line:84%
And it's really unique because
they will be independent.

00:12:02.600 --> 00:12:04.820 align:middle line:84%
And the way that you
distribute them is you

00:12:04.820 --> 00:12:08.420 align:middle line:84%
send them to a group
interactive directory.

00:12:08.420 --> 00:12:11.330 align:middle line:84%
So as long as a user
is a member of a group

00:12:11.330 --> 00:12:14.330 align:middle line:84%
they will inherit
this password policy

00:12:14.330 --> 00:12:17.470 align:middle line:90%
that the group is applied to.

00:12:17.470 --> 00:12:20.650 align:middle line:84%
One caveat with this
is that it can only

00:12:20.650 --> 00:12:22.430 align:middle line:90%
be applied to global groups.

00:12:22.430 --> 00:12:28.750 align:middle line:84%
So you cannot use it for local
domain groups for example.

00:12:28.750 --> 00:12:31.690 align:middle line:84%
Now let's move into the
environment and, as an example,

00:12:31.690 --> 00:12:34.990 align:middle line:84%
just create a fine-grained
password policy

00:12:34.990 --> 00:12:37.770 align:middle line:90%
for administrative accounts.

00:12:37.770 --> 00:12:40.570 align:middle line:84%
Now I'm connected to
our domain controller.

00:12:40.570 --> 00:12:45.940 align:middle line:84%
So I will start Active
Directory Administrative Center.

00:12:45.940 --> 00:12:48.370 align:middle line:84%
Which is where we can create
these fine-grained password

00:12:48.370 --> 00:12:49.653 align:middle line:90%
policies.

00:12:49.653 --> 00:12:51.070 align:middle line:84%
It's important to
mention that you

00:12:51.070 --> 00:12:53.050 align:middle line:84%
need to have
administrative access to be

00:12:53.050 --> 00:12:55.670 align:middle line:90%
able to modify these values.

00:12:55.670 --> 00:12:57.430 align:middle line:84%
So I switched into
tree view just

00:12:57.430 --> 00:13:01.030 align:middle line:84%
because I find it
slightly better

00:13:01.030 --> 00:13:03.160 align:middle line:90%
for me to follow on the screen.

00:13:03.160 --> 00:13:09.160 align:middle line:84%
And we need to go into
System and Password Settings

00:13:09.160 --> 00:13:10.720 align:middle line:90%
container.

00:13:10.720 --> 00:13:14.390 align:middle line:84%
Now in here, we'll see that
the screen is completely empty.

00:13:14.390 --> 00:13:16.150 align:middle line:90%
There's nothing defined.

00:13:16.150 --> 00:13:18.070 align:middle line:84%
This is the container
which will contain

00:13:18.070 --> 00:13:20.090 align:middle line:84%
the fine-grained
password policies.

00:13:20.090 --> 00:13:24.840 align:middle line:84%
So we can go forward, press
New, and new Password Settings.

00:13:24.840 --> 00:13:28.450 align:middle line:84%
Now this is where we create
the definition for our password

00:13:28.450 --> 00:13:29.800 align:middle line:90%
policy.

00:13:29.800 --> 00:13:32.350 align:middle line:84%
So we'll create,
we'll set a name

00:13:32.350 --> 00:13:40.130 align:middle line:84%
and we'll set it as
"Password Policy Admins".

00:13:40.130 --> 00:13:41.680 align:middle line:90%
We'll put a Precedence of 1.

00:13:41.680 --> 00:13:44.400 align:middle line:90%


00:13:44.400 --> 00:13:47.640 align:middle line:84%
We'll enforce a
minimum length of 20,

00:13:47.640 --> 00:13:50.850 align:middle line:84%
as we discussed,
password history of 24,

00:13:50.850 --> 00:13:52.920 align:middle line:90%
Password must meet complexity.

00:13:52.920 --> 00:13:57.070 align:middle line:84%
We do not store using reversible
encryption, minimum password

00:13:57.070 --> 00:14:01.490 align:middle line:84%
age, 1, maximum
password age 180.

00:14:01.490 --> 00:14:05.880 align:middle line:84%
And we actually want to
lock the user accounts.

00:14:05.880 --> 00:14:10.070 align:middle line:84%
So if there's more than 3
consecutive failed login

00:14:10.070 --> 00:14:13.100 align:middle line:84%
attempts we want these
accounts to actually

00:14:13.100 --> 00:14:18.660 align:middle line:84%
get locked out until someone
unlocks the account itself.

00:14:18.660 --> 00:14:22.230 align:middle line:84%
And this is important,
because this

00:14:22.230 --> 00:14:25.440 align:middle line:84%
might work in one
environment but it might not

00:14:25.440 --> 00:14:26.997 align:middle line:90%
work in other environments.

00:14:26.997 --> 00:14:28.830 align:middle line:84%
And you should be careful
with this setting.

00:14:28.830 --> 00:14:30.330 align:middle line:84%
If you want to go
this way you might

00:14:30.330 --> 00:14:33.810 align:middle line:84%
want to adjust this
value to maybe 5 or 10.

00:14:33.810 --> 00:14:35.970 align:middle line:84%
But in a small environment,
such as the one

00:14:35.970 --> 00:14:38.100 align:middle line:84%
that I have currently
in here, 3 it

00:14:38.100 --> 00:14:42.690 align:middle line:84%
would be more sufficient because
the users or administrators

00:14:42.690 --> 00:14:45.300 align:middle line:84%
would have longer passwords
that most likely they'll

00:14:45.300 --> 00:14:48.420 align:middle line:84%
just copy/paste from
password managers.

00:14:48.420 --> 00:14:51.210 align:middle line:84%
So we don't even expect
failed login attempts

00:14:51.210 --> 00:14:54.360 align:middle line:90%
to occur in this environment.

00:14:54.360 --> 00:14:57.350 align:middle line:84%
Now I'm also going to set the
"Reset failed logon attempts

00:14:57.350 --> 00:15:01.760 align:middle line:84%
after", and in case someone
mistypes their password,

00:15:01.760 --> 00:15:07.620 align:middle line:84%
I'll just set here
the value of 3 hours.

00:15:07.620 --> 00:15:09.890 align:middle line:84%
So if someone tries to
brute force the passwords

00:15:09.890 --> 00:15:10.770 align:middle line:90%
on the network.

00:15:10.770 --> 00:15:13.010 align:middle line:84%
It will make it impossible
for them to actually

00:15:13.010 --> 00:15:17.600 align:middle line:84%
have a dictionary against
our other accounts.

00:15:17.600 --> 00:15:22.160 align:middle line:84%
We can put a Description for
our password policy if we desire

00:15:22.160 --> 00:15:26.810 align:middle line:84%
and the last part is to
select who does it apply to.

00:15:26.810 --> 00:15:31.530 align:middle line:84%
And in this case, since it's a
administrative password policy

00:15:31.530 --> 00:15:35.480 align:middle line:84%
I want this to apply to everyone
who is in Domain Admins.

00:15:35.480 --> 00:15:37.310 align:middle line:84%
So I'll set the
Domain Admins group

00:15:37.310 --> 00:15:40.880 align:middle line:84%
to be the one that is going to
inherit this password policy.

00:15:40.880 --> 00:15:43.340 align:middle line:84%
But actually, this should
be all your administrators

00:15:43.340 --> 00:15:46.830 align:middle line:84%
in the domain regardless of
which tier they're located.

00:15:46.830 --> 00:15:48.870 align:middle line:90%
So this is a great thing here.

00:15:48.870 --> 00:15:52.670 align:middle line:84%
What we could do is, let's
take an example where

00:15:52.670 --> 00:15:54.920 align:middle line:90%
I would just create one group.

00:15:54.920 --> 00:15:59.690 align:middle line:84%
And we can use it as an example,
called Fine-Grained Password

00:15:59.690 --> 00:16:01.970 align:middle line:90%
Policy Admins.

00:16:01.970 --> 00:16:04.870 align:middle line:84%
It will be a Global
group of type Security,

00:16:04.870 --> 00:16:06.620 align:middle line:84%
because this is the
one that we can assign

00:16:06.620 --> 00:16:08.480 align:middle line:90%
fine-grained password policies.

00:16:08.480 --> 00:16:09.780 align:middle line:90%
We created it.

00:16:09.780 --> 00:16:12.530 align:middle line:84%
And now everyone who is
a member of this group

00:16:12.530 --> 00:16:15.080 align:middle line:84%
will make it so they
automatically inherit

00:16:15.080 --> 00:16:16.190 align:middle line:90%
the new password policy.

00:16:16.190 --> 00:16:20.720 align:middle line:84%
So I'll just add one member
who is not a Domain Admin.

00:16:20.720 --> 00:16:25.040 align:middle line:84%
But this user is an
admin on workstations.

00:16:25.040 --> 00:16:28.280 align:middle line:84%
To apply this password
policy on this account,

00:16:28.280 --> 00:16:31.820 align:middle line:84%
I'll just have to add this
group in here as well.

00:16:31.820 --> 00:16:33.350 align:middle line:90%
That was FGPP_Admins.

00:16:33.350 --> 00:16:35.870 align:middle line:90%


00:16:35.870 --> 00:16:39.650 align:middle line:84%
Now these two groups, Domain
Admins and FGPP_Admins,

00:16:39.650 --> 00:16:43.250 align:middle line:84%
will automatically inherit
this password policy

00:16:43.250 --> 00:16:44.820 align:middle line:90%
which we just created.

00:16:44.820 --> 00:16:48.550 align:middle line:84%
And now we can see
it here as well.

00:16:48.550 --> 00:16:52.140 align:middle line:84%
So the process of creating
this password policies it's

00:16:52.140 --> 00:16:53.340 align:middle line:90%
rather simple.

00:16:53.340 --> 00:16:54.780 align:middle line:90%
But they're really effective.

00:16:54.780 --> 00:16:57.600 align:middle line:84%
And we can go forward with
more for service accounts,

00:16:57.600 --> 00:17:02.160 align:middle line:84%
one for 100 characters,
one for 32 characters,

00:17:02.160 --> 00:17:04.780 align:middle line:90%
a VIP, regular user, and so on.

00:17:04.780 --> 00:17:08.890 align:middle line:84%
We can create a bunch of
fine-grained password policies,

00:17:08.890 --> 00:17:10.069 align:middle line:90%
as many as we desire.

00:17:10.069 --> 00:17:13.400 align:middle line:90%


00:17:13.400 --> 00:17:16.369 align:middle line:84%
The next thing that we're going
to discuss in this video lesson

00:17:16.369 --> 00:17:19.140 align:middle line:90%
is the tool Get-bADpassword.

00:17:19.140 --> 00:17:23.240 align:middle line:84%
Now, this image might look
confusing and trust me it

00:17:23.240 --> 00:17:24.440 align:middle line:90%
really isn't.

00:17:24.440 --> 00:17:27.420 align:middle line:84%
There are three things
that you need to look into.

00:17:27.420 --> 00:17:30.980 align:middle line:84%
So the tool itself is a
simple PowerShell script.

00:17:30.980 --> 00:17:36.380 align:middle line:84%
What it does is it loads a list
of predefined password hashes,

00:17:36.380 --> 00:17:40.700 align:middle line:84%
and those password hashes are
of known weak and bad passwords.

00:17:40.700 --> 00:17:45.150 align:middle line:84%
They come from places
such as Have I Been Pwned?

00:17:45.150 --> 00:17:46.760 align:middle line:90%
You can also add custom lists.

00:17:46.760 --> 00:17:50.900 align:middle line:84%
You can create something
that is directly

00:17:50.900 --> 00:17:52.380 align:middle line:90%
associated with your company.

00:17:52.380 --> 00:17:55.460 align:middle line:84%
So you can have
yourcompanyname123 or the year.

00:17:55.460 --> 00:17:58.250 align:middle line:84%
You can create all these
custom passwords as well

00:17:58.250 --> 00:18:00.630 align:middle line:90%
and add them in the solution.

00:18:00.630 --> 00:18:04.940 align:middle line:84%
So this PowerShell script will
get those known bad password

00:18:04.940 --> 00:18:06.048 align:middle line:90%
hashes.

00:18:06.048 --> 00:18:08.090 align:middle line:84%
At the same time, it will
extract password hashes

00:18:08.090 --> 00:18:10.250 align:middle line:84%
from Active Directory
and then just compare

00:18:10.250 --> 00:18:13.160 align:middle line:84%
known bad with the current
passwords of users.

00:18:13.160 --> 00:18:16.460 align:middle line:84%
And it will just
generate a report.

00:18:16.460 --> 00:18:18.800 align:middle line:84%
That is showcased
in this diagram.

00:18:18.800 --> 00:18:21.350 align:middle line:84%
It might look complex
but it really isn't.

00:18:21.350 --> 00:18:23.600 align:middle line:84%
The top part defines
that the script

00:18:23.600 --> 00:18:26.390 align:middle line:84%
is looking into Active
Directory to extract hashes.

00:18:26.390 --> 00:18:30.740 align:middle line:84%
The middle part is loading
the list of bad passwords.

00:18:30.740 --> 00:18:34.490 align:middle line:84%
And the bottom part is showing
that it's outputting the data

00:18:34.490 --> 00:18:37.170 align:middle line:90%
into different reports.

00:18:37.170 --> 00:18:39.463 align:middle line:84%
So one thing about
the reports, which

00:18:39.463 --> 00:18:41.630 align:middle line:84%
I'm not going to showcase
in the demonstration which

00:18:41.630 --> 00:18:43.970 align:middle line:84%
is coming up, is that
the tool can send

00:18:43.970 --> 00:18:46.910 align:middle line:90%
an email with all the results.

00:18:46.910 --> 00:18:49.850 align:middle line:84%
So you can schedule this
to run as a scheduled task.

00:18:49.850 --> 00:18:53.060 align:middle line:84%
And then once a week, or once
a month, whatever you desire.

00:18:53.060 --> 00:18:54.320 align:middle line:90%
Once a day If you want.

00:18:54.320 --> 00:18:58.280 align:middle line:84%
It can run and generate
this summary for you

00:18:58.280 --> 00:18:59.540 align:middle line:90%
and send you an email.

00:18:59.540 --> 00:19:02.300 align:middle line:84%
It's a really easy
way for management,

00:19:02.300 --> 00:19:05.060 align:middle line:84%
or your CISO, or
head of security

00:19:05.060 --> 00:19:10.610 align:middle line:84%
to track passwords over time
and see how they progress.

00:19:10.610 --> 00:19:14.240 align:middle line:84%
But also it's really nice for
us, as security professionals,

00:19:14.240 --> 00:19:17.420 align:middle line:84%
because we will know the
strength of our users'

00:19:17.420 --> 00:19:20.610 align:middle line:84%
passwords without having
to break them ourselves.

00:19:20.610 --> 00:19:24.150 align:middle line:84%
And if a password exists
in a leaked database

00:19:24.150 --> 00:19:27.970 align:middle line:84%
then we know for sure that
this is a bad password.

00:19:27.970 --> 00:19:30.060 align:middle line:84%
Now let's move into
the environment

00:19:30.060 --> 00:19:34.860 align:middle line:84%
and see how this
tool actually works.

00:19:34.860 --> 00:19:38.310 align:middle line:84%
I will be running this tool
on the domain controller

00:19:38.310 --> 00:19:42.180 align:middle line:84%
simply because
this tool requires

00:19:42.180 --> 00:19:44.430 align:middle line:84%
to extract Active
Directory database so it

00:19:44.430 --> 00:19:46.620 align:middle line:90%
needs high privileges.

00:19:46.620 --> 00:19:48.270 align:middle line:84%
If it runs on a
domain controller

00:19:48.270 --> 00:19:52.230 align:middle line:84%
it needs to run as the system
user or domain admin account.

00:19:52.230 --> 00:19:54.035 align:middle line:84%
If it runs on a
separate server, which

00:19:54.035 --> 00:19:55.410 align:middle line:84%
is what I would
recommend to have

00:19:55.410 --> 00:19:57.840 align:middle line:84%
a separate dedicated
server for this tool,

00:19:57.840 --> 00:20:00.630 align:middle line:84%
then the account which
is running this tool

00:20:00.630 --> 00:20:03.360 align:middle line:84%
needs to have the
directory replication

00:20:03.360 --> 00:20:05.430 align:middle line:90%
changes permissions.

00:20:05.430 --> 00:20:09.010 align:middle line:84%
Essentially, the account will
be doing the DCSync attack.

00:20:09.010 --> 00:20:11.050 align:middle line:84%
I have downloaded
the tool already

00:20:11.050 --> 00:20:14.260 align:middle line:84%
and installed the prerequisites
that are required for it.

00:20:14.260 --> 00:20:17.200 align:middle line:84%
So we don't have to go
through it together.

00:20:17.200 --> 00:20:21.130 align:middle line:84%
One of the things we had to
do was to manually download

00:20:21.130 --> 00:20:26.560 align:middle line:84%
this BIN file, which contains
the password hashes of all

00:20:26.560 --> 00:20:27.910 align:middle line:90%
the weak passwords.

00:20:27.910 --> 00:20:32.200 align:middle line:84%
I have also created the
common bad password lists.

00:20:32.200 --> 00:20:35.560 align:middle line:84%
They can be created with
this PowerShell scripts which

00:20:35.560 --> 00:20:38.030 align:middle line:90%
come as part of the tool.

00:20:38.030 --> 00:20:39.500 align:middle line:84%
I can just show
you, as an example,

00:20:39.500 --> 00:20:42.610 align:middle line:90%
what is common bad passwords.

00:20:42.610 --> 00:20:45.640 align:middle line:84%
So this is the word "test"
in different variations

00:20:45.640 --> 00:20:48.490 align:middle line:90%
with different endings.

00:20:48.490 --> 00:20:50.320 align:middle line:90%
We have "QWERT" words.

00:20:50.320 --> 00:20:55.210 align:middle line:84%
We have a lot of variations of
different "password" spelling.

00:20:55.210 --> 00:20:57.310 align:middle line:90%
We have "welcome", "start".

00:20:57.310 --> 00:21:01.540 align:middle line:84%
Now these common things that
people may end up using.

00:21:01.540 --> 00:21:04.150 align:middle line:84%
And they actually do
use them quite often.

00:21:04.150 --> 00:21:05.920 align:middle line:84%
We also have weak
passwords based

00:21:05.920 --> 00:21:11.420 align:middle line:84%
on English words which
includes days, months,

00:21:11.420 --> 00:21:14.250 align:middle line:90%
and just common phrases.

00:21:14.250 --> 00:21:17.430 align:middle line:84%
Now to run the tool we
need to start our shell

00:21:17.430 --> 00:21:20.460 align:middle line:90%
as administrators.

00:21:20.460 --> 00:21:25.440 align:middle line:84%
And we need to execute
"powershell -exec bypass".

00:21:25.440 --> 00:21:28.440 align:middle line:84%
So we can bypass the
current execution policy

00:21:28.440 --> 00:21:32.670 align:middle line:84%
to allow us to run unsigned
PowerShell scripts.

00:21:32.670 --> 00:21:37.980 align:middle line:84%
So it's really as simple as
just running the script itself.

00:21:37.980 --> 00:21:39.660 align:middle line:84%
Before running
the script itself,

00:21:39.660 --> 00:21:41.700 align:middle line:84%
there are some
prerequisites that

00:21:41.700 --> 00:21:43.860 align:middle line:90%
need to be configured inside.

00:21:43.860 --> 00:21:46.800 align:middle line:84%
I will just open it to show
you what I had to configure.

00:21:46.800 --> 00:21:51.390 align:middle line:84%
And that was the information
about the domain,

00:21:51.390 --> 00:21:54.210 align:middle line:90%
that my domain name is "prod".

00:21:54.210 --> 00:21:58.200 align:middle line:84%
And the naming
context is prod.local.

00:21:58.200 --> 00:22:02.580 align:middle line:84%
And at the very bottom,
you need to define

00:22:02.580 --> 00:22:04.350 align:middle line:90%
where should the email be sent.

00:22:04.350 --> 00:22:06.750 align:middle line:84%
I have simply commented
out this part.

00:22:06.750 --> 00:22:09.100 align:middle line:84%
So I'm not going to
receive an email.

00:22:09.100 --> 00:22:11.400 align:middle line:84%
I'll just get the
summary on the screen.

00:22:11.400 --> 00:22:13.230 align:middle line:84%
And that's just
good enough for me

00:22:13.230 --> 00:22:16.170 align:middle line:84%
to demonstrate some of
the ability of this tool.

00:22:16.170 --> 00:22:18.330 align:middle line:84%
Because since it's
a PowerShell script,

00:22:18.330 --> 00:22:22.200 align:middle line:84%
you can go forward yourself
and modify it in any way

00:22:22.200 --> 00:22:23.250 align:middle line:90%
that you desire.

00:22:23.250 --> 00:22:26.370 align:middle line:84%
For example, you can configure
that it will automatically

00:22:26.370 --> 00:22:29.070 align:middle line:84%
require users to change their
passwords next time they login

00:22:29.070 --> 00:22:30.480 align:middle line:90%
if they have a weak password.

00:22:30.480 --> 00:22:31.620 align:middle line:90%
That could be one action.

00:22:31.620 --> 00:22:34.950 align:middle line:84%
But I can think of many
reasons that your users might

00:22:34.950 --> 00:22:37.470 align:middle line:84%
be unsatisfied if this
happens, and especially

00:22:37.470 --> 00:22:39.150 align:middle line:90%
if they're traveling.

00:22:39.150 --> 00:22:43.410 align:middle line:84%
So be careful with how
you want to approach this.

00:22:43.410 --> 00:22:45.720 align:middle line:84%
The most common approach
I've seen at companies

00:22:45.720 --> 00:22:48.780 align:middle line:84%
is they'll send an
email to that user

00:22:48.780 --> 00:22:51.860 align:middle line:84%
with a short memo of
how they should create

00:22:51.860 --> 00:22:57.340 align:middle line:84%
a new passphrase, a strong
password, and asking them

00:22:57.340 --> 00:22:59.590 align:middle line:84%
to actually change it within
a certain amount of time,

00:22:59.590 --> 00:23:03.330 align:middle line:84%
for example, within the
next two days or so.

00:23:03.330 --> 00:23:06.050 align:middle line:90%
Now let's run the script itself.

00:23:06.050 --> 00:23:10.000 align:middle line:84%
It will take some time depending
on how big your environment is.

00:23:10.000 --> 00:23:13.320 align:middle line:84%
Since I have very little,
very small environment

00:23:13.320 --> 00:23:16.890 align:middle line:84%
with very few users it
runs almost instantly.

00:23:16.890 --> 00:23:19.920 align:middle line:84%
It loads the lists and then
it just compares the data back

00:23:19.920 --> 00:23:20.790 align:middle line:90%
to me.

00:23:20.790 --> 00:23:23.010 align:middle line:84%
Now while it's working
it shows information

00:23:23.010 --> 00:23:26.010 align:middle line:84%
that it finds users
who have weak passwords

00:23:26.010 --> 00:23:29.550 align:middle line:84%
and in here it says,
I found the user

00:23:29.550 --> 00:23:33.527 align:middle line:84%
whose password is in the
list weak-password-common.

00:23:33.527 --> 00:23:35.610 align:middle line:84%
Now it's not going to show
me the password itself.

00:23:35.610 --> 00:23:36.690 align:middle line:90%
I don't really need it.

00:23:36.690 --> 00:23:38.783 align:middle line:84%
We should never
really need it, even

00:23:38.783 --> 00:23:40.200 align:middle line:84%
though the tool
has a switch where

00:23:40.200 --> 00:23:45.690 align:middle line:84%
it will save the passwords in
plain text of the users whose

00:23:45.690 --> 00:23:52.300 align:middle line:84%
password was discovered
to be part of these lists.

00:23:52.300 --> 00:23:54.760 align:middle line:84%
Now I get the list
of all the users

00:23:54.760 --> 00:23:58.960 align:middle line:84%
that were detected
to have bad passwords

00:23:58.960 --> 00:23:59.920 align:middle line:90%
and that's quite a bit.

00:23:59.920 --> 00:24:03.100 align:middle line:84%
You can see that we have
users from normal tiers,

00:24:03.100 --> 00:24:06.250 align:middle line:84%
from different tiers, privileged
users, service accounts.

00:24:06.250 --> 00:24:09.320 align:middle line:84%
And this is what you'd normally
expect in a large organization.

00:24:09.320 --> 00:24:12.440 align:middle line:84%
You would see that many
accounts would come back

00:24:12.440 --> 00:24:14.840 align:middle line:90%
with weak passwords.

00:24:14.840 --> 00:24:18.680 align:middle line:84%
And the next part
that we'll look into

00:24:18.680 --> 00:24:24.510 align:middle line:84%
is an outline that shows which
users shared the same password.

00:24:24.510 --> 00:24:27.740 align:middle line:84%
So the users on this
line, all of them,

00:24:27.740 --> 00:24:30.170 align:middle line:84%
they have exactly the
same password set.

00:24:30.170 --> 00:24:35.570 align:middle line:84%
So this gives me so
much more insight

00:24:35.570 --> 00:24:38.540 align:middle line:84%
into the users who are
saving this password.

00:24:38.540 --> 00:24:42.320 align:middle line:84%
And primarily because, if
you look into my account

00:24:42.320 --> 00:24:47.990 align:middle line:84%
I have an account which is
"t1_maro" and I have "t0_maro".

00:24:47.990 --> 00:24:51.410 align:middle line:84%
This is telling me
that the maro user

00:24:51.410 --> 00:24:54.290 align:middle line:84%
has the same password across
his different accounts

00:24:54.290 --> 00:24:55.490 align:middle line:90%
in different tiers.

00:24:55.490 --> 00:25:00.350 align:middle line:84%
And this is effectively
bypassing our added security

00:25:00.350 --> 00:25:02.660 align:middle line:84%
by having multiple
accounts in multiple tiers.

00:25:02.660 --> 00:25:05.360 align:middle line:84%
We shouldn't have users
having the same passwords

00:25:05.360 --> 00:25:06.590 align:middle line:90%
across different tiers.

00:25:06.590 --> 00:25:10.195 align:middle line:84%
And this is what this tool
is going to discover here.

00:25:10.195 --> 00:25:13.700 align:middle line:84%
It will showcase us this
administrative account

00:25:13.700 --> 00:25:16.740 align:middle line:84%
who is actually
bridging the gap for us.

00:25:16.740 --> 00:25:19.880 align:middle line:84%
We also have a list
of two other users

00:25:19.880 --> 00:25:21.750 align:middle line:90%
who are sharing passwords.

00:25:21.750 --> 00:25:23.430 align:middle line:90%
But this password is different.

00:25:23.430 --> 00:25:29.400 align:middle line:84%
So the tool is going to
output the users per line that

00:25:29.400 --> 00:25:32.680 align:middle line:90%
are sharing passwords.

00:25:32.680 --> 00:25:35.230 align:middle line:84%
And there was also a
summary that there was only

00:25:35.230 --> 00:25:38.120 align:middle line:84%
two share passwords that
the tool discovered.

00:25:38.120 --> 00:25:42.500 align:middle line:84%
Now, I really hope that this
small demonstration gives you

00:25:42.500 --> 00:25:43.610 align:middle line:90%
a good overview.

00:25:43.610 --> 00:25:46.010 align:middle line:84%
And you can see the
benefit of having something

00:25:46.010 --> 00:25:47.420 align:middle line:90%
like this constantly running.

00:25:47.420 --> 00:25:50.600 align:middle line:84%
You can identify users,
and service accounts,

00:25:50.600 --> 00:25:54.050 align:middle line:84%
and everything that is having
weak in your environment

00:25:54.050 --> 00:25:56.440 align:middle line:84%
and try to improve it
before an attacker has

00:25:56.440 --> 00:25:57.440 align:middle line:90%
the opportunity to abuse

00:25:57.440 --> 00:25:58.990 align:middle line:90%
it.

00:25:58.990 --> 00:26:00.000 align:middle line:90%