WEBVTT

00:01.780 --> 00:10.240
Welcome to the video Sparta and eyewitness in this video we will use a built in Kelly tool called Sparta

00:10.810 --> 00:16.870
which will help not only automate our unmap scans but also automatically run pen testing tools against

00:16.870 --> 00:18.160
our target hosts.

00:18.160 --> 00:24.580
Based on what services are running will also install and use a free tool called eye witness together

00:24.580 --> 00:29.710
web VANOC or RTP screenshots from a list of targets.

00:30.680 --> 00:37.700
Up until now we've focused primarily on using unmap to discover information about the hosts and vulnerabilities

00:37.760 --> 00:38.770
on our network.

00:39.320 --> 00:45.440
And we've started to take a dive into how we can use various commands and flags to fine tune our scans

00:45.440 --> 00:48.450
for just the specific information we're looking for.

00:49.240 --> 00:54.250
We're going to get back to that in a bit but I wanted to call a brief time out and show you some other

00:54.250 --> 01:01.010
great tools that can give you a jumpstart on a numerator in your network as well Sparta is one that

01:01.010 --> 01:06.080
comes built right into Kally and in what will likely be a relief for some of you.

01:06.200 --> 01:13.690
It has a nice slick gooey interface once you get Sparta open you can simply click where it says Click

01:13.690 --> 01:21.170
here to add hostes to scope and type in the network or networks you'd like to scan I suggest leaving

01:21.170 --> 01:27.980
the two checkbox settings alone and simply clicking add to scope as soon as you do.

01:28.000 --> 01:35.260
Sparta gets to scanning as you can see in the log area of the screen there is actually a staged map

01:35.260 --> 01:37.120
scan happening behind the scenes.

01:38.220 --> 01:40.700
We'll get into how to tune that a little bit later.

01:41.040 --> 01:47.550
But for now you'll also notice that Sparta is running a handful of other tools such as nikto which is

01:47.550 --> 01:50.780
good at finding Web site vulnerabilities.

01:50.800 --> 01:58.080
It also appears that Sparta is taking screenshots of services it finds along the left side of the Spart

01:58.080 --> 02:05.380
a window we can click through our scan results host by host to see open ports as well as the associated

02:05.380 --> 02:08.060
service name and version.

02:08.200 --> 02:15.280
And then as we work our way across the tabs along the top we can see the results of the nikto scan a

02:15.280 --> 02:21.910
screenshot of the web service on port 80 as well as a check for the existence of default credentials

02:22.510 --> 02:23.340
on the hosts.

02:23.350 --> 02:27.460
My sequel and FCP service which is pretty cool.

02:29.540 --> 02:31.250
Bacot the Services menu.

02:31.490 --> 02:37.680
Notice that we can right click any service and be prompted with a contextual menu.

02:37.710 --> 02:43.970
So if I wanted to open this service with telnet I can do that with a quick click in this menu.

02:45.410 --> 02:53.050
Same for S-sh and I can quickly open the site's web service in a browser as well.

02:54.080 --> 03:00.960
Additionally Sparta has some tools to let you do some deeper testing of a host's services.

03:01.030 --> 03:09.430
For example if I right click the service and click send to bruit I can now come over to this bruit tab

03:10.150 --> 03:12.500
and set up for a brute force attack.

03:13.710 --> 03:21.150
I can feed bruit a large list of usernames as well as a large list of passwords.

03:21.280 --> 03:24.720
Then I simply click run and we're off and running.

03:28.420 --> 03:34.310
Another feature that is incredibly handy and smart is a tab where you can fill in notes.

03:34.510 --> 03:40.300
So if you're using Sparta for a pen test engagement you can jot some notes about your testing down for

03:40.300 --> 03:44.680
later each host has its own notes field.

03:44.870 --> 03:53.120
So it's easy to organize your thoughts and perhaps best of all it's easy to save a Sparta project file

03:53.750 --> 03:55.900
and then come back to it at a later time.

03:57.370 --> 04:01.470
Now you might remember back to when we first started the network scan with Sparta.

04:01.870 --> 04:07.850
We saw a screen indicating that a staged in MAP scan was happening.

