WEBVTT

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


00:00:09.960 --> 00:00:12.360 align:middle line:84%
There are many tools that
can be utilized for asset

00:00:12.360 --> 00:00:14.550 align:middle line:90%
management for auditing.

00:00:14.550 --> 00:00:18.720 align:middle line:84%
We're going to talk about
one, Nessus by Tenable.

00:00:18.720 --> 00:00:22.680 align:middle line:84%
There is a Essentials which
is free and anyone can use it.

00:00:22.680 --> 00:00:26.220 align:middle line:84%
There's also Home, and
Professional, and Enterprise.

00:00:26.220 --> 00:00:29.197 align:middle line:84%
We're going to take a look
at just the Essential one.

00:00:29.197 --> 00:00:35.660 align:middle line:90%


00:00:35.660 --> 00:00:37.850 align:middle line:90%
Nessus runs off of a server.

00:00:37.850 --> 00:00:40.453 align:middle line:84%
In this case, it's
hosted locally,

00:00:40.453 --> 00:00:41.870 align:middle line:84%
but we're going
to be reaching out

00:00:41.870 --> 00:00:47.550 align:middle line:84%
to another machine
on the network

00:00:47.550 --> 00:00:49.575 align:middle line:90%
and scanning that machine.

00:00:49.575 --> 00:00:54.060 align:middle line:90%


00:00:54.060 --> 00:01:03.990 align:middle line:84%
Just to explain, our
IP is this 192.93.34.2.

00:01:03.990 --> 00:01:07.830 align:middle line:84%
And we're going to be
working with demo.any.local.

00:01:07.830 --> 00:01:10.950 align:middle line:90%


00:01:10.950 --> 00:01:14.820 align:middle line:84%
You can see there
that that's the .3.

00:01:14.820 --> 00:01:16.320 align:middle line:84%
It's another machine
on the network.

00:01:16.320 --> 00:01:22.090 align:middle line:90%


00:01:22.090 --> 00:01:24.540 align:middle line:90%
So we log in to Nessus.

00:01:24.540 --> 00:01:27.600 align:middle line:84%
And we're going to tell
it the demo.any.local.

00:01:27.600 --> 00:01:32.220 align:middle line:90%


00:01:32.220 --> 00:01:33.690 align:middle line:84%
And you could put
in an IP address.

00:01:33.690 --> 00:01:34.440 align:middle line:90%
You could put in a range.

00:01:34.440 --> 00:01:35.770 align:middle line:90%
You put in a whole network.

00:01:35.770 --> 00:01:40.920 align:middle line:84%
In this case, we're just going
to put in the domain name.

00:01:40.920 --> 00:01:44.820 align:middle line:84%
And it ran a scan,
a discovery scan,

00:01:44.820 --> 00:01:50.400 align:middle line:84%
and found this IP address,
which is what we saw down there.

00:01:50.400 --> 00:01:53.940 align:middle line:90%
It did the same thing we did.

00:01:53.940 --> 00:01:57.750 align:middle line:84%
And now it's running
a basic network scan.

00:01:57.750 --> 00:02:00.030 align:middle line:84%
All that's running-- you
can come take a look.

00:02:00.030 --> 00:02:02.850 align:middle line:84%
There's this my
host discovery scan.

00:02:02.850 --> 00:02:06.530 align:middle line:90%
If we really wanted to dig in--

00:02:06.530 --> 00:02:08.010 align:middle line:90%
it did a WHOIS request.

00:02:08.010 --> 00:02:14.110 align:middle line:90%


00:02:14.110 --> 00:02:19.055 align:middle line:84%
And we can see some version
information for Nessus.

00:02:19.055 --> 00:02:23.500 align:middle line:84%
Go right to the scans and
the basic network scan

00:02:23.500 --> 00:02:25.210 align:middle line:90%
is still running.

00:02:25.210 --> 00:02:27.880 align:middle line:84%
We can take a look
at what it found.

00:02:27.880 --> 00:02:31.660 align:middle line:84%
It ran a SYN scanner,
a port scanner.

00:02:31.660 --> 00:02:39.280 align:middle line:84%
It did a host fully-qualified
domain name resolution,

00:02:39.280 --> 00:02:40.030 align:middle line:90%
not too crazy.

00:02:40.030 --> 00:02:54.450 align:middle line:90%


00:02:54.450 --> 00:02:56.760 align:middle line:84%
For these vulnerabilities,
you can see severity.

