WEBVTT

00:00.600 --> 00:02.315
Welcome to The End, Matt, scripting

00:02.430 --> 00:04.169
engine vulnerability scanning and

00:04.170 --> 00:06.299
exploitation lesson in previous

00:06.300 --> 00:07.739
lessons, we've covered various

00:07.740 --> 00:09.689
aspects of mapped scripting engine.

00:10.080 --> 00:11.309
I've shown you how to perform a

00:11.310 --> 00:13.259
couple script scans and get

00:13.260 --> 00:15.029
help information about scripts from

00:15.030 --> 00:17.039
both the command line and in zone

00:17.040 --> 00:18.029
map.

00:18.030 --> 00:19.709
This lesson will go over some of

00:19.710 --> 00:21.376
that stuff, but we'll focus on the

00:21.420 --> 00:22.792
use of NSC for vulnerability

00:23.520 --> 00:25.320
scanning and target exploitation.

00:25.770 --> 00:27.485
The truth is NSA could be an entire

00:27.930 --> 00:29.489
training series on its own.

00:29.730 --> 00:31.769
So this lesson will focus on giving

00:31.770 --> 00:33.329
you the tools to get started.

00:33.690 --> 00:35.009
Here are the learning objectives for

00:35.010 --> 00:36.010
this lesson.

00:36.360 --> 00:37.799
First, we'll briefly answer the

00:37.800 --> 00:38.769
questions.

00:38.770 --> 00:40.349
What is the unmap scripting engine

00:40.350 --> 00:41.350
and how does it work?

00:41.940 --> 00:43.529
We'll examine how and map scripting

00:43.530 --> 00:44.999
engine gives us the ability to

00:45.000 --> 00:46.450
perform advanced scanning.

00:47.400 --> 00:48.689
Then we'll go through a lab that

00:48.690 --> 00:49.915
demonstrates its use as a

00:50.160 --> 00:51.569
vulnerability scanner and

00:51.570 --> 00:52.619
exploitation tool.

00:53.880 --> 00:55.350
So what is the unmap scripting

00:55.440 --> 00:56.219
engine?

00:56.220 --> 00:58.289
Well, up until this point, many

00:58.290 --> 00:59.879
of the features and functions that

00:59.880 --> 01:01.379
we've learned about in MAP basically

01:01.380 --> 01:03.179
require you to execute one command

01:03.180 --> 01:05.489
at a time, then gather the results,

01:05.790 --> 01:07.169
which generally leads to more and

01:07.170 --> 01:08.639
more single commands for further

01:08.640 --> 01:09.640
investigation.

01:10.170 --> 01:11.738
One of the neat things that NIST

01:11.760 --> 01:13.230
allows us to do is write out a

01:13.380 --> 01:14.969
series of commands in the form of a

01:14.970 --> 01:16.538
script that can be dependent and

01:16.950 --> 01:18.539
related to one another in such a way

01:18.540 --> 01:19.919
that our time can be much more

01:19.920 --> 01:21.439
better focused on analyzing the

01:21.780 --> 01:23.620
results instead of on

01:23.670 --> 01:25.409
typing in a command at a time and

01:25.410 --> 01:26.410
weighting.

01:26.610 --> 01:28.400
The way you do this is by using and

01:28.410 --> 01:30.060
maps built in scripting engine,

01:30.360 --> 01:31.781
which uses the LUA programing

01:31.980 --> 01:32.969
language.

01:32.970 --> 01:34.499
The creators of that map like to say

01:34.500 --> 01:36.329
that Nessy provides the ability

01:36.690 --> 01:38.340
to automate networking tasks.

01:38.550 --> 01:40.069
Lua works very nicely for Unmap

01:40.530 --> 01:41.902
because it is an interpreted

01:42.150 --> 01:43.650
language and not compiled.

01:43.830 --> 01:45.119
That basically means that you can

01:45.120 --> 01:46.786
use any text editor to create your

01:46.890 --> 01:48.213
scripts, then run them from

01:48.870 --> 01:50.438
the unmap command line or within

01:50.760 --> 01:51.760
Zenab.

