WEBVTT

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


00:00:10.680 --> 00:00:13.950 align:middle line:84%
Welcome to our lesson on
network-based attacks.

00:00:13.950 --> 00:00:15.450 align:middle line:84%
In this one, we're
going to tell you

00:00:15.450 --> 00:00:19.780 align:middle line:84%
about what is a network-based
attack and start that now.

00:00:19.780 --> 00:00:21.660 align:middle line:84%
So a network-based
attack is one that

00:00:21.660 --> 00:00:23.940 align:middle line:84%
deals with network
and network services.

00:00:23.940 --> 00:00:26.440 align:middle line:90%
It is fairly straightforward.

00:00:26.440 --> 00:00:29.610 align:middle line:84%
It's really just something that
isn't related to the operating

00:00:29.610 --> 00:00:30.540 align:middle line:90%
system.

00:00:30.540 --> 00:00:35.690 align:middle line:84%
Instead, it deals with
network, the packets traveling

00:00:35.690 --> 00:00:38.090 align:middle line:84%
across the network,
or on services

00:00:38.090 --> 00:00:41.540 align:middle line:84%
that utilize the network,
but are more operating

00:00:41.540 --> 00:00:45.150 align:middle line:90%
system-agnostic, if you will.

00:00:45.150 --> 00:00:53.030 align:middle line:84%
So that would include our ARP,
our DHCP, SMB, FTP, Telnet,

00:00:53.030 --> 00:00:55.520 align:middle line:90%
and SSH.

00:00:55.520 --> 00:00:59.780 align:middle line:84%
A lot of those services we can
take advantage of, and we have.

00:00:59.780 --> 00:01:02.990 align:middle line:84%
We've done that in
exploitation as well as

00:01:02.990 --> 00:01:05.930 align:middle line:84%
in footprinting scanning
and enumeration.

00:01:05.930 --> 00:01:08.570 align:middle line:84%
We looked at some of these
services and the ways

00:01:08.570 --> 00:01:10.700 align:middle line:84%
that we can interact
and take advantage

00:01:10.700 --> 00:01:16.190 align:middle line:84%
of a null session
or a SSH session

00:01:16.190 --> 00:01:21.620 align:middle line:84%
and attacking it with a password
spraying or brute forcing it.

00:01:21.620 --> 00:01:23.630 align:middle line:84%
Those are some
network-based attacks.

00:01:23.630 --> 00:01:26.130 align:middle line:84%
And we've already
done several of them.

00:01:26.130 --> 00:01:29.720 align:middle line:84%
What we're going to
get into in this course

00:01:29.720 --> 00:01:31.460 align:middle line:84%
is going to be more
"man in the middle"

00:01:31.460 --> 00:01:34.137 align:middle line:84%
attacks, where we
have two systems that

00:01:34.137 --> 00:01:35.720 align:middle line:84%
are talking to each
other on a network

00:01:35.720 --> 00:01:37.460 align:middle line:90%
that we are also connected to.

00:01:37.460 --> 00:01:39.890 align:middle line:90%
And they talk back and forth.

00:01:39.890 --> 00:01:44.120 align:middle line:84%
And what we are able to
do is hear their traffic

00:01:44.120 --> 00:01:46.550 align:middle line:84%
because here's
one of the things.

00:01:46.550 --> 00:01:51.560 align:middle line:84%
When network traffic
goes out, it has--

00:01:51.560 --> 00:01:54.140 align:middle line:84%
if it's on the
network, then it is

00:01:54.140 --> 00:01:58.790 align:middle line:84%
encased in some Layer 1, Layer
2, and Layer 3 protocols.

00:01:58.790 --> 00:02:03.860 align:middle line:84%
And when it gets sent out,
it's not broadcast out.

00:02:03.860 --> 00:02:05.930 align:middle line:90%
It is sent to an endpoint.

00:02:05.930 --> 00:02:08.310 align:middle line:90%
But it's electrical signals.

00:02:08.310 --> 00:02:14.930 align:middle line:84%
So depending on how things
are set up on the network,

00:02:14.930 --> 00:02:18.680 align:middle line:84%
traffic might hit all the
points on the network,

00:02:18.680 --> 00:02:21.000 align:middle line:90%
usually with a switch.

00:02:21.000 --> 00:02:22.940 align:middle line:84%
You don't have
any of that issue.

00:02:22.940 --> 00:02:24.830 align:middle line:84%
Back in the hub
days, it was really

00:02:24.830 --> 00:02:27.950 align:middle line:84%
easy to listen to
everyone else's traffic.

00:02:27.950 --> 00:02:32.510 align:middle line:84%
Now that those are
a thing of the past,

