WEBVTT

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


00:00:03.416 --> 00:00:06.832 align:middle line:90%
[MUSIC PLAYING]

00:00:06.832 --> 00:00:10.260 align:middle line:90%


00:00:10.260 --> 00:00:14.070 align:middle line:84%
In our first lesson
on vulnerabilities,

00:00:14.070 --> 00:00:20.210 align:middle line:84%
we're going to start with,
what is a vulnerability?

00:00:20.210 --> 00:00:25.570 align:middle line:84%
So you might think many
different things, frankly,

00:00:25.570 --> 00:00:28.240 align:middle line:84%
when you start thinking about
what a vulnerability is.

00:00:28.240 --> 00:00:30.490 align:middle line:84%
For anyone who's been around
in the space for a while,

00:00:30.490 --> 00:00:33.430 align:middle line:84%
you might automatically
go to CVEs.

00:00:33.430 --> 00:00:36.040 align:middle line:84%
And while that is important
and it's definitely

00:00:36.040 --> 00:00:37.990 align:middle line:84%
something we're going
to cover, there's

00:00:37.990 --> 00:00:41.680 align:middle line:84%
more to vulnerabilities
than just that.

00:00:41.680 --> 00:00:44.890 align:middle line:84%
NIST had a nice
definition of it for us.

00:00:44.890 --> 00:00:46.180 align:middle line:90%
It's very technical.

00:00:46.180 --> 00:00:50.290 align:middle line:84%
A weakness in
computational logic code

00:00:50.290 --> 00:00:52.060 align:middle line:84%
found in software and
hardware components

00:00:52.060 --> 00:00:55.390 align:middle line:84%
that, when exploited,
results in a negative impact

00:00:55.390 --> 00:00:58.330 align:middle line:84%
to confidentiality,
integrity, and availability--

00:00:58.330 --> 00:01:00.295 align:middle line:90%
or availability, and/or.

00:01:00.295 --> 00:01:03.490 align:middle line:90%


00:01:03.490 --> 00:01:06.520 align:middle line:84%
I like to think of
it all like a heist.

00:01:06.520 --> 00:01:09.303 align:middle line:84%
I love thinking about
cybersecurity like a heist

00:01:09.303 --> 00:01:11.470 align:middle line:84%
because what we're trying
to do is protect something

00:01:11.470 --> 00:01:12.970 align:middle line:90%
that other people want to get.

00:01:12.970 --> 00:01:16.750 align:middle line:84%
Now, in a heist,
thinking of a heist movie

00:01:16.750 --> 00:01:17.980 align:middle line:90%
or real life crime--

00:01:17.980 --> 00:01:18.670 align:middle line:90%
I don't know.

00:01:18.670 --> 00:01:20.045 align:middle line:84%
This stuff might
actually happen.

00:01:20.045 --> 00:01:21.970 align:middle line:90%
I just don't hear about it.

00:01:21.970 --> 00:01:22.750 align:middle line:90%
There's jewels.

00:01:22.750 --> 00:01:23.650 align:middle line:90%
There's money.

00:01:23.650 --> 00:01:26.440 align:middle line:84%
There's information that's
being stored somewhere.

00:01:26.440 --> 00:01:30.683 align:middle line:84%
And a group or an individual
is trying to get access to it.

00:01:30.683 --> 00:01:32.350 align:middle line:84%
And if you think about
any of the movies

00:01:32.350 --> 00:01:33.370 align:middle line:90%
that you might watch--

00:01:33.370 --> 00:01:35.140 align:middle line:90%
I love heist movies--

00:01:35.140 --> 00:01:38.230 align:middle line:84%
there's so many different
pieces that go into it

00:01:38.230 --> 00:01:39.910 align:middle line:90%
that they have to think about.

00:01:39.910 --> 00:01:43.310 align:middle line:84%
And there's many
different vulnerabilities.

00:01:43.310 --> 00:01:46.570 align:middle line:84%
There's little things that
can be exploited to get in.

00:01:46.570 --> 00:01:49.280 align:middle line:90%


00:01:49.280 --> 00:01:53.300 align:middle line:84%
Now, generally, for a
heist or bank robbery,

00:01:53.300 --> 00:01:57.140 align:middle line:84%
you might be thinking about
physical vulnerabilities.

00:01:57.140 --> 00:02:00.200 align:middle line:84%
And that's a layer
on the OSI model.

00:02:00.200 --> 00:02:05.810 align:middle line:84%
We got to think of the full
stack of the OSI model.

00:02:05.810 --> 00:02:07.700 align:middle line:90%
And the physical layer is there.

00:02:07.700 --> 00:02:08.780 align:middle line:90%
You can cut power.

00:02:08.780 --> 00:02:11.090 align:middle line:90%
You can cut lines.

00:02:11.090 --> 00:02:12.590 align:middle line:90%
You could gain physical access.

00:02:12.590 --> 00:02:16.340 align:middle line:90%
You could get around people.

00:02:16.340 --> 00:02:17.780 align:middle line:90%
That is very important.

00:02:17.780 --> 00:02:19.430 align:middle line:84%
And that's something
that we have

00:02:19.430 --> 00:02:22.160 align:middle line:84%
to worry about ourselves when
talking about cybersecurity.

00:02:22.160 --> 00:02:24.860 align:middle line:90%
There are physical controls.

00:02:24.860 --> 00:02:27.080 align:middle line:84%
And that is something
that's really important.

00:02:27.080 --> 00:02:36.000 align:middle line:84%
Man traps, vaults, proper door
locks, gates, fences, lighting,

00:02:36.000 --> 00:02:39.690 align:middle line:84%
cameras, those are all
parts of physical controls.

00:02:39.690 --> 00:02:45.070 align:middle line:84%
And there can be vulnerabilities
in those as well.

00:02:45.070 --> 00:02:49.650 align:middle line:84%
Let's move to some more in
the computer type things.

00:02:49.650 --> 00:02:55.320 align:middle line:84%
Cybersecurity
vulnerabilities-- they

00:02:55.320 --> 00:02:59.400 align:middle line:84%
are weakness which can be
exploited by a threat actor.

00:02:59.400 --> 00:03:05.370 align:middle line:84%
And there is a whole course
specifically about host

00:03:05.370 --> 00:03:08.970 align:middle line:84%
and system based attacks, where
you will dive in and learn

00:03:08.970 --> 00:03:15.960 align:middle line:84%
how to exploit really well
vulnerabilities on a machine,

00:03:15.960 --> 00:03:18.520 align:middle line:84%
usually about the operating
system or a service running

00:03:18.520 --> 00:03:19.020 align:middle line:90%
on it.

00:03:19.020 --> 00:03:23.250 align:middle line:90%


00:03:23.250 --> 00:03:25.760 align:middle line:84%
And those are the
common places where

00:03:25.760 --> 00:03:28.430 align:middle line:84%
these technical
vulnerabilities come from,

00:03:28.430 --> 00:03:32.930 align:middle line:84%
from the operating system
itself or a service that

