WEBVTT

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


00:00:02.770 --> 00:00:03.650 align:middle line:90%
Hi.

00:00:03.650 --> 00:00:06.940 align:middle line:84%
Welcome to this INE video
lesson on Privileged Access

00:00:06.940 --> 00:00:08.020 align:middle line:90%
Workstation.

00:00:08.020 --> 00:00:11.300 align:middle line:84%
The agenda for this
video is as follows.

00:00:11.300 --> 00:00:13.300 align:middle line:84%
First, we'll look
into the problem

00:00:13.300 --> 00:00:16.420 align:middle line:84%
and why is it that we need
privileged access workstations.

00:00:16.420 --> 00:00:18.700 align:middle line:84%
Then we'll discuss
what privileged access

00:00:18.700 --> 00:00:23.050 align:middle line:84%
workstation is, go through some
of the core concepts behind it.

00:00:23.050 --> 00:00:26.560 align:middle line:84%
And finally, we'll finish
with a demonstration

00:00:26.560 --> 00:00:29.680 align:middle line:84%
in our environment of a
privileged access workstation

00:00:29.680 --> 00:00:34.080 align:middle line:84%
so we can showcase what
difference a PAW creates

00:00:34.080 --> 00:00:35.890 align:middle line:90%
in our environment.

00:00:35.890 --> 00:00:37.650 align:middle line:90%
Now, what is the problem?

00:00:37.650 --> 00:00:40.290 align:middle line:84%
The real problem
here is the risk

00:00:40.290 --> 00:00:44.220 align:middle line:84%
that an attacker could
compromise a workstation of one

00:00:44.220 --> 00:00:45.750 align:middle line:90%
of our administrators.

00:00:45.750 --> 00:00:48.750 align:middle line:84%
And by using keylogging
or credential dumping,

00:00:48.750 --> 00:00:52.830 align:middle line:84%
the attacker might be able to
get the privileged credentials

00:00:52.830 --> 00:00:55.920 align:middle line:84%
of the administrator
running on that workstation.

00:00:55.920 --> 00:00:58.200 align:middle line:84%
And in this case,
this workstation

00:00:58.200 --> 00:01:00.690 align:middle line:84%
is the one that
our administrator

00:01:00.690 --> 00:01:03.910 align:middle line:84%
is using for their daily
operations, reading emails,

00:01:03.910 --> 00:01:06.010 align:middle line:90%
for browsing internet.

00:01:06.010 --> 00:01:09.790 align:middle line:84%
They tend to have only one
device for all their purposes,

00:01:09.790 --> 00:01:12.870 align:middle line:84%
including for
administrative tasks.

00:01:12.870 --> 00:01:14.310 align:middle line:84%
And of course, we
don't want this

00:01:14.310 --> 00:01:18.660 align:middle line:84%
to happen because in real life
this would be game over for us

00:01:18.660 --> 00:01:20.850 align:middle line:84%
if this machine gets
compromised simply

00:01:20.850 --> 00:01:24.570 align:middle line:84%
because if this administrator,
who type their domain admin

00:01:24.570 --> 00:01:28.950 align:middle line:84%
credentials while performing RDP
or any kind of other connection

00:01:28.950 --> 00:01:32.130 align:middle line:84%
to a server or a
privileged machine,

00:01:32.130 --> 00:01:33.900 align:middle line:84%
these credentials
might be stolen.

00:01:33.900 --> 00:01:36.480 align:middle line:84%
And again, that would
just be game over for us

00:01:36.480 --> 00:01:40.430 align:middle line:84%
because our entire environment
would be compromised.

00:01:40.430 --> 00:01:43.790 align:middle line:84%
Then we bring the concept of
privileged access workstation.

00:01:43.790 --> 00:01:46.670 align:middle line:84%
This is a dedicated
workstation that is only

00:01:46.670 --> 00:01:49.640 align:middle line:90%
used for administrative tasks.

00:01:49.640 --> 00:01:54.260 align:middle line:84%
And this workstation is really
security hardened feature

00:01:54.260 --> 00:01:56.000 align:middle line:90%
and functionality locked-down.

00:01:56.000 --> 00:01:59.300 align:middle line:84%
It will have very limited
functionality that

00:01:59.300 --> 00:02:02.480 align:middle line:84%
is available to it simply
because everything that is not

00:02:02.480 --> 00:02:07.650 align:middle line:84%
available is going to
be disabled by default.

00:02:07.650 --> 00:02:11.160 align:middle line:84%
By doing this, by really
having this separate machine

00:02:11.160 --> 00:02:14.310 align:middle line:84%
and security hardening
it, we are protecting

00:02:14.310 --> 00:02:17.340 align:middle line:84%
against the phishing
against our administrators

