WEBVTT

00:00:00.000 --> 00:00:10.130 align:middle line:90%


00:00:10.130 --> 00:00:12.170 align:middle line:84%
Now that we understand
what SMB is,

00:00:12.170 --> 00:00:15.590 align:middle line:84%
we'll get into how to
actually enumerate it.

00:00:15.590 --> 00:00:18.500 align:middle line:84%
Now this is the real
meat and potatoes

00:00:18.500 --> 00:00:20.450 align:middle line:84%
of what we're
trying to get after.

00:00:20.450 --> 00:00:23.630 align:middle line:84%
We're going to utilize
some Nmaps scripts in order

00:00:23.630 --> 00:00:27.080 align:middle line:84%
to actually find
some information out

00:00:27.080 --> 00:00:28.330 align:middle line:90%
from this service.

00:00:28.330 --> 00:00:33.332 align:middle line:84%
Now that we know it exists
and that it's on the system,

00:00:33.332 --> 00:00:34.290 align:middle line:90%
what can we do with it?

00:00:34.290 --> 00:00:35.790 align:middle line:90%
What can we learn from it?

00:00:35.790 --> 00:00:37.290 align:middle line:90%
That's what enumeration is.

00:00:37.290 --> 00:00:39.500 align:middle line:84%
You find a service
from port scanning.

00:00:39.500 --> 00:00:41.190 align:middle line:90%
Now, what do we do with it?

00:00:41.190 --> 00:00:42.450 align:middle line:90%
What can we learn from it?

00:00:42.450 --> 00:00:43.867 align:middle line:84%
We're not going
to exploit it yet,

00:00:43.867 --> 00:00:47.390 align:middle line:84%
but we want to gather
more information.

00:00:47.390 --> 00:00:49.675 align:middle line:90%
Nmap has a scripting engine.

00:00:49.675 --> 00:00:51.050 align:middle line:84%
It's a bunch of
scripts that have

00:00:51.050 --> 00:00:55.480 align:middle line:84%
been written that work alongside
what we've already utilized.

00:00:55.480 --> 00:00:57.230 align:middle line:84%
So we're going to take
advantage of those.

00:00:57.230 --> 00:01:01.340 align:middle line:84%
You can find a bunch of
information on the Nmap website

00:01:01.340 --> 00:01:04.310 align:middle line:90%
or within the documentation.

00:01:04.310 --> 00:01:06.680 align:middle line:90%
And I'll show you some examples.

00:01:06.680 --> 00:01:11.490 align:middle line:90%


00:01:11.490 --> 00:01:15.470 align:middle line:84%
So we have an IP
address, this 10.4.31.90.

00:01:15.470 --> 00:01:17.105 align:middle line:90%
It came with this machine.

00:01:17.105 --> 00:01:24.570 align:middle line:90%


00:01:24.570 --> 00:01:27.660 align:middle line:90%
So we'll ping it.

00:01:27.660 --> 00:01:30.200 align:middle line:84%
And it looks like we've
got a good connection.

00:01:30.200 --> 00:01:33.110 align:middle line:90%


00:01:33.110 --> 00:01:33.800 align:middle line:90%
That's good.

00:01:33.800 --> 00:01:35.870 align:middle line:90%
That means it's live.

00:01:35.870 --> 00:01:39.290 align:middle line:90%
We'll run an Nmap scan.

00:01:39.290 --> 00:01:43.910 align:middle line:84%
And it's kind of what we
would expect 135, 139, NetBios

00:01:43.910 --> 00:01:45.170 align:middle line:90%
and 445.

00:01:45.170 --> 00:01:47.000 align:middle line:84%
I'm guessing it's
a Windows machine

00:01:47.000 --> 00:01:49.655 align:middle line:90%
and it looks like it's got SMB.

00:01:49.655 --> 00:01:52.300 align:middle line:90%


00:01:52.300 --> 00:01:56.330 align:middle line:84%
So now we're going to
add to our Nmap scan.

