WEBVTT

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


00:00:10.140 --> 00:00:15.390 align:middle line:84%
So now we've got date,
time down to seconds.

00:00:15.390 --> 00:00:18.300 align:middle line:90%
Well, that's kind of useful.

00:00:18.300 --> 00:00:24.392 align:middle line:90%
That's a lot of decimals still.

00:00:24.392 --> 00:00:26.850 align:middle line:84%
You might have seen before,
down here, we can go automatic,

00:00:26.850 --> 00:00:28.890 align:middle line:90%
or I just want seconds.

00:00:28.890 --> 00:00:31.200 align:middle line:84%
I'm not going to do more
with tenths of seconds.

00:00:31.200 --> 00:00:37.350 align:middle line:84%
It's already in order,
so seconds is fine.

00:00:37.350 --> 00:00:40.050 align:middle line:84%
Hour, minute, seconds--
yes, all these things

00:00:40.050 --> 00:00:41.910 align:middle line:90%
happened very quickly.

00:00:41.910 --> 00:00:44.040 align:middle line:90%
That's computers.

00:00:44.040 --> 00:00:47.050 align:middle line:90%
That's what happens.

00:00:47.050 --> 00:00:49.860 align:middle line:84%
So our time, we've
got our source IP--

00:00:49.860 --> 00:00:56.520 align:middle line:84%
what I like to do is align this
one right and this one right.

00:00:56.520 --> 00:00:58.410 align:middle line:84%
And what we're going
to add in here--

00:00:58.410 --> 00:01:01.650 align:middle line:84%
we've got source IP
and destination IP.

00:01:01.650 --> 00:01:09.760 align:middle line:84%
We're going to edit columns,
so column preferences,

00:01:09.760 --> 00:01:12.220 align:middle line:90%
and brought up columns.

00:01:12.220 --> 00:01:18.430 align:middle line:84%
Click on this guy twice,
get new columns, and going

00:01:18.430 --> 00:01:26.300 align:middle line:84%
to call this source port and
this one destination port

00:01:26.300 --> 00:01:27.350 align:middle line:90%
or just dest port.

00:01:27.350 --> 00:01:31.190 align:middle line:90%


00:01:31.190 --> 00:01:32.630 align:middle line:90%
That works.

00:01:32.630 --> 00:01:37.940 align:middle line:84%
And right now, it just says
number, but there we go.

00:01:37.940 --> 00:01:43.290 align:middle line:84%
This one is the
destination port,

00:01:43.290 --> 00:01:46.950 align:middle line:90%
and we'll leave it unresolved.

00:01:46.950 --> 00:01:54.150 align:middle line:84%
And source port, let's go with
that, just destination port,

00:01:54.150 --> 00:01:56.280 align:middle line:90%
neither resolved nor unresolved.

00:01:56.280 --> 00:01:59.190 align:middle line:90%
And then let's reorder them--

00:01:59.190 --> 00:02:05.620 align:middle line:84%
so source, source port,
destination, destination port.

00:02:05.620 --> 00:02:06.120 align:middle line:90%
Bingo.

00:02:06.120 --> 00:02:15.960 align:middle line:90%


00:02:15.960 --> 00:02:24.970 align:middle line:84%
So I put addresses to the
right, ports to the left,

00:02:24.970 --> 00:02:29.620 align:middle line:84%
address to the right
and port to the left.

00:02:29.620 --> 00:02:32.438 align:middle line:90%
There we go.

00:02:32.438 --> 00:02:34.320 align:middle line:90%
OK.

00:02:34.320 --> 00:02:39.850 align:middle line:84%
So now you've got 192.112.112.2
port 5284, the ephemeral port,

00:02:39.850 --> 00:02:42.010 align:middle line:90%
going to 443.

00:02:42.010 --> 00:02:43.900 align:middle line:84%
So guess which one
is the web server,

00:02:43.900 --> 00:02:45.670 align:middle line:84%
the one where the
destination port is

00:02:45.670 --> 00:02:49.450 align:middle line:90%
443, kind of useful now.

00:02:49.450 --> 00:02:52.600 align:middle line:84%
This follows a format we're
used to, at least if you've

00:02:52.600 --> 00:02:54.940 align:middle line:84%
been working with network
practice for a while,

00:02:54.940 --> 00:02:57.070 align:middle line:90%
IP then port.

00:02:57.070 --> 00:02:59.090 align:middle line:90%
That's how Netcat works.

00:02:59.090 --> 00:03:01.210 align:middle line:84%
That's how many things
are going to work.

00:03:01.210 --> 00:03:04.810 align:middle line:90%
It's IP address then port.

00:03:04.810 --> 00:03:08.260 align:middle line:84%
And then we've got protocol, and
this is just generic protocol.

00:03:08.260 --> 00:03:15.790 align:middle line:84%
You can see it gets into
some detail down here, HTTP.

00:03:15.790 --> 00:03:20.260 align:middle line:84%
We've got packet length, and
I like to align that center.

00:03:20.260 --> 00:03:24.980 align:middle line:84%
That way, it leaves a gap
for what our packets are.

00:03:24.980 --> 00:03:27.770 align:middle line:84%
And then you can see
details of the packets.

00:03:27.770 --> 00:03:28.270 align:middle line:90%
Neat.

00:03:28.270 --> 00:03:30.960 align:middle line:90%


00:03:30.960 --> 00:03:32.850 align:middle line:90%
All right.

00:03:32.850 --> 00:03:38.410 align:middle line:84%
So those are our fields,
like this one's a--

00:03:38.410 --> 00:03:40.620 align:middle line:90%
where's a good GET request--

