Compliance
Firewall Audit Checklist for ISO 27001 Compliance: What Auditors Check

A firewall audit checklist covers eight areas: the rulebase (every rule has an owner, a business reason and a review date), change records, administrator access, logging, configuration backups, network segmentation, firmware currency, and the review cadence that keeps the rest current. For ISO 27001 compliance, each area maps to an Annex A control, mostly 8.20 Networks security, 8.32 Change management and 8.15 Logging. The checklist below works on any vendor; the control-by-control detail for ISO 27001 follows it.
Certification auditors look at the firewall estate in every surveillance and recertification audit. Most teams prepare by reading the whole Annex A control set. You get further by preparing the records an auditor will ask you to open, which is what this page lists.
What Goes on a Firewall Audit Checklist?
A vendor-neutral firewall audit checklist asks one question per area: can you show a record that proves the control works? The table lists the check, the evidence an auditor accepts, and the matching ISO/IEC 27001:2022 Annex A control. If you audit against PCI DSS, NIS2 or an internal policy instead, keep the first three columns and swap the last one.
| Area | What to check | Evidence | ISO 27001:2022 Annex A |
|---|---|---|---|
| Rulebase | Every rule has an owner, a business reason and a ticket reference; no undocumented any-to-any rules; unused and shadowed rules flagged | Rule export with owner and ticket columns, last-hit report | 8.20 Networks security |
| Change records | Each change traces from request to approval, implementation and verification; emergency changes reviewed afterwards | Change tickets matched to the firewall's own config log | 8.32 Change management |
| Admin access | Named accounts only, MFA on management access, admin list reviewed and leavers removed | Admin account list, last access review with sign-off | 8.2 Privileged access rights, 5.15 Access control, 5.18 Access rights |
| Logging | Traffic logs and admin/config logs leave the box, are retained for the period your policy sets, and someone watches them | Log forwarding config, SIEM retention setting, sample alert | 8.15 Logging, 8.16 Monitoring activities |
| Config backups | Scheduled off-device backups, an approved baseline, and a restore that was actually tested | Backup job history, last restore test, baseline diff | 8.13 Information backup, 8.9 Configuration management |
| Segmentation | Zones match the network diagram; inter-zone rules enforce the design; segmentation is tested | Current diagram, zone-to-zone rule matrix, test result | 8.22 Segregation of networks |
| Firmware | Every firewall runs a supported release; open vendor advisories tracked to closure | Inventory with versions, advisory tracker | 8.8 Management of technical vulnerabilities |
| Review cadence | Rule reviews happen at the frequency the policy sets, with findings tracked and a named approver | Recertification reports with dates and sign-off | 5.36 Compliance with policies, rules and standards for information security |
In our experience the log entry and the ticket usually both exist. The finding comes from the missing link between them: a rule changed on Tuesday, a ticket approved on Thursday, and nothing that ties the two together. A firewall rule audit before the certification audit is where you find those gaps, and retiring the rules nobody owns removes most of the rulebase findings before an auditor sees them.
Vendor Notes: Where Each Firewall Keeps the Evidence
Every major vendor already records most of what the checklist asks for. The audit question is whether you can export it and match it to a ticket. A Check Point firewall audit checklist and a Palo Alto one cover the same eight areas; only the place you pull the records from changes.
- Check Point: in SmartConsole, Manage & Settings > Revisions shows the history of published changes. Each revision is a restore point that holds only the changes since the previous one, and the bottom pane shows the audit logs for that revision. That gives you change records and a rollback point in one place.
- Palo Alto Networks: PAN-OS config logs record the date and time, the administrator username, the source IP, the client type (Web, CLI or Panorama), the command, whether it succeeded, the configuration path and the values before and after the change. Pull the entries for each sampled change and attach them to the ticket.
- Fortinet: FortiGate can create a configuration revision every time an administrator logs out (
config system global,set revision-backup-on-logout enable), andexecute revision list configlists the stored revisions, per a Fortinet technical tip. Those revisions serve as both backup evidence and a before/after record. - Cisco: Secure Firewall Management Center records user activity in read-only audit logs. From version 7.4.0 it can stream configuration changes to syslog as part of the audit data (System > Configuration > Audit Log > Send Audit Log to Syslog), which gets them into the same SIEM as your other evidence.
Running more than one of these brands makes the matching harder, because each one exports a different format. That is the case for a single change record across vendors, covered in multi-vendor firewall management.
Why Are Firewalls Central to ISO 27001 Compliance?
Firewalls sit at the intersection of multiple Annex A control domains: network security, access control, change management, logging, and incident response. A single firewall touches controls from at least four different categories. This makes the firewall one of the most frequently examined assets during an ISO 27001 audit.
Auditors know this, so expect a dedicated block of the audit for firewall controls, longer at initial certification than at a surveillance visit. They will ask to see configurations, change logs, approval records, review evidence, and access control lists. Being prepared for these requests is the difference between a clean audit and a corrective action plan.
Which ISO 27001 Annex A Controls Apply to Firewalls?
The following controls from ISO 27001:2022 Annex A directly affect firewall management. For each control, we list what auditors look for and what evidence you need.
1. A.8.20, Networks Security
This is the primary firewall control. Auditors verify that network services, including firewalls, are identified, documented, and managed with defined security requirements. They want to see a network security architecture document that shows where firewalls are deployed, what they protect, and how they are configured at a high level.
Evidence Required
- Network diagram showing all firewall placements and trust zones
- Firewall inventory with vendor, model, firmware version, and responsible team
- Security requirements document defining what each firewall must enforce
2. A.8.21, Security of Network Services
This control extends A.8.20 to cover managed services and third-party network security. If you use managed firewall services, cloud security groups, or SASE platforms, auditors will check that service level agreements include security requirements and that you have visibility into the configurations managed by third parties.
3. A.8.22, Segregation of Networks
Network segmentation is one of the most closely examined controls. Auditors verify that different security domains (production, development, DMZ, management) are separated by firewalls with appropriate rules. They will ask to see specific rules that enforce segmentation and may request evidence that segmentation is tested periodically. If different segments run different firewall brands, the vendor notes above tell you where each one keeps its records.
4. A.5.1, Policies for Information Security
Auditors expect a documented firewall management policy that covers rule creation, modification, deletion, review, and emergency changes. This policy should reference the organization's overall information security policy and define roles, responsibilities, and escalation procedures for firewall management.
5. A.8.9, Configuration Management
This control requires that firewall configurations are managed through a defined process. Auditors check that configurations are baselined, changes are tracked, and there is a process to detect unauthorized modifications. This is where policy drift detection becomes essential, it provides continuous evidence that configurations match their approved baselines.
6. A.8.32, Change Management
The change management control is where most audit findings occur. Auditors will select a sample of firewall changes from the past 12 months and trace each one through the full change management workflow: request, risk assessment, approval, implementation, and verification. If any step is missing from even one sampled change, the auditor can raise a nonconformity.
What Auditors Typically Sample, in Our Experience
- 3-5 standard changes from the past 12 months (full workflow trace)
- 1-2 emergency changes (retroactive documentation and review)
- 1 denied/rejected change (proves the approval process has teeth)
7. A.5.15, Access Control
Auditors verify that access to firewall management interfaces is restricted to authorized personnel only. This means documented access control lists for who can log into each firewall, multi-factor authentication for management access, and evidence that access reviews are performed at the interval your policy sets. Shared accounts or generic “admin” credentials are an immediate finding.
8. A.8.15, Logging
Firewall logging must cover both traffic logs (what the firewall permitted and denied) and management logs (who logged in, what they changed, when). Auditors check that logs are sent to a centralized system, retained for the period defined in your policy, and protected from tampering. They may ask to see specific log entries for sampled changes.
9. A.8.16, Monitoring Activities
Beyond logging, auditors want evidence that firewall events are actively monitored. This includes alerts for failed authentication attempts, configuration changes outside of approved windows, and traffic anomalies. If you have a SIEM integration, be prepared to show the alert rules and escalation procedures.
10. A.8.8, Management of Technical Vulnerabilities
This control covers firewall firmware patching and vulnerability scanning. Auditors check that firewalls are on supported firmware versions, that known vulnerabilities are tracked and remediated within defined timelines, and that the vulnerability management process covers network infrastructure (not just servers and endpoints).
11. A.5.36, Compliance with Policies, Rules and Standards
Auditors verify that regular reviews confirm firewall configurations comply with documented policies. This is the rule recertification control. Evidence must show that rule reviews happen at the frequency defined in your policy, that findings are tracked to resolution, and that someone with appropriate authority signs off on the review.
12. A.5.24, Information Security Incident Management Planning and Preparation
Firewall-related incidents must be handled through the incident management process. Auditors may ask for examples of firewall incidents (blocked attacks, misconfigurations causing outages, unauthorized changes) and how they were detected, responded to, and documented. This connects to your emergency change procedures.
Top 5 Audit Failures and How to Avoid Them
| Finding | Control | Prevention |
|---|---|---|
| Missing change approval for sampled rule | A.8.32 | Automated change workflow that blocks unapproved changes |
| No evidence of periodic rule review | A.5.36 | Scheduled recertification with sign-off records |
| Shared firewall admin credentials | A.5.15 | Individual accounts with MFA, annual access reviews |
| Firewall logs not centrally collected | A.8.15 | SIEM integration with 12-month retention |
| Outdated network diagram | A.8.20 | Quarterly diagram reviews, auto-generated topology maps |
Audit Preparation Timeline
Start preparing at least 8 weeks before your audit date. Here is a suggested timeline:
- 8 weeks before: Run a full firewall rule audit across all firewalls. Identify and remediate findings.
- 6 weeks before: Complete any overdue rule recertifications. Verify all changes from the past 12 months have full documentation.
- 4 weeks before: Update network diagrams and firewall inventory. Verify firmware versions are current and supported.
- 2 weeks before: Conduct a mock audit. Sample 5 random changes and trace them through the full workflow. Fix any gaps.
- 1 week before: Prepare evidence packages: change logs, approval records, review reports, access lists, log retention evidence.
Frequently Asked Questions
How many firewall changes will the auditor sample?
In our experience, typically 3-5 standard changes and 1-2 emergency changes from the past 12 months. Auditors may also ask for a denied change to verify the approval process works in both directions. For organizations with high change volumes, the sample size may increase to 8-10. The auditor selects the sample, you do not get to choose which changes are reviewed.
Do we need to document every single firewall rule?
ISO 27001 does not explicitly require documentation for every rule, but it does require that rules can be traced to a business justification and that the change that created them went through the change management process. In practice, this means every rule should have an associated change request. Legacy rules that predate your ISMS should be covered by a baseline review.
What is the difference between ISO 27001 and TISAX firewall requirements?
TISAX assessments use the VDA Information Security Assessment (ISA) catalogue, and the resulting labels cover objectives such as information security, data protection or prototype protection, per ENX, which runs TISAX. In our experience, a firewall setup that passes ISO 27001 already covers most of what a TISAX assessment asks about firewalls; the extra work sits in the automotive-specific items.
Does ISO 27001 help with SOC 2 Type II?
Yes. In our experience, much of the ISO 27001 evidence (change records, access reviews, logging) can be reused for SOC 2, so an existing certification gives a SOC 2 program a head start. If you also sell into the US market, see SOC 2 Type II for European companies.
How often should firewall rules be reviewed for ISO 27001?
The standard does not prescribe a specific frequency. In our view, quarterly for high-risk firewalls (internet-facing, DMZ) and every six months for internal firewalls is a sensible default. Whatever frequency you define in your policy, you must demonstrate adherence. If you also work to BSI IT-Grundschutz, check its requirements for your review cycle as well.
Check Where You Stand Before the Auditor Does
Ten questions, a few minutes, and a clear view of the gaps in your firewall governance.
Run the free NIS2 readiness check →

