IVS-03 Network Security
Restrict traffic between environments to authenticated and authorised connections, encrypt and monitor it, and review the configuration at least annually with a written justification for every allowed service, protocol,
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Evidence of encryption and monitoring on inter-environment traffic · SIEM / log platform
periodic reviewEvidence produced at each review
- Annual review record of the rule set · Cloud console / configuration management
governing documentDocuments that govern the control
- Firewall and network policy rule sets between environments · Policy repository / GRC workspace
- The written business justification for each allowed service, protocol and port · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Rules accumulated over years with no justification recorded
- Any to any rules left in place from a migration
- Annual review performed on the perimeter only, not between internal environments
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 sheetIVS-02 Capacity and Resource Planning · IVS-04 OS Hardening and Base Controls