00:03:40.620 --> 00:03:42.630 align:middle line:84%
just GET request
for the web page.

00:03:42.630 --> 00:03:48.430 align:middle line:90%


00:03:48.430 --> 00:03:51.070 align:middle line:90%
Well, what is happening?

00:03:51.070 --> 00:03:58.780 align:middle line:84%
Starts at frames, goes up
by protocols, if you will.

00:03:58.780 --> 00:04:03.880 align:middle line:84%
Think of a reverse
of your TCP/IP.

00:04:03.880 --> 00:04:09.930 align:middle line:84%
So frame is going to
cover our interface.

00:04:09.930 --> 00:04:19.130 align:middle line:84%
All right, physical error,
so Ethernet I. And then,

00:04:19.130 --> 00:04:22.580 align:middle line:84%
in here, we have
got Ethernet II.

00:04:22.580 --> 00:04:26.660 align:middle line:84%
So [INAUDIBLE],, what is
our actual connection.

00:04:26.660 --> 00:04:28.520 align:middle line:90%
OK?

00:04:28.520 --> 00:04:31.130 align:middle line:84%
Then what's working at that
layer, our NIC, and our NIC

00:04:31.130 --> 00:04:34.380 align:middle line:90%
has a Mac address.

00:04:34.380 --> 00:04:38.990 align:middle line:90%
So that is us, our source.

00:04:38.990 --> 00:04:41.630 align:middle line:84%
And then our destination
tells you what kind it is,

00:04:41.630 --> 00:04:44.240 align:middle line:84%
and you can keep
diving into this info.

00:04:44.240 --> 00:04:47.510 align:middle line:84%
And you might be wondering
what all this is down here.

00:04:47.510 --> 00:04:51.050 align:middle line:90%
This is the packet.

00:04:51.050 --> 00:04:53.330 align:middle line:84%
Some of this stuff,
the hex dump,

00:04:53.330 --> 00:04:55.175 align:middle line:90%
doesn't make any sense in ASCII.

00:04:55.175 --> 00:04:57.800 align:middle line:84%
But over here, you can see there
is some information that makes

00:04:57.800 --> 00:05:02.250 align:middle line:90%
sense, and then encoded data.

00:05:02.250 --> 00:05:08.300 align:middle line:84%
So as I go through
this whole frame

00:05:08.300 --> 00:05:12.760 align:middle line:84%
and see if anything
actually matters--

00:05:12.760 --> 00:05:17.480 align:middle line:84%
and it's not going
to on that one

00:05:17.480 --> 00:05:20.870 align:middle line:84%
because it doesn't actually have
anything to do with the packet.

00:05:20.870 --> 00:05:25.170 align:middle line:84%
The packet begins with
our physical address.

00:05:25.170 --> 00:05:27.020 align:middle line:90%
So where is it going?

00:05:27.020 --> 00:05:29.600 align:middle line:90%
Where is it coming from?

00:05:29.600 --> 00:05:30.930 align:middle line:90%
Does that makes sense?

00:05:30.930 --> 00:05:37.775 align:middle line:84%
Those are the beginning, that's
that header for that layer.

00:05:37.775 --> 00:05:40.970 align:middle line:84%
It breaks down a little bit
and what the protocol is,

00:05:40.970 --> 00:05:42.110 align:middle line:90%
and that is that header.

00:05:42.110 --> 00:05:51.640 align:middle line:84%
So then we get to TCP/IP or
internet protocol, IP address,

00:05:51.640 --> 00:05:52.560 align:middle line:90%
so our internet layer.

00:05:52.560 --> 00:05:56.478 align:middle line:84%
And this has some
header information,

00:05:56.478 --> 00:05:58.020 align:middle line:84%
a lot of header
information actually,

00:05:58.020 --> 00:06:04.020 align:middle line:84%
but eventually, it gets to
our IP addresses, our source

00:06:04.020 --> 00:06:05.220 align:middle line:90%
and our destination.

00:06:05.220 --> 00:06:10.020 align:middle line:84%
And this is what they break
up to in hex out of the bits.

00:06:10.020 --> 00:06:10.860 align:middle line:90%
And guess what.

00:06:10.860 --> 00:06:13.380 align:middle line:84%
We don't need to spend a lot
of time looking at the bits,

00:06:13.380 --> 00:06:21.590 align:middle line:84%
but I just wanted to show you
how this correlates to that.

00:06:21.590 --> 00:06:24.920 align:middle line:84%
And dive in a little more, our
transmission control error,

00:06:24.920 --> 00:06:27.740 align:middle line:90%
more header information in bits.

00:06:27.740 --> 00:06:30.530 align:middle line:84%
And that's not what I'm
doing in this course.

00:06:30.530 --> 00:06:35.220 align:middle line:84%
I mean, you could look
at what flags are set.

00:06:35.220 --> 00:06:43.745 align:middle line:84%
So this was a ACK push, kind
of makes sense for an HTTP GET.

00:06:43.745 --> 00:06:48.110 align:middle line:84%
The rest, it's just
acknowledging receipt

00:06:48.110 --> 00:06:52.600 align:middle line:84%
and pushing more information,
more header information.

00:06:52.600 --> 00:06:55.500 align:middle line:90%
It finally gets to the data.

00:06:55.500 --> 00:06:59.660 align:middle line:84%
So we've got HTTP data
and it's a GET request.

00:06:59.660 --> 00:07:04.550 align:middle line:84%
So that was all of our
headers for 0, 1, 2, 3

00:07:04.550 --> 00:07:07.520 align:middle line:90%
physical internet transmission.