00:02:17.340 --> 00:02:20.550 align:middle line:84%
and that will also protect
us against credential theft

00:02:20.550 --> 00:02:22.440 align:middle line:90%
attacks, Pass-the-Hash.

00:02:22.440 --> 00:02:24.360 align:middle line:84%
We're protecting
privileged credentials

00:02:24.360 --> 00:02:26.850 align:middle line:84%
in a separate
machine and as you're

00:02:26.850 --> 00:02:29.460 align:middle line:84%
going to see later
in our demonstration,

00:02:29.460 --> 00:02:32.730 align:middle line:84%
this separate machine is going
to be so locked-down that we'll

00:02:32.730 --> 00:02:36.660 align:middle line:84%
limit the ability of anyone
ever essentially compromising

00:02:36.660 --> 00:02:40.010 align:middle line:90%
this machine remotely.

00:02:40.010 --> 00:02:47.480 align:middle line:84%
Now, PAW creates a trusted
environment as you may say

00:02:47.480 --> 00:02:52.070 align:middle line:84%
and having one PAW per
user is not necessary,

00:02:52.070 --> 00:02:55.640 align:middle line:84%
at least we don't have
to map users to our PAWs.

00:02:55.640 --> 00:02:59.270 align:middle line:84%
Because the PAW machine
is a trusted workstation,

00:02:59.270 --> 00:03:04.210 align:middle line:84%
multiple users can use the same
machine to perform actions.

00:03:04.210 --> 00:03:07.220 align:middle line:84%
With that being said, if you
have people who are on call

00:03:07.220 --> 00:03:10.010 align:middle line:84%
or working remotely then
in those cases, of course,

00:03:10.010 --> 00:03:11.900 align:middle line:84%
they need to have one
machine with them.

00:03:11.900 --> 00:03:14.820 align:middle line:84%
But in a shared
office environment

00:03:14.820 --> 00:03:16.730 align:middle line:84%
you also have the
opportunity to share one

00:03:16.730 --> 00:03:19.185 align:middle line:90%
machine with multiple users.

00:03:19.185 --> 00:03:21.060 align:middle line:84%
Of course, having a
separate machine per user

00:03:21.060 --> 00:03:23.930 align:middle line:84%
is going to be
preferred probably

00:03:23.930 --> 00:03:26.330 align:middle line:90%
by the users themselves as well.

00:03:26.330 --> 00:03:29.460 align:middle line:84%
The implementation can consist
of multiple variations.

00:03:29.460 --> 00:03:31.970 align:middle line:84%
I've seen quite a
few and the reason

00:03:31.970 --> 00:03:33.950 align:middle line:84%
why there's multiple
variations is simply

00:03:33.950 --> 00:03:38.360 align:middle line:84%
because we're introducing
a separate machine

00:03:38.360 --> 00:03:42.650 align:middle line:84%
to our administrators and that
tends to drive them crazy.

00:03:42.650 --> 00:03:45.440 align:middle line:84%
They're saying, having to
bring another laptop with me

00:03:45.440 --> 00:03:48.470 align:middle line:90%
all the time, that's a no-go.

00:03:48.470 --> 00:03:51.320 align:middle line:84%
This is by far the
best option we have,

00:03:51.320 --> 00:03:54.150 align:middle line:84%
to have a separate
physical machine.

00:03:54.150 --> 00:03:57.760 align:middle line:84%
But in case this is not a
solution in your environment,

00:03:57.760 --> 00:04:02.500 align:middle line:84%
another option would be to use
virtualization on your machine.

00:04:02.500 --> 00:04:04.890 align:middle line:84%
But the caveat is that
the host machine has

00:04:04.890 --> 00:04:06.840 align:middle line:84%
to be the privileged
access workstation

00:04:06.840 --> 00:04:09.510 align:middle line:84%
or the virtual machine
will be the one that

00:04:09.510 --> 00:04:14.160 align:middle line:84%
is being used for the
operations' emails, internet,

00:04:14.160 --> 00:04:18.029 align:middle line:84%
and basically whatever else the
administrator needs that is not

00:04:18.029 --> 00:04:19.899 align:middle line:90%
an administrative task.

00:04:19.899 --> 00:04:22.890 align:middle line:84%
So the host is going to be a
hardened locked-down machine,

00:04:22.890 --> 00:04:26.520 align:middle line:84%
a PAW and the virtual machine
or virtual machines running

00:04:26.520 --> 00:04:32.660 align:middle line:84%
on it will be acting as their
day-to-day operation laptops.

00:04:32.660 --> 00:04:36.890 align:middle line:84%
This is preferred by some
users and not so much by others

