AC.L2-3.1.2 Transaction & Function Control
Confine each authorized user to the specific transactions and functions their role permits, so privileges bound what can be executed and not merely whether access is granted.
4
artefacts
0
held by a system
2
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
- Approval records for role assignment per user · Identity provider / directory
- Evidence of enforcement testing on a restricted role · Identity provider / directory
governing documentDocuments that govern the control
- Role definitions mapping roles to permitted transactions and functions · Policy repository / GRC workspace
- Application and system permission matrices as configured · 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
- Access granted at system level with no function-level restriction
- Roles defined on paper but not enforced in the application
- Broad default roles assigned for convenience
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 sheetAC.L2-3.1.1 Authorized Access Control · AC.L2-3.1.3 Control CUI Flow