EvidenceSheet

8.3 Information access restriction

Requires access to information and other associated assets to be restricted in accordance with the established topic specific policy on access control.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Evidence of restriction on functions as well as data, including read against write against delete and export · Identity provider / directory

periodic reviewEvidence produced at each review

  • Evidence of controls over dynamic access such as reporting tools and direct query access · Identity provider / directory
  • Records of testing that the restriction actually holds, such as access testing results · Identity provider / directory

governing documentDocuments that govern the control

  • Evidence access to information is restricted per the access control policy, sampled at the system and data level rather than only at the network level · Policy repository / GRC workspace
  • Configuration of the restriction mechanisms, such as application roles, database permissions, file share permissions and cloud storage policies · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

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

8.2 Privileged access rights · 8.4 Access to source code