00:03:32.930 --> 00:03:37.430 align:middle line:84%
is part of the operating
system or in something that's

00:03:37.430 --> 00:03:40.910 align:middle line:84%
been installed, a service
that's running that's software

00:03:40.910 --> 00:03:44.220 align:middle line:90%
installed on that machine.

00:03:44.220 --> 00:03:48.080 align:middle line:84%
So these can be found either
by DevSec engineers, people

00:03:48.080 --> 00:03:51.410 align:middle line:84%
who are looking at applications,
updating them, looking

00:03:51.410 --> 00:03:53.780 align:middle line:84%
for these vulnerabilities
in the products

00:03:53.780 --> 00:03:57.140 align:middle line:84%
that they're putting out or
that they're now working on

00:03:57.140 --> 00:03:58.400 align:middle line:90%
for their team.

00:03:58.400 --> 00:04:01.730 align:middle line:84%
Security researchers--
got some good friends

00:04:01.730 --> 00:04:08.630 align:middle line:84%
who go ahead and do this
on the regular for MSSPs

00:04:08.630 --> 00:04:14.630 align:middle line:84%
or researching firms trying to
find vulnerabilities to better

00:04:14.630 --> 00:04:18.350 align:middle line:84%
our infrastructure,
our ecosystem.

00:04:18.350 --> 00:04:20.750 align:middle line:84%
Pen testers often
find vulnerabilities.

00:04:20.750 --> 00:04:22.700 align:middle line:84%
The difference
between a pen tester

00:04:22.700 --> 00:04:29.888 align:middle line:84%
and a cybersecurity researcher
is a very narrow line.

00:04:29.888 --> 00:04:31.430 align:middle line:84%
It all depends on
what your scope is,

00:04:31.430 --> 00:04:32.638 align:middle line:90%
what you're doing day to day.

00:04:32.638 --> 00:04:34.820 align:middle line:90%
But they think a lot the same.

00:04:34.820 --> 00:04:37.790 align:middle line:84%
Software developers might find
their own vulnerabilities.

00:04:37.790 --> 00:04:40.340 align:middle line:84%
They might find vulnerabilities
in other people's code.

00:04:40.340 --> 00:04:45.440 align:middle line:84%
Again, the lines between these
different roles are very thin.

00:04:45.440 --> 00:04:47.840 align:middle line:84%
Users-- users often
find vulnerabilities.

00:04:47.840 --> 00:04:51.290 align:middle line:84%
And by playing
like a user, that's

00:04:51.290 --> 00:04:54.620 align:middle line:84%
often how researchers
or pen testers come

00:04:54.620 --> 00:04:56.617 align:middle line:90%
across some vulnerabilities.

00:04:56.617 --> 00:05:00.100 align:middle line:90%


00:05:00.100 --> 00:05:04.450 align:middle line:84%
Fortunately, the United
States government in it's

00:05:04.450 --> 00:05:08.140 align:middle line:84%
always putting a lot of money
and effort behind things

00:05:08.140 --> 00:05:13.720 align:middle line:84%
no matter what has a national
cybersecurity federally funded

00:05:13.720 --> 00:05:17.050 align:middle line:84%
research and development
center that worries about CVEs,

00:05:17.050 --> 00:05:19.210 align:middle line:90%
that tracks the CVE program.

00:05:19.210 --> 00:05:22.930 align:middle line:84%
CVE is being common
vulnerabilities and exposures.

00:05:22.930 --> 00:05:25.210 align:middle line:84%
And there is a CVE
website that is

00:05:25.210 --> 00:05:28.060 align:middle line:90%
managed by MITRE Corporation.

00:05:28.060 --> 00:05:35.020 align:middle line:84%
They maintain the system and a
lot of the logistics behind it.

00:05:35.020 --> 00:05:37.690 align:middle line:84%
And it's funded through
the National Cyber Security

00:05:37.690 --> 00:05:44.470 align:middle line:84%
Division of US Department of
Homeland Security since 1999.

00:05:44.470 --> 00:05:46.540 align:middle line:84%
Or at least it's been
around since 1999.

00:05:46.540 --> 00:05:48.040 align:middle line:90%
Homeland Security-- not so much.

00:05:48.040 --> 00:05:50.950 align:middle line:90%


00:05:50.950 --> 00:05:54.340 align:middle line:84%
We've got NIST, who maintains
the National Vulnerability

00:05:54.340 --> 00:05:55.360 align:middle line:90%
Database.

00:05:55.360 --> 00:05:58.420 align:middle line:90%
It's very similar, very related.

00:05:58.420 --> 00:06:03.820 align:middle line:84%
And we will take a look at both
the CVE page and the National

00:06:03.820 --> 00:06:07.180 align:middle line:90%
Vulnerability Database.

00:06:07.180 --> 00:06:09.940 align:middle line:90%
Now, CVEs have identifiers.

00:06:09.940 --> 00:06:14.050 align:middle line:84%
You could also call it a CVE
name, number, IDs, or just

00:06:14.050 --> 00:06:16.672 align:middle line:90%
CVEs, CVE blank.

00:06:16.672 --> 00:06:18.130 align:middle line:84%
A few that we're
going to look at--

00:06:18.130 --> 00:06:22.660 align:middle line:90%
CVE-2021-44228, Log4j.

00:06:22.660 --> 00:06:26.740 align:middle line:84%
If you're seeing this,
there's a fresh course.

00:06:26.740 --> 00:06:30.370 align:middle line:84%
You might not want to hear
that term, Log4j, right now.

00:06:30.370 --> 00:06:35.770 align:middle line:84%
CVE-2014-0160, which was the
Heartbleed vulnerability--

00:06:35.770 --> 00:06:37.220 align:middle line:90%
we'll dive into that one.

00:06:37.220 --> 00:06:45.040 align:middle line:84%
And then CVE-2017-0143
or MS MS17-010,

00:06:45.040 --> 00:06:50.320 align:middle line:84%
also known as EternalBlue, part
of the WannaCry ransomware.

00:06:50.320 --> 00:06:53.420 align:middle line:90%
And NotPetya and a few others.

00:06:53.420 --> 00:06:57.460 align:middle line:84%
These are vulnerabilities
that had high impact

00:06:57.460 --> 00:07:00.670 align:middle line:84%
or were critical
vulnerabilities.

00:07:00.670 --> 00:07:04.390 align:middle line:84%
And we'll dive into what all
that means with some examples

00:07:04.390 --> 00:07:07.410 align:middle line:90%
in just a second.

00:07:07.410 --> 00:07:09.850 align:middle line:84%
The things that we kind
of need to understand

00:07:09.850 --> 00:07:14.440 align:middle line:84%
and get comfortable looking at
are the vulnerability details

00:07:14.440 --> 00:07:15.058 align:middle line:90%
pages.

00:07:15.058 --> 00:07:16.600 align:middle line:84%
So there's going to
be a description.

