In our challenge, we were taking a look at how to conduct a
basic scan inside of OpenVos, and that's exactly what we're
going to be doing. And I'm going to do this on the actual
host VM in Hyper-V for our lab environment 192168.01. And
in the default window here, originally we start off a
dashboard inside of OpenVos. If you expand scans on the left,
as I zoom in for you here, I'm just going to go into Task.
And inside of task, I'm just going to click on our new word
document and say new task, new word document icon. I want to
clarify that. Now I'm going to call this one specifically
Hyper-V. And I'm going to comment that this is the host
Hyper-V. Now for scan targets, I don't already have this inside
of my target list. I'm going to create a new one by clicking on
the document icon to create a new target. And I'm going to call
this the Hyper-V host. I'm going to manually input the IP
address in of 192.168.0.1. And I'm going to leave everything
else default as far as the target is concerned. I'm going to save
and then go back to our new task window and leave everything
in the default here as well, because I just want to do a very
basic scan inside of OpenVos. Click on Save and we see that
it's already added inside of the actual task window itself.
Now at this point, since I didn't select any kind of duration
for our scheduling, I can just go ahead and click on the start
or play button for this particular scan. And I'm going to
jump ahead to when this scan is actually completed and then
come back to the results.
I did them. I do want to point out that on the left, right
below the scans drop down is the assets. And if you expand
that and go into host while the scan is still running, you will
see that 0.13 is the only one that we have in there. After
the scan, you will see that 0.1 is going to be added as well.
And you could also browse through here to look at different
types of targets. On the left, if you go into configuration,
drop down and I'll zoom in for you here real quick, you could
see that there is a targets list on there. And we're just going
to select targets. And you could see that they're on there
named first by order of alphabetical. And then the actual
IP address that it's actually belonging to. So this is a little
bit elbow to hand as we keep saying inside of OpenVos. But
for me, it's the results over the actual configuration of how
this works inside of its GUI form. I'm going to go back to my
task and check on the scan running and I'll be back right
after this is complete. And just like that, our scan is
complete. Now I want to show you something real quick first so
that way you don't think I'm hiding anything. If we expand
the Hyper-V target under name inside of our task here and
scroll down, we can get an idea about how long this actually
took instead of just a split second that I changed frames
here for a second. And that is as we zoom in duration of last
scan, 13 minutes. And we can easily just scroll back up and
take a look at the results by clicking on the number right
below reports in that same column, which is one. And you can
see here that we have our actual report nicked up and there are
only mediums as the highest severity level for what was
actually reported by going into it, we can go straight to the
closed CBEs because as you can see as I zoom in, there's no open
CBEs that are actually reported on this particular instance. The
only ones that came up were all these that have already been
closed. And you could see by the CBE year that they've been
around for quite some time. So I'm willing to bet that this
Hyper-V host of Windows server edition is one that was had a
basic install put on it. And with wasn't done with with
security at the forefront, it was just made to be a host for
that lab environment, which is perfectly fine in this
environment because it is a lab environment and doesn't have
that much outreach to the rest of the world, along with the
fact that they're not on very long. We move over here, we can
see that those have been rated high just because primarily
because of the age behind them. But if we go into the actual
results tab, and we could see where this that medium came
from, zooming in, we can see that this is a common, common
occurrence inside of Windows operating system, specifically
with server. So if you start doing a lot of scans and you're
on, let's say like a blue team, you'll be seeing DC/RPC come up
a lot. And the reason for that is because inside of our lab
environment, we're remote into it using RDP. And that's going
to be tying into that MSRPC service that allows us to be able
to tie in those services and functions for us to allow that
to happen. But you can actually go further into it. I just
wanted to go into the idea that we can run our scans, get an
idea for them and also get familiar with another vulnerability
assessment scanning tool for our pintesting toolkit that doesn't
have to be necessary, and can provide us not only results to
verify things that we've seen in other vulnerability scanners,
but also maybe find some other stuff that we haven't really
noticed before, and have that whole trust but verify platform
ahead of us so that way we can zone in on some of the things
that are easier to attack as pintesters, so long as it's
written scope and the rules engagement. I hope this has
been informative for you, and I'd like to thank you for viewing.
[BLANK_AUDIO]