00:04:36.890 --> 00:04:39.110 align:middle line:84%
because they're,
again, starting to get

00:04:39.110 --> 00:04:42.505 align:middle line:84%
annoyed by having to operate
in virtual environments

00:04:42.505 --> 00:04:45.430 align:middle line:90%
on their daily tasks.

00:04:45.430 --> 00:04:47.380 align:middle line:84%
And I've also seen
some alternatives

00:04:47.380 --> 00:04:49.810 align:middle line:84%
to implementing this,
they're not really

00:04:49.810 --> 00:04:54.820 align:middle line:84%
recommended compared to the
separate physical machine

00:04:54.820 --> 00:04:57.920 align:middle line:84%
but it's also an option of how
we can go forward and implement

00:04:57.920 --> 00:04:58.555 align:middle line:90%
this.

00:04:58.555 --> 00:05:02.830 align:middle line:84%
One of the most common scenarios
I've seen being pushed out

00:05:02.830 --> 00:05:06.880 align:middle line:84%
is a jump host or the
concept of jump host

00:05:06.880 --> 00:05:09.430 align:middle line:84%
but the jump host
itself is acting

00:05:09.430 --> 00:05:13.370 align:middle line:84%
and it's locked-down as if it
was an actual power machine.

00:05:13.370 --> 00:05:16.450 align:middle line:84%
So you will lock
down that server

00:05:16.450 --> 00:05:21.340 align:middle line:84%
that only one type of
incoming connection is allowed

00:05:21.340 --> 00:05:24.730 align:middle line:84%
and that incoming connection
will require a second factor

00:05:24.730 --> 00:05:26.030 align:middle line:90%
for authentication.

00:05:26.030 --> 00:05:29.320 align:middle line:84%
So if we take for
an example a Windows

00:05:29.320 --> 00:05:34.210 align:middle line:84%
server we can block all
incoming connections except RDP

00:05:34.210 --> 00:05:37.760 align:middle line:84%
and then require multi-factor
authentication with the RDP

00:05:37.760 --> 00:05:38.420 align:middle line:90%
logging.

00:05:38.420 --> 00:05:41.680 align:middle line:84%
So username and password
is not enough alone

00:05:41.680 --> 00:05:43.750 align:middle line:90%
to get into the jump host.

00:05:43.750 --> 00:05:46.330 align:middle line:84%
And in the number
one implementation,

00:05:46.330 --> 00:05:50.890 align:middle line:84%
administrators will use
their day-to-day operation

00:05:50.890 --> 00:05:53.050 align:middle line:84%
workstation to
connect to jump host

00:05:53.050 --> 00:05:55.890 align:middle line:84%
but they'll have a jump
host on their accounts.

00:05:55.890 --> 00:05:59.410 align:middle line:84%
An account which is only for
locked-down specific jump host,

00:05:59.410 --> 00:06:02.030 align:middle line:84%
username and password and
multi-factor authentication

00:06:02.030 --> 00:06:03.560 align:middle line:90%
required in the connection.

00:06:03.560 --> 00:06:06.520 align:middle line:84%
Once they're connected
to that jump host then

00:06:06.520 --> 00:06:08.440 align:middle line:84%
they'll have the ability
to perform a new RDP

00:06:08.440 --> 00:06:12.100 align:middle line:84%
connection from that jump host
to connect to tier-0 systems.

00:06:12.100 --> 00:06:13.920 align:middle line:84%
And if you think
about this concept,

00:06:13.920 --> 00:06:16.450 align:middle line:84%
the privileged credentials
are isolated with the jump

00:06:16.450 --> 00:06:23.650 align:middle line:84%
off itself, they never touch
the unprivileged workstation

00:06:23.650 --> 00:06:28.450 align:middle line:84%
that the initial
connection originates from.

00:06:28.450 --> 00:06:30.690 align:middle line:84%
So what we really want
to achieve with the PAW

00:06:30.690 --> 00:06:33.510 align:middle line:84%
is having these
two channels where

00:06:33.510 --> 00:06:36.000 align:middle line:84%
the administrator
on their daily tasks

00:06:36.000 --> 00:06:39.060 align:middle line:84%
will have their user channel,
a separate channel that

00:06:39.060 --> 00:06:42.030 align:middle line:84%
doesn't interfere in any way
with administrative tasks,

00:06:42.030 --> 00:06:43.590 align:middle line:84%
and then a whole
separate channel

00:06:43.590 --> 00:06:45.750 align:middle line:84%
for administrative tasks
that does interfere

00:06:45.750 --> 00:06:47.860 align:middle line:90%
with user interactions.

00:06:47.860 --> 00:06:52.740 align:middle line:84%
So any potential exploitation
of vulnerabilities