00:07:16.600 --> 00:07:17.830 align:middle line:90%
It'll go into severity.

00:07:17.830 --> 00:07:19.810 align:middle line:84%
And we'll talk about
severity while we're

00:07:19.810 --> 00:07:21.280 align:middle line:90%
looking at the page.

00:07:21.280 --> 00:07:22.900 align:middle line:84%
And there's a nice
tool that we can

00:07:22.900 --> 00:07:27.860 align:middle line:84%
look at to kind of weigh
the severity ourselves

00:07:27.860 --> 00:07:30.670 align:middle line:84%
to criticality, depending
on our situation

00:07:30.670 --> 00:07:40.240 align:middle line:84%
and how a vulnerability actually
goes from the impetus to being

00:07:40.240 --> 00:07:42.940 align:middle line:90%
exploited or used.

00:07:42.940 --> 00:07:46.750 align:middle line:84%
Some weakness enumeration
and preferences--

00:07:46.750 --> 00:07:49.570 align:middle line:84%
what white papers,
what exploits,

00:07:49.570 --> 00:07:52.900 align:middle line:84%
what proof of concepts
have been collected

00:07:52.900 --> 00:07:56.440 align:middle line:90%
as part of the database.

00:07:56.440 --> 00:08:01.090 align:middle line:84%
Again, this enumeration,
what do they produce

00:08:01.090 --> 00:08:03.820 align:middle line:84%
or what has been collected
so that these vulnerabilities

00:08:03.820 --> 00:08:06.820 align:middle line:84%
can be found more easily
by vulnerability scanners

00:08:06.820 --> 00:08:09.910 align:middle line:90%
or other research firms?

00:08:09.910 --> 00:08:12.250 align:middle line:84%
And then known affected
software configurations--

00:08:12.250 --> 00:08:13.810 align:middle line:90%
that's also quite important.

00:08:13.810 --> 00:08:15.400 align:middle line:84%
Those are things
that as a pen tester

00:08:15.400 --> 00:08:17.025 align:middle line:84%
you might want to
become familiar with.

00:08:17.025 --> 00:08:19.150 align:middle line:84%
Some of the obvious
ones come out at you.

00:08:19.150 --> 00:08:23.750 align:middle line:84%
And we'll talk about
those when we get there.

00:08:23.750 --> 00:08:27.490 align:middle line:84%
But others-- if someone
is implementing,

00:08:27.490 --> 00:08:29.590 align:middle line:84%
these software
configurations, they

00:08:29.590 --> 00:08:33.280 align:middle line:84%
need to be aware that the
vulnerabilities exist in them

00:08:33.280 --> 00:08:36.130 align:middle line:90%
prior to implementation.

00:08:36.130 --> 00:08:38.770 align:middle line:90%
And we'll get to it later.

00:08:38.770 --> 00:08:41.409 align:middle line:84%
But accepting certain
levels of vulnerability,

00:08:41.409 --> 00:08:46.900 align:middle line:84%
certain levels of risk, it's
kind of up to the organization.

00:08:46.900 --> 00:08:51.590 align:middle line:84%
But they need to be aware
of what is out there.

00:08:51.590 --> 00:08:59.260 align:middle line:84%
So we're going to swap
on over to the CVE page.

00:08:59.260 --> 00:09:04.430 align:middle line:90%
This is CVE-2021-44228 Log4j.

00:09:04.430 --> 00:09:06.850 align:middle line:84%
And let's take a
look at what we got.

00:09:06.850 --> 00:09:07.910 align:middle line:90%
We have the CVE ID.

00:09:07.910 --> 00:09:09.910 align:middle line:84%
And there's a link to the
National Vulnerability

00:09:09.910 --> 00:09:11.320 align:middle line:90%
Database.

00:09:11.320 --> 00:09:13.060 align:middle line:90%
They are interconnected.

00:09:13.060 --> 00:09:15.130 align:middle line:90%
And we will look at both.

00:09:15.130 --> 00:09:17.822 align:middle line:90%


00:09:17.822 --> 00:09:19.030 align:middle line:90%
Then we've got a description.

00:09:19.030 --> 00:09:24.490 align:middle line:84%
And so this one, it says that
Apache Log4j 2.0-beta9 through

00:09:24.490 --> 00:09:31.720 align:middle line:84%
to 2.12.1 JNDI features used
in configuration, log messages,

00:09:31.720 --> 00:09:35.170 align:middle line:84%
and parameters do not protect
against attacker controlled

00:09:35.170 --> 00:09:38.920 align:middle line:84%
LDAP and other JNDI
related endpoints.

00:09:38.920 --> 00:09:42.520 align:middle line:84%
Now, this might not make
any sense to you right now.

00:09:42.520 --> 00:09:43.600 align:middle line:90%
And that's fine.

00:09:43.600 --> 00:09:47.650 align:middle line:84%
In the next lesson,
we're going to go

00:09:47.650 --> 00:09:49.330 align:middle line:84%
into the details of
what all this means

00:09:49.330 --> 00:09:50.800 align:middle line:90%
and what it means for an attack.

00:09:50.800 --> 00:09:53.980 align:middle line:84%
But you can see here that
there's a description of what's

00:09:53.980 --> 00:09:54.680 align:middle line:90%
going on.

00:09:54.680 --> 00:09:56.410 align:middle line:90%
There's some technical jargon.

00:09:56.410 --> 00:09:58.150 align:middle line:84%
And if you weren't
a programmer, if you

00:09:58.150 --> 00:10:01.482 align:middle line:84%
haven't worked with Java, if
you aren't familiar with LDAP,

00:10:01.482 --> 00:10:03.440 align:middle line:84%
then this might not make
a lot of sense to you.

00:10:03.440 --> 00:10:05.107 align:middle line:84%
And we will get to
that in a little bit.

00:10:05.107 --> 00:10:05.720 align:middle line:90%
I promise.

00:10:05.720 --> 00:10:07.887 align:middle line:84%
But the important thing
here is seeing that there is

00:10:07.887 --> 00:10:13.130 align:middle line:84%
an explanation of what's going
on and we can read that and use

00:10:13.130 --> 00:10:16.010 align:middle line:84%
that later, as you become more
familiar with all of these

00:10:16.010 --> 00:10:18.530 align:middle line:84%
things, because that's
kind of what's required

00:10:18.530 --> 00:10:21.620 align:middle line:84%
in cybersecurity-- become
more aware of the different

00:10:21.620 --> 00:10:24.890 align:middle line:84%
technologies, the
different languages,

00:10:24.890 --> 00:10:30.710 align:middle line:84%
the different software being
used and how we can either

00:10:30.710 --> 00:10:37.010 align:middle line:84%
utilize it for pen test or
help organizations become more

00:10:37.010 --> 00:10:40.400 align:middle line:84%
secure by pointing out the
vulnerabilities and being able

00:10:40.400 --> 00:10:42.500 align:middle line:84%
to explain this and
why this is a problem--