00:02:32.510 --> 00:02:34.880 align:middle line:84%
in order to listen
to traffic that

00:02:34.880 --> 00:02:38.240 align:middle line:84%
isn't meant for your
machine, you either

00:02:38.240 --> 00:02:40.400 align:middle line:84%
need to connect to
a SPAN port, which

00:02:40.400 --> 00:02:47.300 align:middle line:84%
listens to all the traffic on a
switch, or you need to poison.

00:02:47.300 --> 00:02:49.430 align:middle line:84%
The easiest way to
poison is ARP poisoning.

00:02:49.430 --> 00:02:50.870 align:middle line:90%
And we'll practice that.

00:02:50.870 --> 00:02:54.320 align:middle line:84%
It's where you start
broadcasting out

00:02:54.320 --> 00:03:00.380 align:middle line:84%
ARP packets that tell the
other machines on the network

00:03:00.380 --> 00:03:04.520 align:middle line:84%
that you are a
certain IP address.

00:03:04.520 --> 00:03:07.360 align:middle line:90%


00:03:07.360 --> 00:03:11.210 align:middle line:84%
Inside a network, packets
are bound to an IP address.

00:03:11.210 --> 00:03:15.790 align:middle line:84%
But they get routed inside the
network based on MAC address.

00:03:15.790 --> 00:03:18.690 align:middle line:90%


00:03:18.690 --> 00:03:23.650 align:middle line:84%
So you spoof with ARP
poisoning a MAC address.

00:03:23.650 --> 00:03:27.620 align:middle line:84%
Then you can have traffic
meant for another machine come

00:03:27.620 --> 00:03:28.670 align:middle line:90%
to you.

00:03:28.670 --> 00:03:33.540 align:middle line:84%
And we'll dive more into
that in a future lesson.

00:03:33.540 --> 00:03:36.260 align:middle line:84%
But another thing that we
can do is promiscuous mode,

00:03:36.260 --> 00:03:38.720 align:middle line:90%
where we listen to all traffic.

00:03:38.720 --> 00:03:41.540 align:middle line:84%
If we're lucky, we might hear
traffic that's-- even though

00:03:41.540 --> 00:03:44.630 align:middle line:84%
it's not intended
for our machine,

00:03:44.630 --> 00:03:47.960 align:middle line:84%
if we turn on promiscuous mode,
which is pretty standard with

00:03:47.960 --> 00:03:51.560 align:middle line:84%
most packet captures, then we
will be able to listen to other

00:03:51.560 --> 00:03:53.060 align:middle line:90%
traffic on the network.

00:03:53.060 --> 00:03:57.270 align:middle line:84%
And I'll give you a taste
of what that looks like.

00:03:57.270 --> 00:04:01.777 align:middle line:84%
We're going to jump into
a virtual environment.

00:04:01.777 --> 00:04:03.860 align:middle line:84%
And we'll live in here for
the rest of the lesson.

00:04:03.860 --> 00:04:07.340 align:middle line:90%


00:04:07.340 --> 00:04:08.810 align:middle line:90%
This is a Linux environment.

00:04:08.810 --> 00:04:12.950 align:middle line:90%


00:04:12.950 --> 00:04:14.425 align:middle line:90%
So let's look at our IP address.

00:04:14.425 --> 00:04:17.943 align:middle line:90%


00:04:17.943 --> 00:04:18.985 align:middle line:90%
And you can see we have--

00:04:18.985 --> 00:04:22.360 align:middle line:90%


00:04:22.360 --> 00:04:24.040 align:middle line:90%
[INAUDIBLE]-- there we go--

00:04:24.040 --> 00:04:24.940 align:middle line:90%
a few connections.

00:04:24.940 --> 00:04:26.950 align:middle line:84%
But our IP address
in it is going

00:04:26.950 --> 00:04:33.760 align:middle line:84%
to be 192.112.112.2
on a 24 network.

00:04:33.760 --> 00:04:37.690 align:middle line:84%
Let's do a quick Nmap
scan of this network.

00:04:37.690 --> 00:04:40.770 align:middle line:90%


00:04:40.770 --> 00:04:45.450 align:middle line:84%
Let's go 0/24 and just
see what's out there.

00:04:45.450 --> 00:04:50.930 align:middle line:90%


00:04:50.930 --> 00:04:56.240 align:middle line:84%
And we've got a
.1, .3, .4, and .2.

00:04:56.240 --> 00:05:06.050 align:middle line:84%
So if we do 1 through 4, and
let's also do a service scan--

00:05:06.050 --> 00:05:09.050 align:middle line:90%
well, let's go just aggressive.