00:02:56.760 --> 00:02:58.560 align:middle line:90%
It just says info.

00:02:58.560 --> 00:03:01.710 align:middle line:84%
So while it's under
vulnerabilities,

00:03:01.710 --> 00:03:03.723 align:middle line:84%
these don't actually
have anything

00:03:03.723 --> 00:03:04.890 align:middle line:90%
that we need to worry about.

00:03:04.890 --> 00:03:06.540 align:middle line:84%
You can see the
categories over here

00:03:06.540 --> 00:03:10.590 align:middle line:84%
go from low, medium,
high to critical.

00:03:10.590 --> 00:03:14.250 align:middle line:84%
We have more coming
in, found 17.

00:03:14.250 --> 00:03:20.850 align:middle line:84%
Again, all of these are
just info that it ran scans

00:03:20.850 --> 00:03:23.940 align:middle line:84%
and it found things, not
necessarily that they're

00:03:23.940 --> 00:03:26.020 align:middle line:90%
good or bad.

00:03:26.020 --> 00:03:28.710 align:middle line:90%
It just found a lot of things.

00:03:28.710 --> 00:03:35.280 align:middle line:84%
Now, simple auditing, you
would want to see and compare

00:03:35.280 --> 00:03:37.350 align:middle line:84%
what do we know
about the system?

00:03:37.350 --> 00:03:41.070 align:middle line:84%
Does this match
what we have set?

00:03:41.070 --> 00:03:45.180 align:middle line:84%
If you're going into a pen test
with information given to you,

00:03:45.180 --> 00:03:48.300 align:middle line:84%
maybe like a gray or a
white [INAUDIBLE] test,

00:03:48.300 --> 00:03:50.370 align:middle line:84%
then you would also want
to compare those things

00:03:50.370 --> 00:03:52.800 align:middle line:84%
because your findings
really need to reflect

00:03:52.800 --> 00:03:54.540 align:middle line:90%
what's useful to your customer.

00:03:54.540 --> 00:03:59.093 align:middle line:90%


00:03:59.093 --> 00:04:00.135 align:middle line:90%
Here we can see a medium.

00:04:00.135 --> 00:04:04.000 align:middle line:90%


00:04:04.000 --> 00:04:09.370 align:middle line:84%
And it's based on the
version of jQuery,

00:04:09.370 --> 00:04:11.202 align:middle line:90%
and it might be vulnerable.

00:04:11.202 --> 00:04:14.580 align:middle line:90%


00:04:14.580 --> 00:04:17.797 align:middle line:84%
Two multiple cross-site
scripting vulnerabilities,

00:04:17.797 --> 00:04:18.839 align:middle line:90%
that's not a great thing.

00:04:18.839 --> 00:04:20.730 align:middle line:90%
We don't want that.

00:04:20.730 --> 00:04:23.700 align:middle line:90%
If we can stop it--

00:04:23.700 --> 00:04:26.256 align:middle line:90%
sorry, basically [INAUDIBLE].

00:04:26.256 --> 00:04:29.130 align:middle line:90%
It came across two of those.

00:04:29.130 --> 00:04:42.660 align:middle line:84%
Yeah, it was off [INAUDIBLE],,
it looks like, not too crazy.

00:04:42.660 --> 00:04:46.070 align:middle line:84%
We could take the
results of our scan

00:04:46.070 --> 00:04:50.930 align:middle line:84%
and we could go here to
report at the top right.

00:04:50.930 --> 00:04:53.300 align:middle line:90%
And we get export--

00:04:53.300 --> 00:04:55.280 align:middle line:90%
let's make this full screen--

00:04:55.280 --> 00:05:01.280 align:middle line:84%
as a PDF, HTML, or a Comma
Separated Value, CSV file.

00:05:01.280 --> 00:05:02.120 align:middle line:90%
It's an Excel file.

00:05:02.120 --> 00:05:05.360 align:middle line:90%
But not in an iso fun way.

00:05:05.360 --> 00:05:07.760 align:middle line:84%
[INAUDIBLE] detail
vulnerabilities by host,

00:05:07.760 --> 00:05:12.740 align:middle line:84%
vulnerabilities by plug-in, or
all vulnerability operations.

00:05:12.740 --> 00:05:14.720 align:middle line:84%
We're going to
run one more scan.