00:10:42.500 --> 00:10:44.150 align:middle line:84%
that's going to
go in our report.

00:10:44.150 --> 00:10:45.860 align:middle line:84%
We need to understand
what this means.

00:10:45.860 --> 00:10:50.960 align:middle line:84%
If we exploit it and we
can't explain why it matters,

00:10:50.960 --> 00:10:52.940 align:middle line:84%
then there's no
value in our report.

00:10:52.940 --> 00:10:55.970 align:middle line:84%
So that's important
to understand.

00:10:55.970 --> 00:11:00.050 align:middle line:84%
I'll give you the full screen
so you can see it better.

00:11:00.050 --> 00:11:04.130 align:middle line:84%
It goes into some more
detail, some more versioning.

00:11:04.130 --> 00:11:04.940 align:middle line:90%
That's fine.

00:11:04.940 --> 00:11:06.080 align:middle line:90%
There's references.

00:11:06.080 --> 00:11:10.430 align:middle line:84%
And these can include
proof of concepts,

00:11:10.430 --> 00:11:13.850 align:middle line:90%
articles, white papers.

00:11:13.850 --> 00:11:19.040 align:middle line:84%
And these actually feature
different versions of software

00:11:19.040 --> 00:11:23.000 align:middle line:90%
here, which is [INAUDIBLE].

00:11:23.000 --> 00:11:28.670 align:middle line:84%
You can see who the
assigning CNA is.

00:11:28.670 --> 00:11:33.890 align:middle line:84%
And that's the CVE numbering
authority, the CNA.

00:11:33.890 --> 00:11:37.160 align:middle line:84%
This one, its Apache
Software Foundation.

00:11:37.160 --> 00:11:41.930 align:middle line:84%
Apache owns and
produces Java and Log4j.

00:11:41.930 --> 00:11:44.810 align:middle line:90%
So it kind of makes sense.

00:11:44.810 --> 00:11:50.450 align:middle line:84%
See the date created, came out
at the end of November 2021,

00:11:50.450 --> 00:11:54.500 align:middle line:84%
and the date reflected when
it was allocated or reserved,

00:11:54.500 --> 00:11:58.230 align:middle line:84%
not necessarily when
it was discovered.

00:11:58.230 --> 00:11:59.960 align:middle line:90%
So that's important to know.

00:11:59.960 --> 00:12:02.570 align:middle line:90%
That is the CVE page.

00:12:02.570 --> 00:12:04.110 align:middle line:84%
Sometimes there's
more information.

00:12:04.110 --> 00:12:07.730 align:middle line:84%
But this one usually
just launches you

00:12:07.730 --> 00:12:13.910 align:middle line:84%
to the NIST National
Vulnerability Database.

00:12:13.910 --> 00:12:19.160 align:middle line:84%
Now, we see the same
information, CVE-2021-44228,

00:12:19.160 --> 00:12:21.740 align:middle line:84%
with details and
another description.

00:12:21.740 --> 00:12:23.300 align:middle line:90%
These are very, very similar.

00:12:23.300 --> 00:12:27.250 align:middle line:90%


00:12:27.250 --> 00:12:29.170 align:middle line:84%
Pretty much the
exact same language.

00:12:29.170 --> 00:12:35.920 align:middle line:84%
Now, here there is
analysis description,

00:12:35.920 --> 00:12:38.170 align:middle line:84%
which in this situation is
the exact same description.

00:12:38.170 --> 00:12:39.070 align:middle line:90%
That's fine.

00:12:39.070 --> 00:12:43.010 align:middle line:84%
If it gets updated, then this
information might change.

00:12:43.010 --> 00:12:44.290 align:middle line:90%
That's perfectly fine.

00:12:44.290 --> 00:12:45.380 align:middle line:90%
That's good.

00:12:45.380 --> 00:12:47.740 align:middle line:84%
You want the most up to date
information in the database

00:12:47.740 --> 00:12:48.920 align:middle line:90%
correct.

00:12:48.920 --> 00:12:51.160 align:middle line:84%
So here we have a
gauge of severity.

00:12:51.160 --> 00:12:55.560 align:middle line:84%
And there is an older
version and a newer version.

00:12:55.560 --> 00:12:58.930 align:middle line:90%
I tend to just look at the 3.x.

00:12:58.930 --> 00:13:03.580 align:middle line:84%
But there is debate on
which one is more useful.

00:13:03.580 --> 00:13:05.170 align:middle line:90%
And we'll dig into criticality.

00:13:05.170 --> 00:13:07.610 align:middle line:84%
In just second, I'll
come back up to it.

00:13:07.610 --> 00:13:10.960 align:middle line:84%
There's the references to
advisory, solutions, and tools.

00:13:10.960 --> 00:13:14.590 align:middle line:84%
And in here, there's
websites talking

00:13:14.590 --> 00:13:17.570 align:middle line:90%
about how to utilize it.

00:13:17.570 --> 00:13:23.320 align:middle line:84%
We should have some tools and
proof of concepts in here.

00:13:23.320 --> 00:13:27.620 align:middle line:90%


00:13:27.620 --> 00:13:30.020 align:middle line:84%
And then we get into the
weakness enumeration.

00:13:30.020 --> 00:13:32.810 align:middle line:84%
So this, they're created
by these sources.

00:13:32.810 --> 00:13:36.440 align:middle line:84%
So either Apache themselves
or NIST alongside the Apache

00:13:36.440 --> 00:13:39.020 align:middle line:90%
came up with CWE IDs.

00:13:39.020 --> 00:13:42.005 align:middle line:84%
And we could dive into
those and what they mean.

00:13:42.005 --> 00:13:44.900 align:middle line:90%


00:13:44.900 --> 00:13:47.180 align:middle line:84%
But, basically, the
weakness enumeration

00:13:47.180 --> 00:13:52.550 align:middle line:84%
then is part of identifying
how this could be solved

00:13:52.550 --> 00:13:54.710 align:middle line:90%
in the future and avoid it.

00:13:54.710 --> 00:13:57.290 align:middle line:84%
But your known affected
software configurations

00:13:57.290 --> 00:13:58.940 align:middle line:90%
are critically important.

00:13:58.940 --> 00:14:05.400 align:middle line:90%
The CPE is hugely important.

00:14:05.400 --> 00:14:09.920 align:middle line:84%
And if you're at all
curious what a CPE is,

00:14:09.920 --> 00:14:13.370 align:middle line:84%
NIST has this understanding
vulnerability details pages

00:14:13.370 --> 00:14:15.750 align:middle line:90%
and description.

00:14:15.750 --> 00:14:19.820 align:middle line:84%
It gives an explanation of that,
explains severity references

00:14:19.820 --> 00:14:22.160 align:middle line:90%
or what they are.

00:14:22.160 --> 00:14:25.040 align:middle line:84%
But your it affected
software configurations--

00:14:25.040 --> 00:14:28.460 align:middle line:84%
this common platform
enumeration specification

