A firewall is only as clear as the notes behind its rules
Firewall configuration documentation records what your firewall allows, why, and who asked for it: the rule base with a business justification for each rule, NAT, remote-access VPN, intrusion prevention profiles, management access, firmware versions and the configuration backups that let you restore it.
Most rule bases grow one ticket at a time. Years later nobody knows whether the rule for an old vendor can go, which port forward still serves a real system, or why a broad allow sits near the top. Without notes, every cleanup is risky, so nobody cleans up. Documentation turns the rule base back into something your team can manage.
This page is vendor-neutral and covers next-generation firewalls and other network security controls alike. It connects to the network documentation, the IP address plan and the WAN circuit register.

What firewall configuration documentation records for each rule
The configuration file says what a rule does. The register says why it exists.
| Field | What to record | Why it matters |
|---|---|---|
| Rule ID and position | The rule name or number and where it sits in the policy order | Order decides which rule wins |
| Source, destination, service | Zones, address objects and ports in plain language, not only object names | A manager can read what is allowed |
| Action and logging | Allow or deny, and whether hits are logged | Logs are evidence the rule is used, or not |
| Business justification | The system or business process that needs the rule | PCI DSS Req. 1.2.5 expects a defined business need for every allowed service |
| Owner | The person or role who can confirm the rule is still needed | Someone answers at review time |
| Change record | Ticket that requested and approved the rule, with date | Links the rule to approval under change control |
| Expiry or review date | End date for temporary rules; next review date for the rest | Temporary vendor access does not become permanent |
Sample rule-justification register: Harborview Dental Group
An extract for FW-HQ-01. Names, tickets and dates are fictional.
| Rule | From → To | Service | Action | Business justification | Owner | Change | Review |
|---|---|---|---|---|---|---|---|
| FW-R-010 | Clinical VLAN 10 → SRV-PM-01 | Practice-management app ports | Allow · log | Operatory PCs open patient charts | Office manager | CHG-0098 | Mar 2027 |
| FW-R-020 | Clinical VLAN 10 → NAS-BK-01 | Any | Deny · log | Workstations never write to backups directly | IT | CHG-0098 | Mar 2027 |
| FW-R-030 | Guest VLAN 40 → internal VLANs | Any | Deny · log | Guest Wi-Fi is internet only | IT | CHG-0104 | Mar 2027 |
| FW-R-044 | Vendor remote access → SRV-PM-01 | Remote support over VPN with MFA | Allow · log | Software vendor support sessions | Office manager | CHG-0131 | Expires Dec 2026 |
| FW-R-055 | Any → Any | Any | Allow | None found | None | None | Flagged: remove after review |
| NAT 1 | Public IP 2 → SRV-PM-01 | HTTPS | Port forward | None found; vendor portal moved to cloud | None | None | Flagged: confirm and remove |
The two flagged rows are the kind of finding the register exposes on day one: rules with no reason and no owner that nobody felt safe removing.
The rest of the firewall configuration to document
Rules are only part of the picture. These settings decide who can reach the firewall and how it behaves.
NAT
Each port forward and one-to-one NAT with the public IP, internal host and service, plus outbound NAT for each network. Cross-check against the public IPs in the circuit register.
Remote-access VPN
VPN type, the identity source (for example Entra ID or Active Directory), MFA method, who is allowed to connect, split or full tunnel, and the address pool handed to clients.
IDS/IPS and filtering
Which intrusion prevention, malware and web-filtering profiles apply to which rules, whether they block or only alert, and when signatures last updated.
Management-plane access
Which interfaces and source networks can reach the admin console, SSH and SNMP, admin accounts and roles, MFA on admin sign-in, and where logs are sent.
Firmware and support
Current version, the vendor’s recommended release, support and license expiry dates, and high-availability pairing if used.
Golden configuration
A reviewed, known-good baseline configuration stored safely offline, used to rebuild a failed unit and to compare against the running configuration.
How every firewall change leaves a record
PCI DSS Req. 1.2.2 expects changes to network connections and security-control configurations to be approved and managed under change control. This is the record trail we document.
Ticket with the business reason and owner
Risk noted, approver named
Configuration saved before the change
Made by your IT team or MSP
Before-and-after diff, test result attached
Register, diagram and change log updated
Configuration backup tools such as Oxidized, Unimus, RANCID or SolarWinds NCM can save router, switch and firewall configurations on a schedule; they do not capture cloud network settings, which need their own records. More on these tools on the configuration backup and change tools page, and on the full change process on IT change management.
Set a rule review cadence and keep the evidence
Documentation makes reviews quick. Without it, reviews stall on the first rule nobody recognizes.
PCI DSS v4.0.1 asks that configurations of network security controls be reviewed at least once every six months to confirm they are relevant and effective (Req. 1.2.7), that all allowed services, protocols and ports have a defined business need (Req. 1.2.5), and that the network diagram stays accurate (Req. 1.2.3). Even outside card-data environments, that six-month rhythm is a sensible baseline for most small and mid-sized businesses.
At each review, the owner confirms or retires each rule, temporary rules past their expiry are removed through a change record, and the review itself is dated and signed off. Keep the before-and-after configuration diff with the review record so an auditor can see what changed.
If you work with card data, our PCI DSS readiness service shows how these records fit into an assessment. For HIPAA, ISO 27001 and other frameworks, see IT documentation for compliance.
Firewall records reviewed or built, without touching the firewall
In the IT Documentation Audit we compare your rule records, backups and change history with a read-only export of the running configuration and list every gap. In the IT Documentation Build we create the rule-justification register, NAT and VPN records and backup log with your team. Each is $3,500 fixed, one-time, as shown on the IT documentation pricing page.
For a security assessment of the firewall itself, see our firewall security audit; for Cisco devices, the Cisco configuration backup service. We work on-site across Orange County and Southern California from Irvine, and remotely nationwide. Rule cleanup itself can be handled by IT Perfection.

Where to go next
IT change management
The request, risk, approval, test, rollback and diff record behind every firewall change.
Configuration backup and change tools
How device-level backup tools, mapping tools and cloud configuration exports fit together.
Page 7 of 22: Firewall and network settings documentation
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation
- 6. WAN and ISP circuit documentation
- 7. Firewall and network settings documentation (this page)
- 8. Cloud documentation: Microsoft 365, Azure, AWS
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management
- 13. Runbooks and disaster-recovery documentation
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali reads each rule with its owner in plain language, so the register reflects how the business actually uses the network.
Questions about firewall configuration documentation
Isn’t the firewall’s own configuration file enough documentation?
The configuration shows what each rule does, not why it exists, who owns it or when it should be reviewed. Those answers live in the rule register and change records.
Do you need write access to our firewall?
No. We work from read-only accounts and configuration exports. Your team or MSP stays in control, and we never change a rule.
What is a golden configuration?
It is a reviewed, known-good baseline of the firewall’s settings, stored safely. It lets you rebuild a failed unit quickly and spot drift by comparing it with the running configuration.
How often should firewall rules be reviewed?
PCI DSS v4.0.1 Req. 1.2.7 sets at least once every six months for in-scope network security controls. Using the same cadence for every firewall, plus a review after any major change, is a sensible baseline.
Do you document firewalls from any vendor?
Yes. The documentation format is vendor-neutral. For Cisco environments we also offer a dedicated configuration backup service.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

Know why every firewall rule exists
Tell us how many firewalls and sites you have. Schedule a consultation and we will scope the work on a 30-minute call.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