00:01:56.330 --> 00:02:01.738 align:middle line:84%
We're going to look only at port
445 because that's the SMB one.

00:02:01.738 --> 00:02:04.280 align:middle line:84%
So we don't really need to run
these scripts against anything

00:02:04.280 --> 00:02:07.400 align:middle line:90%
else, so run it just on 445.

00:02:07.400 --> 00:02:09.350 align:middle line:84%
Then we'll look at
the SMB protocols.

00:02:09.350 --> 00:02:15.210 align:middle line:84%
This will tell us what protocols
and dialects that it's using.

00:02:15.210 --> 00:02:17.940 align:middle line:84%
And this is helpful because
it's basically versioning

00:02:17.940 --> 00:02:19.200 align:middle line:90%
information, if you will.

00:02:19.200 --> 00:02:21.930 align:middle line:90%


00:02:21.930 --> 00:02:27.490 align:middle line:84%
So it's got NTLM 0
and 2, otherwise known

00:02:27.490 --> 00:02:30.010 align:middle line:84%
as SMB version 1,
which is dangerous.

00:02:30.010 --> 00:02:32.860 align:middle line:90%
But it's the default version.

00:02:32.860 --> 00:02:36.460 align:middle line:84%
Now, you might have
heard of WannaCry.

00:02:36.460 --> 00:02:39.800 align:middle line:84%
There's a lot that takes
advantage of this SMB version

00:02:39.800 --> 00:02:40.300 align:middle line:90%
1.

00:02:40.300 --> 00:02:42.920 align:middle line:84%
And there's a good reason
why it's not used anymore.

00:02:42.920 --> 00:02:44.660 align:middle line:84%
It's dangerous,
but it's default.

00:02:44.660 --> 00:02:49.870 align:middle line:84%
So this is a misconfiguration
that we could utilize

00:02:49.870 --> 00:02:52.390 align:middle line:90%
or the criminals could utilize.

00:02:52.390 --> 00:02:55.010 align:middle line:90%


00:02:55.010 --> 00:02:57.340 align:middle line:84%
So let's look at
the security mode.

00:02:57.340 --> 00:02:58.810 align:middle line:90%
There's a script for that.

00:02:58.810 --> 00:03:00.400 align:middle line:90%
The way we enter these scripts--

00:03:00.400 --> 00:03:01.870 align:middle line:90%
kind of blew past that--

00:03:01.870 --> 00:03:05.560 align:middle line:84%
is tack, tack script and
then the name of the script.

00:03:05.560 --> 00:03:07.420 align:middle line:84%
Again, this is all
in the documentation.

00:03:07.420 --> 00:03:10.330 align:middle line:84%
Or you can go and
look at the thousands

00:03:10.330 --> 00:03:12.130 align:middle line:90%
of scripts that are included.

00:03:12.130 --> 00:03:15.640 align:middle line:84%
But looking at the
documentation is most useful.

00:03:15.640 --> 00:03:21.870 align:middle line:90%


00:03:21.870 --> 00:03:27.000 align:middle line:84%
And we can see that
it's got a guest account

00:03:27.000 --> 00:03:31.820 align:middle line:84%
that authenticates to a
user and message signing

00:03:31.820 --> 00:03:36.536 align:middle line:84%
is disabled, which is dangerous
but, again, a default.

00:03:36.536 --> 00:03:39.695 align:middle line:84%
Default configurations
usually get people in trouble.

00:03:39.695 --> 00:03:43.900 align:middle line:90%


00:03:43.900 --> 00:03:47.710 align:middle line:84%
That's why auditing and
vulnerability scans and pen

00:03:47.710 --> 00:03:51.100 align:middle line:84%
tests are useful to point
out things that people miss,

00:03:51.100 --> 00:03:55.750 align:middle line:90%
that are default but dangerous.

00:03:55.750 --> 00:04:00.490 align:middle line:84%
So how is this guest
account useful?

00:04:00.490 --> 00:04:04.095 align:middle line:90%
We'll do this SMB enum sessions.