00:14:28.460 --> 00:14:30.448 align:middle line:90%
is very, very, very important.

00:14:30.448 --> 00:14:32.240 align:middle line:84%
This is how vulnerability
scanners are then

00:14:32.240 --> 00:14:38.090 align:middle line:84%
going to take this
signature, if you will,

00:14:38.090 --> 00:14:41.180 align:middle line:84%
to find the vulnerability
throughout an ecosystem,

00:14:41.180 --> 00:14:42.080 align:middle line:90%
throughout a network.

00:14:42.080 --> 00:14:47.420 align:middle line:84%
And you dive in and read
the heck out of this.

00:14:47.420 --> 00:14:49.440 align:middle line:84%
It's worthwhile to get
an understanding of it

00:14:49.440 --> 00:14:52.580 align:middle line:84%
and if you were searching
for a specific vulnerability

00:14:52.580 --> 00:14:54.125 align:middle line:84%
to become familiar
with the CPEs.

00:14:54.125 --> 00:14:58.370 align:middle line:90%


00:14:58.370 --> 00:15:00.710 align:middle line:84%
But there are a lot
of configurations.

00:15:00.710 --> 00:15:02.910 align:middle line:90%
Java is used in a lot of places.

00:15:02.910 --> 00:15:06.830 align:middle line:84%
And over 84% of
Java applications

00:15:06.830 --> 00:15:09.000 align:middle line:90%
utilize the Log4j library.

00:15:09.000 --> 00:15:13.340 align:middle line:84%
So there it is,
all the places it

00:15:13.340 --> 00:15:19.070 align:middle line:84%
is used, which I'm going to
use that to bring us back

00:15:19.070 --> 00:15:21.980 align:middle line:84%
to this base score
for criticality.

00:15:21.980 --> 00:15:28.060 align:middle line:84%
And you can see if I hover
over the critical right there,

00:15:28.060 --> 00:15:28.910 align:middle line:90%
it highlights.

00:15:28.910 --> 00:15:31.080 align:middle line:90%
We can click on it.

00:15:31.080 --> 00:15:34.190 align:middle line:84%
And it brings up the
scoring calculator.

00:15:34.190 --> 00:15:40.850 align:middle line:84%
Now, there are some base
metrics, base score metrics.

00:15:40.850 --> 00:15:46.800 align:middle line:84%
And that 10.0 was a
very big part of it.

00:15:46.800 --> 00:15:50.900 align:middle line:84%
And a lot's based on how
the attack vector gets in.

00:15:50.900 --> 00:15:52.640 align:middle line:90%
It comes through the network.

00:15:52.640 --> 00:15:54.090 align:middle line:90%
You have to be on the network.

00:15:54.090 --> 00:15:55.760 align:middle line:84%
Some of it, you need
physical access.

00:15:55.760 --> 00:15:57.260 align:middle line:90%
You just need local access.

00:15:57.260 --> 00:15:59.390 align:middle line:84%
You can be on an
adjacent network.

00:15:59.390 --> 00:16:02.420 align:middle line:84%
That will change
your base scores--

00:16:02.420 --> 00:16:03.440 align:middle line:90%
the complexity.

00:16:03.440 --> 00:16:05.285 align:middle line:90%
It's not a very complex attack.

00:16:05.285 --> 00:16:08.450 align:middle line:90%


00:16:08.450 --> 00:16:10.610 align:middle line:84%
You're exploiting
the vulnerability.

00:16:10.610 --> 00:16:12.770 align:middle line:84%
It doesn't require
any privileges.

00:16:12.770 --> 00:16:14.220 align:middle line:90%
User interaction is low.

00:16:14.220 --> 00:16:16.520 align:middle line:84%
You don't need someone
else to click on anything.

00:16:16.520 --> 00:16:20.400 align:middle line:84%
The scope in this
situation has changed.

00:16:20.400 --> 00:16:22.910 align:middle line:84%
And you can get into
the details of what all

00:16:22.910 --> 00:16:25.950 align:middle line:84%
that means if you
really want to.

00:16:25.950 --> 00:16:27.290 align:middle line:90%
And then there's the impact.

00:16:27.290 --> 00:16:32.360 align:middle line:84%
And, again, impact
is going to be

00:16:32.360 --> 00:16:36.080 align:middle line:84%
the part that really is going
to matter to our customers.

00:16:36.080 --> 00:16:37.550 align:middle line:90%
They want to know.

00:16:37.550 --> 00:16:39.410 align:middle line:84%
And that's the customers
or our pen test

00:16:39.410 --> 00:16:45.380 align:middle line:84%
or our security net
analysis, if you will.

00:16:45.380 --> 00:16:48.440 align:middle line:84%
Whoever it is that we're
turning over the results to

00:16:48.440 --> 00:16:52.740 align:middle line:84%
and whoever is going to
take this and run with it,

00:16:52.740 --> 00:16:55.860 align:middle line:84%
they need to know what
the potential impact is.

00:16:55.860 --> 00:16:58.880 align:middle line:84%
And so that's why these
are worth looking at.

00:16:58.880 --> 00:17:01.640 align:middle line:84%
Confidentiality,
integrity, and availability

00:17:01.640 --> 00:17:05.690 align:middle line:84%
are very high for this
because if exploited,

00:17:05.690 --> 00:17:08.119 align:middle line:84%
they can run whatever
code they want.

00:17:08.119 --> 00:17:12.560 align:middle line:90%
And you could change data.

00:17:12.560 --> 00:17:14.359 align:middle line:90%
You could deny data.

00:17:14.359 --> 00:17:16.130 align:middle line:90%
You could steal data.

00:17:16.130 --> 00:17:18.890 align:middle line:90%
And that's all three.

00:17:18.890 --> 00:17:21.200 align:middle line:84%
That's all three
sides of the triad.

00:17:21.200 --> 00:17:28.250 align:middle line:84%
Now, if we dig in a
little more, this temporal

00:17:28.250 --> 00:17:33.350 align:middle line:84%
score-- you could see there are
functional exploits that exist

00:17:33.350 --> 00:17:36.200 align:middle line:90%
because it's been exploited.

00:17:36.200 --> 00:17:40.970 align:middle line:84%
The remediation level
has an official fix.

00:17:40.970 --> 00:17:45.200 align:middle line:84%
Java has put out a fix,
and a lot of organizations

00:17:45.200 --> 00:17:48.290 align:middle line:90%
are implementing those changes.

00:17:48.290 --> 00:17:51.110 align:middle line:84%
A lot of software
vendors in this situation

00:17:51.110 --> 00:17:53.230 align:middle line:84%
had to update-- once
they updated the Java,

00:17:53.230 --> 00:17:54.980 align:middle line:84%
then they had to update
their application,

00:17:54.980 --> 00:17:59.060 align:middle line:84%
and then organizations needed
to then update and patch

00:17:59.060 --> 00:18:01.787 align:middle line:84%
that software once the
patch was available.

00:18:01.787 --> 00:18:04.650 align:middle line:90%


