It can be a single device or a combination of systems that is capable of supervising the FLOW of traffic between distinctive parts of your network. A good firewall is capable of protecting your systems and network from external threats, but also from the internal threats. Of course, you need protection at each level of the hierarchy of your networking systems.
This post is intended to look at Firewalls from basic implementation perspective.
Why is basic Firewall Configuration so important?
Gartner highlighted the size and magnitude of this issue, predicting that 99% of firewall breaches would be caused by misconfigurations in 2020 (and onwards).
How To Configure A Firewall Properly?
1. Secure the Firewall itself
-
Update with the latest firmware
-
Never putting firewalls into production without appropriate configurations in place
-
Deleting, disabling, or renaming default accounts and changing default passwords
-
Use unique, long and secure passwords
-
Never using shared user-accounts. If a firewall will be managed by multiple administrators, additional admin accounts must have limited privileges based on individual responsibilities. Remember, the Zero Trust!
-
Track who made what changes and why. Accountability promotes due diligence in making changes.
-
Limit where people can make changes from to reduce your attack surface, i.e., changes can only be made from trusted subnets within your corporation.
-
Disabling the Simple Network Management Protocol (SNMP), which collects and organizes information about devices on IP networks, or configuring it for secure usage
-
Restricting outgoing and incoming network traffic for specific applications or the Transmission Control Protocol (TCP)
2. Creating Zones
A general rule is that the more zones created, the more secure the network is. You may not want to expose the other network zones to users of another zone. However, having more zones also demands more time to manage them.
-
Link to the Internet, assigned with the lowest-level of security.
-
A link to DMZ assigned a medium-security because of the presence of servers.
-
A link to the organization, situated at the remote end, assigned medium-security.
-
The highest-security is assigned to the internal network.
General Rules to guide you are the followings:
-
Internal devices to DMZ, remote organization, and the internet.
-
DMZ to the remote organization and the internet.
3. Configure ACLs
Access control lists (ACLs) would enable your organizations to determine WHICH traffic is allowed to flow in and out of each zone. ACLs act as firewall rules, which organizations can apply to each firewall interface and sub-interface.
-
ACLs must be made specific to the exact source and destination port numbers and IP addresses.
-
Each ACL should have a “deny all” rule created at the end of it, which enables organizations to filter out unapproved traffic.
-
Each interface and sub-interface also needs an inbound and outbound ACL to ensure only approved traffic can reach each zone.
-
It is also advisable to disable firewall administration interfaces from public access to protect the configuration and disable unencrypted firewall management protocols.
4. Configure Other Firewall Services and Logging
-
Can it block traffic based on web categories?
-
Can you turn on advanced scanning of files?
-
Does it contain some level of IPS functionality.
However, you must never forget to configure your firewall to report to a LOGGING Service, otherwise you will fail to comply with the 'Requirement #10' of PCI-DSS or other regulations.
5. Test the Firewall Configuration
You should always test your firewall configuration, before you place your firewall in production-environments. If everything checks out, your firewall is ready for production.
Some Designing Facts To Help You
-
A Packet-filtering firewall should be used at the boundary of the network to give enhanced security.
-
Every server having exposure to a public network such as the Internet will be placed in DMZ. Servers having crucial data will be equipped with host-based firewall software within them. In addition to these on servers, all unwanted services should be disabled.
-
If your network is having critical database servers such as HLR server, IN, and SGSN which is used in mobile operations, then multiple DMZ will be deployed.
-
If external sources such as far-end organizations want to access your server placed in an internal network of security system then use VPN.
-
For crucial internal sources, such as R&D or financial sources, IDS should be used to monitor and deal with internal attacks. By imposing levels of security separately, extra security can be provided to the internal network.
-
For e-mail services, all outgoing emails should be pass through the DMZ e-mail server firstly and then some extra security software so that internal threats can be avoided.
-
For incoming e-mail, in addition to the DMZ server, antivirus, spam, and host-based software should be installed and run on the server every time a mail enters the server.
Continuous Monitoring
This Article Was Written & published by Meena R, Senior Manager - IT, at Luminis Consulting Services Pvt. Ltd, India.
Over the past 16 years, Meena has built a following of IT professionals, particularly in Cybersecurity, Cisco Technologies, and Networking...
She is so obsessed with Cybersecurity domain that she is going out of her way and sharing hugely valuable posts and writings about Cybersecurity on website, and social media platforms.
34,000+ professionals are following her on Facebook and mesmerized by the quality of content of her posts on Facebook.
If you haven't yet been touched by her enthusiastic work of sharing quality info about Cybersecurity, then you can follow her on Facebook:
Click Here to follow her: Cybersecurity PRISM