00:05:09.050 --> 00:05:13.480 align:middle line:84%
Let's just see what these
machines are, what's on them.

00:05:13.480 --> 00:05:16.840 align:middle line:84%
Aggressive mode is going
to do a few extra things.

00:05:16.840 --> 00:05:21.730 align:middle line:84%
It's going to run, obviously,
the port scan, but a service

00:05:21.730 --> 00:05:25.300 align:middle line:84%
scan, operating system scan,
and some default scripts.

00:05:25.300 --> 00:05:27.040 align:middle line:90%
It's the same as [INAUDIBLE].

00:05:27.040 --> 00:05:29.814 align:middle line:84%
So it should return to
some useful information.

00:05:29.814 --> 00:05:32.420 align:middle line:90%


00:05:32.420 --> 00:05:36.130 align:middle line:84%
If you don't mind being
loud, an aggressive scan

00:05:36.130 --> 00:05:39.880 align:middle line:90%
will usually get you some info.

00:05:39.880 --> 00:05:41.860 align:middle line:90%
So .1 has SSH open.

00:05:41.860 --> 00:05:44.380 align:middle line:90%
It's got HTTP and HTTPS.

00:05:44.380 --> 00:05:47.245 align:middle line:84%
That's what we should be
expecting for this lab.

00:05:47.245 --> 00:05:50.650 align:middle line:90%


00:05:50.650 --> 00:05:53.020 align:middle line:84%
We've got .3--
also has HTTP open.

00:05:53.020 --> 00:05:56.130 align:middle line:90%


00:05:56.130 --> 00:06:00.590 align:middle line:90%
It's also got a MySQL database.

00:06:00.590 --> 00:06:03.800 align:middle line:90%
.4 has HTTP and HTTPS.

00:06:03.800 --> 00:06:08.215 align:middle line:90%


00:06:08.215 --> 00:06:08.715 align:middle line:90%
Perfect.

00:06:08.715 --> 00:06:12.920 align:middle line:90%


00:06:12.920 --> 00:06:16.280 align:middle line:90%
So the joy is--

00:06:16.280 --> 00:06:19.820 align:middle line:84%
let's go look around
at what's in here.

00:06:19.820 --> 00:06:41.020 align:middle line:84%
192.112.112.1-- if it doesn't
return anything quickly,

00:06:41.020 --> 00:06:41.830 align:middle line:90%
then we'll move on.

00:06:41.830 --> 00:07:04.820 align:middle line:90%


00:07:04.820 --> 00:07:07.770 align:middle line:90%
.1 is our router.

00:07:07.770 --> 00:07:12.650 align:middle line:90%
.3 has bWAPP.

00:07:12.650 --> 00:07:17.340 align:middle line:90%


00:07:17.340 --> 00:07:20.360 align:middle line:90%
Let's go with HTTPS.

00:07:20.360 --> 00:07:21.050 align:middle line:90%
It's not there.

00:07:21.050 --> 00:07:29.700 align:middle line:90%


00:07:29.700 --> 00:07:32.760 align:middle line:90%
And that should fit.

00:07:32.760 --> 00:07:34.470 align:middle line:90%
Correct.

00:07:34.470 --> 00:07:36.583 align:middle line:90%
So .3 doesn't have 443.

00:07:36.583 --> 00:07:37.875 align:middle line:90%
So it shouldn't have that open.

00:07:37.875 --> 00:07:40.750 align:middle line:90%


00:07:40.750 --> 00:07:43.790 align:middle line:90%
So we go 4.

00:07:43.790 --> 00:07:45.490 align:middle line:90%
4 has some issues.

00:07:45.490 --> 00:07:49.330 align:middle line:90%
But I trust it.

00:07:49.330 --> 00:07:51.400 align:middle line:90%
It's bWAPP on HTTPS.

00:07:51.400 --> 00:07:52.150 align:middle line:90%
So that's good.

00:07:52.150 --> 00:07:55.490 align:middle line:90%


00:07:55.490 --> 00:08:02.260 align:middle line:84%
We should also have a
default. That's good.

00:08:02.260 --> 00:08:05.730 align:middle line:90%


00:08:05.730 --> 00:08:10.350 align:middle line:90%
So .3 only has HTTP.

00:08:10.350 --> 00:08:17.100 align:middle line:90%
And .4 has HTTP and HTTPS.

00:08:17.100 --> 00:08:17.790 align:middle line:90%
We're .2.

00:08:17.790 --> 00:08:18.930 align:middle line:90%
So don't worry about that.

00:08:18.930 --> 00:08:24.710 align:middle line:90%