00:18:04.650 --> 00:18:07.325 align:middle line:84%
And there is confirmed
report confidence.

00:18:07.325 --> 00:18:10.070 align:middle line:90%
So that's high.

00:18:10.070 --> 00:18:16.700 align:middle line:84%
And then if we look at
exploitability metrics,

00:18:16.700 --> 00:18:18.470 align:middle line:84%
this is where we
can see an impact

00:18:18.470 --> 00:18:20.210 align:middle line:90%
on the score in a highway.

00:18:20.210 --> 00:18:22.400 align:middle line:84%
Already by changing
that temporal,

00:18:22.400 --> 00:18:25.070 align:middle line:90%
it dropped down to a 9.3.

00:18:25.070 --> 00:18:26.450 align:middle line:90%
That still matters.

00:18:26.450 --> 00:18:27.620 align:middle line:90%
That still matters a lot.

00:18:27.620 --> 00:18:33.780 align:middle line:90%


00:18:33.780 --> 00:18:37.400 align:middle line:84%
But if you only need
access to the network,

00:18:37.400 --> 00:18:40.430 align:middle line:90%
you could be actually in--

00:18:40.430 --> 00:18:45.770 align:middle line:84%
yeah, in the network, the
complexity is still low.

00:18:45.770 --> 00:18:53.978 align:middle line:84%
If you find a place to
do your JNDI injection,

00:18:53.978 --> 00:18:55.520 align:middle line:84%
then the rest kind
of falls together.

00:18:55.520 --> 00:18:58.235 align:middle line:90%
It's not very complicated.

00:18:58.235 --> 00:19:01.250 align:middle line:84%
You don't need
privileges usually.

00:19:01.250 --> 00:19:02.345 align:middle line:90%
User interactions-- none.

00:19:02.345 --> 00:19:04.595 align:middle line:84%
You don't need anyone to
click on any links in emails.

00:19:04.595 --> 00:19:07.220 align:middle line:90%


00:19:07.220 --> 00:19:08.990 align:middle line:84%
In this situation,
it shows you what

00:19:08.990 --> 00:19:11.870 align:middle line:90%
unchanged or changed means.

00:19:11.870 --> 00:19:17.600 align:middle line:84%
We went with unchanged
and then high impacts.

00:19:17.600 --> 00:19:23.390 align:middle line:90%


00:19:23.390 --> 00:19:25.940 align:middle line:84%
And here, requirements
is useful.

00:19:25.940 --> 00:19:31.280 align:middle line:90%


00:19:31.280 --> 00:19:36.980 align:middle line:84%
And again, these ones
are going to be high.

00:19:36.980 --> 00:19:41.660 align:middle line:84%
We can see how the modifiers
change the overall score.

00:19:41.660 --> 00:19:44.130 align:middle line:84%
Now, in the end, doesn't
matter that much.

00:19:44.130 --> 00:19:45.320 align:middle line:90%
It's still a 9.1.

00:19:45.320 --> 00:19:49.790 align:middle line:84%
So the severity--
it's very severe.

00:19:49.790 --> 00:19:52.670 align:middle line:84%
Then it becomes, OK,
what's the impact?

00:19:52.670 --> 00:19:54.290 align:middle line:84%
If they have something
that's publicly

00:19:54.290 --> 00:19:58.970 align:middle line:84%
facing that anyone can
attack and it takes down

00:19:58.970 --> 00:20:02.448 align:middle line:84%
the whole server,
then that's not good,

00:20:02.448 --> 00:20:04.490 align:middle line:84%
especially if they don't
need to be authenticated

00:20:04.490 --> 00:20:08.180 align:middle line:84%
and there's no way
of protecting it.

00:20:08.180 --> 00:20:12.260 align:middle line:84%
Now, during your pen
test, you will find

00:20:12.260 --> 00:20:14.390 align:middle line:90%
how critical it actually is.

00:20:14.390 --> 00:20:18.290 align:middle line:84%
If it's exploitable, you
can say how you exploited it

00:20:18.290 --> 00:20:22.130 align:middle line:84%
and how easy it was to do
and give recommendations

00:20:22.130 --> 00:20:23.240 align:middle line:90%
for remediation.

00:20:23.240 --> 00:20:26.000 align:middle line:84%
What could they put in place
to avoid that and stop it?

00:20:26.000 --> 00:20:29.350 align:middle line:84%
If it's as easy as patch the
software, that's one thing.

00:20:29.350 --> 00:20:31.100 align:middle line:84%
But what if they can't
patch the software?

00:20:31.100 --> 00:20:34.670 align:middle line:84%
What if it's an application
that requires that older

00:20:34.670 --> 00:20:36.890 align:middle line:84%
version of Java, that
requires that older version

00:20:36.890 --> 00:20:38.540 align:middle line:90%
of Log4j for some reason?

00:20:38.540 --> 00:20:43.790 align:middle line:84%
The software vendor that
created the software that's

00:20:43.790 --> 00:20:48.440 align:middle line:84%
being used by the company, maybe
they've gone out of business.

00:20:48.440 --> 00:20:52.220 align:middle line:90%
Maybe they can't patch.

00:20:52.220 --> 00:20:55.068 align:middle line:84%
These are all things that need
to be taken into account when

00:20:55.068 --> 00:20:57.110 align:middle line:84%
you're making recommendations
from your pen test,

00:20:57.110 --> 00:20:57.860 align:middle line:90%
from your reports.

00:20:57.860 --> 00:21:00.230 align:middle line:90%


00:21:00.230 --> 00:21:06.110 align:middle line:84%
Now, those are our
vulnerability details pages,

00:21:06.110 --> 00:21:10.010 align:middle line:84%
both from the CVE page and
the National Vulnerability

00:21:10.010 --> 00:21:11.000 align:middle line:90%
Database.

00:21:11.000 --> 00:21:17.315 align:middle line:84%
And you might be wondering
about zero day attacks.

00:21:17.315 --> 00:21:19.190 align:middle line:84%
These vulnerabilities
that we were looking at

00:21:19.190 --> 00:21:28.490 align:middle line:84%
have all been submitted to
the CVE numbering authority,

00:21:28.490 --> 00:21:33.110 align:middle line:84%
and they have determined that
it's worth actually posting

00:21:33.110 --> 00:21:36.000 align:middle line:90%
somewhere to the CVE database.

00:21:36.000 --> 00:21:41.450 align:middle line:84%
Now, there's going to
be exploits out there

00:21:41.450 --> 00:21:44.300 align:middle line:84%
for vulnerabilities
that haven't been found.

00:21:44.300 --> 00:21:48.275 align:middle line:84%
That we call a zero day
exploit, meaning no one else

00:21:48.275 --> 00:21:50.150 align:middle line:84%
knows about it, or no
one else has exploited,

00:21:50.150 --> 00:21:52.970 align:middle line:84%
or no one else has
at least reported it

00:21:52.970 --> 00:21:55.970 align:middle line:90%
to the CVE organization.