00:07:07.520 --> 00:07:09.680 align:middle line:84%
And everything else
is kind of going

00:07:09.680 --> 00:07:14.600 align:middle line:84%
to be up here in your data
layer, TCP/IP instead of OSI

00:07:14.600 --> 00:07:20.630 align:middle line:84%
model, if you will, and just
some really basic information.

00:07:20.630 --> 00:07:25.070 align:middle line:84%
Truth be told, this stuff makes
the most sense in the hex dump.

00:07:25.070 --> 00:07:30.860 align:middle line:84%
It's almost plain text because
it's HTTP instead of HTTPS.

00:07:30.860 --> 00:07:33.890 align:middle line:84%
And that's kind
of the breakdown.

00:07:33.890 --> 00:07:36.360 align:middle line:84%
So what else do we
want to do here?

00:07:36.360 --> 00:07:37.940 align:middle line:90%
Well, this is a GET request.

00:07:37.940 --> 00:07:39.830 align:middle line:90%
That's neat.

00:07:39.830 --> 00:07:41.280 align:middle line:90%
What does it do?

00:07:41.280 --> 00:07:45.140 align:middle line:84%
Well, we went to a
website, and that

00:07:45.140 --> 00:07:46.730 align:middle line:90%
makes a whole conversation.

00:07:46.730 --> 00:07:47.780 align:middle line:90%
What we can do--

00:07:47.780 --> 00:07:50.700 align:middle line:84%
I right-clicked, go
into follow, and you go

00:07:50.700 --> 00:07:53.180 align:middle line:90%
to TCP stream or HTTP stream.

00:07:53.180 --> 00:07:59.710 align:middle line:84%
Let's do HTTP stream because
it's an HTTP request.

00:07:59.710 --> 00:08:03.970 align:middle line:84%
And it got a 302 found,
which is a redirect.

00:08:03.970 --> 00:08:04.960 align:middle line:90%
Kind of makes sense.

00:08:04.960 --> 00:08:07.390 align:middle line:90%
What did it send back?

00:08:07.390 --> 00:08:08.740 align:middle line:90%
Nothing.

00:08:08.740 --> 00:08:12.220 align:middle line:84%
What we can do here,
in this follow,

00:08:12.220 --> 00:08:15.370 align:middle line:84%
you could look at one
side of the conversation

00:08:15.370 --> 00:08:20.860 align:middle line:84%
or the other or the
entire conversation.

00:08:20.860 --> 00:08:23.590 align:middle line:84%
And right now, it's
displaying in ASCII,

00:08:23.590 --> 00:08:29.260 align:middle line:84%
but you could put it
in raw and it's what?

00:08:29.260 --> 00:08:30.160 align:middle line:90%
[INAUDIBLE]

00:08:30.160 --> 00:08:33.142 align:middle line:90%


00:08:33.142 --> 00:08:39.490 align:middle line:84%
Click the hex dump,
not super helpful.

00:08:39.490 --> 00:08:42.980 align:middle line:84%
None of this is
really [INAUDIBLE]..

00:08:42.980 --> 00:08:47.890 align:middle line:84%
What it did do is, when
we follow the TCP stream,

00:08:47.890 --> 00:08:49.390 align:middle line:90%
it pulled out that whole stream.

00:08:49.390 --> 00:08:52.840 align:middle line:90%
It put in a display filter.

00:08:52.840 --> 00:09:00.490 align:middle line:84%
This stream is TCP stream
3005, and so it is only

00:09:00.490 --> 00:09:04.960 align:middle line:84%
displaying the packets
related to that stream.

00:09:04.960 --> 00:09:08.500 align:middle line:84%
Down here, you can see
we captured 8,800 packets

00:09:08.500 --> 00:09:10.700 align:middle line:84%
and we're only
displaying 10 of them.

00:09:10.700 --> 00:09:12.610 align:middle line:84%
So we didn't get
rid of anything.

00:09:12.610 --> 00:09:15.640 align:middle line:84%
We're just choosing
what to display up here

00:09:15.640 --> 00:09:16.945 align:middle line:90%
in the display field.

00:09:16.945 --> 00:09:20.110 align:middle line:90%


00:09:20.110 --> 00:09:22.570 align:middle line:84%
To get rid of that,
see everything else,

00:09:22.570 --> 00:09:26.660 align:middle line:84%
just hit the X. What's neat
is it's going to keep history.

00:09:26.660 --> 00:09:28.420 align:middle line:84%
So if you're like,
oh, I want to go back,

00:09:28.420 --> 00:09:29.650 align:middle line:90%
there's no back button.

00:09:29.650 --> 00:09:31.570 align:middle line:84%
What you can do is you
can get rid of filters

00:09:31.570 --> 00:09:34.930 align:middle line:84%
or you can reapply
filters, and it takes you

00:09:34.930 --> 00:09:37.870 align:middle line:90%
back to where you were.

00:09:37.870 --> 00:09:47.530 align:middle line:84%
Well, what if we want to just
look at one type of stream?

00:09:47.530 --> 00:09:51.340 align:middle line:84%
Did you see the layout
for that follow?

00:09:51.340 --> 00:09:54.100 align:middle line:90%
I'll pull it back up--

00:09:54.100 --> 00:09:59.950 align:middle line:90%
Tc's.stream eq 3005.

00:09:59.950 --> 00:10:04.550 align:middle line:84%
I didn't tell it that when I did
the right-click, follow, HTTP

00:10:04.550 --> 00:10:05.050 align:middle line:90%
stream.

00:10:05.050 --> 00:10:07.503 align:middle line:90%
It applied that filter.

