In many offices, factories and hospitals, the firewall was configured properly once and then changed one request at a time. A vendor needed remote access for a project. A CCTV contractor needed a port opened. Someone added a broad rule to fix an urgent problem on a Saturday. Each change made sense at the time; years later, the rule base allows paths nobody intended and nobody can explain.
A firewall audit compares the rules you have with what the business needs today. This checklist covers the rule base, management access, VPN, segmentation and logging, then explains how to clean up safely. For how attackers test the network itself, see our network penetration testing guide.
Quick answer: A firewall audit confirms that every rule has a business reason, an owner and the narrowest possible source, destination and port. It removes any-any, unused, shadowed and expired rules, keeps management interfaces off the internet, enforces MFA and clean accounts on the VPN, checks segmentation between guest, device, office and server networks, and confirms logging and firmware are current.
Rule base checklist
Start by exporting the configuration of every firewall, including both units of a high-availability pair, along with rule hit counts for a period long enough to include month-end and other busy cycles. Then work through these checks.
| Check | What to look for | Usual fix |
|---|---|---|
| Any-any rules | Source, destination or service set to any | Replace with specific hosts and ports, or remove |
| Inbound from the internet | Services published to the LAN rather than a DMZ | Publish only what is needed, from a separate zone |
| Unused rules | Zero hits over the review period | Disable first, delete after an observation period |
| Shadowed or duplicate rules | Rules that never match because a broader rule above catches the traffic | Reorder, merge or remove |
| Temporary and vendor rules | No owner, no ticket, no end date | Add an owner and expiry, or remove |
| Wide port ranges | Large ranges or all services allowed to servers | Limit to the ports the application uses |
| Unrestricted outbound | Servers allowed to reach any internet address | Allow only updates and known services |
| Logging | Important allow and deny rules not logged | Enable logging and send it to central storage |
Outbound rules deserve attention. Malware on a server usually needs to call out, and a server that can only reach its update sources is much harder to misuse.
Management access and firmware
Firewalls and VPN gateways are attractive targets because they sit on the edge of the network. CERT-In and vendors regularly publish advisories about vulnerabilities in these products, so treat the device itself as part of the audit.
- Admin interface: web and SSH management should not be reachable from the internet. Limit it to a management network or specific admin IPs.
- Admin accounts: one named account per administrator, MFA where the device supports it, default accounts disabled and no shared passwords.
- Firmware: the model and version should still receive security updates. Note the vendor's end-of-support date in your asset register.
- Configuration backups: stored securely, off the device, and tested.
- Time and logs: correct time sync so logs can be matched to other systems during an investigation.
On logs, CERT-In's directions of April 2022 ask covered organisations to keep logs of their ICT systems for a rolling 180 days within India. Check the current text on the CERT-In website to confirm how it applies to you.
VPN and remote access
Remote access is where old accounts and broad permissions pile up fastest. Review it with HR and vendor lists in hand.
- Accounts: disable leavers and accounts that have not logged in for months. Every account should belong to one named person.
- MFA: require it for every VPN user, including senior staff and IT administrators.
- Vendors: give each vendor a separate account that reaches only their system, and enable it only for agreed periods.
- Access by group: finance users should reach finance systems, not the whole LAN. A flat VPN that lands everyone on the internal network turns one stolen password into full access.
- Legacy protocols: retire old options such as PPTP and outdated portals that are no longer patched.
- Split tunnelling: decide on it deliberately and document the reason.
Segmentation checks
Segmentation limits how far an attacker can move after getting in. Check that these boundaries exist and are enforced by firewall rules, not just by separate Wi-Fi names:
- Guest Wi-Fi reaches the internet only, never internal systems.
- CCTV, biometric devices and other IoT sit on their own network with no route to servers or office PCs.
- Factory or medical device networks are separated from the office network, with only specific, documented flows between them.
- Servers accept connections only on the ports their applications need.
- Backup systems are isolated, so ransomware on an office PC cannot reach them. Our backup and disaster recovery team can help design this.
Reading the configuration tells you what should happen. Only testing from each network tells you what actually happens, which is where network VAPT comes in.
Cleaning up without breaking the business
Firewall clean-up fails when a rule is deleted on Friday and payroll stops working on Monday. A careful sequence avoids that:
- Back up the current configuration and confirm you can restore it.
- Classify every rule as keep, tighten, disable or remove, with the owner's agreement.
- Disable rules before deleting them, and watch for complaints and denied traffic over a full business cycle.
- Make changes in an agreed change window with a written rollback plan.
- Tell the helpdesk what changed, so connection problems are traced quickly.
- Record the owner, reason and review date for every rule you keep.
- Test again from outside and inside to confirm the paths are really closed.
NIST's guidance on firewall policy, SP 800-41 Revision 1, is a useful reference for writing and reviewing the policy itself.
How EthicsComputer can help
Our network VAPT and firewall audit reviews your rule base for any-any, unused and shadowed rules, assesses VPN configuration and account hygiene, and tests your external and internal networks to show which paths are open in practice. Most assessments typically take 5 to 15 working days. If you want help implementing the clean-up, our IT infrastructure and network security team can plan and carry out the changes.
When was your firewall rule base last reviewed line by line?
Tell us about your firewalls, sites and remote users, and we will propose an audit and test scope that fits your network.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.