00:04:04.095 --> 00:04:05.470 align:middle line:84%
And we'll enumerate
the sessions.

00:04:05.470 --> 00:04:10.980 align:middle line:90%


00:04:10.980 --> 00:04:20.560 align:middle line:84%
And what we'll find is that Bob
has been logged in as a user.

00:04:20.560 --> 00:04:24.250 align:middle line:84%
And since we didn't pass any
information, we kind of--

00:04:24.250 --> 00:04:28.810 align:middle line:84%
we also had Nmap
log in as a user

00:04:28.810 --> 00:04:32.320 align:middle line:84%
and see who else was logged
in under that guest account

00:04:32.320 --> 00:04:36.550 align:middle line:84%
because we didn't pass
any username or password.

00:04:36.550 --> 00:04:38.770 align:middle line:90%
Let's try it now.

00:04:38.770 --> 00:04:42.730 align:middle line:84%
Again, enum sessions and
we'll pass script args.

00:04:42.730 --> 00:04:44.500 align:middle line:84%
So after your tack,
tack script, you

00:04:44.500 --> 00:04:48.910 align:middle line:84%
name the name of the script,
and you pass arguments, tack,

00:04:48.910 --> 00:04:51.310 align:middle line:90%
tack script, tack args.

00:04:51.310 --> 00:04:52.690 align:middle line:90%
And in this case--

00:04:52.690 --> 00:04:54.880 align:middle line:84%
again, it's going to be
in the documentation what

00:04:54.880 --> 00:04:56.330 align:middle line:90%
these things are--

00:04:56.330 --> 00:05:01.390 align:middle line:84%
we use SMB username
administrator and SMB password,

00:05:01.390 --> 00:05:17.480 align:middle line:90%
SMB server 771, our IP.

00:05:17.480 --> 00:05:29.428 align:middle line:84%
Let's put it all on one
line and add in this guy,

00:05:29.428 --> 00:05:30.345 align:middle line:90%
give it an IP address.

00:05:30.345 --> 00:05:35.840 align:middle line:90%


00:05:35.840 --> 00:05:38.120 align:middle line:90%
And so now we saw Bob logged in.

00:05:38.120 --> 00:05:39.680 align:middle line:84%
And we can even see
the time that he

00:05:39.680 --> 00:05:42.170 align:middle line:90%
was logged in as a user.

00:05:42.170 --> 00:05:46.760 align:middle line:84%
And then we've got an active
session as administrator

00:05:46.760 --> 00:05:52.130 align:middle line:84%
connected from 10.10.3.2
which should be us.

00:05:52.130 --> 00:05:57.160 align:middle line:90%


00:05:57.160 --> 00:06:02.750 align:middle line:90%
10.10.3.2 just logged in.

00:06:02.750 --> 00:06:09.930 align:middle line:84%
And that even tells you it's
probably you idle for not idle.

00:06:09.930 --> 00:06:13.920 align:middle line:84%
So with that, enum
sessions passing a username

00:06:13.920 --> 00:06:20.430 align:middle line:84%
and password, it authenticated
and pulled the session

00:06:20.430 --> 00:06:21.150 align:middle line:90%
information.

00:06:21.150 --> 00:06:25.830 align:middle line:90%


00:06:25.830 --> 00:06:28.170 align:middle line:90%
Now let's enumerate the shares.

00:06:28.170 --> 00:06:30.270 align:middle line:84%
We've seen how a
share normally works.

00:06:30.270 --> 00:06:34.926 align:middle line:90%


00:06:34.926 --> 00:06:38.940 align:middle line:84%
You can go in and
configure a drive

00:06:38.940 --> 00:06:42.740 align:middle line:90%
to share in different ways.

00:06:42.740 --> 00:06:45.590 align:middle line:84%
We want to see how
this one is configured.

00:06:45.590 --> 00:06:50.930 align:middle line:84%
Do we have access to everything
or what is the breakdown?

00:06:50.930 --> 00:07:00.523 align:middle line:90%