00:08:24.710 --> 00:08:26.360 align:middle line:90%
Awesome.

00:08:26.360 --> 00:08:29.510 align:middle line:84%
Well, we are making
some network traffic.

00:08:29.510 --> 00:08:32.150 align:middle line:90%
Let's take a look at it.

00:08:32.150 --> 00:08:33.080 align:middle line:90%
This is Wireshark.

00:08:33.080 --> 00:08:36.049 align:middle line:84%
We have played with
Wireshark before.

00:08:36.049 --> 00:08:41.720 align:middle line:84%
We want to be
interacting on eth1.

00:08:41.720 --> 00:08:44.510 align:middle line:90%


00:08:44.510 --> 00:08:48.353 align:middle line:90%
So eth0 here was a 10.1.

00:08:48.353 --> 00:08:49.770 align:middle line:84%
We don't need to
worry about that.

00:08:49.770 --> 00:08:53.750 align:middle line:90%
That's just for the VM to talk.

00:08:53.750 --> 00:08:56.660 align:middle line:90%
Eth1, though, has our 192.112.

00:08:56.660 --> 00:09:00.350 align:middle line:90%
So let's listen on eth1.

00:09:00.350 --> 00:09:03.225 align:middle line:90%
And begin.

00:09:03.225 --> 00:09:04.100 align:middle line:90%
Click the little fin.

00:09:04.100 --> 00:09:06.230 align:middle line:90%
And it will start capturing.

00:09:06.230 --> 00:09:07.700 align:middle line:90%
Now, what is it doing?

00:09:07.700 --> 00:09:12.150 align:middle line:84%
Let's refresh this so it
gets some network traffic.

00:09:12.150 --> 00:09:15.803 align:middle line:84%
We could also run
our scan again,

00:09:15.803 --> 00:09:16.970 align:middle line:90%
create some network traffic.

00:09:16.970 --> 00:09:19.830 align:middle line:90%


00:09:19.830 --> 00:09:21.927 align:middle line:84%
We could even run
that aggressive scan,

00:09:21.927 --> 00:09:23.135 align:middle line:90%
just create a ton of traffic.

00:09:23.135 --> 00:09:27.765 align:middle line:90%


00:09:27.765 --> 00:09:28.265 align:middle line:90%
Perfect.

00:09:28.265 --> 00:09:31.520 align:middle line:90%


00:09:31.520 --> 00:09:34.145 align:middle line:90%
So these are packets.

00:09:34.145 --> 00:09:36.800 align:middle line:90%


00:09:36.800 --> 00:09:39.620 align:middle line:90%
A lot of these are TCP packets.

00:09:39.620 --> 00:09:42.170 align:middle line:84%
Makes sense-- I just
did a TCP scan--

00:09:42.170 --> 00:09:49.010 align:middle line:84%
should be tons of TCP
packets going to and from .2,

00:09:49.010 --> 00:09:52.250 align:middle line:84%
which is my machine,
out to .4, initially.

00:09:52.250 --> 00:09:53.600 align:middle line:90%
That was that HTTP traffic.

00:09:53.600 --> 00:09:56.570 align:middle line:90%


00:09:56.570 --> 00:09:58.520 align:middle line:90%
And then-- did that ARP scan.

00:09:58.520 --> 00:10:02.120 align:middle line:84%
And this was two MAC
addresses because, remember,

00:10:02.120 --> 00:10:03.450 align:middle line:90%
that's how ARP works.

00:10:03.450 --> 00:10:06.950 align:middle line:84%
So when I did that [INAUDIBLE],,
it did an ARP scan.

00:10:06.950 --> 00:10:12.020 align:middle line:84%
And then it did some
other scans, got back.

00:10:12.020 --> 00:10:15.290 align:middle line:90%
Who is where? .4 is at 04.

00:10:15.290 --> 00:10:20.680 align:middle line:90%


00:10:20.680 --> 00:10:22.960 align:middle line:90%
Cool.

00:10:22.960 --> 00:10:23.500 align:middle line:90%
That's neat.

00:10:23.500 --> 00:10:25.060 align:middle line:84%
So we captured--
there's not going

00:10:25.060 --> 00:10:27.477 align:middle line:84%
to be any more traffic because
we created all the traffic.

00:10:27.477 --> 00:10:28.750 align:middle line:90%
So we will stop the capture.

00:10:28.750 --> 00:10:30.820 align:middle line:90%
Just hit Stop there.

00:10:30.820 --> 00:10:33.910 align:middle line:90%
So what do you do in Wireshark?

00:10:33.910 --> 00:10:35.980 align:middle line:90%
Well, let's walk our way across.

