WEBVTT

00:12.500 --> 00:16.180
Hi my name is you have from teach ethics.

00:16.460 --> 00:20.280
Welcome you all to the Cisco firewalls course.

00:20.870 --> 00:31.090
In this view we will cover the topic of states full and status firewalls by the end of this video.

00:31.140 --> 00:38.420
You will be able to understand what is the difference between what we call a state's will and status

00:38.440 --> 00:44.200
firewall and actually how each one of them works.

00:44.230 --> 00:55.020
So let's start states for firewall as the main as the name says it stores information of a specific

00:55.020 --> 00:57.930
connection user's connection.

00:57.950 --> 01:02.580
In fact even this table we call it a state table.

01:02.780 --> 01:06.110
Sometime sometime we call it a connection table.

01:06.330 --> 01:07.780
So state is stable.

01:07.890 --> 01:10.470
Sometimes state tables sometimes connection.

01:10.490 --> 01:20.560
Table right the function or the purpose of this connection table is to store information about specific

01:20.800 --> 01:24.670
connection for future use.

01:24.970 --> 01:33.070
Which means if a user connected from the inside network which is your land for example to the Internet

01:33.610 --> 01:44.060
and this connection was denied this fateful firewall stores this information in that state table for

01:44.060 --> 01:44.930
future use.

01:45.440 --> 01:52.370
So if the user tries to connect again with the same IP address with the same conditions.

01:52.370 --> 01:58.490
The firewall will quickly take the same decision it took before.

01:59.120 --> 02:07.550
Which means it will be faster to take decisions because already it has this connection information stored

02:07.610 --> 02:08.200
in the state.

02:08.200 --> 02:21.480
David one example of the states for firewall is a Cisco a is 8 which we discuss later in future videos.

02:21.520 --> 02:25.470
The second type which is the opposite of the state's full firewall is the state.

02:25.480 --> 02:34.190
This firewall as the name implies it's the opposite of the states for firewall which means it does not

02:34.580 --> 02:45.140
look at the state table and it does not Tor connection information in state table or status table or

02:45.140 --> 02:48.330
connection with OK.

02:48.470 --> 02:58.500
One example of the state despite all is the extended access control list which we will cover also in

02:59.010 --> 03:02.280
future videos and we will have a lab on it.

03:04.580 --> 03:12.860
The access control list actually is a list that you actually create in order to either deny or allow

03:13.010 --> 03:23.980
a specific connection based on some rules or conditions that you actually dictate the firewall to do.

03:25.060 --> 03:32.850
So let's summarize this let's start by the states first the states firewall.

03:32.850 --> 03:39.750
It doesn't use state table it only relies on the IP packet.

03:39.760 --> 03:51.590
Heather every IP packet contains a header which looks like this 32 bits that main information contained

03:51.650 --> 04:00.580
in the packet Heather is the source IP address destination protocol type and the time to leave those

04:00.580 --> 04:05.070
out of the main information contained in the packets.

04:05.650 --> 04:12.090
So the status firewall only relies on the packet header of the IP packet.

04:12.160 --> 04:17.620
It does not look at the actual contents of the packet on the other hand.

04:17.650 --> 04:25.800
The states will firewall extents the stateless firewall by performing

04:28.070 --> 04:36.320
correctness checking upon the protocols that it gateways which means it looks deeper in the IP packet.

04:36.410 --> 04:42.530
It looks at the contents of the IP packet and instead of looking only at the packet Heather.

04:43.250 --> 04:51.710
And as we mentioned above the filtering decision is based on flows on flows means on the conviction

04:52.340 --> 04:58.670
status or the connection history instead of relying only on the packet.

04:58.670 --> 05:06.160
Heather All right so let's move to the next slide.

05:06.190 --> 05:15.970
Here is an example of a connection between an internal P.C. and an external Web server in that is states

05:15.970 --> 05:23.900
where firewall the Internet client here tries to connect with the external Web server from these IP

05:25.060 --> 05:34.990
to these destination IP so the states will firewall as we said stores this information in a table like

05:34.990 --> 05:37.680
this.

05:37.700 --> 05:49.210
This is an example of the state table main information contained are protocol type DCP and an IP address

05:49.270 --> 05:51.520
which is best source IP address.

05:51.520 --> 06:01.830
This one the Internet port sixty to six hundred external IP address which is this one one twenty three

06:01.830 --> 06:11.420
thousand eighty five the thirty four external Port says this is our server so it's an HDTV server which

06:11.420 --> 06:23.070
has the port of 80 and the status is okay which means the connection is established the below figure

06:23.070 --> 06:33.090
also shows an example of how the state table might look like the exact figure differs from one file

06:33.090 --> 06:37.140
to another depends on the model on the brand.

06:37.140 --> 06:45.840
So the main information contained are as I said of address source port destination address destination

06:45.840 --> 06:52.000
port and the connection state established or okay.

06:52.200 --> 06:52.830
It's the same.

06:52.830 --> 07:01.250
Same meaning all right so let's move on to the next slide.

07:01.330 --> 07:08.710
We will summarize what we just said states with firewalls operate faster than states.

07:08.780 --> 07:09.740
Why faster.

07:10.010 --> 07:20.010
Because it already has the connection details stored in the state table so it doesn't need to start

07:20.010 --> 07:27.050
from scratch to take decision if the connection status started already.

07:27.050 --> 07:34.650
The firewall will look into the state table will take the decision immediately whether allow or deny

07:35.370 --> 07:42.900
or ask you to do some something so mainly it's faster OK.

07:45.300 --> 07:55.200
As we mentioned any existing connection can be described by several properties such as source and destination

07:55.230 --> 08:06.490
ip addresses protocol type whether it's UDP or DCP port numbers and the current stage which is actually

08:07.480 --> 08:10.090
whether it's established refused.

08:10.150 --> 08:11.170
Okay.

08:11.320 --> 08:13.340
As we mentioned in the previous slide.

08:13.550 --> 08:15.660
OK.

08:15.810 --> 08:24.800
On the other hand the status firewall actually since it doesn't require or store connections that is

08:24.920 --> 08:26.430
in a table.

08:26.750 --> 08:33.620
So it requires less memory because it doesn't store any information.

08:33.620 --> 08:39.850
It just starts from scratch every time a connection tries to be established.

08:39.860 --> 08:44.000
So it occupies less memory.

08:44.000 --> 08:54.670
So to make it short it will firewall faster stores connection information in a state table and on the

08:54.670 --> 09:04.270
other hand the stateless firewall requires less memory no storing of connection information in a table

09:06.510 --> 09:14.580
on the next video we will cover the topic of what we call and next generation firewalls.

09:14.740 --> 09:17.080
I hope you enjoy the video.

09:17.080 --> 09:20.650
Thank you for watching and see you on the next video.