00:07:00.523 --> 00:07:02.690 align:middle line:84%
This one's going to take a
little bit longer because

00:07:02.690 --> 00:07:07.420 align:middle line:84%
rather than quickly
logging in, logging out,

00:07:07.420 --> 00:07:10.120 align:middle line:84%
it actually needs to pull
a bunch of information.

00:07:10.120 --> 00:07:21.200 align:middle line:90%


00:07:21.200 --> 00:07:22.055 align:middle line:90%
We have our results.

00:07:22.055 --> 00:07:25.680 align:middle line:90%


00:07:25.680 --> 00:07:28.950 align:middle line:84%
In here, we can see
account used was guest

00:07:28.950 --> 00:07:35.460 align:middle line:84%
because it used that default
guest account that was allowed.

00:07:35.460 --> 00:07:38.950 align:middle line:90%
And it doesn't find a whole lot.

00:07:38.950 --> 00:07:42.618 align:middle line:90%
This is hidden for admins.

00:07:42.618 --> 00:07:43.910 align:middle line:90%
It's not going to tell us much.

00:07:43.910 --> 00:07:45.050 align:middle line:90%
The C drive exists.

00:07:45.050 --> 00:07:49.400 align:middle line:90%


00:07:49.400 --> 00:07:51.560 align:middle line:90%
There's a documents.

00:07:51.560 --> 00:07:53.750 align:middle line:90%
There's downloads.

00:07:53.750 --> 00:07:55.790 align:middle line:90%
There's this one, IPC.

00:07:55.790 --> 00:07:57.200 align:middle line:90%
IPC is useful.

00:07:57.200 --> 00:08:00.180 align:middle line:90%
That's a null session.

00:08:00.180 --> 00:08:05.510 align:middle line:84%
So a null session is like
an anonymous session.

00:08:05.510 --> 00:08:08.840 align:middle line:84%
Not only could you
get in as a guest,

00:08:08.840 --> 00:08:13.730 align:middle line:84%
but you can utilize this
null session, this IPC.

00:08:13.730 --> 00:08:16.550 align:middle line:90%
Looks like there's also prints.

00:08:16.550 --> 00:08:20.590 align:middle line:84%
It's very common
for us to be-- well,

00:08:20.590 --> 00:08:26.260 align:middle line:84%
it is a use of SMB to
share printer information.

00:08:26.260 --> 00:08:29.140 align:middle line:84%
This is how the printer
can print to or print

00:08:29.140 --> 00:08:32.260 align:middle line:84%
from different
machines on the network

00:08:32.260 --> 00:08:36.190 align:middle line:84%
or scan in two different
machines on the network.

00:08:36.190 --> 00:08:45.680 align:middle line:90%


00:08:45.680 --> 00:08:49.330 align:middle line:84%
So now let's enumerate the
shares after authenticating.

00:08:49.330 --> 00:08:54.090 align:middle line:90%


00:08:54.090 --> 00:08:57.466 align:middle line:90%
And we have our results back.

00:08:57.466 --> 00:09:00.320 align:middle line:84%
You see it's a little different
now that we're authenticated.

00:09:00.320 --> 00:09:03.296 align:middle line:90%
We use an administrator account.

00:09:03.296 --> 00:09:05.395 align:middle line:90%
And we see admins.

00:09:05.395 --> 00:09:08.460 align:middle line:90%
We see the path, if you will.

00:09:08.460 --> 00:09:11.050 align:middle line:90%


00:09:11.050 --> 00:09:13.836 align:middle line:90%
We saw that C drive.

00:09:13.836 --> 00:09:16.670 align:middle line:90%
We see what our access is.

00:09:16.670 --> 00:09:28.280 align:middle line:84%
We can read-- in the actual C
drive we can read and write.

00:09:28.280 --> 00:09:30.850 align:middle line:90%
This can be very useful.

00:09:30.850 --> 00:09:35.460 align:middle line:84%
But, again, that IPC is there
and anonymous access is none.