00:10:07.503 --> 00:10:08.920 align:middle line:84%
Well, let's find
something that we

00:10:08.920 --> 00:10:11.305 align:middle line:90%
know is going to work better.

00:10:11.305 --> 00:10:13.840 align:middle line:90%


00:10:13.840 --> 00:10:17.390 align:middle line:90%
All right, get rid of that.

00:10:17.390 --> 00:10:22.180 align:middle line:90%


00:10:22.180 --> 00:10:24.008 align:middle line:84%
Let's look at some
of this information.

00:10:24.008 --> 00:10:24.925 align:middle line:90%
This is from our scan.

00:10:24.925 --> 00:10:29.835 align:middle line:90%


00:10:29.835 --> 00:10:30.960 align:middle line:90%
Did I sort something funny?

00:10:30.960 --> 00:10:40.200 align:middle line:90%


00:10:40.200 --> 00:10:42.170 align:middle line:90%
Yes, I did.

00:10:42.170 --> 00:10:42.670 align:middle line:90%
My bad.

00:10:42.670 --> 00:10:43.962 align:middle line:90%
Let's start from the beginning.

00:10:43.962 --> 00:10:47.910 align:middle line:84%
Let's follow this TCP
stream from our first.

00:10:47.910 --> 00:10:50.983 align:middle line:90%
See this is packet number one.

00:10:50.983 --> 00:10:51.900 align:middle line:90%
Let's see what it did.

00:10:51.900 --> 00:10:54.900 align:middle line:90%


00:10:54.900 --> 00:10:57.060 align:middle line:84%
Something that doesn't
make any sense whatsoever.

00:10:57.060 --> 00:10:59.700 align:middle line:90%


00:10:59.700 --> 00:11:01.130 align:middle line:90%
This is encrypted traffic.

00:11:01.130 --> 00:11:05.890 align:middle line:90%


00:11:05.890 --> 00:11:09.020 align:middle line:84%
When you have it set to
ASCII and it looks like this,

00:11:09.020 --> 00:11:10.580 align:middle line:90%
it's encrypted traffic.

00:11:10.580 --> 00:11:12.400 align:middle line:84%
So let's just filter
out that stream.

00:11:12.400 --> 00:11:16.310 align:middle line:84%
Now it's doing a not
TCP stream equals 0.

00:11:16.310 --> 00:11:16.810 align:middle line:90%
OK?

00:11:16.810 --> 00:11:18.880 align:middle line:90%
Well, what about this one?

00:11:18.880 --> 00:11:21.910 align:middle line:90%


00:11:21.910 --> 00:11:23.950 align:middle line:90%
That's nothing.

00:11:23.950 --> 00:11:25.790 align:middle line:84%
Sometimes you can
just keep filtering.

00:11:25.790 --> 00:11:27.610 align:middle line:84%
These are going to
be ARP scans, so they

00:11:27.610 --> 00:11:28.990 align:middle line:90%
don't have a conversation.

00:11:28.990 --> 00:11:33.640 align:middle line:90%
ARP is not TCP.

00:11:33.640 --> 00:11:36.400 align:middle line:84%
That's why, when we looked at
hierarchy, it didn't count,

00:11:36.400 --> 00:11:38.710 align:middle line:90%
because ARP works at level two.

00:11:38.710 --> 00:11:47.160 align:middle line:84%
It's just IP addresses
and Mac addresses.

00:11:47.160 --> 00:11:52.320 align:middle line:84%
Let's apply a filter
ourselves, and not ARP.

00:11:52.320 --> 00:11:56.287 align:middle line:84%
As I was typing, you could see
it is going to kind of guess

00:11:56.287 --> 00:11:57.495 align:middle line:90%
and give me things to choose.

00:11:57.495 --> 00:12:00.400 align:middle line:90%


00:12:00.400 --> 00:12:02.580 align:middle line:90%
So let's go with that.

00:12:02.580 --> 00:12:06.510 align:middle line:84%
Did you see it's red,
that whole bar right now?

00:12:06.510 --> 00:12:09.510 align:middle line:84%
It means, if I try to
run this, it won't.

00:12:09.510 --> 00:12:13.260 align:middle line:84%
Even over here, it's
got a little do not, not

00:12:13.260 --> 00:12:14.700 align:middle line:90%
allowed sign.

00:12:14.700 --> 00:12:18.130 align:middle line:90%
I finish that P, it turns green.

00:12:18.130 --> 00:12:25.005 align:middle line:84%
And if I hit Enter, it did not
display all of the ARP packets.

00:12:25.005 --> 00:12:29.070 align:middle line:90%


00:12:29.070 --> 00:12:30.120 align:middle line:90%
We can even go back.

00:12:30.120 --> 00:12:33.090 align:middle line:84%
Right now, we're
looking at 8,116.

00:12:33.090 --> 00:12:38.880 align:middle line:84%
If I go to the one
before that, 8,642.

00:12:38.880 --> 00:12:44.070 align:middle line:84%
That was the change,
lost like 500 ARP packets

00:12:44.070 --> 00:12:50.370 align:middle line:90%
from our host scan.

00:12:50.370 --> 00:12:57.935 align:middle line:84%
Now we've also got a
mess of ACK resets.

00:12:57.935 --> 00:13:01.040 align:middle line:90%


00:13:01.040 --> 00:13:08.046 align:middle line:90%
What if we got rid of and TCP?

00:13:08.046 --> 00:13:10.240 align:middle line:84%
Is that' going to
work or is that

00:13:10.240 --> 00:13:11.650 align:middle line:90%
going to get rid of everything?