00:10:35.980 --> 00:10:39.620 align:middle line:84%
Wireshark has some
neat things in here.

00:10:39.620 --> 00:10:42.640 align:middle line:90%
We can open captures.

00:10:42.640 --> 00:10:43.810 align:middle line:90%
We can save captures.

00:10:43.810 --> 00:10:45.070 align:middle line:90%
Let's do that.

00:10:45.070 --> 00:10:48.640 align:middle line:90%
Let's call this "rando."

00:10:48.640 --> 00:10:51.940 align:middle line:84%
And I'm just going to
save it to the desktop.

00:10:51.940 --> 00:10:55.330 align:middle line:84%
And it's going to
save it as a pcapng.

00:10:55.330 --> 00:10:58.840 align:middle line:84%
It's next-generation PCAP,
which is a packet capture.

00:10:58.840 --> 00:11:01.970 align:middle line:90%
It's a Wireshark file.

00:11:01.970 --> 00:11:04.210 align:middle line:90%
So save that.

00:11:04.210 --> 00:11:09.224 align:middle line:84%
It is now on the
desktop, somewhere.

00:11:09.224 --> 00:11:18.920 align:middle line:90%


00:11:18.920 --> 00:11:21.650 align:middle line:90%
I don't see it.

00:11:21.650 --> 00:11:22.970 align:middle line:90%
There it is, on the desktop.

00:11:22.970 --> 00:11:23.900 align:middle line:90%
So we can save it.

00:11:23.900 --> 00:11:30.495 align:middle line:84%
We could open a new
one, rando.pcapng.

00:11:30.495 --> 00:11:34.180 align:middle line:84%
I already have it
open-- so no change.

00:11:34.180 --> 00:11:36.340 align:middle line:90%
You can import hex dumps.

00:11:36.340 --> 00:11:38.648 align:middle line:90%
You can export some packets.

00:11:38.648 --> 00:11:39.940 align:middle line:90%
I'll get into that in a second.

00:11:39.940 --> 00:11:43.060 align:middle line:90%


00:11:43.060 --> 00:11:45.450 align:middle line:84%
We have a few different
views, some things

00:11:45.450 --> 00:11:47.020 align:middle line:90%
that we can change in here.

00:11:47.020 --> 00:11:49.380 align:middle line:90%
So name resolution is neat.

00:11:49.380 --> 00:11:51.400 align:middle line:84%
We could resolve
physical addresses.

00:11:51.400 --> 00:11:52.950 align:middle line:90%
So that's MAC addresses.

00:11:52.950 --> 00:11:57.270 align:middle line:84%
If our MAC address
relates to a known host,

00:11:57.270 --> 00:11:59.160 align:middle line:90%
then it'll tell us the name.

00:11:59.160 --> 00:12:01.290 align:middle line:84%
But if it doesn't
know it, then it'll

00:12:01.290 --> 00:12:02.400 align:middle line:90%
just show the MAC address.

00:12:02.400 --> 00:12:05.580 align:middle line:84%
Same with network
addresses-- if we were--

00:12:05.580 --> 00:12:08.040 align:middle line:90%
there we go-- demossl.ine.local.

00:12:08.040 --> 00:12:10.680 align:middle line:90%


00:12:10.680 --> 00:12:12.120 align:middle line:90%
That is, apparently, us.

00:12:12.120 --> 00:12:16.050 align:middle line:84%
And INE is the machine
that we're hitting.

00:12:16.050 --> 00:12:18.390 align:middle line:90%
So it resolved that for us.

00:12:18.390 --> 00:12:24.040 align:middle line:90%


00:12:24.040 --> 00:12:26.980 align:middle line:90%
And these were broadcast.

00:12:26.980 --> 00:12:29.620 align:middle line:84%
Remember, ARP scan,
it was broadcast.

00:12:29.620 --> 00:12:32.050 align:middle line:84%
So it resolved
our MAC addresses.

00:12:32.050 --> 00:12:35.590 align:middle line:90%


00:12:35.590 --> 00:12:37.220 align:middle line:90%
I turned that back off.

00:12:37.220 --> 00:12:37.780 align:middle line:90%
See?

00:12:37.780 --> 00:12:38.500 align:middle line:90%
There you go.

00:12:38.500 --> 00:12:41.710 align:middle line:90%
Resolved-- INE to broadcast.

00:12:41.710 --> 00:12:43.990 align:middle line:84%
Otherwise, it would
look like this.

00:12:43.990 --> 00:12:47.560 align:middle line:90%


00:12:47.560 --> 00:12:52.620 align:middle line:84%
It's fairly common to keep
physical address resolution on.