00:21:55.970 --> 00:21:59.310 align:middle line:90%


00:21:59.310 --> 00:22:02.670 align:middle line:84%
Many pen testers like
to find zero days.

00:22:02.670 --> 00:22:09.840 align:middle line:84%
It bolsters you as a pen tester
in a lot of the community

00:22:09.840 --> 00:22:13.680 align:middle line:84%
for finding something by going
through the fuzzing steps,

00:22:13.680 --> 00:22:16.590 align:middle line:84%
by doing the research,
by identifying something

00:22:16.590 --> 00:22:19.890 align:middle line:84%
that the developers didn't
find, that no one else found.

00:22:19.890 --> 00:22:23.250 align:middle line:84%
And there's a lot of
prestige among some pen

00:22:23.250 --> 00:22:26.400 align:middle line:84%
testers for finding and
utilizing zero days.

00:22:26.400 --> 00:22:27.930 align:middle line:90%
And that's neat.

00:22:27.930 --> 00:22:29.530 align:middle line:84%
Software is going
to be vulnerable.

00:22:29.530 --> 00:22:33.150 align:middle line:84%
And if you can find
one, utilize it.

00:22:33.150 --> 00:22:37.620 align:middle line:84%
Help the ecosystem,
help the industry

00:22:37.620 --> 00:22:40.170 align:middle line:84%
by identifying these things,
putting them in your reports,

00:22:40.170 --> 00:22:44.190 align:middle line:84%
and sharing them with
a numbering authority.

00:22:44.190 --> 00:22:45.630 align:middle line:90%
That's going to help everyone.

00:22:45.630 --> 00:22:50.550 align:middle line:90%
And that's all good things.

00:22:50.550 --> 00:22:54.520 align:middle line:84%
Now, not all vulnerabilities
are computer code.

00:22:54.520 --> 00:22:57.300 align:middle line:84%
We talked about this when
we were talking about heists

00:22:57.300 --> 00:22:58.980 align:middle line:90%
and physical security.

00:22:58.980 --> 00:23:02.460 align:middle line:84%
You've also got
layer 8, the people.

00:23:02.460 --> 00:23:07.980 align:middle line:84%
Often, social engineering and
utilizing interpersonal skills

00:23:07.980 --> 00:23:11.820 align:middle line:84%
are going to be just as helpful
for a hacker or a pen tester

00:23:11.820 --> 00:23:15.270 align:middle line:84%
in order to get access to
information or the network

00:23:15.270 --> 00:23:17.070 align:middle line:90%
as a whole.

00:23:17.070 --> 00:23:22.680 align:middle line:84%
That can include using
known social engineering

00:23:22.680 --> 00:23:26.280 align:middle line:84%
techniques for passwords
or taking advantage

00:23:26.280 --> 00:23:33.690 align:middle line:84%
of maybe some of your physical
operational technology

00:23:33.690 --> 00:23:40.170 align:middle line:84%
controls, such as card
readers or access badges.

00:23:40.170 --> 00:23:44.320 align:middle line:84%
If you can make up an access
badge that looks like it's good

00:23:44.320 --> 00:23:46.560 align:middle line:84%
and you know that the
guards don't check that well

00:23:46.560 --> 00:23:48.540 align:middle line:84%
and there's nothing
stopping someone

00:23:48.540 --> 00:23:52.350 align:middle line:84%
from tailgating, perhaps,
through a gate if there

00:23:52.350 --> 00:23:57.780 align:middle line:84%
is a gate, then that's an
easy way for an adversary,

00:23:57.780 --> 00:24:01.500 align:middle line:84%
or a pen tester pretending to be
an adversary, to get in and get

00:24:01.500 --> 00:24:02.310 align:middle line:90%
physical access.

00:24:02.310 --> 00:24:05.230 align:middle line:84%
If you get physical
access to a network,

00:24:05.230 --> 00:24:08.770 align:middle line:90%
then it changes the game.

00:24:08.770 --> 00:24:11.970 align:middle line:84%
There's a lot of things
that you can do internally

00:24:11.970 --> 00:24:15.780 align:middle line:84%
that will give you more
access than if you were

00:24:15.780 --> 00:24:20.040 align:middle line:84%
trying to attack externally,
maybe through a web server

00:24:20.040 --> 00:24:22.260 align:middle line:90%
or externally facing services.

00:24:22.260 --> 00:24:26.750 align:middle line:90%


00:24:26.750 --> 00:24:30.140 align:middle line:84%
Again, scope, impact,
and usefulness

00:24:30.140 --> 00:24:33.763 align:middle line:84%
will all come down
to business needs.

00:24:33.763 --> 00:24:35.930 align:middle line:84%
Smaller businesses might
look at things differently.

00:24:35.930 --> 00:24:38.600 align:middle line:84%
Giant corporations might
look at things differently.

00:24:38.600 --> 00:24:41.900 align:middle line:84%
Hospitals or banks or
specific organizations

00:24:41.900 --> 00:24:45.500 align:middle line:84%
with specific needs and
compliance and regulations

00:24:45.500 --> 00:24:48.200 align:middle line:84%
are all going to have
different requirements.

00:24:48.200 --> 00:24:50.860 align:middle line:90%


00:24:50.860 --> 00:24:56.950 align:middle line:84%
The management of all this
goes alongside business risk

00:24:56.950 --> 00:25:01.720 align:middle line:84%
management into overall
risk management.

00:25:01.720 --> 00:25:05.140 align:middle line:84%
Some risk management has to
do with mergers, acquisitions,

00:25:05.140 --> 00:25:10.300 align:middle line:84%
hiring, firing, a lot of
different parts of the business

00:25:10.300 --> 00:25:15.910 align:middle line:84%
that aren't at all
technology, IT, or cyber.

00:25:15.910 --> 00:25:19.300 align:middle line:84%
Including cyber in there
will help the organization

00:25:19.300 --> 00:25:20.350 align:middle line:90%
as a whole.

00:25:20.350 --> 00:25:23.470 align:middle line:84%
And you need to understand
your recommendations go

00:25:23.470 --> 00:25:27.250 align:middle line:84%
into that overall risk
management concept.

00:25:27.250 --> 00:25:28.820 align:middle line:84%
Even if it's a
small organization,

00:25:28.820 --> 00:25:32.973 align:middle line:84%
they don't have a
foundation or a framework

00:25:32.973 --> 00:25:34.390 align:middle line:84%
for risk management,
they're going

00:25:34.390 --> 00:25:36.085 align:middle line:90%
to be doing it at some level.

00:25:36.085 --> 00:25:37.960 align:middle line:84%
They're going to be
sitting down and deciding

00:25:37.960 --> 00:25:39.502 align:middle line:84%
where are we going
to spend our money

00:25:39.502 --> 00:25:40.870 align:middle line:90%
and how are we going to use it.

00:25:40.870 --> 00:25:44.120 align:middle line:84%
And if it's not formalized,
it's still happening.