00:06:52.740 --> 00:06:55.050 align:middle line:84%
that could come
from a user concept,

00:06:55.050 --> 00:06:56.490 align:middle line:84%
they would be
mitigated by having

00:06:56.490 --> 00:07:00.400 align:middle line:84%
this separate
administrative channel.

00:07:00.400 --> 00:07:02.920 align:middle line:84%
Now, what we would
normally recommend for PAW

00:07:02.920 --> 00:07:07.450 align:middle line:84%
hardening is you should take
security hardening guidelines

00:07:07.450 --> 00:07:10.870 align:middle line:84%
such as the ones from the
Sys or the Microsoft security

00:07:10.870 --> 00:07:13.150 align:middle line:84%
guidelines, but normally
I recommend the Sys ones

00:07:13.150 --> 00:07:14.900 align:middle line:84%
because they're way
more complete compared

00:07:14.900 --> 00:07:16.870 align:middle line:84%
to the Microsoft ones
but the Microsoft can

00:07:16.870 --> 00:07:18.490 align:middle line:90%
be a starting point as well.

00:07:18.490 --> 00:07:22.540 align:middle line:84%
But some of the features such
as LAPS, really lock-down host

00:07:22.540 --> 00:07:26.870 align:middle line:84%
firewall, Bitlocker, Credential
Guard, Windows Defender

00:07:26.870 --> 00:07:28.600 align:middle line:90%
Application Control.

00:07:28.600 --> 00:07:31.870 align:middle line:84%
Actual strict
application whitelisting

00:07:31.870 --> 00:07:35.530 align:middle line:84%
is really necessary on these
machines because on a PAW

00:07:35.530 --> 00:07:38.740 align:middle line:84%
the only thing you'll be doing
is performing an RDP connection

00:07:38.740 --> 00:07:41.950 align:middle line:84%
or running one specific tool
that you need to connect

00:07:41.950 --> 00:07:43.570 align:middle line:90%
to your remote machines.

00:07:43.570 --> 00:07:48.070 align:middle line:84%
So creating a complete
lock-down whitelisting solution

00:07:48.070 --> 00:07:50.770 align:middle line:90%
is more than realistic.

00:07:50.770 --> 00:07:54.950 align:middle line:84%
And finally we need to manage
the user right assignments, now

00:07:54.950 --> 00:07:59.410 align:middle line:84%
PAW, who have access to logging
that PAW physically, who

00:07:59.410 --> 00:08:02.440 align:middle line:84%
have access to login to that
PAW remotely, and so on.

00:08:02.440 --> 00:08:05.030 align:middle line:84%
And really no one should
need to have the ability

00:08:05.030 --> 00:08:06.760 align:middle line:90%
to log into a PAW remotely.

00:08:06.760 --> 00:08:10.070 align:middle line:84%
It should only be
allowed physically.

00:08:10.070 --> 00:08:11.900 align:middle line:84%
Let's go to the
environment and have

00:08:11.900 --> 00:08:14.420 align:middle line:84%
a look at a sample
implementation

00:08:14.420 --> 00:08:17.770 align:middle line:84%
of a privileged
access workstation.

00:08:17.770 --> 00:08:20.590 align:middle line:84%
I'm now connected to
our domain controller

00:08:20.590 --> 00:08:24.520 align:middle line:84%
where I have the probably
familiar to you already,

00:08:24.520 --> 00:08:27.260 align:middle line:84%
this tiering structure
in our environment.

00:08:27.260 --> 00:08:31.630 align:middle line:84%
And in the PAW organizational
unit I have created some GPOs.

00:08:31.630 --> 00:08:33.940 align:middle line:84%
If we go into the same
organizational units

00:08:33.940 --> 00:08:36.340 align:middle line:84%
in [? existing ?]
computers we'll

00:08:36.340 --> 00:08:41.169 align:middle line:84%
see that there is now a
workstation called PAW01.

00:08:41.169 --> 00:08:43.570 align:middle line:84%
So all the GPOs that
we have linked in here

00:08:43.570 --> 00:08:47.360 align:middle line:84%
will be applied to
that PAW machine.

00:08:47.360 --> 00:08:50.290 align:middle line:84%
Now looking at the
GPOs many of them

00:08:50.290 --> 00:08:53.840 align:middle line:84%
are the standard Sys
hardening guidelines.

00:08:53.840 --> 00:08:58.030 align:middle line:84%
I have simply split them into
multiple organizational units

00:08:58.030 --> 00:09:01.420 align:middle line:84%
because it's much easier for me
to debug if something breaks,

00:09:01.420 --> 00:09:03.880 align:middle line:84%
by having them in
separate containers.

