WEBVTT

00:01.110 --> 00:08.580
Welcome to the video and map output formats in this video we will learn how to output our and map scan

00:08.580 --> 00:14.530
data into a simple text file either silently or with live output in the terminal window.

00:15.320 --> 00:23.780
And we'll also look at some other popular formats such as credible output SML and HMO and even unmap

00:23.780 --> 00:29.390
shortcut that lets you export a scan to several popular formats all at the same time.

00:30.410 --> 00:37.320
In a few of our past videos I showed you how to make a quick and dirty report of your and map scan data.

00:37.340 --> 00:44.270
One way is by simply typing your full and mapped command then at a greater than sign followed by the

00:44.270 --> 00:45.780
name of an output file.

00:47.410 --> 00:50.870
And when you do that you get a plain text dump of your scan.

00:51.980 --> 00:55.030
However there are a few disadvantages to this method.

00:55.960 --> 01:01.830
First of all you may have noticed that we didn't see any output from our scan till it was complete.

01:01.870 --> 01:04.220
That's not a big deal for a single host.

01:04.540 --> 01:10.130
But if we were scanning a whole subnet for example it's difficult to know how long the scan will take

01:13.090 --> 01:14.850
it could be minutes.

01:15.010 --> 01:18.360
It could be years.

01:18.370 --> 01:23.550
So to get the best of both worlds let's run the map scan with the TAC.

01:23.590 --> 01:32.540
O capital N command followed by the name of the output file followed by our targets.

01:32.570 --> 01:37.260
You'll notice that this time around we'll see the scan results as they come pouring in.

01:39.230 --> 01:44.580
Another disadvantage to text file reports is they don't let us easily search for information.

01:44.600 --> 01:54.290
We might want to see from a large output for example grep is a popular command to search files for patterns.

01:54.340 --> 02:00.460
For example if I wanted to quickly see anything that came up in my end map scan for my printer which

02:00.460 --> 02:08.250
is 1 9 2 1 6 8 3 100 I could do a search like this.

02:08.320 --> 02:14.980
Unfortunately nothing turned up because the text file I searched is not in a grep will format.

02:14.980 --> 02:19.890
However I can create a group of all output by using the unmap space.

02:19.920 --> 02:23.440
Tak o capital G.

02:23.440 --> 02:31.140
Then a file name followed by my target's and if I run my grep command again.

02:31.140 --> 02:34.410
Now I can see everything and map found on this host

02:37.480 --> 02:43.340
grep can do some extremely powerful searches but here are a few quick helpful ones.

02:44.150 --> 02:51.710
First if you just want to know what Live hosts turned up in your scan you can do that with grep quote

02:51.830 --> 03:01.940
status colon space up quote and then the name of your output file.

03:01.980 --> 03:06.980
Or maybe we want to know if any of our scanned hosts have a web service running on them.

03:07.050 --> 03:13.380
We can do that with the grep command plus the name of the port 80 in this case.

03:13.380 --> 03:22.390
Plus slash open and that will work for any port we want to do a search match on.

03:22.420 --> 03:32.540
So if we wanted to find where all my sequel servers are in the scan we could use 3 3 06 slash open and

03:32.540 --> 03:38.530
it looks like this host has my sequel plus a whole host of other interesting ports open that we'd want

03:38.530 --> 03:40.550
to investigate further.

03:40.570 --> 03:48.040
Grep has a ton of great use cases so I encourage you to check out its man page by typing man space grep

03:49.810 --> 03:56.550
on other popular output format is SML which can be read by web browsers and other software packages

03:57.060 --> 04:00.830
like text editors and Microsoft Excel.

04:01.000 --> 04:04.780
If later in your studies you start getting into penetration testing.

04:04.870 --> 04:10.930
You will find that an end map scan in SML format can easily be pulled into the Metis Boit framework

04:11.410 --> 04:18.300
which is also built right into Kalli First let's look at how you actually get a scan into SML format

04:19.080 --> 04:25.230
similar to past commands we've run we use and map plus Ptak lowercase O.

04:25.800 --> 04:36.490
And this time followed by capital x then we specify a file name and our targets.

04:36.510 --> 04:40.920
Personally I use and map data in SML format for two simple reasons.

04:41.750 --> 04:48.440
First I often find myself taking a scan from Kally and opening it in Zenn map on my Mac at a later time

04:49.690 --> 04:55.950
here and then map the ex-MIL data is really easy to click through to find exactly what I'm looking for.

04:58.220 --> 05:07.020
Another reason I like SML is it's a stepping stone towards creating a report in H.T. MLA format unfortunately

05:07.030 --> 05:11.320
unmap doesn't have a direct way to create an h tim old report.

05:11.370 --> 05:22.230
So what we do is use a command called X s l t P R O C followed by the SML file name followed by.

05:23.350 --> 05:31.200
Followed by the name of the T.M. file we want to create once we have created it we can pop it open with

05:31.200 --> 05:38.990
our favorite web browser and we've got a nice report broken down by IPS MAC addresses and open ports.

05:41.380 --> 05:46.990
Now all this monkeying around might leave you thinking well why don't I just create all the popular

05:46.990 --> 05:53.400
scanned formats when I do my scan so I can just decide later exactly what I want to do with the data.

05:54.320 --> 05:57.250
That's a great question and it makes perfect sense.

05:57.680 --> 06:01.710
So it's to do a big bad scan that will cover all your bases.

06:01.910 --> 06:10.430
We can use the TAC o capital a flag followed by the name of the scan report.

06:10.440 --> 06:20.160
Note that this time we don't add an extension and our list of targets Once the scan is done we'll do

06:20.160 --> 06:22.140
an ls in this directory.

06:22.990 --> 06:30.040
And you should now have a report in unmap format graspable format and SML format

06:34.640 --> 06:39.300
while we're here let's sneak in one extra little tip just for fun.

06:39.560 --> 06:45.890
Linux enthusiasts often love to do as much as possible with a single command either by stringing multiple

06:45.890 --> 06:52.860
commands together or sending the output of one command to another program for further processing.

06:53.170 --> 07:00.050
And these are just some simple examples Well you remember how we said and map had no built in way to

07:00.050 --> 07:02.580
create an HMO report.

07:02.730 --> 07:11.110
Since that's the case let's run our big bad output scan one more time and this time will add in to ampersands

07:11.980 --> 07:19.380
which basically is saying OK terminal run this and map command and then also run whatever I type next

07:20.730 --> 07:24.500
and let's have that second command B S S L T.

07:24.510 --> 07:34.470
Proc command to convert our SML file to an HVM Alpha.

07:34.680 --> 07:39.330
When the scan finishes we can do our ls command again and boom.

07:39.390 --> 07:45.500
This time we've got four output files and we're ready to use our map data in a web browser.

07:45.600 --> 07:52.970
A text editor or any other number of software tools in our next video we will look at a few other tools

07:52.970 --> 07:58.200
built in McCawley besides and map that help us accomplish some basic network scans.
