A firewall is a network security system which monitors and takes actions on the ingoing or outgoing packets based on the defined rules. It can be a hardware device or a software.
An organisation that cannot afford a hardware firewall device uses an alternative i.e implementing firewall features on Cisco IOS router by using CBAC or by using Zone-based firewall.CBAC is a predecessor to Zone-based firewall.
Zone-based Firewall –
A Zone-based firewall is an advanced method of stateful firewall. In stateful firewall, a stateful database is maintained in which source IP address, destination IP address, source Port number, destination port number is recorded. Due to this, only the replies are allowed i.e if the traffic is Generated from inside the network then only the replies (of inside network traffic) coming from outside the network is allowed.
Cisco IOS router can be made firewall through two methods:
- By using CBAC: create an access-list and apply it to the interfaces keeping in mind what traffic should be allowed or denied and in what direction. This has an extra overhead for the administrator.
- Using a Zone-based firewall.
- Zone – A zone is a logical area in which the devices having same trust levels resides. After creating a zone, an interface is assigned to a zone.By default, traffic is not allowed from one zone to another.
For example, first we create a zone called inside then if the router interface fa0/0 resides on the most trusted network which we name as inside, then fa0/0 is assigned to inside zone.
- Zone-pair – Policies are defined in which traffic is identified (what type of traffic) then what action should be taken (Inspect Denied, permit). Then we have to apply this policies to a zone-pair. A zone-pair is always unidirectional. If we want to make it bidirectional then we have to create another zone-pair.
For instance, we want to allow the traffic from inside to outside network then we have to create a zone-pair. If we have chosen the action inspect then the reply is permitted from outside the network if the traffic is generated from the inside network (stateful filtering).
Now, if we want to allow outside traffic to be able to reach inside network then we have to make a separate zone-pair. This zone-pair will allow the traffic to reach the inside network if the traffic is generated from the outside network.
- Self-zone – Traffic destined to the router itself, irrespective of which device has send, is known as self zone. The traffic generated from router is known as traffic coming from self-zone. Traffic going to router is considered as traffic going to Self-zone. By default, the traffic to or from the Self-zone is allowed however it can be changed according to the policies applied.
First, the zones are defined and named. Although, we can give any name but by naming convention that makes sense, name the zones as inside, outside and DMZ.
- inside: The most trusted (private) network.
- outside: The most untrusted (public) network.
- DMZ: (public zone) contains devices like servers.
Now, as zones have been named, policies are created which will include what type of traffic is allowed to be generated and allowed to go through from inside network to outside network and what actions (such as inspect [stateful inspection]) should be taken on the traffic.
The actions can be:
- inspect: an entry will be made in stateful database for the protocols (for which the policies has been applied) so that the replies (for inside network) can come back.
- drop: default action if the traffic does not match the policies.
- pass: the traffic will be allowed from one zone to another but no session is maintained.
The traffic which will not match the policies will be dropped due to default policy. This policies will be defined for one direction (such as inside to outside) in a zone pair.
If conditions requires to allow initial traffic to be generated in both directions (inside to outside network and outside to inside network), then two separate zone-pairs will be created and separate policies are applied.
Advantages – Some of the advantages are:
- By default, the traffic is blocked unlike CBAC. In Zone-based firewall, no traffic is allowed from one zone to another while in CBAC, all traffic is allowed if no explicit ACL is applied.
- Unlike CBAC, Zone-based firewall is no heavily dependent on ACL.
- It is easy to add another interface as only the zone has to be declared to which the interface belongs as all the policies will be same as applied explicitly before for that zone.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Difference between Traditional Firewall and Next Generation Firewall
- Difference between Hardware Firewall and Software Firewall
- Introduction of Firewall in Computer Network
- Firewall methodologies
- Zone-based firewall Configuration
- How to setup firewall in Linux?
- Types of firewall and possible attacks
- Difference between Firewall and Antivirus
- Difference between Router and Firewall
- Difference between Firewall and Proxy Server
- EPC Gen 2 Physical Layer
- Cyber Security - Types of Enumeration
- Tag identification Message formats
- Difference between SONET and SDH
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.