00:12:52.620 --> 00:12:56.160 align:middle line:84%
Sometimes, people even want
their transport address.

00:12:56.160 --> 00:12:59.667 align:middle line:90%


00:12:59.667 --> 00:13:01.550 align:middle line:84%
So it says in here
what things are.

00:13:01.550 --> 00:13:06.108 align:middle line:90%


00:13:06.108 --> 00:13:07.400 align:middle line:90%
But I'm going to turn that off.

00:13:07.400 --> 00:13:11.110 align:middle line:90%


00:13:11.110 --> 00:13:14.610 align:middle line:84%
You can zoom if you
need to change size.

00:13:14.610 --> 00:13:16.840 align:middle line:84%
There is colorization
of packets.

00:13:16.840 --> 00:13:19.360 align:middle line:90%
So all these packets--

00:13:19.360 --> 00:13:22.150 align:middle line:90%
I want that back on.

00:13:22.150 --> 00:13:27.090 align:middle line:84%
What I meant to show you
was the coloring rules.

00:13:27.090 --> 00:13:29.520 align:middle line:84%
So in here, you can see
different types of packets

00:13:29.520 --> 00:13:33.690 align:middle line:84%
mean different things
in this coloring scheme.

00:13:33.690 --> 00:13:37.080 align:middle line:84%
It's not too terrible
to understand.

00:13:37.080 --> 00:13:41.400 align:middle line:84%
ICMP traffic-- so
our HTTP traffic--

00:13:41.400 --> 00:13:42.510 align:middle line:90%
fairly common to see.

00:13:42.510 --> 00:13:45.110 align:middle line:90%


00:13:45.110 --> 00:13:45.610 align:middle line:90%
That's neat.

00:13:45.610 --> 00:13:46.380 align:middle line:90%
You can change it up.

00:13:46.380 --> 00:13:48.547 align:middle line:84%
You can turn things on,
turn things off if you want.

00:13:48.547 --> 00:13:53.890 align:middle line:90%


00:13:53.890 --> 00:13:57.870 align:middle line:84%
And then you can change some of
your columns and your layout.

00:13:57.870 --> 00:14:00.720 align:middle line:84%
We'll get into that
in a little bit.

00:14:00.720 --> 00:14:04.070 align:middle line:90%
You can use some keys.

00:14:04.070 --> 00:14:07.340 align:middle line:84%
This menu is only really helpful
to tell you what the keys are.

00:14:07.340 --> 00:14:09.800 align:middle line:84%
Moving through the
packets, through this menu,

00:14:09.800 --> 00:14:13.270 align:middle line:90%
is not super helpful.

00:14:13.270 --> 00:14:18.520 align:middle line:84%
But using those hotkeys can
make some of your work faster.

00:14:18.520 --> 00:14:19.420 align:middle line:90%
There's captures.

00:14:19.420 --> 00:14:23.730 align:middle line:84%
We started to
capture [INAUDIBLE]..

00:14:23.730 --> 00:14:25.380 align:middle line:84%
There's some options
for captures.

00:14:25.380 --> 00:14:27.960 align:middle line:84%
You can choose which
interface you want to use.

00:14:27.960 --> 00:14:30.060 align:middle line:90%
You can apply capture filters.

00:14:30.060 --> 00:14:32.540 align:middle line:90%
I'll get to filters in a bit.

00:14:32.540 --> 00:14:35.130 align:middle line:84%
You can even hone in on
some of these things?

00:14:35.130 --> 00:14:39.810 align:middle line:84%
Which IP address are you going
to use on that interface?

00:14:39.810 --> 00:14:42.250 align:middle line:84%
You can choose where your
output is going to go.

00:14:42.250 --> 00:14:45.780 align:middle line:84%
You can save it as
a pcapng or a pcap

00:14:45.780 --> 00:14:48.750 align:middle line:84%
and create new
files after so long.

00:14:48.750 --> 00:14:52.170 align:middle line:84%
That can be really helpful
if you have a long capture.

00:14:52.170 --> 00:14:56.890 align:middle line:84%
We'll play with that
in TShark as well.

00:14:56.890 --> 00:14:57.900 align:middle line:90%
It's more options.

00:14:57.900 --> 00:15:00.930 align:middle line:84%
Again, stop the capture
after a certain time.

00:15:00.930 --> 00:15:02.890 align:middle line:84%
It's very similar
to make a new file.

00:15:02.890 --> 00:15:07.635 align:middle line:84%
And you can have it collect
with resolved names.

00:15:07.635 --> 00:15:10.680 align:middle line:90%


00:15:10.680 --> 00:15:12.390 align:middle line:90%
Then there's some analysis.