00:13:11.650 --> 00:13:14.140 align:middle line:90%
Thought so, OK.

00:13:14.140 --> 00:13:19.480 align:middle line:84%
Now it takes us to the ICMP,
because again, we did TAC SN

00:13:19.480 --> 00:13:21.130 align:middle line:90%
so it included a ping scan.

00:13:21.130 --> 00:13:23.860 align:middle line:84%
After it did our ARP
scan, it did a ping scan.

00:13:23.860 --> 00:13:30.430 align:middle line:84%
And we also see this EDP,
probably because, when it saw--

00:13:30.430 --> 00:13:38.260 align:middle line:90%


00:13:38.260 --> 00:13:39.790 align:middle line:84%
oh, probably one
of the scripts also

00:13:39.790 --> 00:13:43.540 align:middle line:90%
ran EDP checking for something.

00:13:43.540 --> 00:13:47.590 align:middle line:84%
Cool, so that's how we can
play with some display filters.

00:13:47.590 --> 00:13:56.880 align:middle line:84%
But while that was
kind of useful,

00:13:56.880 --> 00:14:00.480 align:middle line:84%
let's really dive
into display filters.

00:14:00.480 --> 00:14:02.430 align:middle line:84%
So over here, we've
got this plus sign.

00:14:02.430 --> 00:14:06.820 align:middle line:84%
It says, add a
display filter button.

00:14:06.820 --> 00:14:09.660 align:middle line:84%
And we can get into
preferences, but you

00:14:09.660 --> 00:14:13.410 align:middle line:84%
can create a specific
display filter

00:14:13.410 --> 00:14:17.502 align:middle line:84%
and name it something,
save it, have it for later.

00:14:17.502 --> 00:14:18.960 align:middle line:84%
I think it would
be kind of useful.

00:14:18.960 --> 00:14:21.480 align:middle line:90%


00:14:21.480 --> 00:14:22.020 align:middle line:90%
That's all.

00:14:22.020 --> 00:14:38.940 align:middle line:90%


00:14:38.940 --> 00:14:41.040 align:middle line:84%
There we go, display
filter expression.

00:14:41.040 --> 00:14:45.030 align:middle line:84%
I right-clicked the
field, pulled it up.

00:14:45.030 --> 00:14:50.400 align:middle line:84%
There are, I think, 600,000
different display filters

00:14:50.400 --> 00:14:53.550 align:middle line:90%
on the Wireshark website.

00:14:53.550 --> 00:14:56.190 align:middle line:84%
There's so many different
types of filters.

00:14:56.190 --> 00:15:00.690 align:middle line:84%
You can filter by any
sort of network traffic

00:15:00.690 --> 00:15:06.390 align:middle line:84%
that can be ingested and
breaking it up in any way

00:15:06.390 --> 00:15:07.710 align:middle line:90%
you want.

00:15:07.710 --> 00:15:09.540 align:middle line:90%
It's kind of a mess.

00:15:09.540 --> 00:15:12.510 align:middle line:90%


00:15:12.510 --> 00:15:16.890 align:middle line:84%
But one of the easiest
ones, IP addresses--

00:15:16.890 --> 00:15:24.270 align:middle line:90%


00:15:24.270 --> 00:15:25.580 align:middle line:90%
so many IP addresses.

00:15:25.580 --> 00:15:30.005 align:middle line:90%


00:15:30.005 --> 00:15:31.380 align:middle line:84%
If you wanted
something specific,

00:15:31.380 --> 00:15:34.830 align:middle line:84%
you could come into here,
dig through, and figure out

00:15:34.830 --> 00:15:41.307 align:middle line:84%
how to create what
it is you want,

00:15:41.307 --> 00:15:42.390 align:middle line:90%
and then it will apply it.

00:15:42.390 --> 00:15:45.690 align:middle line:90%


00:15:45.690 --> 00:15:48.090 align:middle line:84%
That's not going to match
anything because I kind of just

00:15:48.090 --> 00:15:48.780 align:middle line:90%
made it up.

00:15:48.780 --> 00:15:52.390 align:middle line:90%
What is most useful, IP address.

00:15:52.390 --> 00:15:55.170 align:middle line:90%
So ip.addr.

00:15:55.170 --> 00:15:59.980 align:middle line:84%
because I'm following
what it shows there,

00:15:59.980 --> 00:16:07.780 align:middle line:90%
equals equals 192.0.2.1.

00:16:07.780 --> 00:16:16.090 align:middle line:84%
So it found things with
the IP address 192.0.2.1,

00:16:16.090 --> 00:16:18.250 align:middle line:90%
which I'm not exactly seeing.

00:16:18.250 --> 00:16:27.440 align:middle line:84%
But what we can do is
search, and it should take us

00:16:27.440 --> 00:16:32.510 align:middle line:90%
to what we're looking for.

00:16:32.510 --> 00:16:42.090 align:middle line:90%


00:16:42.090 --> 00:16:42.590 align:middle line:90%
Sorry.

00:16:42.590 --> 00:16:54.990 align:middle line:90%


00:16:54.990 --> 00:16:57.450 align:middle line:84%
So it found things
that applied to that.

00:16:57.450 --> 00:17:07.170 align:middle line:84%
What would make the most sense
is 112.112., so we get 3.

00:17:07.170 --> 00:17:12.660 align:middle line:84%
This is all the traffic that
applied to 192.112.112.3.

00:17:12.660 --> 00:17:21.710 align:middle line:84%
There's some scan information,
and then finally, some talking.

00:17:21.710 --> 00:17:25.220 align:middle line:84%
So we did pull up a
website eventually.

