FW.4 Approve and Document Inbound Rules
Every inbound firewall rule that permits traffic must be approved and documented by an authorised individual with documented business need.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Firewall change tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Approval workflow evidence · Document repository
governing documentDocuments that govern the control
- Rule register with owner/justification · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- legacy rules with no owner
- any-any rules retained
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetFW.3 Block Unauthenticated Inbound Connections · FW.5 Remove or Disable Unused Rules