04:07.880 --> 04:10.680
So what exactly is a staged and map scan.

04:10.880 --> 04:13.740
And how can we get some more granular control over it.

04:14.030 --> 04:18.550
Well all this part of magic happens in a file called Sparta.

04:18.780 --> 04:27.890
If we can find that file quickly on our calling instance by simply typing in locate space Sparta com

04:29.680 --> 04:32.500
I'll open it up N.A. here so we can have a look at it.

04:34.380 --> 04:37.880
Now while at first glance this file might look intimidating.

04:37.950 --> 04:45.690
It's broken down into several logical chunks first since we're talking about unmap Let's hop down to

04:45.780 --> 04:48.030
staged in MAP settings.

04:48.850 --> 04:55.960
This section essentially details in order several and map scans that will be run.

04:56.210 --> 05:06.830
We can see that and map will first scan for ports 80 and 443 then move on to hitting 25 137 and a slew

05:06.830 --> 05:08.360
of other common ports.

05:09.730 --> 05:19.590
Stage three gets into telnet FGP and S-sh and so on until eventually all 65000 plus ports are scanned.

05:21.340 --> 05:26.820
Now let's take a look at the section called Host actions host actions or options.

05:26.830 --> 05:34.570
You can see when you right click on host in Sparta if we want to add actions of our own we can just

05:34.570 --> 05:39.810
follow the syntax which starts with a unique identifier.

05:39.880 --> 05:46.430
I'll just make a simple one called Ping then a label we want displayed in the pop up menu itself.

05:47.500 --> 05:54.040
And then the command we actually want to run with the word IP in brackets.

05:55.290 --> 05:57.100
So let's save this file out.

05:58.390 --> 06:03.800
And then we will restart Sparta and give this a shot.

06:03.840 --> 06:12.430
I'll open my previously saved Sparta project and then I'm going to write cook a host and click ping

06:12.430 --> 06:18.150
seven times.

06:18.320 --> 06:25.650
Notice that a new tab is opened with our ping tool output.

06:25.710 --> 06:30.740
There are just a few other things I want to call your attention to in the Sparta Khant file.

06:32.770 --> 06:37.760
The port actions are tools that can be run when you right click a port or service.

06:37.780 --> 06:44.630
In Sparta and again these can be customized by following the syntax of an existing menu entry.

06:45.870 --> 06:49.770
Once support action is run its output is saved to a tab.

06:49.770 --> 07:00.190
In Sparta such as the GRABBE banner tool shown here in a similar fashion the port terminal actions can

07:00.190 --> 07:01.680
be customized as well.

07:02.430 --> 07:09.210
But what makes these different from Port actions is that these actions will respond in an external terminal

07:09.210 --> 07:09.890
window.

07:11.210 --> 07:15.380
For example if we want to open a telnet connection to a host.

07:15.380 --> 07:18.310
Notice how it opens in a brand new terminal window.

07:19.730 --> 07:25.700
Lastly you may have noticed that once our initial Sparta and map scan finished it also kicked off a

07:25.700 --> 07:31.740
whole other slew of tools like nikto and some default credential checkers.

07:31.870 --> 07:38.410
If you want to turn all that off scroll up near the top of the config file and where it says enables

07:38.410 --> 07:44.930
schedular equals true change the word true to false.

07:44.940 --> 07:52.610
Now the next time you do aspire to scan the staged and map scan will still kick off and finish but the

07:52.610 --> 08:00.560
additional tools such as nikto or the screenshot utility or the default credential checkers will not

08:00.650 --> 08:01.240
be launched

08:04.190 --> 08:13.640
for additional information about Sparta visit Sparta SEC force dot com slash documentation.

08:13.710 --> 08:19.230
Now there are dozens of other tools that can help you conduct basic network scanning but I want to show

08:19.230 --> 08:25.280
you one that has been particularly helpful for me as part of my penetration testing process.

08:25.330 --> 08:30.310
I can't tell you how many times I would wrap up a test and then be annoyed at myself for forgetting

08:30.310 --> 08:33.250
to capture screenshots of the hosts that were in scope.

