CC6.2 Prior to granting access, registration and authorization processes are established
Prior to issuing system credentials and granting system access, the entity registers and authorizes new internal and external users whose access is administered by the entity. For those users whose access is administered.
5
artefacts
0
held by a system
4
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
none for this control
periodic reviewEvidence produced at each review
- Authorisation records for users provisioned in the period, showing the requester, the approver and the access requested · Identity provider / directory
- Evidence credentials were issued only after authorisation, with dates supporting the sequence · Identity provider / directory
- Evidence of removal of access when access is no longer authorised, with the interval between the trigger and the removal · Identity provider / directory
- Evidence covering users whose access is administered by the entity on behalf of a customer, where that applies · Identity provider / directory
governing documentDocuments that govern the control
- The registration and authorisation procedure that must complete before credentials are issued, for internal and external users · 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 first and approved retrospectively, which reverses the order the criterion requires
- Approval by the requester's peer or by the person implementing the change, so no independent authorisation exists
- External and customer administered users provisioned through a different route with no equivalent authorisation record
- Removal triggered by a manual notification that is sometimes not sent, so leavers retain credentials
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 sheetCC6.1 Implements logical access security software, infrastructure and architectures over protected information assets · CC6.3 Role-based access and least privilege are enforced