WEBVTT

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


00:00:04.284 --> 00:00:07.140 align:middle line:90%
[SMOOTH MUSIC]

00:00:07.140 --> 00:00:10.010 align:middle line:90%


00:00:10.010 --> 00:00:11.990 align:middle line:84%
In order to get started
with enumeration,

00:00:11.990 --> 00:00:16.190 align:middle line:84%
we first need to cover
servers and services.

00:00:16.190 --> 00:00:18.600 align:middle line:84%
We're going to work to try
to answer these questions.

00:00:18.600 --> 00:00:19.860 align:middle line:90%
What is a service?

00:00:19.860 --> 00:00:21.290 align:middle line:90%
What is a server?

00:00:21.290 --> 00:00:23.150 align:middle line:90%
Why are they important?

00:00:23.150 --> 00:00:27.688 align:middle line:84%
And what do they mean
to cybersecurity?

00:00:27.688 --> 00:00:29.480 align:middle line:84%
When you think about
a server, you probably

00:00:29.480 --> 00:00:31.790 align:middle line:90%
picture something like this.

00:00:31.790 --> 00:00:34.490 align:middle line:84%
A server farm with a bunch
of computers all connected

00:00:34.490 --> 00:00:36.260 align:middle line:84%
in an efficient
manner for controlling

00:00:36.260 --> 00:00:39.140 align:middle line:84%
the electricity,
connectivity, and temperature

00:00:39.140 --> 00:00:40.470 align:middle line:90%
of each machine.

00:00:40.470 --> 00:00:44.320 align:middle line:90%
But what is it really doing?

00:00:44.320 --> 00:00:47.890 align:middle line:84%
Well, server is called a
server not because it's

00:00:47.890 --> 00:00:50.170 align:middle line:84%
a special piece of
computer hardware,

00:00:50.170 --> 00:00:51.970 align:middle line:90%
it's because of what it does.

00:00:51.970 --> 00:00:56.180 align:middle line:84%
It serves something
up for the user.

00:00:56.180 --> 00:00:58.640 align:middle line:84%
It provides some sort of
functionality specialized

00:00:58.640 --> 00:01:01.205 align:middle line:84%
to that machine that can be
utilized from other devices.

00:01:01.205 --> 00:01:05.030 align:middle line:90%


00:01:05.030 --> 00:01:08.030 align:middle line:84%
We most often think about
this in an office context,

00:01:08.030 --> 00:01:09.860 align:middle line:84%
where we have a bunch
of computers used

00:01:09.860 --> 00:01:11.720 align:middle line:90%
by many different employees.

00:01:11.720 --> 00:01:14.720 align:middle line:84%
To work efficiently,
we pool resources ,

00:01:14.720 --> 00:01:18.590 align:middle line:84%
such as file storage, or email,
or even administrative control,

00:01:18.590 --> 00:01:19.625 align:middle line:90%
over the entire network.

00:01:19.625 --> 00:01:22.350 align:middle line:90%


00:01:22.350 --> 00:01:25.410 align:middle line:84%
We pool these resources
in specialized computers,

00:01:25.410 --> 00:01:27.030 align:middle line:90%
those computers we call servers.

00:01:27.030 --> 00:01:29.890 align:middle line:90%


00:01:29.890 --> 00:01:32.290 align:middle line:84%
The server can be running
a Windows operating system,

00:01:32.290 --> 00:01:33.580 align:middle line:90%
a Linux operating system.

00:01:33.580 --> 00:01:37.000 align:middle line:84%
It could even be
running macOS server.

00:01:37.000 --> 00:01:39.940 align:middle line:84%
Technically, any computer
could be a server

00:01:39.940 --> 00:01:42.820 align:middle line:90%
depending on how you set it up.

00:01:42.820 --> 00:01:44.560 align:middle line:84%
Different operating
systems are used

00:01:44.560 --> 00:01:47.890 align:middle line:84%
because of licensing or
compatibility, or in order

