Welcome to the lesson on constructing an end map scan.
This lesson is not intended to go into detail about building complex and map scans. The main point of it is really to show you several important command line switches. You should know about an end map because they're critical to consider in every single and maps can.
And I want you to see that map scans congee constructed in a variety of different ways. My hope is that you will figure out a way that works well for you and stick with it as you experiment within map.
Let's get started.
Here are the learning objectives for this lesson.
First, I'll remind you about how to get help.
Next, we'll go over basic requirements oven and maps can.
Then I'll answer the question. Does it matter what order options are blazed in and maps can?
Well, then cover two really important options that you should consider in every and maps can.
I'll talk to you briefly about a regular scan versus a script scan and finally will go through a quick lab on constructing an end maps can that will demonstrate the concepts discussed in this lesson.
If you haven't already. I suggest going back and revisiting Lesson 2.9, which was about ways and map. Users can get help
as a refresher. Let's go over a couple
simply diving in map or and map of space. Dash H Been hitting. Enter on your keyboard at the command. Prompt will show you many of the different options you have available in N map.
There isn't a tiny detail there, but it's a great way to remind yourself of the many options available and how to use them.
If you're considering running an NSC script,
you can type in map space. Dash dash, script dash help
space the name of the script
than hitting. Enter
if you want much more detail and are running Lennox or UNIX, Mac Os included.
You can type man space and map, then hit Enter
to dig his deepest possible. You should go to the End map website, which now includes Theodore's entire book.
I put a couple of key or else in this slide
finally, either create for yourself or find a cheat sheet online.
I will include one in this lesson, and I believe it will help a lot.
I won't include every single command or command sequence, but we'll share a single page of what I consider to be the most important and map scans, especially when you're starting out.
So what are the basic requirements? Oven end map scan?
Well, first of all, you must have an map installed properly.
If you've installed it according to my previous lessons, you should be good to go.
Secondly, and especially when starting out
open your terminal or Windows Command prompt as a privileged user
or what I should say is, if you're using Lennox UNIX or the Mac OS,
run and map using pseudo.
If you're running windows, open the command prompt. As administrator,
I'm sure you know what I mean here, but I'll demonstrate this in the lab.
The next thing to consider is where in the file system you are running and map from and whether your environment variables specifically the path variable are set correctly.
I'll show you this in the lab.
Finally, the most important thing that you must include in every single and maps can is the target.
No matter how sophisticated your scan is without a target, it will fail
every time I execute a command line program. I wonder, Does it matter what order I placed the switches or options in?
Well, unlike some programs or environments, an end map it really doesn't matter too much. In other words, you can type the switches that indicate the type of scan before or after the target.
For example, you could tell and map to scan 1 92.1 68 that one. That one
been placed. The details about the type of scan you want to perform, such as the dash capital A for an advanced scan or
dash capital O
for an operating system detection at the end.
You can also provide details about what layer for protocol or what ports before or after the type of scan or the target.
This provides for a lot of flexibility and a lot of different styles.
So does it really matter what order you put your command line options? Not really.
One thing that I think you should determine early on in your end map. Scanning adventures, though, is where you put your target and output options,
play around with a couple of different ways to do it and decide which way suits your needs.
I'll tell you the way that I usually do it, though, just in case it makes sense to you.
I typically place all my command line switches before the target and output. In other words, I put the target an output type at the end of every end map statement
as we go through scans later on, you'll see exactly what I mean.
But as an example, if I'm doing a simple advanced scan on a target, let's say scan me dot and map dot or GE and want toe out. Put the results into an XML file.
I would type
and map space, dash capital, a space scan me dot and map dot or GE
space. The target
dash oh, capital X space results dot xml.
So the type of scan was determined by the dash capital? A.
Then I put the target.
Then I put the output option.
The reason I like this is that scans can sometimes get really long
after they execute. I can simply hit the up arrow on my keyboard, then on Lee change the name of the output file or the target very simply because they're at the end of the command.
So even though it really doesn't matter too much from n mouse perspective
from a success or failure or performance standpoint, it matters from a usability standpoint.
I'll show you what I mean in the lab, just in case this isn't clear.
Another thing I think you may want to consider is the previous lesson on any maps can phases.
So think about how unmapped processes a scan from phase two phase
and try to put your command line switches in that general order.
Sometimes this helps from a conceptual standpoint because it forces you to think about what it will take for your scan to be optimized.
This will take a little bit of time to master and may only be pertinent to some of you.
But I'd say that thinking about scans in this manner
has really helped me a lot to learn and map and memorize most important options and how and why they're used.
find a standard that works well for you and stick to it
along with higher level reasoning and conceptualization. I'm a firm believer that most of us get really effective and efficient through rote memorization, executing and map scans using the same basic format every single time will really help you to burn the most important command line options into your mind.
Pick the style that works best for you and stick to it.
Now that I explained to you that I like to put the target and output type at the end, I'll discuss a little bit of detail about these two options.
For the target specifications, you can use many different options. You can use a local or remote host name or fully qualified domain name.
You can use an I P address where you can use multiple host names or I p addresses.
Additionally, you can use an entire network insider notation. For example. 192.168 dot 1.0 slash 24 would indicate every host on the 1 92.1 68 that 1.0 network.
You can also provide and map with a file that has all of the host names and or I P addresses that you want to scan.
The options are almost unlimited.
In fact, you can even ask and map to choose a number of random targets.
You can also provide and map with a bunch of targets than tell it which ones of those to exclude.
We'll go over all this stuff later on.
Now for the output
again. And map has a lot of capabilities here. The big things to consider our one. Do you want your output to go to the screen or to a file
too? If you wanted to go to a file, what format do you want it in? And three. How much detail do you want? Your skin and its results.
Dash Oh, capital end, followed by a foul name, will output the results to a text file that you specified in the normal and Matt format
Dash Oh, Capital X will output it to an XML formatted file
dash Oh, Capital s will out. Put it in script, Kiddie format
dash Oh, Capital G will output the results in a gribble format. For those of you who like to use ***
if he used dash oh, Capital A, followed by a file name without an extension
and map will create three different output files in normal xml incredible format.
The last two options I put here are Dash V and Dash V V
replaced them with all the output formats because what thes two options do is determine the level of detail or verbosity, which is what the V stands for
in the output.
If you leave them out
and map will output a normal level of detail. If you add the Dash V switch, it will increase the level of detail.
And if you add the dash V V, it will increase the level of detail even more
again. Play around with these options with some simple scans, you'll figure out the amount of detail that's right for you,
even though you have a lot of flexibility with how you construct your own map scan statements. There's a key distinction I'd like to make, and that's between a regular scan and an NSC script scan.
The same rules about the target and the output still apply, but a standard regular scan is usually simpler.
For example, you can run a regular simple scan against scan me dot and map dot org's by simply typing and map space. Scan me dot and map dot org's.
However, if you want to execute one of N maps and A C scripts against the same target, you would have to type and map space.
Dash s Capital C Space Scan me dot and map dot or GE,
which will run every NSC script labeled as default against the target,
or you would type
and map space. Dash Dash script equals the script name
Space Scan me dot and map dot org's
the main point that I'm trying to make here. Is that a simple script? Skin as one additional command line switch as a basic requirement of a scan?
We'll go into much more detail about NSC scripts later on, and I'll show you what I'm talking about in this lessons lab so you can follow along.
In this lesson. I reminded you about the value of help and where you can get it quickly.
I talked with you about the basic requirements Oven and Mount scan statement.
We discuss whether or not the order in which an end maps can statement is typed matters.
I showed you the two most important options target an output that you need to consider in every scan.
We then looked at the difference between a simple regular scan versus a script scan. The next lesson will run through the lab on constructing an end Maps can.
Thanks so much for walking through this lesson with me and I'll talk to you in the next lesson.