00:09:35.460 --> 00:09:39.480 align:middle line:84%
Our current user access
is read and write.

00:09:39.480 --> 00:09:45.600 align:middle line:84%
If we went back, IPC
anonymous access was none,

00:09:45.600 --> 00:09:50.420 align:middle line:84%
but the guest account
had read and write.

00:09:50.420 --> 00:09:55.890 align:middle line:84%
And it's very,
very good to know.

00:09:55.890 --> 00:09:57.732 align:middle line:84%
As an authenticated
user, looks like

00:09:57.732 --> 00:10:00.315 align:middle line:84%
you can read and write in most
of the places you would expect.

00:10:00.315 --> 00:10:05.900 align:middle line:90%


00:10:05.900 --> 00:10:07.820 align:middle line:84%
Now we're going to
enumerate the users.

00:10:07.820 --> 00:10:11.365 align:middle line:90%
So let's see which users exist.

00:10:11.365 --> 00:10:18.460 align:middle line:90%


00:10:18.460 --> 00:10:20.200 align:middle line:90%
We get our results back.

00:10:20.200 --> 00:10:21.280 align:middle line:90%
There's administrator.

00:10:21.280 --> 00:10:23.725 align:middle line:84%
There's also Bob and
this guest account.

00:10:23.725 --> 00:10:27.050 align:middle line:90%


00:10:27.050 --> 00:10:28.550 align:middle line:84%
It tells us that
the guest account's

00:10:28.550 --> 00:10:34.062 align:middle line:84%
a built-in account for guest
access, which is dangerous.

00:10:34.062 --> 00:10:35.020 align:middle line:90%
We got some flags here.

00:10:35.020 --> 00:10:36.490 align:middle line:90%
Password doesn't expire.

00:10:36.490 --> 00:10:38.260 align:middle line:90%
Password's not required.

00:10:38.260 --> 00:10:40.960 align:middle line:84%
And it gives you a
normal user account.

00:10:40.960 --> 00:10:42.400 align:middle line:90%
It's a misconfiguration.

00:10:42.400 --> 00:10:46.060 align:middle line:84%
This is something you would
want to write up as a finding.

00:10:46.060 --> 00:10:50.740 align:middle line:84%
Thinking like the adversary,
this is the sort of thing

00:10:50.740 --> 00:10:53.140 align:middle line:84%
that you'd want to see,
OK, what else can I learn?

00:10:53.140 --> 00:10:56.625 align:middle line:84%
What can I take away
from this finding?

00:10:56.625 --> 00:11:00.900 align:middle line:90%


00:11:00.900 --> 00:11:06.300 align:middle line:84%
Now we'll look at the server
statistics using the server

00:11:06.300 --> 00:11:08.400 align:middle line:90%
stats script.

00:11:08.400 --> 00:11:10.080 align:middle line:90%
And we'll authenticate.

00:11:10.080 --> 00:11:12.190 align:middle line:90%
A lot of this remains the same.

00:11:12.190 --> 00:11:15.570 align:middle line:84%
We just change the
script we're utilizing.

00:11:15.570 --> 00:11:19.038 align:middle line:90%


00:11:19.038 --> 00:11:19.830 align:middle line:90%
And this is useful.

00:11:19.830 --> 00:11:22.350 align:middle line:84%
We can see how much data
was sent and received,

00:11:22.350 --> 00:11:26.900 align:middle line:84%
how many failed logins,
permission errors, if there's

00:11:26.900 --> 00:11:29.789 align:middle line:90%
print jobs or files open, some--

00:11:29.789 --> 00:11:33.461 align:middle line:90%


00:11:33.461 --> 00:11:36.140 align:middle line:84%
a lot of information
together remotely.

00:11:36.140 --> 00:11:39.520 align:middle line:90%


00:11:39.520 --> 00:11:41.380 align:middle line:84%
We can see what
domains exist here.

00:11:41.380 --> 00:11:44.330 align:middle line:90%


