You may find yourself sometimes trying to remember all the different options
and flags
and everything like that to go with all the different commands that we use,
along with the tools inside of Cali and beyond. And that's okay, because what
we're doing is
not necessarily learning everything by the syntax. We're learning its actual
use and getting
familiar with what tool to actually call upon in time of need. To be able to
remember everything is
really not obtainable, but we can always use references because in the real
world we'll have
our notebooks, we'll have access to the internet. So don't be afraid to be able
to use references
or even come back to this very skill and course in case you need a little bit
of a refresher inside
of in-map or some of the other tools we use. Now bring that up for a very
specific reason.
And what we're taking a look at here on the side screen is over there an in-map
cheat sheet for
all the different flags and everything that we'll be using. Some of them will
be using throughout
this course in order to be able to conduct our actual scanning process within
the pentesting
life cycle. Now we're not going to go over each and everything within here, but
I do want to make
this available to you. And that's why it's an attachment file below this very
video. So if you
do get a little confused or like me just flat out and get some of the things
that these commands
are here for you in order for us to learn and make ourselves better at pent
esting. In addition to that,
everything that we're going to be doing inside of in-map can be replicated
inside of in-map,
which is the GUI representation of in-map or vice versa if you want to do that.
Because I've
often used in-map here in order to refresh myself over in-map syntax. So by
combining the actual
GUI form of in-map here along with the cheat sheet that we have available to us
inside of the
skill itself, we should have plenty of resources to be able to go through and
start piecing together
how it is that we want to begin our scanning. And for a quick refresher on how
to use in-map,
I'm going to zoom in and show you real quick that up on the top left is our
actual target.
Now this target can be an individual system or an actual subnet. And if you're
going to use a
subnet, the cider notation needs to be used on the network ID. So for instance,
if I want to be
able to scan 192.168.247.0/24, that's going to scan the entirety of the actual
class C subnet.
And based on the quick options that we have now that I'm zooming in for us,
here under profile,
we can go to a preset that's available to us and get also the syntax that would
go with that inside
of actual in-map or in-map itself. For instance, if we wanted to do an intense
scan and all TCP
ports, we can see right here as I zoom back in for us on the command line that
we have in-map,
that's P1 through 65,000, 535, et cetera, et cetera, et cetera. And if we
correlate that with our
actual cheat sheet that's available to us right below this video, we can see
that all of these
different flags line up with all the different commands that we want to utilize
. And we can tailor
between using ZenMap as our baseline for learning along with the cheat sheet
for whatever else
in-map needs to be utilized for and combine those two together to run it inside
the actual
terminal window itself. Now, you may be wondering why we would still want to
use the actual terminal
itself. And there's a couple of reasons that I want to point out here for you.
First and foremost,
it makes us more versatile in running command at the terminal level. So that
way we're more
familiar and comfortable with it. Number two, our system resources. As you can
see back here,
I'm actually developing a lab right now for us to be able to use in this skill,
but it's resource intensive. And it's going to take a little bit for me to get
this made for you
along with configuring all the different things that we want to use. And that's
because a lot of
what's being the utilized in here is GUI based. Now, yes, we are wanting to use
GUI based systems
and displays for us to be able to get a better feel of what's going on. But the
fast,
nitty gritty straight to the point is always using the terminal for that low
overhead cost on the
resources.