00:05:14.720 --> 00:05:16.250 align:middle line:90%
Go back here to my scans.

00:05:16.250 --> 00:05:18.890 align:middle line:90%
And we can create a new scan.

00:05:18.890 --> 00:05:21.320 align:middle line:90%
I'll do an advanced scan.

00:05:21.320 --> 00:05:29.530 align:middle line:84%
We'll just call it
advancednetworkscan, a slightly

00:05:29.530 --> 00:05:34.690 align:middle line:90%
more advanced network scan.

00:05:34.690 --> 00:05:36.790 align:middle line:84%
You would want to put
in whatever information

00:05:36.790 --> 00:05:39.370 align:middle line:90%
is most helpful to you.

00:05:39.370 --> 00:05:43.462 align:middle line:84%
[INAUDIBLE] local is still
going to be our target.

00:05:43.462 --> 00:05:52.180 align:middle line:84%
Go to discovery, these all
look fine for port scanning.

00:05:52.180 --> 00:05:54.850 align:middle line:84%
Let's do a TCP network
scan. instead of just a SYN

00:05:54.850 --> 00:05:57.192 align:middle line:90%
scan, a TCP scan.

00:05:57.192 --> 00:05:58.150 align:middle line:90%
So I'll try to connect.

00:05:58.150 --> 00:06:03.280 align:middle line:90%


00:06:03.280 --> 00:06:06.280 align:middle line:84%
Service discovery's
fine, let's go in here

00:06:06.280 --> 00:06:09.820 align:middle line:84%
to assessment and
web applications

00:06:09.820 --> 00:06:11.950 align:middle line:90%
and scan web applications.

00:06:11.950 --> 00:06:18.680 align:middle line:90%


00:06:18.680 --> 00:06:20.780 align:middle line:84%
We'll enable generic
web application tests.

00:06:20.780 --> 00:06:24.490 align:middle line:90%


00:06:24.490 --> 00:06:28.330 align:middle line:84%
That's fine, maximum
runtime, five minutes.

00:06:28.330 --> 00:06:30.820 align:middle line:84%
That's reasonable for the
next level of scanning.

00:06:30.820 --> 00:06:37.010 align:middle line:90%


00:06:37.010 --> 00:06:39.110 align:middle line:84%
And we'll go into it,
and we'll watch it.

00:06:39.110 --> 00:06:42.678 align:middle line:90%


00:06:42.678 --> 00:06:43.970 align:middle line:90%
There might be some magic here.

00:06:43.970 --> 00:06:45.178 align:middle line:90%
We'll see when it's complete.

00:06:45.178 --> 00:06:47.600 align:middle line:90%


00:06:47.600 --> 00:06:50.240 align:middle line:90%
Looks like our scan is complete.

00:06:50.240 --> 00:06:53.390 align:middle line:84%
Let's go take a look
at our vulnerabilities.

00:06:53.390 --> 00:06:59.570 align:middle line:84%
We have some highs, a lot
of mediums, some mixed.

00:06:59.570 --> 00:07:03.380 align:middle line:84%
We'll say you look
at this first high.

00:07:03.380 --> 00:07:06.170 align:middle line:84%
This is something that we
should know about, that there's

00:07:06.170 --> 00:07:10.730 align:middle line:90%
some SQL injection possible.

00:07:10.730 --> 00:07:13.685 align:middle line:90%
We can go look at the output.

00:07:13.685 --> 00:07:20.120 align:middle line:90%


00:07:20.120 --> 00:07:21.440 align:middle line:90%
See where it is possible.

00:07:21.440 --> 00:07:29.270 align:middle line:90%


00:07:29.270 --> 00:07:37.800 align:middle line:84%
Looks like it's in this
page name parameter.

00:07:37.800 --> 00:07:40.320 align:middle line:84%
So that's something
useful that we

00:07:40.320 --> 00:07:43.490 align:middle line:84%
would want to write
down and include

00:07:43.490 --> 00:07:47.720 align:middle line:90%
in our report on vulnerability.

00:07:47.720 --> 00:07:51.740 align:middle line:84%
SQL injection is something
that should be remedied fairly

00:07:51.740 --> 00:07:55.830 align:middle line:90%
easily with some code review.

00:07:55.830 --> 00:07:58.790 align:middle line:84%
And in this
situation, maybe we're

00:07:58.790 --> 00:08:05.580 align:middle line:84%
using a third party
software on our site.

