6.6.1 Business requirements of access control
The access control policy and the rules for access to networks and network services apply as the base guidance requires, read as governing access to personal data.
3
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Access control policy referencing personal data as a governed class · Policy repository / GRC workspace
- Network and service access rules · Policy repository / GRC workspace
- Evidence the policy drives actual entitlement design · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Policy written at the level of systems, so personal data access is inherited rather than granted
- Network access rules that permit broad internal reachability to data stores
- Policy and implemented entitlements never reconciled
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 sheet