WEBVTT

00:01.720 --> 00:10.570
Identifying open ports and services on systems in this video we will discover any open TCAP and UDP

00:10.570 --> 00:12.500
ports on our target systems.

00:13.360 --> 00:17.700
We'll use that information to enumerate software packages running on those ports.

00:18.520 --> 00:24.430
And we'll attempt to identify the operating system running on each host as we talked about in several

00:24.430 --> 00:30.220
of our past videos and map is an incredibly powerful tool for learning more about what's connected to

00:30.220 --> 00:31.340
our networks.

00:31.570 --> 00:37.180
In the last module we did a simple ping sweep of the network to find our live hosts and we saved it

00:37.180 --> 00:40.640
to a file called Target ATX XTi.

00:40.660 --> 00:46.210
So now we're ready to perform some deeper scanning and figure out what software and operating systems

00:46.240 --> 00:47.640
are running on these hosts.

00:48.500 --> 00:53.870
Before we scan this entire list of hosts though let's get more familiar with some unmap commands by

00:53.870 --> 01:01.200
targeting just a single host for the time being the most basic and map scan you can run is just the

01:01.380 --> 01:04.860
map command followed by the target IP.

01:04.950 --> 01:14.110
I'm going to use this 1 9 2 1 6 8 3 5 IP which is the DNS server here in my test lab.

01:14.210 --> 01:17.450
From the results we get back we can glean a few things.

01:18.300 --> 01:23.510
First that map has reported the host as being live on the network.

01:23.610 --> 01:33.090
The host has S-sh DNS and HTP open and unmap has determined that this system is likely running with

01:33.100 --> 01:36.260
a VM where manufacturer network card.

01:36.510 --> 01:40.960
Also we can see here that the scan ran pretty quick.

01:40.980 --> 01:46.350
I also want to call your attention to this line here showing that nine hundred ninety seven ports were

01:46.350 --> 01:47.760
closed.

01:47.760 --> 01:53.250
It's important to know that when you do this basic and map scan with no additional flags and map is

01:53.250 --> 01:57.010
going to scan the 1000 most common ports.

01:57.230 --> 02:01.510
Now how does it determine which ports are the 1000 most common ports.

02:02.260 --> 02:10.420
By referencing the built in end map services file located here at slash us our slash share slash and

02:10.420 --> 02:10.690
map

02:14.080 --> 02:20.320
the third field in this file assigns a frequency value to each port and that frequency value is based

02:20.320 --> 02:28.770
on end maps own in-house research as well as data from IAEA and a the Internet assigned numbers authority.

02:28.780 --> 02:33.520
Now if you're interested in looking at which thousand ports are the most common you might find that

02:33.520 --> 02:40.300
challenging as this list is currently sorted by port number not by the frequency value.

02:40.340 --> 02:47.210
Fortunately with a little Linux command line kung fu we can use a command called sort to do just that.

02:47.210 --> 02:50.380
Now I know this sort command is nothing we've covered so far.

02:50.390 --> 02:55.820
But don't worry as I've done in previous videos I just like to sprinkle in some more advanced commands

02:55.820 --> 02:59.240
now and then to show you how useful the command line can be.

02:59.360 --> 03:04.230
In cases like this where we need to manipulate data to get the most value out of it.

03:05.100 --> 03:07.220
The tack are will reverse.

03:07.230 --> 03:16.100
Sort the results and the TAC K-3 will sort by the third field which is the frequency value and then

03:16.100 --> 03:22.180
I'm adding a pipe symbol followed by the word more so that we can see the results one screen at a time.

03:24.190 --> 03:29.160
We can see the end map services file is now sorted by port frequency value.

03:29.410 --> 03:37.840
So we can get a feel for which thousand ports and map is looking for by default OK let me run that initial

03:37.840 --> 03:44.030
and map scan again and point out another important consideration that often confuses new and map users.

03:44.900 --> 03:52.910
The system I'm scanning is a DNS server so we'd normally expect to see UDP port 53 open as well but

03:52.910 --> 03:55.280
we don't see that here in our output.

03:55.280 --> 04:03.540
So why is that well with a default and maps scan only the top 1000 TCAP ports get scanned if you want

04:03.540 --> 04:13.170
to scan UDP ports you need to specify that with the TAC lowercase s capital you Flegg noticed that scanning

04:13.170 --> 04:20.100
for the top thousand TZP ports took just a few seconds whereas scanning UDP ports took considerably

04:20.100 --> 04:21.900
longer.

04:21.910 --> 04:26.860
We'll talk more about why that is and how to fine tune our scans to be a bit more efficient.

04:27.040 --> 04:32.910
A little later in this course in our next video we will take the information we gathered from some of

04:32.910 --> 04:39.960
our target systems and use a built in Cali tool called Search split to identify and remediate potential

04:39.960 --> 04:41.220
vulnerabilities.
