Boards at SAMA-regulated institutions are asking more precise questions about who holds privileged access and how that access is controlled. This article sets out the SAMA CSF identity governance privileged access metrics that a quarterly board report should carry, and a detection method that shows your joiner-mover-leaver process runs on a weekly cycle rather than only on paper.
A note on scope. The SAMA Cyber Security Framework covers identity and access management within its access-control requirements. Where a circular amendment or regulator communication has changed your obligations, confirm the exact wording and control references with your compliance function before you finalise the report. The metrics below are our recommended way to evidence those expectations; they are not a quotation of the regulation.
Why the board report needs to change
Most quarterly cybersecurity reports describe activity: policies approved, tools deployed, reviews scheduled. A regulator or a risk committee member reading about privileged access wants something different. They want to know whether the control operated, how often, and what was found.
Evidence beats statements. "Leavers are disabled within the agreed window" is a policy position. A list of leavers, the dates their accounts were disabled, and the exceptions that remained open is evidence. The four metrics below are built to produce the second kind of answer.
The four metrics to request
1. Privileged account inventory and ownership coverage
Report the number of privileged accounts across key systems, and how many have a named, current human owner and a documented business justification. Include service and shared accounts separately, since they are where ownership most often lapses.
The board question this answers: do we know who holds privileged access, and who is accountable for each account?
2. Privileged access review completion and outcomes
Report which privileged-access reviews were due in the quarter, which were completed on time, and how many entitlements were revoked or changed as a result. Completion alone is weak; a review that revokes nothing deserves a question about its rigor.
The board question: are reviews happening on schedule, and do reviewers actually change access?
3. Leaver and mover timeliness
Report the time between a leaver's or mover's effective date in the HR record and the removal or adjustment of access in connected systems. Show it for general and privileged access separately, and list outstanding exceptions with their age.
The board question: when someone leaves or changes role, how quickly does their access follow?
4. Orphaned and unowned account count, with trend
Report accounts that are active but cannot be matched to a current employee or contractor, the number remediated, and the number still open at quarter end. The trend across quarters matters more than a single figure.
The board question: is the gap between HR reality and system reality closing?
The orphaned-account method that shows the process runs weekly
Metric four is also your best test of whether joiner-mover-leaver is operating as designed. If the process truly runs weekly, orphaned accounts should rarely live longer than a week. If it runs monthly, or only when someone remembers, the ages will show it.
- Extract the authoritative list. Pull current employees and contractors from the HR system or contractor register on a fixed day each week, and keep each extract.
- Extract account lists. Pull active accounts from the directory and from each key system, including privileged and service accounts.
- Match on a stable identifier. Use an employee or contractor number, not a display name, and list every account that has no match.
- Classify the unmatched. Separate genuine orphans from approved service accounts, break-glass accounts and vendor accounts that have a recorded owner.
- Record the first-seen date. Each orphan keeps the date it first appeared in the unmatched list.
- Measure age and closure. An orphan first seen in one weekly run and removed before the next supports a weekly cycle. Orphans first seen several runs earlier point to a slower one.
- Retain the evidence. Keep the weekly extracts, the match results and the closure records so a reviewer can reproduce the finding.
What you are looking for is the age distribution of orphans, not the raw count. A small number of old orphans tells you more about process failure than a larger number of recent ones.
Common reasons the metrics look better than reality
- HR records are updated late, so the process runs on time against stale data.
- Contractors sit outside the HR feed and are never matched.
- Privileged accounts in infrastructure and databases are not in the extract.
- Service accounts are labelled as approved without a named owner.
- Reviews are marked complete after approval without any entitlement being examined.
Each of these is a scoping issue rather than a tooling issue, and each is worth a line in the board commentary when it applies.
Signs it is time to strengthen identity governance
An organization usually needs outside help with this when one or more of the following is true:
- The board report cannot show leaver timeliness without manual spreadsheet work.
- Privileged accounts cannot be traced to named owners.
- Access reviews are done, but nobody can produce the evidence afterwards.
- Roles have grown by exception and no one can describe the intended access model.
- A regulator communication has raised privileged-access expectations and the existing report does not answer them.
What a good outcome looks like
A good outcome is a board report where each of the four metrics is produced from retained data, on a repeatable cycle, with a named owner. Orphaned accounts are found and closed within a short, known window. Reviews change access. Exceptions are visible, aged and explained. The conversation at the risk committee moves from whether the control exists to whether it is working.
How we run this work
Our Identity & Access Governance service strengthens how access is granted, reviewed and removed, covering joiner-mover-leaver processes, privileged access, segregation of duties and periodic access reviews. It is delivered as a project of 6–10 weeks, aligned to SAMA CSF and NCA ECC.
The work follows four stages:
- Baseline: current processes, systems and access data.
- Design: roles, rules and processes.
- Review: first access review campaign.
- Embed: handover and recurring cycle.
The deliverables are an IAM policy and procedures, a role catalog for key systems, a privileged access standard and an access review evidence pack. The evidence pack is what supports the metrics above when the board, internal audit or the regulator asks how a figure was produced.
Where the issue is how identity information reaches the board in the first place, our Cybersecurity Governance & Organization service addresses committees, reporting lines and how decisions reach the board.
Next step
If your next quarterly report cannot yet answer the four questions above with evidence, the starting point is a baseline of your current joiner-mover-leaver process and access data. Speak to CISO Consulting about our Identity & Access Governance service, and we will scope that baseline with you.