00:15:12.390 --> 00:15:14.340 align:middle line:84%
This is really just
applying display filters

00:15:14.340 --> 00:15:17.160 align:middle line:84%
and playing around with
things as we see them.

00:15:17.160 --> 00:15:19.570 align:middle line:84%
Statistics, though,
is quite useful.

00:15:19.570 --> 00:15:21.660 align:middle line:84%
So we can go to
Protocol Hierarchy

00:15:21.660 --> 00:15:24.370 align:middle line:84%
and see what protocols
are on this network.

00:15:24.370 --> 00:15:28.436 align:middle line:84%
So most of it's all
Ethernet frames, IPv4--

00:15:28.436 --> 00:15:31.350 align:middle line:90%


00:15:31.350 --> 00:15:34.200 align:middle line:84%
guess there's some traffic that
was Ethernet that was not IPv4.

00:15:34.200 --> 00:15:36.660 align:middle line:90%
But it's not marked as IPv6.

00:15:36.660 --> 00:15:37.965 align:middle line:90%
It's going to be our ARP.

00:15:37.965 --> 00:15:42.220 align:middle line:90%


00:15:42.220 --> 00:15:47.610 align:middle line:90%
Is that under-- yeah.

00:15:47.610 --> 00:15:48.110 align:middle line:90%
Sorry.

00:15:48.110 --> 00:15:49.070 align:middle line:90%
Some of the tabbing--

00:15:49.070 --> 00:15:52.220 align:middle line:90%
that is that other 6%.

00:15:52.220 --> 00:15:55.550 align:middle line:90%
We have some UDP traffic.

00:15:55.550 --> 00:15:58.880 align:middle line:84%
Our TCP traffic includes
a whole bunch of stuff

00:15:58.880 --> 00:16:00.600 align:middle line:90%
because we did that scan.

00:16:00.600 --> 00:16:02.330 align:middle line:90%
So it found the MySQL.

00:16:02.330 --> 00:16:04.440 align:middle line:84%
So it sent some
scripts for the MySQL.

00:16:04.440 --> 00:16:05.150 align:middle line:90%
It found SSH.

00:16:05.150 --> 00:16:08.630 align:middle line:84%
So it sent some scripts for
SSH, set some extra things

00:16:08.630 --> 00:16:10.190 align:middle line:90%
to connect.

00:16:10.190 --> 00:16:11.930 align:middle line:84%
And so that's the
protocol hierarchy.

00:16:11.930 --> 00:16:15.170 align:middle line:84%
We can see what kind of
packets are in this capture.

00:16:15.170 --> 00:16:18.290 align:middle line:90%


00:16:18.290 --> 00:16:20.330 align:middle line:84%
We can dissect them
by conversation.

00:16:20.330 --> 00:16:23.060 align:middle line:84%
So which machine talked
to which machine?

00:16:23.060 --> 00:16:25.700 align:middle line:84%
Initially, over Ethernet, it's
just going to be MAC addresses.

00:16:25.700 --> 00:16:27.080 align:middle line:90%
We can look at IPv4.

00:16:27.080 --> 00:16:31.970 align:middle line:84%
We could even resolve
this, if we wanted to.

00:16:31.970 --> 00:16:39.740 align:middle line:84%
Turn on that name resolution
and the conversations off.

00:16:39.740 --> 00:16:41.300 align:middle line:90%
New resolution turns on there--

00:16:41.300 --> 00:16:44.200 align:middle line:90%


00:16:44.200 --> 00:16:48.160 align:middle line:84%
no IPv6, though there
was TCP traffic.

00:16:48.160 --> 00:16:52.210 align:middle line:84%
And you can scroll through and
see all the conversations--

00:16:52.210 --> 00:16:58.680 align:middle line:90%


00:16:58.680 --> 00:17:01.050 align:middle line:84%
so different than
the overall packages.

00:17:01.050 --> 00:17:02.430 align:middle line:90%
A lot of these packets--

00:17:02.430 --> 00:17:04.230 align:middle line:84%
packages-- a lot
of these packets

00:17:04.230 --> 00:17:05.430 align:middle line:90%
are part of a conversation.

00:17:05.430 --> 00:17:07.530 align:middle line:84%
You can see over
here on the left,

00:17:07.530 --> 00:17:13.170 align:middle line:84%
there's this line
going alongside.

00:17:13.170 --> 00:17:14.190 align:middle line:90%
Well, it goes dotted.

00:17:14.190 --> 00:17:17.940 align:middle line:84%
And it'll eventually
end down there.

00:17:17.940 --> 00:17:22.530 align:middle line:84%
That was all one
conversation, or it