00:17:25.220 --> 00:17:26.720 align:middle line:90%
We got a 302 found.

00:17:26.720 --> 00:17:30.260 align:middle line:84%
And then what it did is it
sent another ACK, FIN, ACK.

00:17:30.260 --> 00:17:35.060 align:middle line:90%


00:17:35.060 --> 00:17:44.950 align:middle line:84%
Eventually, should have
returned-- there we go, 200 OK.

00:17:44.950 --> 00:17:48.820 align:middle line:90%
Let's follow this TCP stream.

00:17:48.820 --> 00:17:50.950 align:middle line:90%
So got to login.php.

00:17:50.950 --> 00:17:53.890 align:middle line:90%


00:17:53.890 --> 00:17:55.030 align:middle line:90%
That was redirected.

00:17:55.030 --> 00:17:56.155 align:middle line:90%
That's why we got the 302.

00:17:56.155 --> 00:17:58.330 align:middle line:90%
It redirected.

00:17:58.330 --> 00:18:03.760 align:middle line:84%
That returned a 200
OK, an API reply saying

00:18:03.760 --> 00:18:06.700 align:middle line:90%
that, hey, this does exist.

00:18:06.700 --> 00:18:10.240 align:middle line:90%
And it returned a text/HTML doc.

00:18:10.240 --> 00:18:13.543 align:middle line:84%
We did it in a browser,
so it interpreted the HTML

00:18:13.543 --> 00:18:14.960 align:middle line:84%
and actually showed
you something,

00:18:14.960 --> 00:18:16.420 align:middle line:90%
but this is what it looks like.

00:18:16.420 --> 00:18:20.350 align:middle line:90%


00:18:20.350 --> 00:18:24.730 align:middle line:84%
And if you know HTML,
this makes some sense.

00:18:24.730 --> 00:18:27.360 align:middle line:90%
But hey, this is it.

00:18:27.360 --> 00:18:33.330 align:middle line:84%
There's an image
in here, bee_1.png.

00:18:33.330 --> 00:18:38.460 align:middle line:84%
Now, that in and of itself,
it says there to look for it,

00:18:38.460 --> 00:18:48.290 align:middle line:84%
but I don't think we're
going to find it in this.

00:18:48.290 --> 00:19:02.110 align:middle line:84%
Instead, we should see
it in the next exchange

00:19:02.110 --> 00:19:04.135 align:middle line:90%
asking to send that image.

00:19:04.135 --> 00:19:09.470 align:middle line:90%


00:19:09.470 --> 00:19:11.750 align:middle line:84%
And you could sit
and dig through

00:19:11.750 --> 00:19:15.890 align:middle line:84%
and try to read this data,
or we have an object.

00:19:15.890 --> 00:19:16.880 align:middle line:90%
We have an image.

00:19:16.880 --> 00:19:21.380 align:middle line:84%
We know we have an image because
we saw it in the browser.

00:19:21.380 --> 00:19:24.260 align:middle line:84%
But you could just see what
other images altogether

00:19:24.260 --> 00:19:26.540 align:middle line:90%
are in this capture.

00:19:26.540 --> 00:19:34.020 align:middle line:84%
Go to HTTP, and there
is info in here.

00:19:34.020 --> 00:19:36.020 align:middle line:84%
These are text, text,
text, text, text,

00:19:36.020 --> 00:19:38.720 align:middle line:90%
text, and that can be useful.

00:19:38.720 --> 00:19:41.540 align:middle line:90%
Here is an image.

00:19:41.540 --> 00:19:45.530 align:middle line:84%
This one's a favicon
for Microsoft.

00:19:45.530 --> 00:19:47.250 align:middle line:90%
There should also be a bee.

00:19:47.250 --> 00:19:51.210 align:middle line:90%


00:19:51.210 --> 00:19:52.650 align:middle line:84%
It might be showing
up as nothing.

00:19:52.650 --> 00:20:01.890 align:middle line:90%


00:20:01.890 --> 00:20:03.690 align:middle line:90%
Let's save it all.

00:20:03.690 --> 00:20:06.750 align:middle line:84%
Let's put it on the
desktop in a folder.

00:20:06.750 --> 00:20:12.130 align:middle line:84%
Because otherwise,
we'll have to sift

00:20:12.130 --> 00:20:14.620 align:middle line:90%
through a lot on our desktop.

00:20:14.620 --> 00:20:24.032 align:middle line:90%


00:20:24.032 --> 00:20:25.960 align:middle line:90%
I keep saving stuff there and--

00:20:25.960 --> 00:20:32.570 align:middle line:90%


00:20:32.570 --> 00:20:34.520 align:middle line:84%
I've been saving
things in roots.

00:20:34.520 --> 00:20:35.224 align:middle line:90%
I'm in root.

00:20:35.224 --> 00:21:00.430 align:middle line:90%


00:21:00.430 --> 00:21:03.160 align:middle line:90%
There we go.

00:21:03.160 --> 00:21:04.120 align:middle line:90%
It's there.

00:21:04.120 --> 00:21:05.395 align:middle line:90%
Why is it not here?

00:21:05.395 --> 00:21:12.817 align:middle line:90%


00:21:12.817 --> 00:21:13.650 align:middle line:90%
Well, that's trippy.

00:21:13.650 --> 00:21:21.090 align:middle line:90%


00:21:21.090 --> 00:21:22.990 align:middle line:84%
I'm not going to try
to make sense of that.

00:21:22.990 --> 00:21:25.320 align:middle line:90%
All right.

00:21:25.320 --> 00:21:31.800 align:middle line:84%
Well, we pulled all those
objects into our machine

