WEBVTT

00:01.260 --> 00:10.110
Welcome to the video advanced scanning with open Vohs in this video we will import a list of targets

00:10.530 --> 00:16.670
such as that from an end map scan will tune the scan to make it as efficient as possible.

00:17.810 --> 00:22.790
We'll scan the target with credentials to get a more complete picture of the vulnerabilities that may

00:22.790 --> 00:29.620
lie within the host and we'll schedule scans to ease the load on the network during peak hours.

00:31.190 --> 00:37.700
In the last video we talked about how easy it was to do a point and shoot scan of an IP on your network

00:37.850 --> 00:39.700
using open bus.

00:39.870 --> 00:45.120
But there's a good chance you are going to want to scan multiple hosts or subnets.

00:45.190 --> 00:51.430
You also may have noticed that in the last video we performed our scan in an authenticated fashion.

00:51.580 --> 00:57.010
In other words I didn't try to connect to any hosts using valid credentials and thus I can only see

00:57.010 --> 01:01.940
a surface level picture of the vulnerabilities that might lie inside.

01:01.940 --> 01:07.460
So it's important that we know how to scan multiple hosts with open files and also know how to pass

01:07.460 --> 01:11.980
credentials to these hosts to get the most value out of our scans as possible.

01:12.890 --> 01:19.880
Now I prefer to use open Avaaz primarily as a vulnerability scanner and not for the host discovery phase

01:19.970 --> 01:21.150
of a project.

01:21.530 --> 01:26.790
So I'm going to use one of the nmap scans we talked about in the past video.

01:26.850 --> 01:32.470
First let's cap a file called subnet CTX T which contains the networks.

01:32.490 --> 01:41.430
I want to scan then I'm going to use and map plus the TAC s and flag which essentially does a ping sweep

01:42.560 --> 01:50.450
and I'll add the tech O.G. flag to create a graspable output and then the rest of the command essentially

01:50.450 --> 01:57.950
takes the result of our scan identifies any hosts that return a ping and outputs them to a nice clean

01:57.950 --> 02:03.890
list one IP per line to a file called libe hosts Dotti XTi

02:08.880 --> 02:12.100
let's catch this file as well to see what's in it.

02:12.400 --> 02:15.570
And it looks like we have our target list ready to go.

02:16.970 --> 02:23.450
Next I want to give open Avaaz a set of credentials so that if it scans any Windows machines in my environment

02:23.900 --> 02:26.730
it will connect with those credentials.

02:26.930 --> 02:32.960
Again like I said earlier doing this type of authenticated scan will yield greater results than what

02:32.960 --> 02:35.130
we'd see in an uncredentialed scan.

02:36.310 --> 02:40.530
So let's go to the configuration menu and click credentials.

02:41.710 --> 02:46.460
Then I'll hit this star over on the left side of the screen to enter a new credential.

02:47.900 --> 02:55.050
And then I'll give this set of credentials a name a description and a username and password itself.

02:57.480 --> 03:04.260
I'll click Create and then we can see the credentials in our little credential vault of sorts here.

03:07.020 --> 03:11.260
Now we'll want to get our targets ready to receive a credentialed scan.

03:11.700 --> 03:19.270
So let's go under configuration menu again and click targets will hit the star icon again to create

03:19.270 --> 03:20.430
a new target.

03:20.740 --> 03:24.310
And then here all give the target list a name and comment.

03:25.740 --> 03:32.260
Then I'll click to browse and point to the Live hosts we created earlier with our map scan.

03:34.370 --> 03:41.420
Under the live test you'll see we've got several choices we can pick from to make open vised discover

03:41.480 --> 03:48.270
Live hosts on the network now because I've already done this ahead of time with any map I'm just going

03:48.270 --> 03:48.800
to click.

03:48.810 --> 03:57.460
Consider a live and then under the credentials for authenticated checks you'll see we can provide S-sh

03:57.970 --> 04:02.890
SMB or V.M. where yes XCI credentials.

04:03.020 --> 04:10.280
I'm going to click the dropdown next to SNB and pick Windows which is what I nicknamed my windows credentials

04:10.280 --> 04:10.930
set.

04:12.590 --> 04:20.600
We should be good to go here so all click Create and we'll see this target list pop up on our screen.

04:20.710 --> 04:26.060
Now before we actually kick the scan off we might want to set up an alert so that we get an e-mail when

04:26.060 --> 04:28.100
the scan completes.

04:28.100 --> 04:37.060
So let's hit the configuration menu again and click alerts.

04:37.260 --> 04:44.310
I'll give mine an appropriate name and comment and I'll choose to have the scanned completion be the

04:44.310 --> 04:57.020
event that triggers the alert then I'll fill in my e-mail to and from address and click Create.

04:57.060 --> 05:00.080
OK so I should be set to kick the scanner off.

05:00.130 --> 05:03.350
But let's say we wanted to ease the load on the network.

05:03.630 --> 05:10.310
And so rather than run this now during business hours we want to run it when nobody's in the office.

05:10.480 --> 05:18.130
So let's go to configuration and schedules and then choose to create a new schedule and all set up my

05:18.130 --> 05:20.460
scans so that it runs just before midnight.

05:20.470 --> 05:30.190
In my time zone which is Central will hit create and then we should be ready to pull the trigger on

05:30.190 --> 05:31.490
this scan.

05:31.510 --> 05:38.730
So let's go under the scans menu and click tasks will choose to start a new task.

05:38.830 --> 05:46.660
We will give it a name a comment and we'll also choose to be alerted via the alert that we just set

05:46.660 --> 05:52.080
up and we'll also have this scan follow the after hours schedule.

05:52.130 --> 05:57.430
We built called after hours and that's it.

05:57.430 --> 06:06.070
We should be set now in the interest of time I'm not going to wait until 11:45 to watch the scan kickoff.

06:06.230 --> 06:09.300
So I will just trigger it by clicking the arrow now.

06:13.110 --> 06:19.590
I found that sometimes scans will seem to be completely frozen and the percentage bar won't move for

06:19.590 --> 06:20.460
a long time.

06:21.540 --> 06:26.340
If you want to get it behind the scenes look at what the scanner is actually doing.

06:26.370 --> 06:35.670
You can drop to a terminal and then do a tail of the open vase M.D logfile shown at the path here.

06:36.610 --> 06:46.660
And add a TAC F at the end as a reminder the tail command with a TAC F at the end essentially means

06:47.020 --> 06:50.900
show me a live view of what is at the end of this file.

06:51.130 --> 06:54.980
And if new data is written to the file show me that as well.

06:56.260 --> 07:02.700
And by watching this log for a bit we can see that the scan actually has flipped to a Donne's status.

07:02.920 --> 07:05.070
But the web GUI is not reflecting that.

07:06.090 --> 07:15.690
However if we just do a refresh of the page we'll see that the scan now shows 100 percent completion.

07:15.910 --> 07:24.640
And just like with our last scan we can now drill several levels deep into the results of the scan and

07:24.670 --> 07:27.270
learn more about each discovered vulnerability.

07:28.300 --> 07:34.120
We'll also see a nice write up with recommendations on what remediation we need to take if necessary

07:35.730 --> 07:36.660
in our next video.

07:36.660 --> 07:42.610
We'll look at additional Kalli tools we can leverage to scan for vulnerabilities in web applications.