00:09:03.880 --> 00:09:07.120 align:middle line:84%
And while the default ones
are not really interesting

00:09:07.120 --> 00:09:09.850 align:middle line:84%
because they're just coming
up from the recommendations

00:09:09.850 --> 00:09:16.660 align:middle line:84%
from Sys, what I want to spend
time on is two of these GPOs.

00:09:16.660 --> 00:09:20.890 align:middle line:84%
The first one is the
IPsec RDP, the firewall

00:09:20.890 --> 00:09:23.810 align:middle line:90%
and the user rights assignment.

00:09:23.810 --> 00:09:26.830 align:middle line:84%
I will start by looking at
the user rights assignment.

00:09:26.830 --> 00:09:31.000 align:middle line:84%
What I want to outline
here is my implementation

00:09:31.000 --> 00:09:33.740 align:middle line:90%
of who can access this machine.

00:09:33.740 --> 00:09:36.940 align:middle line:84%
So if we look at who can
log into the machine,

00:09:36.940 --> 00:09:39.790 align:middle line:84%
we'll see that a
group, PAW users,

00:09:39.790 --> 00:09:41.770 align:middle line:84%
and the built-in
administrators' groups

00:09:41.770 --> 00:09:45.260 align:middle line:84%
are only allowed to
log into this machine.

00:09:45.260 --> 00:09:49.940 align:middle line:84%
At the same time, denied
access on this computer

00:09:49.940 --> 00:09:51.950 align:middle line:84%
from the network,
we're basically

00:09:51.950 --> 00:09:56.400 align:middle line:84%
denying access to all privileged
users in our environment.

00:09:56.400 --> 00:10:02.390 align:middle line:84%
So no privileged user can access
this machine remotely and also

00:10:02.390 --> 00:10:05.850 align:middle line:84%
locally as you'll see further
on in this implementation.

00:10:05.850 --> 00:10:08.930 align:middle line:84%
So the only real way to
login to our workstation

00:10:08.930 --> 00:10:13.130 align:middle line:84%
will be to be a PAW user
or be a member of PAW users

00:10:13.130 --> 00:10:17.650 align:middle line:84%
and log on to this
machine locally.

00:10:17.650 --> 00:10:20.040 align:middle line:84%
Now, this is very
important because we

00:10:20.040 --> 00:10:22.500 align:middle line:84%
are limiting who can
access our machine

00:10:22.500 --> 00:10:26.490 align:middle line:84%
and by doing so we are
limiting the potential risk

00:10:26.490 --> 00:10:28.590 align:middle line:84%
of credentials
being compromised,

00:10:28.590 --> 00:10:32.290 align:middle line:84%
and then our PAW being
compromised remotely.

00:10:32.290 --> 00:10:34.050 align:middle line:90%
Which brings us to the firewall.

00:10:34.050 --> 00:10:35.910 align:middle line:90%
The firewall is really strict.

00:10:35.910 --> 00:10:40.320 align:middle line:84%
I will just go inside the GPO
because showing the firewall

00:10:40.320 --> 00:10:45.280 align:middle line:84%
rules in theory is much
easier and more comprehensive.

00:10:45.280 --> 00:10:48.250 align:middle line:84%
The firewall rules are in
Windows Defender Firewall

00:10:48.250 --> 00:10:49.330 align:middle line:90%
with Advanced Security.

00:10:49.330 --> 00:10:53.620 align:middle line:84%
I will expand the window
and then select the firewall

00:10:53.620 --> 00:10:54.790 align:middle line:90%
itself.

00:10:54.790 --> 00:10:58.900 align:middle line:84%
Let's begin by first looking
at the firewall properties.

00:10:58.900 --> 00:11:01.510 align:middle line:84%
As you can already
see in here, we

00:11:01.510 --> 00:11:03.970 align:middle line:84%
have enabled the
firewall on all profiles

00:11:03.970 --> 00:11:05.550 align:middle line:84%
and what is interesting
is that we're

00:11:05.550 --> 00:11:10.060 align:middle line:84%
blocking both inbound and
outbound connections that

00:11:10.060 --> 00:11:11.950 align:middle line:90%
do not match a rule.

00:11:11.950 --> 00:11:15.790 align:middle line:84%
So unless a specific
explicit rule exists,

00:11:15.790 --> 00:11:18.600 align:middle line:84%
connection is going
to be blocked.

00:11:18.600 --> 00:11:20.680 align:middle line:84%
Now, if we're
looking at the rules,

00:11:20.680 --> 00:11:23.190 align:middle line:84%
let's start by looking
into inbound rules.

00:11:23.190 --> 00:11:27.300 align:middle line:84%
So these are the very
few rules that we're