00:21:31.800 --> 00:21:34.620 align:middle line:84%
and we were able to save
them from Wireshark.

00:21:34.620 --> 00:21:36.323 align:middle line:84%
That was what I was
trying to get at,

00:21:36.323 --> 00:21:38.490 align:middle line:84%
that we were able to take
the objects and save them.

00:21:38.490 --> 00:21:41.870 align:middle line:90%


00:21:41.870 --> 00:21:44.240 align:middle line:84%
Then you go through and try
to see what they all mean.

00:21:44.240 --> 00:21:47.330 align:middle line:84%
So that is how we
can use Wireshark

00:21:47.330 --> 00:21:49.720 align:middle line:90%
to look at some traffic.

00:21:49.720 --> 00:21:55.530 align:middle line:90%
Let's start a clean one.

00:21:55.530 --> 00:22:03.090 align:middle line:90%


00:22:03.090 --> 00:22:06.370 align:middle line:90%
Still have this one open.

00:22:06.370 --> 00:22:07.665 align:middle line:90%
Let's make some traffic.

00:22:07.665 --> 00:22:18.700 align:middle line:90%


00:22:18.700 --> 00:22:23.340 align:middle line:84%
That's not going to
resolve, but it tried to.

00:22:23.340 --> 00:22:30.410 align:middle line:84%
All right, let's stop capturing
there, follow some streams,

00:22:30.410 --> 00:22:33.370 align:middle line:90%
see if there's anything.

00:22:33.370 --> 00:22:34.850 align:middle line:90%
Nope, that was all encrypted.

00:22:34.850 --> 00:22:38.350 align:middle line:84%
And that should be
because, yes, HTTPS.

00:22:38.350 --> 00:22:42.200 align:middle line:90%


00:22:42.200 --> 00:22:46.205 align:middle line:84%
Let's show the difference
if we look at .3.

00:22:46.205 --> 00:22:48.783 align:middle line:90%


00:22:48.783 --> 00:22:49.950 align:middle line:90%
I guess we could leave that.

00:22:49.950 --> 00:22:55.210 align:middle line:90%


00:22:55.210 --> 00:22:57.420 align:middle line:84%
So all this traffic
looks like nothing

00:22:57.420 --> 00:22:59.580 align:middle line:84%
when we follow a TCP
stream because it's

00:22:59.580 --> 00:23:01.680 align:middle line:90%
over HTTPS, which is encrypted.

00:23:01.680 --> 00:23:03.820 align:middle line:90%
And did we capture--

00:23:03.820 --> 00:23:11.220 align:middle line:90%


00:23:11.220 --> 00:23:13.290 align:middle line:84%
should have captured
the TLS handshake.

00:23:13.290 --> 00:23:41.050 align:middle line:90%


00:23:41.050 --> 00:23:45.220 align:middle line:84%
OK, it's just
playing with me now.

00:23:45.220 --> 00:23:46.120 align:middle line:90%
It's toying with me.

00:23:46.120 --> 00:23:49.960 align:middle line:90%


00:23:49.960 --> 00:23:54.430 align:middle line:84%
We'll continue this one
without saving or capture,

00:23:54.430 --> 00:23:59.270 align:middle line:84%
and let's capture this
one-- it is not encrypted--

00:23:59.270 --> 00:23:59.770 align:middle line:90%
or .3.

00:23:59.770 --> 00:24:04.832 align:middle line:90%


00:24:04.832 --> 00:24:07.290 align:middle line:84%
Oh, and that's definitely why
we didn't get objects before.

00:24:07.290 --> 00:24:24.300 align:middle line:90%


00:24:24.300 --> 00:24:29.475 align:middle line:84%
Capturing on the wrong eth
interface, rookie mistake.

00:24:29.475 --> 00:24:32.340 align:middle line:90%


00:24:32.340 --> 00:24:33.900 align:middle line:90%
I should know better than that.

00:24:33.900 --> 00:24:36.030 align:middle line:90%
There we go.

00:24:36.030 --> 00:24:40.620 align:middle line:90%
Capture on the right interface.

00:24:40.620 --> 00:24:44.860 align:middle line:84%
That'll help your
analysis go much better.

00:24:44.860 --> 00:24:45.360 align:middle line:90%
OK.

00:24:45.360 --> 00:24:51.960 align:middle line:90%


00:24:51.960 --> 00:24:55.830 align:middle line:84%
So we got a GET request
to the login page,

00:24:55.830 --> 00:24:59.940 align:middle line:90%
and let's follow that.

00:24:59.940 --> 00:25:01.240 align:middle line:90%
It's really straightforward.

00:25:01.240 --> 00:25:04.710 align:middle line:84%
It downloaded the same thing
we saw before, clicked around,

00:25:04.710 --> 00:25:05.925 align:middle line:90%
and it pulled up--

00:25:05.925 --> 00:25:07.275 align:middle line:90%
it's also got the CSS.

00:25:07.275 --> 00:25:10.440 align:middle line:90%


00:25:10.440 --> 00:25:11.370 align:middle line:90%
Clicked on new user.

00:25:11.370 --> 00:25:12.453 align:middle line:90%
That brought up something.

00:25:12.453 --> 00:25:13.350 align:middle line:90%
I clicked on info.

00:25:13.350 --> 00:25:20.200 align:middle line:84%
That brought up a new page,
pulled up training.php.

00:25:20.200 --> 00:25:21.070 align:middle line:90%
It's great.

00:25:21.070 --> 00:25:25.930 align:middle line:84%
If I filter out
this whole stream,

