Vulnerability Scanner Setup and Configuration of Core Impact Part 2

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

8 hours 49 minutes
Video Transcription
Hi, everyone. Welcome back to the core. So in the last video, we went ahead and launched her core impact pro, and we ran our first skin. 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 this video. So go ahead and pause this one. Go back to the last video and make sure you run that initial scan here.
As I mentioned, it takes roughly around 45 minutes to run the skin.
I just went ahead and stop the video, and we picked things back up in this one. So you'll notice here at the top, right? My status now says finished. So I'm all finished with that fast skin.
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 credit in the center of our screen here is kind of the bottom part of the center. We see our results. So we see the devices that we found in the scam.
So, of course, the number one here is gonna 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 through that one there. So if I click on the wind file here,
we could 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 standard without hyper visa service back on there. And you should have the same result in your end. Unless something's dramatically change 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 gonna run a little a little longer. Scan now a little more in depth skin. So we're going to do that now. So same thing here. We're gonna go back to the network information gathering, so we're gonna double click out on the top left here.
Let's go and do that. Now, again, it opens up our wizard for us. We're just going to say next to that initial one. There were also going to just stay with core impact prose Well,
and we're gonna keep I p v version City sees me version for
as well as our network range will leave that alone. Now, here's where we will differentiate it. So we're actually gonna do a detailed scan. So let's go back to our lab document here.
So we've gone through set 22. We went ahead and click next after we launched the network information gathering wizard
we left. The default is core impact Pro. We left in his I p v four and we also left our i p address range intact.
And then again, the only change here is where instead, gonna 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 Paul's 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. Seacon,
uh, posit and take a look once we pick things back up once it's actually finished the skin,
so leave it as default of detailed here and then just say next.
The other thing you want to do here is just unchecked. This box is top boxes. Says perform surveillance cameras of fingerprinting because we don't actually have surveillance cameras hooked up here. So I will 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 of right here. So again, I'm gonna go ahead Paul's video here and pick it back up Once this says finished, and you could do the same thing, you can pause this video here a cz Well, and once it once you're finishes on your end, you could pick things back up.
All right, so welcome back. My scan is finished on my end again. If your scans still going, you can go ahead. Paul is a video and just wait into your scam finishes. Or you could just follow along and then finish out the lab as yours finishes.
So we went ahead and ran our detailed scans for? Go back to our lab document here, you'll see instead. 26 we went ahead and ran our detailed scan. If you recall, we unchecked that box regarding the secure security or surveillance cameras just because we don't have any of those hooked up on this particular lap
and it took for me, it took right around, Uh, just about two or three minutes, actually. So it's pretty quick this time, but normally it was taking me about 4 to 5 minutes. So hopefully yours is going quickly as well. So my scan's finished the question I want you to look at. An answer is,
Do you notice any differences in the results between the faster the detailed scan? 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 skin that we ran?
So it's kind of look 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. Now it's time to go back up here to this one here.
We don't see quite is in depth information on each, eh? Particular item
it does. It does tell us a little more about these unknowns or at least a shoe. 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 of if we run a quick scan or, you know, something of basically a fast scan
it's not gonna produce is 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 the vulnerability scanner, we're touching this target, so they're gonna know we're doing something. Um, and there's ways, you know, we can office Kate who we are, etcetera. But they're going to generally speaking, no. Who, You know. They're gonna know that somebody's scanning their system and other systems and looking at
the information A potentially. You know, they're gonna assume that's gonna be an attacker
on and shut us down. Essentially, you know, for use in particular I p addresses. We're not masking it for some unbeknownst reason. They're gonna probably shut us down. So this is an easy way to trigger an I. D. S R I. P s system, but it is a valuable approach. Once we're in, the enumeration fades to specifically find a lot of vulnerabilities.
You'll see it more when we do the open Voss 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 court impact again. We just ran a couple quick scans potentially take a look. They're different results. It looks like this time around, it was not functioning properly for some reason. But generally speaking as it is, you can probably assume a detailed scan is gonna 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 vaults in that particular lab
Up Next