00:17:22.530 --> 00:17:25.710 align:middle line:84%
started at one point, had
some breaks where it's dotted.

00:17:25.710 --> 00:17:28.320 align:middle line:84%
These weren't necessarily
conversations.

00:17:28.320 --> 00:17:35.960 align:middle line:90%


00:17:35.960 --> 00:17:38.870 align:middle line:90%
Then they were-- sorry.

00:17:38.870 --> 00:17:39.870 align:middle line:90%
You get endpoints.

00:17:39.870 --> 00:17:40.920 align:middle line:90%
This can be quite useful.

00:17:40.920 --> 00:17:44.580 align:middle line:84%
Also, name resolution
is an option here.

00:17:44.580 --> 00:17:46.530 align:middle line:84%
It's a little-- just
slightly different

00:17:46.530 --> 00:17:48.090 align:middle line:90%
than the conversations.

00:17:48.090 --> 00:17:55.720 align:middle line:90%


00:17:55.720 --> 00:17:57.220 align:middle line:90%
Another one-- packet lengths.

00:17:57.220 --> 00:17:59.110 align:middle line:84%
And then you could
get into some flow

00:17:59.110 --> 00:18:02.000 align:middle line:90%
graphs, which are interesting.

00:18:02.000 --> 00:18:07.930 align:middle line:84%
Some HTTP traffic information
can be quite useful.

00:18:07.930 --> 00:18:10.210 align:middle line:90%
That is that one.

00:18:10.210 --> 00:18:14.660 align:middle line:84%
We're not messing with
telephony in here.

00:18:14.660 --> 00:18:16.030 align:middle line:90%
We could do some cool labs.

00:18:16.030 --> 00:18:21.160 align:middle line:84%
And we will have some
cool labs, but for VoIP.

00:18:21.160 --> 00:18:25.468 align:middle line:84%
So with wireless, we're not
going to get in those today.

00:18:25.468 --> 00:18:26.260 align:middle line:90%
So what do we have?

00:18:26.260 --> 00:18:27.218 align:middle line:90%
What columns are these?

00:18:27.218 --> 00:18:28.600 align:middle line:90%
We have this number column.

00:18:28.600 --> 00:18:30.250 align:middle line:90%
We've got time.

00:18:30.250 --> 00:18:32.950 align:middle line:84%
And it says "format
as specified."

00:18:32.950 --> 00:18:35.770 align:middle line:90%
But that's a decimal.

00:18:35.770 --> 00:18:36.970 align:middle line:90%
And it starts at 0.

00:18:36.970 --> 00:18:41.530 align:middle line:84%
So this is a relative time--
relative time to what?

00:18:41.530 --> 00:18:42.160 align:middle line:90%
Let's find out.

00:18:42.160 --> 00:18:45.940 align:middle line:90%
Right-click and Edit Column.

00:18:45.940 --> 00:18:48.160 align:middle line:84%
And then it says, oh,
time is specified.

00:18:48.160 --> 00:18:51.670 align:middle line:90%
That's really useful here.

00:18:51.670 --> 00:18:53.710 align:middle line:90%
Well, where is it specified?

00:18:53.710 --> 00:18:58.600 align:middle line:84%
Go back up here into
View, Time Display Format.

00:18:58.600 --> 00:19:01.030 align:middle line:84%
And it's seconds since
beginning of capture.

00:19:01.030 --> 00:19:02.980 align:middle line:90%
So those decimals are seconds.

00:19:02.980 --> 00:19:07.210 align:middle line:90%
They're fractions of a second.

00:19:07.210 --> 00:19:15.040 align:middle line:84%
What is most common is UTC Date
and Time of Day, Control-Alt-7,

00:19:15.040 --> 00:19:18.250 align:middle line:84%
just because it looks
the same for everyone.

00:19:18.250 --> 00:19:21.580 align:middle line:84%
And it goes with UTC
because it's common.

00:19:21.580 --> 00:19:22.210 align:middle line:90%
It's easy.

00:19:22.210 --> 00:19:23.807 align:middle line:90%
It's known.

00:19:23.807 --> 00:19:26.140 align:middle line:84%
You can change it into local
time if you really want to.

00:19:26.140 --> 00:19:28.348 align:middle line:84%
But most people who are
working with packet captures,

00:19:28.348 --> 00:19:30.430 align:middle line:90%
doing investigations, don't--

00:19:30.430 --> 00:19:34.600 align:middle line:84%
they leave everything in UTC
and run the investigations

00:19:34.600 --> 00:19:40.500 align:middle line:84%
off that, at least
in my experience.

00:19:40.500 --> 00:19:41.000 align:middle line:90%