So our next topic is zones a zone is a way to group different interfaces interfaces that don't have
any references such as firewall policies and grouped them together into a logical zone a logical zone
that will be used later on in our policy configuration.
It will make things much simpler.
So currently we have only internal 5 that is dedicated to our marketing lab.
Let's add up another report and dedicated to the finance line which is another segment of our network.
All right.
And let's define it as a line.
Let's give it the IP address of 10 that zero dot for that one on the 24 subnet.
Let's allow ping and S&P and the ACP server we know that we currently have only 15 employees.
So we'll allocate 20 IP addresses for that segment.
Deflate gate which stays the same DNS service stays the same.
We can enable device detection with active scanning.
Now once we do it we have two different interfaces.
One is dedicated to the marketing line.
The second one is dedicated to the finance line.
Now we can create a new zone we will name it unified land.
We can also name it DMC or whatever and we'll set up the members of that zone which are marketing and
finance plan.
And once we do it we will see that we have any new logical interface in our interfaces pain that is
the unified land which includes internal 5 and internal 6 marketing and finance.
We can use that zone in our policy configuration to configure one unified policy that all members of
the marketing and finance plan will have to obey.