00:01:47.890 --> 00:01:50.290 align:middle line:90%
to streamline operations.

00:01:50.290 --> 00:01:54.220 align:middle line:84%
In the end, either way, it
means the same thing to us

00:01:54.220 --> 00:01:59.330 align:middle line:84%
security professionals because
we still face the same problem.

00:01:59.330 --> 00:02:03.860 align:middle line:84%
Servers by their very nature
need to be accessed remotely.

00:02:03.860 --> 00:02:06.740 align:middle line:84%
Pooling resources works so
that multiple workstations

00:02:06.740 --> 00:02:10.250 align:middle line:90%
can access the same features.

00:02:10.250 --> 00:02:12.650 align:middle line:84%
The services running
on a server require

00:02:12.650 --> 00:02:16.730 align:middle line:84%
opening up a listening
port on the server

00:02:16.730 --> 00:02:19.850 align:middle line:84%
and accepting
connections remotely.

00:02:19.850 --> 00:02:21.530 align:middle line:90%
I like analogies.

00:02:21.530 --> 00:02:23.640 align:middle line:84%
If you want to go to a
drive-thru restaurant,

00:02:23.640 --> 00:02:26.780 align:middle line:84%
someone has to open a window,
reach out, and hand you

00:02:26.780 --> 00:02:28.290 align:middle line:90%
your food.

00:02:28.290 --> 00:02:30.060 align:middle line:84%
There has to be
some sort of break

00:02:30.060 --> 00:02:31.920 align:middle line:84%
in the barrier
around the building,

00:02:31.920 --> 00:02:34.950 align:middle line:84%
and that allows things to
be passed from one side

00:02:34.950 --> 00:02:36.480 align:middle line:90%
to the other.

00:02:36.480 --> 00:02:38.760 align:middle line:84%
On purpose in this
case, but the same

00:02:38.760 --> 00:02:40.620 align:middle line:84%
is essentially
true for a server.

00:02:40.620 --> 00:02:44.550 align:middle line:84%
We purposefully open up the
barrier protecting the computer

00:02:44.550 --> 00:02:47.820 align:middle line:84%
and allow access to
a program remotely.

00:02:47.820 --> 00:02:53.430 align:middle line:84%
That situation in and of itself
isn't necessarily a problem.

00:02:53.430 --> 00:02:56.670 align:middle line:84%
The problem lies in that
inherent bugs or flaws

00:02:56.670 --> 00:02:58.920 align:middle line:84%
or even features or
misconfigurations

00:02:58.920 --> 00:03:04.500 align:middle line:84%
in the software can give remote
access to the whole system.

00:03:04.500 --> 00:03:06.720 align:middle line:84%
This could let attackers
into the system

00:03:06.720 --> 00:03:09.207 align:middle line:84%
to do whatever they want,
and that's exactly what we're

00:03:09.207 --> 00:03:10.290 align:middle line:90%
trying to protect against.

00:03:10.290 --> 00:03:13.977 align:middle line:90%


00:03:13.977 --> 00:03:15.560 align:middle line:84%
In the rest of the
course, we're going

00:03:15.560 --> 00:03:18.110 align:middle line:84%
to look at different protocols,
services, and software

00:03:18.110 --> 00:03:23.450 align:middle line:84%
that you would see on a
server and could allow exactly

00:03:23.450 --> 00:03:24.870 align:middle line:90%
what we're talking about.

00:03:24.870 --> 00:03:27.000 align:middle line:84%
We're not going to cover
every possible software.

00:03:27.000 --> 00:03:29.970 align:middle line:84%
We're not going to cover every
possible protocol or service.

00:03:29.970 --> 00:03:32.270 align:middle line:84%
But we're going to
cover some common ones

00:03:32.270 --> 00:03:37.480 align:middle line:84%
that you can understand and
move forward from there.

00:03:37.480 --> 00:03:38.000 align:middle line:90%