00:25:25.930 --> 00:25:31.110 align:middle line:84%
it should show you
have more new stuff.

00:25:31.110 --> 00:25:34.630 align:middle line:84%
This is JavaScript
or turned JavaScript.

00:25:34.630 --> 00:25:35.800 align:middle line:90%
Guess what.

00:25:35.800 --> 00:25:40.600 align:middle line:84%
JavaScript is not
human readable here.

00:25:40.600 --> 00:25:42.602 align:middle line:84%
It's got to be
interpreted [INAUDIBLE]..

00:25:42.602 --> 00:25:45.280 align:middle line:90%


00:25:45.280 --> 00:25:48.610 align:middle line:84%
But hey, it triggered
GET some images,

00:25:48.610 --> 00:25:58.258 align:middle line:84%
and looks like some images
were got, and that makes sense.

00:25:58.258 --> 00:25:59.800 align:middle line:84%
So that's what we're
looking at here,

00:25:59.800 --> 00:26:03.340 align:middle line:84%
a whole bunch of images
getting sent across.

00:26:03.340 --> 00:26:04.405 align:middle line:90%
Let's go look at those.

00:26:04.405 --> 00:26:11.145 align:middle line:90%


00:26:11.145 --> 00:26:11.645 align:middle line:90%
Perhaps.

00:26:11.645 --> 00:26:19.740 align:middle line:90%


00:26:19.740 --> 00:26:20.410 align:middle line:90%
I feel silly.

00:26:20.410 --> 00:26:32.210 align:middle line:90%


00:26:32.210 --> 00:26:35.460 align:middle line:90%
Oh, kill the filter.

00:26:35.460 --> 00:26:40.630 align:middle line:90%


00:26:40.630 --> 00:26:42.190 align:middle line:90%
No, I'm just being silly.

00:26:42.190 --> 00:26:47.710 align:middle line:84%
All right, pulled over the HTML
pages, the CSS, the JavaScript.

00:26:47.710 --> 00:26:52.750 align:middle line:84%
But this one, it's not going
to give us any of the images.

00:26:52.750 --> 00:26:54.760 align:middle line:90%
That's fine.

00:26:54.760 --> 00:27:01.300 align:middle line:84%
These are things that you
can play with in Wireshark,

00:27:01.300 --> 00:27:04.330 align:middle line:90%
and I'll quit without saving.

00:27:04.330 --> 00:27:08.020 align:middle line:84%
And that's how we can
intercept traffic and compare

00:27:08.020 --> 00:27:10.030 align:middle line:90%
some HTTP to HTTPS.

00:27:10.030 --> 00:27:20.000 align:middle line:90%


00:27:20.000 --> 00:27:22.730 align:middle line:84%
I know that was kind
of a longish lab.

00:27:22.730 --> 00:27:24.440 align:middle line:84%
It was all over the
place a little bit

00:27:24.440 --> 00:27:27.003 align:middle line:84%
and thank you for
hanging in there with me.

00:27:27.003 --> 00:27:28.670 align:middle line:84%
Hopefully you got
something out of that,

00:27:28.670 --> 00:27:30.800 align:middle line:90%
you got used to Wireshark.

00:27:30.800 --> 00:27:33.140 align:middle line:84%
If you haven't played with
Wireshark, get in there,

00:27:33.140 --> 00:27:35.540 align:middle line:84%
play with it,
enjoy it, have fun,

00:27:35.540 --> 00:27:39.410 align:middle line:84%
and get used to it because
it can be used greatly.

00:27:39.410 --> 00:27:42.680 align:middle line:84%
We're going to do most of the
rest of this in command line

00:27:42.680 --> 00:27:45.830 align:middle line:84%
in TShark just to
simplify it, streamline.

00:27:45.830 --> 00:27:50.780 align:middle line:84%
And unless you're
doing an investigation

00:27:50.780 --> 00:27:52.400 align:middle line:84%
or you're just
playing around, it's

00:27:52.400 --> 00:27:55.790 align:middle line:84%
more likely you're going to run
some scripts utilizing things

00:27:55.790 --> 00:27:59.390 align:middle line:84%
in command line instead
of actually working

00:27:59.390 --> 00:28:03.680 align:middle line:84%
in Wireshark itself, especially
if you're working remotely.

00:28:03.680 --> 00:28:05.240 align:middle line:84%
Some of the things
that we're doing--

00:28:05.240 --> 00:28:06.860 align:middle line:90%
you're sniffing traffic.

00:28:06.860 --> 00:28:09.590 align:middle line:84%
And listening to
someone else's traffic

00:28:09.590 --> 00:28:14.870 align:middle line:84%
is way easier to do
with a quiet sensor.

00:28:14.870 --> 00:28:17.810 align:middle line:84%
And if you don't have to
have a GUI running Wireshark,

00:28:17.810 --> 00:28:21.110 align:middle line:84%
if you can just have a tcpdump
getting that information

00:28:21.110 --> 00:28:25.370 align:middle line:84%
and sending it back,
looking at it, again,

00:28:25.370 --> 00:28:28.490 align:middle line:84%
in command line in
something like TShark,

00:28:28.490 --> 00:28:31.040 align:middle line:84%
the command line
version of Wireshark--

00:28:31.040 --> 00:28:33.350 align:middle line:84%
it's the same tool,
just how you interact

00:28:33.350 --> 00:28:35.690 align:middle line:90%
with it instead of the GUI--

00:28:35.690 --> 00:28:36.890 align:middle line:90%
can be quite useful.

00:28:36.890 --> 00:28:40.510 align:middle line:84%
And we will dive into
that in the next labs.