Firewall configuration documentation that explains every rule — OC Security Audit
Firewall configuration documentation

Firewall configuration documentation that explains every rule

Each rule with a business reason, an owner and a review date, plus NAT, VPN, IPS, management access, firmware and configuration backups, in one record.

Know exactly what changed on the firewall, and when — OC Security Audit
Backups and diffs

Know exactly what changed on the firewall, and when

A known-good golden configuration, scheduled backups and a before-and-after diff for every change make troubleshooting and restores fast.

Rule reviews an auditor can follow from start to finish — OC Security Audit
Rule reviews

Rule reviews an auditor can follow from start to finish

PCI DSS asks for approved changes and a business need for every allowed service. A rule register gives you the record to show it.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote documentation & audits
Why it matters

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.

Two engineers reviewing firewall rules on a laptop in a server room
The rule base

What firewall configuration documentation records for each rule

The configuration file says what a rule does. The register says why it exists.

FieldWhat to recordWhy it matters
Rule ID and positionThe rule name or number and where it sits in the policy orderOrder decides which rule wins
Source, destination, serviceZones, address objects and ports in plain language, not only object namesA manager can read what is allowed
Action and loggingAllow or deny, and whether hits are loggedLogs are evidence the rule is used, or not
Business justificationThe system or business process that needs the rulePCI DSS Req. 1.2.5 expects a defined business need for every allowed service
OwnerThe person or role who can confirm the rule is still neededSomeone answers at review time
Change recordTicket that requested and approved the rule, with dateLinks the rule to approval under change control
Expiry or review dateEnd date for temporary rules; next review date for the restTemporary vendor access does not become permanent
Sample

Sample rule-justification register: Harborview Dental Group

An extract for FW-HQ-01. Names, tickets and dates are fictional.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
RuleFrom → ToServiceActionBusiness justificationOwnerChangeReview
FW-R-010Clinical VLAN 10 → SRV-PM-01Practice-management app portsAllow · logOperatory PCs open patient chartsOffice managerCHG-0098Mar 2027
FW-R-020Clinical VLAN 10 → NAS-BK-01AnyDeny · logWorkstations never write to backups directlyITCHG-0098Mar 2027
FW-R-030Guest VLAN 40 → internal VLANsAnyDeny · logGuest Wi-Fi is internet onlyITCHG-0104Mar 2027
FW-R-044Vendor remote access → SRV-PM-01Remote support over VPN with MFAAllow · logSoftware vendor support sessionsOffice managerCHG-0131Expires Dec 2026
FW-R-055Any → AnyAnyAllowNone foundNoneNoneFlagged: remove after review
NAT 1Public IP 2 → SRV-PM-01HTTPSPort forwardNone found; vendor portal moved to cloudNoneNoneFlagged: 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.

Beyond the rules

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.

01

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.

02

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.

03

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.

04

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.

05

Firmware and support

Current version, the vendor’s recommended release, support and license expiry dates, and high-availability pairing if used.

06

Golden configuration

A reviewed, known-good baseline configuration stored safely offline, used to rebuild a failed unit and to compare against the running configuration.

Backups and diffs

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.

Request

Ticket with the business reason and owner

Approve

Risk noted, approver named

Back up

Configuration saved before the change

Change

Made by your IT team or MSP

Diff and test

Before-and-after diff, test result attached

Update records

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.

Review cadence

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.

How we help

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.

Network engineers checking firewall configuration in a data center
Related

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.

Ali Hassani, CISO, OC Security Audit
CISO-led

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.

FAQ

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.

IT Perfection managed IT
Two IT specialists reviewing who can access documentation in a data center

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.