00:11:27.300 --> 00:11:29.290 align:middle line:84%
going to introduce
in our environment

00:11:29.290 --> 00:11:32.140 align:middle line:84%
and the core ones
really are the ones that

00:11:32.140 --> 00:11:34.930 align:middle line:84%
are associated
with DHCP, so when

00:11:34.930 --> 00:11:36.550 align:middle line:84%
we connect our
machine to the network

00:11:36.550 --> 00:11:39.160 align:middle line:84%
it will be able to
obtain an IP address.

00:11:39.160 --> 00:11:41.910 align:middle line:90%


00:11:41.910 --> 00:11:44.010 align:middle line:84%
Again, this is very
important because we

00:11:44.010 --> 00:11:47.610 align:middle line:84%
are limiting the attack
surface to our machine.

00:11:47.610 --> 00:11:50.560 align:middle line:84%
And what is even more is
that we are explicitly

00:11:50.560 --> 00:11:54.690 align:middle line:84%
denying ports which will allow
for remote code execution

00:11:54.690 --> 00:11:56.230 align:middle line:90%
from being accessed.

00:11:56.230 --> 00:11:58.830 align:middle line:84%
So even if someone
had an account

00:11:58.830 --> 00:12:01.770 align:middle line:84%
to connect to our
PAW machine remotely,

00:12:01.770 --> 00:12:03.360 align:middle line:84%
we're simply blocking
that connection

00:12:03.360 --> 00:12:08.340 align:middle line:84%
from occurring because we're not
allowing BMI SMB or PowerShell

00:12:08.340 --> 00:12:10.230 align:middle line:84%
remoting connections
to our machine

00:12:10.230 --> 00:12:12.840 align:middle line:84%
and we certainly
don't allow RDP either

00:12:12.840 --> 00:12:16.310 align:middle line:90%
since that rule doesn't exist.

00:12:16.310 --> 00:12:18.530 align:middle line:84%
If we go into the
outbound rules,

00:12:18.530 --> 00:12:21.590 align:middle line:84%
we will allow certain
connections to go out.

00:12:21.590 --> 00:12:23.690 align:middle line:90%
But again, this is very limited.

00:12:23.690 --> 00:12:26.480 align:middle line:84%
What you're going to see is
that this machine will not

00:12:26.480 --> 00:12:29.090 align:middle line:84%
have internet access
at all, unless we

00:12:29.090 --> 00:12:35.150 align:middle line:84%
allow a specific machines to be
accessed on that internet port.

00:12:35.150 --> 00:12:38.330 align:middle line:84%
We are really allowing that
our machine should have access

00:12:38.330 --> 00:12:43.100 align:middle line:84%
to certificate authorities,
the domain controllers.

00:12:43.100 --> 00:12:47.180 align:middle line:84%
It needs to have access
to our VPN IP address

00:12:47.180 --> 00:12:50.390 align:middle line:84%
in case we're connecting
someone from outside,

00:12:50.390 --> 00:12:56.210 align:middle line:84%
and the very core needs for this
machine that might be required.

00:12:56.210 --> 00:13:00.170 align:middle line:84%
You might also require to have
a rule which allows connection

00:13:00.170 --> 00:13:04.617 align:middle line:84%
to a SIM system so the
administrators can go and look

00:13:04.617 --> 00:13:08.800 align:middle line:84%
at alerts on that SIM
system by using their PAWs.

00:13:08.800 --> 00:13:12.440 align:middle line:84%
But again this is a very
limited core set of rules

00:13:12.440 --> 00:13:13.590 align:middle line:90%
that we have in here.

00:13:13.590 --> 00:13:15.590 align:middle line:84%
And this is the only
outbound connections

00:13:15.590 --> 00:13:19.360 align:middle line:84%
which we are allowing
from our PAW machine.

00:13:19.360 --> 00:13:21.630 align:middle line:84%
Now, other than that,
you'll see that we actually

00:13:21.630 --> 00:13:25.740 align:middle line:84%
allow unrestricted
outbound RDP connection.

00:13:25.740 --> 00:13:30.230 align:middle line:84%
So from our PAW machine you
can perform unrestricted RDP

00:13:30.230 --> 00:13:30.862 align:middle line:90%
connections.

00:13:30.862 --> 00:13:32.820 align:middle line:84%
And that's really the
purpose of having the PAW

00:13:32.820 --> 00:13:35.520 align:middle line:84%
machine because you want to
manage your servers remotely

00:13:35.520 --> 00:13:39.130 align:middle line:84%
from here, and in this case
that would be [? our ?] RDP

00:13:39.130 --> 00:13:41.910 align:middle line:84%
but you can use any other tool
that you might desire instead.

00:13:41.910 --> 00:13:45.300 align:middle line:90%


