Hi, everyone, welcome back to the
course. So in the last video, we
went ahead and launched her career
Impact Pro and we ran our first
scans. So again, we ran the fast
scan. If you haven't done that yet,
you'll definitely want to do so
before you continue on on this
video. So going pause this one, go
back to the last video and make sure
you run that initial scan here.
As I mentioned, it takes roughly
about four to five minutes to run
the scan. I just went ahead and
stopped the video and we pick things
back up in this one.
So you'll notice here at the top.
Right. My status now has finished.
So I'm all finished with that fast
scan.
So let's go back to our lab document
here. So we've gone ahead and ran
our fast scan here in step 19.
Now, instead, 20 cut in the
center of our screen here is kind of
the bottom part of the center.
We see our results and we see the
devices that we found in the scan.
So, of course, no one here is going
to be on once we click on the wind
file.
What's the operating system?
So that's question number one.
So I want you guys to go ahead and
answer that one there.
So if I click on the wind file here,
we can take a look in the bottom box
here and we can take a look and see
what kind of operating system is in
use.
All right, so for me, I see Windows
2008 standeth
out hypervisor service back
on there, and you should have the
same result in year end unless
something's dramatically changed
when you're watching this video from
the time I filmed it.
But I do not anticipate that.
So we should be good to go.
All right. So now we're going to run
a little a little longer
out a little more in depth scan,
sort of go ahead and do that now.
So same thing here.
We're going to go back to the network
information gathering.
So we're going to double click out
on the top left here.
So let's go into that now.
Again, it opens up our Wizzard for
us. We're just going to say next to
that initial one there, we're also
going to just stay with core impact,
Will, and we're going to keep IPV
Virgencita excuse me for for
as well as our network range.
We'll leave that alone.
Now, here's where we will
differentiate it.
We're actually going to do a
detailed scan.
So let's go back to our lab document
here.
So we've gone through Sep 22.
We went ahead and click next after
we launched the network information
gathering wizard, we
left the default as core impact pro.
We left it as IPV for
and we also left our IP address
range intact.
And then again, the only change
here is we're instead going to
be running a detailed scan this
time. So I want to stress this
one will probably take more than
five minutes.
This one probably takes closer to
seven or eight minutes to complete.
So just keep that in mind.
I'll go ahead and pause video once
I've launched this one here and
we'll pick it back up once it's
completed on my end.
But go ahead and feel free to pause
the video as well on your end so you
can pause it and
take a look once we pick things back
up, once it's actually finished to
scan.
So leave it as default
of detailed here and then just say
next.
The other thing you want to do here
is just uncheck this box is top
boxes says perform surveillance
cameras of fingerprinting because we
don't actually have surveillance
cameras hooked up here, so
we'll not do you any good.
So just go ahead and check that box
and then just click the finish
button next.
And so what you'll see here is
you'll see that scan that we just
started running on the top
right here.
So, again, I'm going to go ahead,
pause the video here and pick it
back up once this is finished and
you could do the same thing.
You can pause this video here
as well. And once it
once you're finished is on your end,
you can pick things back up.
All right. So welcome back.
My scan is finish on my end again.
If you're scared, still going.
You can go ahead, pause the video
and just wait until your scan
finishes or you can just follow
along and then finish out the lab as
yours finishes.
So we went ahead and ran our
detailed scans.
We go back to our lab document here.
You'll see if that ticks.
We went ahead and ran our detailed
scan. If you recall, we uncheck that
box regarding the secure security
or surveillance cameras just because
we don't have any of those hooked
up. And this particular lab
and it took for me, it took right
around just about two
or three minutes, actually.
So it's pretty quick this time.
But normally it was taking me about
four to five minutes. So hopefully
yours is going quickly as well.
So my scans finished.
The question I want you to
look at in answer is,
do you notice any differences in the
results between the faster the
detailed scans?
So if we go back to our
scan output here, so if we take a
look at our detailed one, do we
notice any additional information or
any different information from
the previous scan that we ran?
So it's kind of a around at the
different results and
see if you notice any differences at
all.
So for me, I do notice that the
detailed scan does produce a little
more results, so if you go back up
here to this one here,
we don't see quite as in-depth
information on each particular
item.
It does it does tell us a little
more about these unknowns, or at
least as sure it doesn't look like
it has.
More information, but it actually is
not looking like it did
properly, so what we
should see with a detailed scan is
more information on these targets
specifically. It should be actually
naming this one for us, but
it's not doing so.
It looks like there may be an error
in this particular lab, but do you
get the overall concept if we run
a quick scan or, you know, something
basically a fast scan, it's
not going to produce as much results
in a vulnerability scan as if we
do a detailed scan now, keeping in
mind that we're touching
the target right now.
Right. So with a vulnerability
scanner, we're touching this target.
So they're going to know we're doing
something.
And there's ways, you know, we can
obfuscate who we are, etc.
but they're going to, generally
speaking, know who
you know. They're going to know that
somebody's scanning their system
and or their systems and looking
at the information and potentially,
you know, they're going to assume
that's going to be an attacker and
shut us down.
Essentially, you know, if we're using
a particular IP address, if we're
not asking it for some unbeknownst
reason, they're going to probably
shut us down.
So this is an easy way to trigger an
I.D. rips system,
but it is a valuable
approach.
Once you're in the enumeration phase
to specifically find a lot of
vulnerabilities, you'll see it more.
When we do the open source lab,
you'll see it'll make a lot more
sense because we'll actually be able
to see a listing of vulnerabilities.
So in this video, we just wrapped up
our discussion on core impact.
Again, we just ran a couple of quick
scans to potentially
take a look. There are different
results. It looks like this time
around it was not functioning
properly for some reason, but
generally speaking, it is.
You can probably assume a detailed
scan is going to provide a lot more
information than a quick or fast
scan.
So, again, join me in the next video
where we wrap up our second lab
and we'll be covering open valves in
that particular lab.