00:11:44.330 --> 00:11:46.550 align:middle line:84%
And it never hurts to
gather as much information

00:11:46.550 --> 00:11:48.380 align:middle line:84%
during the enumeration
phase as you can.

00:11:48.380 --> 00:11:52.230 align:middle line:90%


00:11:52.230 --> 00:11:54.650 align:middle line:84%
It's better to come back later
and try to figure out, OK,

00:11:54.650 --> 00:11:55.970 align:middle line:90%
was this useful or not?

00:11:55.970 --> 00:11:58.490 align:middle line:84%
But while you're
enumerating, find out

00:11:58.490 --> 00:12:00.177 align:middle line:90%
as much information as possible.

00:12:00.177 --> 00:12:02.510 align:middle line:84%
You don't know what's going
to be useful and what's not.

00:12:02.510 --> 00:12:05.244 align:middle line:90%


00:12:05.244 --> 00:12:07.360 align:middle line:84%
You won't be able
to figure that out

00:12:07.360 --> 00:12:09.070 align:middle line:90%
unless you gather information.

00:12:09.070 --> 00:12:13.202 align:middle line:90%


00:12:13.202 --> 00:12:14.910 align:middle line:84%
So in this domain, we
can see the groups.

00:12:14.910 --> 00:12:15.900 align:middle line:90%
We can see users.

00:12:15.900 --> 00:12:18.510 align:middle line:84%
We can see some
password information.

00:12:18.510 --> 00:12:21.210 align:middle line:90%


00:12:21.210 --> 00:12:22.530 align:middle line:90%
There's no min length.

00:12:22.530 --> 00:12:23.670 align:middle line:90%
There's no min age.

00:12:23.670 --> 00:12:26.350 align:middle line:90%


00:12:26.350 --> 00:12:29.450 align:middle line:90%
There's no history settings.

00:12:29.450 --> 00:12:32.030 align:middle line:90%
That's all weak configurations.

00:12:32.030 --> 00:12:36.640 align:middle line:90%


00:12:36.640 --> 00:12:39.950 align:middle line:84%
There is complexity
requirements.

00:12:39.950 --> 00:12:42.760 align:middle line:84%
So if we were going to throw a
brute force word list at this,

00:12:42.760 --> 00:12:46.690 align:middle line:84%
we might need to think
about how all that ties in.

00:12:46.690 --> 00:12:52.910 align:middle line:90%


00:12:52.910 --> 00:12:55.910 align:middle line:90%
And that applies to this--

00:12:55.910 --> 00:13:01.200 align:middle line:90%
WinRM remote WMI users.

00:13:01.200 --> 00:13:03.770 align:middle line:90%
So we will get into that later.

00:13:03.770 --> 00:13:07.640 align:middle line:90%


00:13:07.640 --> 00:13:08.490 align:middle line:90%
That's the users.

00:13:08.490 --> 00:13:09.935 align:middle line:90%
Now let's look at the groups.

00:13:09.935 --> 00:13:13.190 align:middle line:90%


00:13:13.190 --> 00:13:21.840 align:middle line:84%
Groups are helpful, break up
users into different levels.

00:13:21.840 --> 00:13:27.140 align:middle line:84%
So we can see our administrators
include administrator and Bob.

00:13:27.140 --> 00:13:30.350 align:middle line:84%
Bob might be easier to get
into than the administrator

00:13:30.350 --> 00:13:34.550 align:middle line:84%
and still exists on the
administrators group.

00:13:34.550 --> 00:13:39.065 align:middle line:84%
So it should have all the same
powers, all the same access.

00:13:39.065 --> 00:13:46.880 align:middle line:90%


00:13:46.880 --> 00:13:50.040 align:middle line:84%
We can look at what
services are running.

00:13:50.040 --> 00:13:52.800 align:middle line:84%
And we're getting
all this from SMB.

00:13:52.800 --> 00:14:06.270 align:middle line:84%
Even though it's not always
specific to the service,

00:14:06.270 --> 00:14:07.350 align:middle line:90%
in this case, yes, it is.

