IAM-16 Authorization Mechanisms
Check that each access to data and system functions is authorised, not merely authenticated.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
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
- Evidence authorisation is enforced server side rather than in the interface · Cloud console / configuration management
- Testing evidence covering authorisation bypass · Document repository
- Evaluation records for the authorisation mechanism · Document repository
governing documentDocuments that govern the control
- Authorisation model documentation per application and platform · Document repository
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
- Authentication treated as sufficient, with any authenticated user able to reach any function
- Authorisation enforced in the user interface only
- No testing for horizontal or vertical privilege escalation
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 sheetIAM-15 Passwords Management · IPY-01 Interoperability and Portability Policy and Procedures