SEC03-BP01 Define access requirements
Document who or what requires access to each resource, what actions are permitted and under what conditions, so least privilege policies can be designed and validated against intent.
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 requirements matrix per workload · Policy repository / GRC workspace
- Role catalogue · Policy repository / GRC workspace
- Data classification mapping to roles · 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
- no documented access intent
- policies built ad hoc
- no link from requirement to policy
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 sheetSEC02-BP06 Employ user groups and attributes · SEC03-BP02 Grant least privilege access