00:14:07.350 --> 00:14:12.780 align:middle line:84%
But we can gather a
lot of information.

00:14:12.780 --> 00:14:14.780 align:middle line:84%
And we can parse through
it later and figure out

00:14:14.780 --> 00:14:16.340 align:middle line:90%
what's most useful.

00:14:16.340 --> 00:14:24.590 align:middle line:84%
We can see what services
are running just

00:14:24.590 --> 00:14:26.345 align:middle line:84%
by going through
some Nmap scripts.

00:14:26.345 --> 00:14:29.210 align:middle line:90%


00:14:29.210 --> 00:14:32.090 align:middle line:84%
This one is a
little more useful.

00:14:32.090 --> 00:14:35.540 align:middle line:84%
Not only would we see
what shares exist,

00:14:35.540 --> 00:14:41.990 align:middle line:84%
but it's going to run the
script SMB enum shares and also

00:14:41.990 --> 00:14:44.965 align:middle line:90%
SMB tack ls.

00:14:44.965 --> 00:14:46.340 align:middle line:84%
So, in this
situation, it's going

00:14:46.340 --> 00:14:51.500 align:middle line:84%
to connect to SMB and run ls,
or the list command in Linux.

00:14:51.500 --> 00:14:54.730 align:middle line:90%


00:14:54.730 --> 00:14:58.870 align:middle line:84%
It's similar to dir in
command line on Windows.

00:14:58.870 --> 00:15:00.490 align:middle line:84%
And it'll tell us
what's actually

00:15:00.490 --> 00:15:02.875 align:middle line:90%
in each of these shares.

00:15:02.875 --> 00:15:08.560 align:middle line:90%


00:15:08.560 --> 00:15:14.130 align:middle line:84%
So not only will we see
the overarching directories

00:15:14.130 --> 00:15:17.875 align:middle line:84%
and folders, we could see
what's inside those folders.

00:15:17.875 --> 00:15:20.660 align:middle line:90%


00:15:20.660 --> 00:15:23.030 align:middle line:84%
That scan took a little
bit of time to run,

00:15:23.030 --> 00:15:24.185 align:middle line:90%
but there's good reason.

00:15:24.185 --> 00:15:26.960 align:middle line:90%


00:15:26.960 --> 00:15:30.440 align:middle line:90%
It enumerated the shares.

00:15:30.440 --> 00:15:33.380 align:middle line:84%
But then, looking
inside each share,

00:15:33.380 --> 00:15:38.740 align:middle line:84%
we can see inside of admin
there's some more directories.

00:15:38.740 --> 00:15:42.500 align:middle line:84%
I don't know exactly what those
mean, but it could be useful.

00:15:42.500 --> 00:15:45.650 align:middle line:90%


00:15:45.650 --> 00:15:50.900 align:middle line:84%
Inside C, we can see
common files and explorer,

00:15:50.900 --> 00:15:52.175 align:middle line:90%
some useful stuff.

00:15:52.175 --> 00:15:56.760 align:middle line:84%
We see that there's
PowerShell, as we might expect.

00:15:56.760 --> 00:16:00.210 align:middle line:84%
Nothing in documents
or downloads.

00:16:00.210 --> 00:16:05.670 align:middle line:84%
There are some files in
print, kind of useful.

00:16:05.670 --> 00:16:11.030 align:middle line:90%


00:16:11.030 --> 00:16:14.150 align:middle line:84%
And in those same
files in C are in C$.

00:16:14.150 --> 00:16:18.730 align:middle line:90%


00:16:18.730 --> 00:16:20.980 align:middle line:84%
We don't know what's useful
and what's not useful

00:16:20.980 --> 00:16:22.630 align:middle line:84%
unless something
jumps out at you.

00:16:22.630 --> 00:16:33.450 align:middle line:84%
But that's how we can enumerate
SMB utilizing some Nmap scans.

00:16:33.450 --> 00:16:34.000 align:middle line:90%