01:52.020 --> 01:53.879
Lua is extremely lightweight and

01:53.880 --> 01:55.259
has been around and refined since

01:55.260 --> 01:56.489
the early 1990s.

01:56.970 --> 01:58.734
Learning it is very easy and I think

01:58.950 --> 02:00.389
you'll find that it is well worth

02:00.390 --> 02:01.811
your time is fully documented

02:02.400 --> 02:03.959
on their website and best of all,

02:03.960 --> 02:05.939
it's free and built into and map.

02:06.870 --> 02:08.438
Each and every script contains a

02:08.669 --> 02:10.433
field that associates it with one or

02:10.470 --> 02:11.470
more categories.

02:11.640 --> 02:13.061
Those categories are auth for

02:13.320 --> 02:15.270
authorization, broadcast

02:15.720 --> 02:17.759
default, discovery.

02:18.240 --> 02:19.680
Most of what and map is known for

02:20.580 --> 02:22.289
dogs. Nihil service

02:22.950 --> 02:24.540
exploit external

02:25.050 --> 02:26.730
foser intrusive

02:26.880 --> 02:28.169
which are potentially hostile

02:28.860 --> 02:30.719
malware for remote

02:30.720 --> 02:31.720
malware detection.

02:32.280 --> 02:34.499
Safe, which has little risk

02:35.250 --> 02:37.169
version for version detection

02:37.170 --> 02:38.939
signatures and vom

02:39.090 --> 02:40.589
for vulnerability detection.

02:41.170 --> 02:42.659
What is really great is that there

02:42.660 --> 02:44.489
are hundreds of NMC scripts

02:44.490 --> 02:45.960
that ship meaning download and

02:45.990 --> 02:47.099
install within MOUT.

02:48.150 --> 02:49.949
We'll go over how to find them, how

02:49.950 --> 02:51.665
to open and examine them and how to

02:51.690 --> 02:52.909
run them in different ways,

02:53.610 --> 02:55.374
they're all very well documented and

02:55.710 --> 02:58.379
map dog whack Nasdaq.

02:59.260 --> 03:00.877
Also, I should note that the code

03:01.150 --> 03:02.919
base of scripts unmap site is

03:02.920 --> 03:04.419
constantly being added to

03:05.500 --> 03:06.970
finally, you really need to be

03:07.000 --> 03:08.820
careful with NSC scripts.

03:09.610 --> 03:10.689
They have the potential to do

03:10.690 --> 03:12.129
harmful things to your computer,

03:12.730 --> 03:14.439
computers on your network and target

03:14.440 --> 03:15.440
hosts.

03:15.460 --> 03:16.989
Make sure you only run scripts that

03:16.990 --> 03:18.749
you downloaded from the map Web site

03:19.240 --> 03:21.099
wrote yourself or got from someone

03:21.100 --> 03:22.100
you really trust.

03:22.480 --> 03:24.146
As with any unmap scan, understand

03:24.460 --> 03:26.289
the effects of the scan on both

03:26.290 --> 03:27.909
your computer and the target.

03:29.730 --> 03:31.079
So how does the end map scripting

03:31.080 --> 03:32.550
engine work while this is sort

03:32.910 --> 03:34.169
of a trick question because there

03:34.170 --> 03:35.519
are several regular command line

03:35.520 --> 03:37.186
switches that cause scripts to run

03:37.410 --> 03:38.410
by default.

03:38.970 --> 03:40.360
For example, I've shown you the and

03:40.380 --> 03:42.419
map dash capital ASCAN in the past,

03:42.660 --> 03:43.889
which I call the advanced and

03:43.890 --> 03:44.890
aggressive scan.

03:45.150 --> 03:46.767
That scan actually runs every NSC

03:47.400 --> 03:48.839
script that has been labeled in the

03:48.840 --> 03:50.261
category default, among other

03:50.490 --> 03:51.490
things.

03:51.720 --> 03:53.340
But for the sake of clarity, there

03:53.370 --> 03:54.719
are two command line switches that

03:54.720 --> 03:56.669
can be used to specifically initiate