00:25:44.120 --> 00:25:46.300 align:middle line:84%
And your recommendations
for cybersecurity

00:25:46.300 --> 00:25:48.310 align:middle line:84%
are going to get
included in that.

00:25:48.310 --> 00:25:50.283 align:middle line:84%
And they might get
prioritized lower

00:25:50.283 --> 00:25:51.700 align:middle line:84%
than what you think
they should as

00:25:51.700 --> 00:25:53.380 align:middle line:90%
a cybersecurity practitioner.

00:25:53.380 --> 00:25:57.070 align:middle line:90%


00:25:57.070 --> 00:25:59.490 align:middle line:84%
So this is, of course,
about pen testing.

00:25:59.490 --> 00:26:01.990 align:middle line:84%
So you might be wondering, when
are we going to get to that?

00:26:01.990 --> 00:26:06.183 align:middle line:84%
And risk management includes
vulnerability management,

00:26:06.183 --> 00:26:07.600 align:middle line:84%
which is what we're
covering here,

00:26:07.600 --> 00:26:10.000 align:middle line:84%
and vulnerability
assessment, in order

00:26:10.000 --> 00:26:11.780 align:middle line:90%
to manage your vulnerability.

00:26:11.780 --> 00:26:14.740 align:middle line:84%
So you need to
know what they are.

00:26:14.740 --> 00:26:18.610 align:middle line:84%
With that, there's vulnerability
scanning and pen testing

00:26:18.610 --> 00:26:20.500 align:middle line:90%
for gap analysis.

00:26:20.500 --> 00:26:23.627 align:middle line:84%
Because often, there might
be a level that you know.

00:26:23.627 --> 00:26:25.600 align:middle line:84%
You might know what
software you have.

00:26:25.600 --> 00:26:27.280 align:middle line:84%
You might know that
it's vulnerable.

00:26:27.280 --> 00:26:33.280 align:middle line:84%
And you might assess the risk
that it is behind the network

00:26:33.280 --> 00:26:37.690 align:middle line:84%
boundary, internal only,
and the impact of it

00:26:37.690 --> 00:26:39.880 align:middle line:84%
is low enough that
it's not worth spending

00:26:39.880 --> 00:26:42.322 align:middle line:84%
the time or the
money to update it.

00:26:42.322 --> 00:26:44.155 align:middle line:84%
And that's up to the
organization to decide.

00:26:44.155 --> 00:26:47.470 align:middle line:84%
You can make your
recommendations.

00:26:47.470 --> 00:26:49.550 align:middle line:84%
But I know what
recommendations you would make

00:26:49.550 --> 00:26:50.800 align:middle line:90%
because I would make the same.

00:26:50.800 --> 00:26:54.680 align:middle line:84%
Let's mitigate as
much as possible.

00:26:54.680 --> 00:26:58.820 align:middle line:84%
But as a pen tester, running
vulnerability assessments,

00:26:58.820 --> 00:27:01.118 align:middle line:84%
doing that gap
analysis, it's all

00:27:01.118 --> 00:27:02.410 align:middle line:90%
going to be part of this chain.

00:27:02.410 --> 00:27:05.310 align:middle line:90%


00:27:05.310 --> 00:27:08.600 align:middle line:84%
So how do we find
these vulnerabilities?

00:27:08.600 --> 00:27:12.830 align:middle line:84%
We've done foot printing and
scanning in this pathway.

00:27:12.830 --> 00:27:18.343 align:middle line:84%
We've done some service
enumeration in this pathway.

00:27:18.343 --> 00:27:19.760 align:middle line:84%
That's all going
to be part of it.

00:27:19.760 --> 00:27:21.890 align:middle line:84%
Asset identification
and research--

00:27:21.890 --> 00:27:24.020 align:middle line:84%
OK, hey, there's
this service running.

00:27:24.020 --> 00:27:26.360 align:middle line:84%
It's this version on
this operating system.

00:27:26.360 --> 00:27:29.480 align:middle line:84%
We need to go and see,
what does that mean?

00:27:29.480 --> 00:27:31.880 align:middle line:84%
And we'll get into
that in the lab.

00:27:31.880 --> 00:27:34.430 align:middle line:84%
But there's places
like Exploit-DB

00:27:34.430 --> 00:27:39.410 align:middle line:84%
and the on-hardware version
SearchSploit maintained

00:27:39.410 --> 00:27:41.990 align:middle line:84%
by offensive security,
and it's a great asset

00:27:41.990 --> 00:27:44.630 align:middle line:90%
for the community.

00:27:44.630 --> 00:27:46.070 align:middle line:90%
Or there's fuzz testing.

00:27:46.070 --> 00:27:47.540 align:middle line:84%
You might get
access to something

00:27:47.540 --> 00:27:53.480 align:middle line:84%
and not be able to find
any vulnerabilities that

00:27:53.480 --> 00:27:55.880 align:middle line:84%
are out there in the
wild, that are known.

00:27:55.880 --> 00:27:59.960 align:middle line:84%
So perhaps you need to
just try some things

00:27:59.960 --> 00:28:03.500 align:middle line:84%
and see if there's a
vulnerability there.

00:28:03.500 --> 00:28:06.560 align:middle line:84%
Input and handling
validation is important.

00:28:06.560 --> 00:28:10.340 align:middle line:84%
And that's, again, how pen
testers find a lot of things.

00:28:10.340 --> 00:28:13.805 align:middle line:84%
You try putting in
passwords that don't

00:28:13.805 --> 00:28:14.930 align:middle line:90%
look like normal passwords.

00:28:14.930 --> 00:28:17.480 align:middle line:84%
You try usernames
that don't look

00:28:17.480 --> 00:28:19.760 align:middle line:84%
like usernames
because maybe there's

00:28:19.760 --> 00:28:23.000 align:middle line:90%
a chance for SQL injection.

00:28:23.000 --> 00:28:25.430 align:middle line:84%
Those are things that we'll
get into in other parts

00:28:25.430 --> 00:28:27.380 align:middle line:84%
of this pathway
in other courses.

00:28:27.380 --> 00:28:31.970 align:middle line:84%
But that's generally how
we find vulnerabilities.

00:28:31.970 --> 00:28:33.620 align:middle line:84%
In the next video,
we're going to take

00:28:33.620 --> 00:28:35.390 align:middle line:90%
a look at some well-known CVEs.

00:28:35.390 --> 00:28:39.170 align:middle line:84%
We'll look at why they matter
and what we can take from them

00:28:39.170 --> 00:28:40.250 align:middle line:90%
now today.

00:28:40.250 --> 00:28:42.440 align:middle line:84%
Even though a couple
of them are bit older,

00:28:42.440 --> 00:28:45.720 align:middle line:90%
one's fairly new and relevant.

00:28:45.720 --> 00:28:49.300 align:middle line:90%
And I think we'll learn a lot.

00:28:49.300 --> 00:28:50.000 align:middle line:90%