00:13:45.300 --> 00:13:49.800 align:middle line:84%
The final GPO which I want to
discuss is the IPsec RDP one.

00:13:49.800 --> 00:13:53.280 align:middle line:84%
The purpose of
this GPO is to use

00:13:53.280 --> 00:13:58.920 align:middle line:84%
IPsec to establish a secure
channel between the PAW

00:13:58.920 --> 00:14:01.890 align:middle line:90%
machine and our tier-0 systems.

00:14:01.890 --> 00:14:06.130 align:middle line:84%
And by doing so we can perform
Kerberos authentication,

00:14:06.130 --> 00:14:08.940 align:middle line:84%
such that our remote
servers are only

00:14:08.940 --> 00:14:11.250 align:middle line:84%
going to allow RDP
connections if they

00:14:11.250 --> 00:14:13.290 align:middle line:90%
come from our PAW machines.

00:14:13.290 --> 00:14:17.940 align:middle line:84%
And to demonstrate this,
I have the policy also

00:14:17.940 --> 00:14:20.790 align:middle line:84%
created on our domain
controllers, which will only

00:14:20.790 --> 00:14:25.410 align:middle line:84%
allow incoming connections if
they originate from this PAW

00:14:25.410 --> 00:14:27.330 align:middle line:90%
machine.

00:14:27.330 --> 00:14:31.370 align:middle line:84%
And I can show you how the
configuration for allowing this

00:14:31.370 --> 00:14:32.630 align:middle line:90%
is created.

00:14:32.630 --> 00:14:35.000 align:middle line:84%
It is, again, the
Windows host firewall.

00:14:35.000 --> 00:14:38.270 align:middle line:84%
And this is one of those hidden
features of the host firewall

00:14:38.270 --> 00:14:41.200 align:middle line:90%
which is really, really nice.

00:14:41.200 --> 00:14:44.805 align:middle line:84%
So if I look at allowed
incoming connections,

00:14:44.805 --> 00:14:50.970 align:middle line:84%
I will see that we're not going
to allow incoming connections

00:14:50.970 --> 00:14:54.660 align:middle line:84%
unless they are
explicitly allowed in here

00:14:54.660 --> 00:14:58.710 align:middle line:84%
and we also specify
the remote connections

00:14:58.710 --> 00:15:01.710 align:middle line:84%
which will be given the
opportunity to connect

00:15:01.710 --> 00:15:04.920 align:middle line:90%
if they have authenticated.

00:15:04.920 --> 00:15:06.900 align:middle line:84%
In this case, the
only machine which

00:15:06.900 --> 00:15:13.770 align:middle line:84%
we allowed to perform this
RDP connection on port 3389

00:15:13.770 --> 00:15:16.740 align:middle line:90%
is the machine called PAW01.

00:15:16.740 --> 00:15:19.970 align:middle line:84%
So let's see how this
works in reality.

00:15:19.970 --> 00:15:24.150 align:middle line:84%
I will go to my PAW
machine, which is just here.

00:15:24.150 --> 00:15:29.160 align:middle line:84%
Then I will attempt to perform a
remote connection to our domain

00:15:29.160 --> 00:15:30.480 align:middle line:90%
controller.

00:15:30.480 --> 00:15:34.230 align:middle line:84%
First connect, it might take
about 10 seconds for the IPsec

00:15:34.230 --> 00:15:37.410 align:middle line:84%
to get established and then I'll
get prompted to authenticate

00:15:37.410 --> 00:15:39.310 align:middle line:90%
with any user that they want.

00:15:39.310 --> 00:15:42.390 align:middle line:84%
And in this case, I'll
use a tier-0 account

00:15:42.390 --> 00:15:46.140 align:middle line:84%
if I wanted to connect
to a tier-0 system

00:15:46.140 --> 00:15:49.510 align:middle line:84%
such as the main controllers,
and this is how it works.

00:15:49.510 --> 00:15:53.410 align:middle line:84%
Now, if I look at a non-PAW
machine, for example,

00:15:53.410 --> 00:15:57.430 align:middle line:84%
this server, I have server
01 and if I try to perform

00:15:57.430 --> 00:16:00.100 align:middle line:84%
the same RDP connection
from the server,

00:16:00.100 --> 00:16:03.520 align:middle line:84%
this connection will just
hang and in about 30 seconds

00:16:03.520 --> 00:16:07.810 align:middle line:84%
or so it's going to error out
because this machine is not

00:16:07.810 --> 00:16:10.570 align:middle line:84%
allowed to perform this
type of remote connections.

00:16:10.570 --> 00:16:13.600 align:middle line:84%
And in this case, we have
allowed this one for RDP