08:34.660 --> 08:40.330
So now I use a tool called eye witness during the recon phase of the pen test so that those screen shots

08:40.330 --> 08:43.670
are good to go when it comes time to write the report.

08:43.720 --> 08:51.490
If you do a quick Google search on eyewitness get hub you will find the get how project for eye witness.

08:51.490 --> 08:53.470
Now if you've never used get heard before.

08:53.470 --> 08:54.540
No worries.

08:54.670 --> 09:00.270
The steps in syntax to install a get how Project is usually pretty simple.

09:00.330 --> 09:08.100
We're going to do is click the clone or download link then copy the command in the pop up into our clipboard

09:10.210 --> 09:12.490
next in a terminal window we'll type.

09:12.490 --> 09:21.100
Get space clone and then paste in our command followed by a destination directory.

09:21.100 --> 09:29.020
Personally I like to use the slash opt folder for this so I'll type slash Opt. slash eyewitness and

09:29.020 --> 09:31.290
hit enter.

09:31.400 --> 09:36.740
Once the project is copied I would normally recommend you read the read me but to save us some time

09:36.740 --> 09:39.350
I'm going to skip ahead and run the set up.

09:39.380 --> 09:46.190
Sh script which automates the installation of any additional dependencies or configuration we might

09:46.190 --> 09:49.250
need to do.

09:49.500 --> 09:50.940
Now that eye witness is good to go.

09:50.940 --> 09:55.280
Let me show you a few simple examples of using it.

09:55.320 --> 10:01.920
Let's say I have a list of your else for my scan or pen test and I simply want eyewitness to fly by

10:01.920 --> 10:03.730
and grab a screenshot of each one.

10:04.630 --> 10:07.430
All we need to do is set up a you are elist.

10:07.730 --> 10:15.160
I'll just call mine you or else directx t and then type a list of your else into it one per line.

10:16.940 --> 10:27.410
Then I'll call eye witness and add a TAC f followed by my you or else RTX t followed by tac tac web

10:28.040 --> 10:30.310
which will take an H TZP screenshot.

10:31.490 --> 10:33.090
So let's let that go.

10:34.180 --> 10:41.620
And when it's done eyewitnesses play it enough to ask us if we'd like to open the report will say yes

10:41.710 --> 10:49.600
and boom our Web browser opens with not only some nice screen shots of each host but a bit more information

10:49.600 --> 10:52.340
on the web services running on it as well.

10:53.890 --> 10:59.920
We can simply click in to each screen shot to get a larger view and from there it's really easy to pull

10:59.920 --> 11:01.370
the image into an editor.

11:01.370 --> 11:03.160
Do some quick cropping.

11:03.160 --> 11:08.400
So it fits a little nicer into your pen test reports.

11:08.420 --> 11:14.660
Now let's say we're doing a scan or a pen test where we already did a full and map scan and saved the

11:14.660 --> 11:18.370
output to the three different file types.

11:18.410 --> 11:25.340
What's really nice is eye witness can simply take advantage of your existing scan in SML format by calling

11:25.380 --> 11:30.200
eyewitness with the TAC X space.

11:30.320 --> 11:40.390
The name of your file that has an X M-L extension plus tac tac weap and once the process is complete

11:41.200 --> 11:47.140
will again be asked if we want to open up the report and boom we are all set.

11:49.280 --> 11:56.800
Also don't forget eyewitness can also snag screenshots of VNC and RTP connections.

11:56.810 --> 12:00.500
The syntax is largely the same as our very first scan.

12:00.860 --> 12:09.770
We'll use eyewitness space tech f space the file name and then at the end you'll add either tac tac

12:09.960 --> 12:19.720
RTP for remote desktop services or tac tac VANOC for VNC coin's.

12:19.880 --> 12:26.570
Overall the flexibility and functionality of I-Witness can help us greatly both on the front and back

12:26.570 --> 12:30.580
ends of our vulnerability scans and penetration tests.

12:32.230 --> 12:38.110
In our next video we will start diving into a tool called Open vals which has a powerful scanning engine

12:38.110 --> 12:42.680
you can use to automate the discovery of vulnerabilities within your network.
