Start where an access mistake would interrupt daily work: for example, the shared scheduling system that staff use to serve customers. Have the responsible manager confirm the scope and who can authorize changes. Download the blank access review register (CSV) to record decisions internally.
Who should be on the approved list?
Ask the business owner which roles need the system today. Include contractors, temporary staff and shared service accounts. For an account used by software, record a human owner and what depends on it. Collect only what the review needs; passwords, recovery codes and private customer records do not belong in the register.
What does one review decision look like?
Illustrative example: an old contractor role is still listed as a scheduling editor after the assignment ended. The scheduling manager confirms the role is no longer needed; the application owner records the approved change. An account that runs reminders would need a different decision: check the dependency before changing it.
Use one row per decision. Record the system, account reference, expected role, observed role, action, owner and due date. Include a reason and review date for any time-limited exception.
When is a finding closed?
After the authorized owner completes the change, have a second person compare the current membership and permissions with the approved decision. Record the check date and a reference to the evidence held in the business’s own system. An assigned ticket or a promise to remove access is still an open finding.
The studio’s example closure record shows this distinction. For the underlying account-management objective, see CIS Control 5: Account Management.
What triggers the next review?
Agree a review date with the owner and a separate trigger for staff departures, role changes and vendor changes. Keep unresolved items with named owners between reviews. This worksheet supports a scoped defensive review; it is not a certification or a substitute for an assessor where one is required.