00:08:05.580 --> 00:08:11.370 align:middle line:84%
And third party risk
management is important.

00:08:11.370 --> 00:08:14.130 align:middle line:84%
Understanding what
vulnerabilities they bring in

00:08:14.130 --> 00:08:15.180 align:middle line:90%
is worthwhile.

00:08:15.180 --> 00:08:18.255 align:middle line:84%
Or it could be something we
built into our own product.

00:08:18.255 --> 00:08:20.790 align:middle line:90%


00:08:20.790 --> 00:08:25.890 align:middle line:84%
And DevSecOps, or DevOps,
needs to take a look at what

00:08:25.890 --> 00:08:29.730 align:middle line:90%
is going on in our web app.

00:08:29.730 --> 00:08:57.710 align:middle line:90%


00:08:57.710 --> 00:08:59.660 align:middle line:90%
We've got our results back.

00:08:59.660 --> 00:09:02.810 align:middle line:84%
And we have four to
four vulnerabilities,

00:09:02.810 --> 00:09:05.240 align:middle line:90%
including some high level ones.

00:09:05.240 --> 00:09:09.410 align:middle line:84%
We could take this whole
report and export it

00:09:09.410 --> 00:09:13.400 align:middle line:84%
as a PDF, or an HTTP,
or HTML, or a CSV

00:09:13.400 --> 00:09:20.270 align:middle line:84%
if we wanted to combine it with
more devices down the line.

00:09:20.270 --> 00:09:25.010 align:middle line:84%
CSV might be more useful
to get a broad scope, one

00:09:25.010 --> 00:09:30.785 align:middle line:84%
single view of the whole
network when we run later scans.

00:09:30.785 --> 00:09:33.590 align:middle line:90%


00:09:33.590 --> 00:09:35.570 align:middle line:84%
HTML is going to be
nice and interactive.

00:09:35.570 --> 00:09:38.630 align:middle line:84%
And a PDF is something that
you could easily hand over

00:09:38.630 --> 00:09:42.020 align:middle line:90%
to someone else who needs it.

00:09:42.020 --> 00:09:48.080 align:middle line:84%
But that is, generally,
how Nessus works.

00:09:48.080 --> 00:09:50.720 align:middle line:84%
And I hope we got
something out of that,

00:09:50.720 --> 00:09:54.020 align:middle line:84%
understanding what a
vulnerability scanner can do

00:09:54.020 --> 00:09:58.370 align:middle line:84%
and how we can integrate it
into our auditing process.

00:09:58.370 --> 00:10:01.340 align:middle line:84%
And then, now, as a pen
tester, understanding

00:10:01.340 --> 00:10:04.850 align:middle line:84%
that they, hopefully,
have been running

00:10:04.850 --> 00:10:07.970 align:middle line:84%
auditing and vulnerability
scans on their network.

00:10:07.970 --> 00:10:12.650 align:middle line:84%
And if they haven't, you could
integrate that and include it

00:10:12.650 --> 00:10:13.820 align:middle line:90%
in the scoping.

00:10:13.820 --> 00:10:16.880 align:middle line:84%
This is an essential
first step, really.

00:10:16.880 --> 00:10:19.340 align:middle line:84%
And depending on the
maturity of the organization,

00:10:19.340 --> 00:10:21.710 align:middle line:84%
they should be doing
this on their own.

00:10:21.710 --> 00:10:24.320 align:middle line:84%
Hiring someone,
just on IT staff,

00:10:24.320 --> 00:10:27.140 align:middle line:84%
who can run the
free version Nessus

00:10:27.140 --> 00:10:30.500 align:middle line:84%
and scan their own
network is not--

00:10:30.500 --> 00:10:32.300 align:middle line:84%
is something-- is
the recommendation

00:10:32.300 --> 00:10:36.410 align:middle line:84%
that you could make that
is highly reasonable,

00:10:36.410 --> 00:10:40.370 align:middle line:84%
so including that, understanding
what you are recommending,

00:10:40.370 --> 00:10:42.740 align:middle line:84%
understanding where
their maturity is at,

00:10:42.740 --> 00:10:47.030 align:middle line:84%
and what is going to be most
valuable to the customer,

00:10:47.030 --> 00:10:51.880 align:middle line:84%
again, is very, very
important as a pen tester.

00:10:51.880 --> 00:10:53.000 align:middle line:90%