00:16:13.600 --> 00:16:17.200 align:middle line:84%
but it can also be configured
for any other protocols.

00:16:17.200 --> 00:16:20.260 align:middle line:84%
Here we can see error
that the server is not

00:16:20.260 --> 00:16:22.940 align:middle line:90%
allowed to connect.

00:16:22.940 --> 00:16:24.950 align:middle line:84%
The PAW machine
also has something

00:16:24.950 --> 00:16:27.740 align:middle line:84%
that is interesting in
the user right assignment

00:16:27.740 --> 00:16:32.150 align:middle line:84%
GPO, which is defining the
administrators of the PAW

00:16:32.150 --> 00:16:34.040 align:middle line:90%
machine.

00:16:34.040 --> 00:16:35.870 align:middle line:84%
We again, since
we're not allowing

00:16:35.870 --> 00:16:38.480 align:middle line:84%
domain names or
any privileged user

00:16:38.480 --> 00:16:41.270 align:middle line:84%
to be allowed to
log in to PAW, we

00:16:41.270 --> 00:16:43.980 align:middle line:84%
need to have different
means of managing it.

00:16:43.980 --> 00:16:46.730 align:middle line:84%
And what I've shown in here is
that I have created a separate

00:16:46.730 --> 00:16:50.300 align:middle line:84%
group called PAW admins and
whoever is a member of this

00:16:50.300 --> 00:16:54.380 align:middle line:84%
group cannot be a member of any
of our other privileged groups

00:16:54.380 --> 00:16:57.600 align:middle line:84%
because the other groups are
denied access to the PAW.

00:16:57.600 --> 00:17:02.960 align:middle line:84%
So this PAW admin account
will be only an account

00:17:02.960 --> 00:17:05.599 align:middle line:90%
that is used on a PAW.

00:17:05.599 --> 00:17:08.599 align:middle line:84%
And this group is going
to be added automatically

00:17:08.599 --> 00:17:10.880 align:middle line:84%
to the built-in
administrator's account

00:17:10.880 --> 00:17:12.500 align:middle line:84%
and whoever is a
member of this group

00:17:12.500 --> 00:17:16.130 align:middle line:84%
will be an administrator
on the PAW.

00:17:16.130 --> 00:17:20.150 align:middle line:84%
It's important to note that the
users who use the PAW machine

00:17:20.150 --> 00:17:23.119 align:middle line:84%
are not administrators
on this machine.

00:17:23.119 --> 00:17:25.369 align:middle line:84%
Administration on this
machine should only

00:17:25.369 --> 00:17:30.800 align:middle line:84%
be required if necessary by a
personnel that has the ability

00:17:30.800 --> 00:17:34.250 align:middle line:84%
and understanding of the
issues that they may create

00:17:34.250 --> 00:17:36.280 align:middle line:90%
by changing the configuration.

00:17:36.280 --> 00:17:40.740 align:middle line:84%
Let's just simply list the
administrators on this machine.

00:17:40.740 --> 00:17:43.370 align:middle line:84%
And what we're going
to see is that those

00:17:43.370 --> 00:17:45.600 align:middle line:84%
are the group which
we just mentioned,

00:17:45.600 --> 00:17:48.950 align:middle line:84%
PAW admins, which come from
the GPO and the account

00:17:48.950 --> 00:17:49.880 align:middle line:90%
administrator.

00:17:49.880 --> 00:17:53.330 align:middle line:84%
The account administrator is
always added by default and we

00:17:53.330 --> 00:17:58.670 align:middle line:84%
cannot remove it from the group
policy object but it's not bad

00:17:58.670 --> 00:18:02.810 align:middle line:84%
to have this account as a way
in to get into the machine.

00:18:02.810 --> 00:18:04.490 align:middle line:84%
And usually this
account is going

00:18:04.490 --> 00:18:07.020 align:middle line:84%
to be managed by a
tool such as LAPS

00:18:07.020 --> 00:18:10.520 align:middle line:84%
so the password is going to
be unique for each machine

00:18:10.520 --> 00:18:12.680 align:middle line:84%
and only domain
administrators will

00:18:12.680 --> 00:18:15.210 align:middle line:90%
have the ability to obtain it.

00:18:15.210 --> 00:18:18.870 align:middle line:84%
I hope that this video gave
you a good introduction of what

00:18:18.870 --> 00:18:21.630 align:middle line:84%
a PAW machine is and
the purpose of it.

00:18:21.630 --> 00:18:24.480 align:middle line:84%
But the real idea is to
lock it down and only

00:18:24.480 --> 00:18:28.500 align:middle line:84%
use it for administrative
tasks in our environment.

00:18:28.500 --> 00:18:29.000 align:middle line:90%