03:56.670 --> 03:58.319
the end map script scripting engine

03:58.710 --> 04:00.569
they are and map dash

04:00.570 --> 04:01.570
s capital C and

04:02.580 --> 04:04.439
map dash dash script

04:05.250 --> 04:07.139
like and map dash capital A

04:07.170 --> 04:08.170
and map dash s.

04:08.550 --> 04:09.677
Capital C also runs and

04:10.710 --> 04:12.269
map scan using all of the scripts

04:12.270 --> 04:13.349
that have been labeled in the

04:13.350 --> 04:15.509
default category on the other hand.

04:15.510 --> 04:17.078
And Map, dash dash script allows

04:17.459 --> 04:19.174
you to specify the exact script you

04:19.200 --> 04:21.059
wish to run or even an

04:21.060 --> 04:22.559
entire category of scripts.

04:23.340 --> 04:24.839
There's some other flexibility with

04:24.840 --> 04:26.399
the dash dash script command line

04:26.400 --> 04:28.319
switch to for example,

04:28.320 --> 04:30.149
you can run every script that starts

04:30.150 --> 04:32.009
with a specific name, two

04:32.010 --> 04:33.569
or more scripts at the same time,

04:34.080 --> 04:35.501
or even use Boolean arguments

04:35.940 --> 04:37.559
to tell and map to run scripts that

04:37.560 --> 04:38.850
match certain criteria.

04:39.360 --> 04:40.699
I'll show you the stuff in the lab.

04:41.700 --> 04:42.869
The main point I'm trying to make

04:42.870 --> 04:44.519
here is that for the most part, if

04:44.520 --> 04:46.039
you want to run and map and see

04:46.110 --> 04:47.727
scripts, you'll be using the dash

04:47.940 --> 04:49.679
dash script, command line switch.

04:50.520 --> 04:52.109
The last bullet point is a link to

04:52.110 --> 04:53.879
the online man page for Nessy.

04:54.420 --> 04:55.589
There are a couple other features

04:55.590 --> 04:56.879
and options that I won't be covering

04:56.880 --> 04:58.619
in this lesson, so I recommend that

04:58.620 --> 05:00.449
you navigate to this page

05:00.450 --> 05:01.769
to see some of the other options

05:01.770 --> 05:03.289
available to you as you run and

05:03.630 --> 05:04.630
see scripts.

05:05.730 --> 05:07.102
OK, so enough talk, let's do

05:07.560 --> 05:09.089
a lab in this lab,

05:09.390 --> 05:10.920
I'm going to demonstrate some of

05:11.190 --> 05:12.190
these capabilities.

05:12.360 --> 05:13.679
My main goal is to give you enough

05:13.680 --> 05:15.329
information about NSC that you feel

05:15.330 --> 05:16.529
comfortable trying it out for

05:16.530 --> 05:17.530
yourself.

05:17.610 --> 05:19.178
Also, I want you to see how good

05:19.470 --> 05:21.149
and maps built in scripts are at

05:21.150 --> 05:22.619
detecting vulnerabilities and

05:22.620 --> 05:23.620
exploiting them.

05:23.910 --> 05:25.319
I truly believe that NSA's

05:25.320 --> 05:27.029
capabilities are only limited by

05:27.030 --> 05:28.304
user support and desire to

05:28.560 --> 05:30.149
contribute to this amazing tool and

05:30.150 --> 05:31.139
community.

05:31.140 --> 05:32.369
We're going to find a Cisco switch

05:32.370 --> 05:33.749
on my network, see if it has some

05:33.750 --> 05:35.416
vulnerabilities, then exploit them

05:35.670 --> 05:36.670
and see what happens.

05:37.080 --> 05:38.549
Before we do that, though, I'll show

05:38.550 --> 05:40.167
you where to find Nze scripts and

05:40.560 --> 05:41.690
remind you how to get help

05:41.700 --> 05:42.870
information about them.

05:43.440 --> 05:45.419
And I'll show you how to run several

05:45.420 --> 05:47.000
or many of them at the same time.

