Access rights review, UAE

Most access reviews are rubber stamps, and everyone involved knows it.

A manager sent a list of group names they cannot interpret will approve all of it, because the alternative is guessing. That produces a completed review, an audit artefact, and no change in who can reach what. Making the review mean something is a design problem, not a compliance one.

Access rights review and certification for UAE organisations
  • Approve-allThe outcome nobody admits to
  • Translate itShow consequences, not group names
  • Within 24 hoursWhat ADHICS requires on exit
  • RecurringA cadence, not a project
What makes a review real

Eight design decisions, and the first one is why most reviews fail.

Access reviews are required by several frameworks and performed badly almost everywhere, and the reason is consistent. The people asked to certify access are given information they cannot act on. Everything below is about closing that gap rather than about tooling.

Translate access into consequences the reviewer understands

A line reading FIN-GL-POST-PROD means nothing to a finance manager. The same line described as can post journal entries to the general ledger in the live system is something they can immediately judge, and they will remove people. This single change does more than any platform, and it is the step almost every review skips because producing the translation takes effort and exporting group names does not.

Give it to somebody who actually knows

The reviewer must be someone who knows what the person does day to day, which usually means the line manager rather than IT or a system owner. IT knows what the access is and not whether it is warranted. A system owner knows the system and not the individual. Sending the review to the wrong person is the second most common design error, and it guarantees approval by default.

Review what matters, not everything

A review covering every system and every permission produces fatigue and blanket approval. One covering privileged access, systems holding regulated or financial data, and anything an external party can reach produces genuine decisions. Scope narrowly enough that reviewers read it. An annual review of everything is worth less than a quarterly review of what matters.

Leavers, which is the specific test everyone fails

The recurring review is the safety net. The primary control is removal at exit, and that is where frameworks are explicit: ADHICS V2 requires access to systems, applications, information and secure areas to be revoked within 24 hours of exit or termination. If leaver removal works, the review finds little. If it does not, the review is doing a job that should have been done months earlier.

Movers, which nobody reviews at all

Someone who changes role keeps the old access and gains the new, and this accumulates for years without anybody noticing because nothing triggers a check. Leavers get attention because a process fires. Movers get none. In most organisations we assess, the people with the widest access are the longest-serving, and it is entirely a byproduct of internal promotions.

Privileged access, reviewed separately and more often

Administrative access deserves its own cycle rather than being buried inside a general review. Several frameworks address this directly. CBUAE Article 13 requires restricting the number of privileged users, prohibits sharing privileged accounts, and requires logging, preserving and monitoring privileged activity including peer review of activity logs. Those are testable requirements, not principles.

Measure removals, not completion

The metric almost every organisation reports is the percentage of reviews completed, which measures whether people clicked. The metric that tells you whether the control works is how much access was removed. A review cycle that completes at 100 percent and removes nothing is a rubber stamp with good statistics, and it is worth saying so to whoever receives the report.

Evidence that satisfies whoever asks

External auditors sample access reviews because ISA 315 names managing access to the IT environment as one of its three IT processes. What they need is the review, the reviewer, the date and what changed as a result. Recording the outcome is as important as performing it, and a review that happened but left no artefact is indistinguishable from one that did not.

The uncomfortable part

A review that removes nothing has told you nothing.

This is worth confronting directly, because the failure is invisible in every metric organisations normally report and obvious the moment you ask a different question.

  • Ask for the last completed access review and count how many entitlements were removed as a result. If the answer is none or nearly none across a large population, the review did not work. Access genuinely does accumulate, so a real review always finds something. A clean result across hundreds of users means the reviewers approved rather than assessed.
  • This is not the reviewers being lazy. They were sent a list of technical group names, given no information about what those permissions allow, no context about what the person actually does, and a deadline. Under those conditions approving everything is the rational response, because the alternative is removing access on a guess and breaking somebody work.
  • The fix is on the sending side, not the receiving side. Translate each entitlement into what it lets somebody do, show when it was last used where you can, flag anything that looks anomalous for that role, and pre-populate a recommendation the reviewer can accept or override. Reviewers engage with that. They cannot engage with a list of group names.
  • Then measure removals rather than completion. Completion tells you whether people clicked a button. Removals tell you whether the control is doing anything. Reporting completion to a board or an audit committee, while removals sit at zero, is a more misleading statistic than reporting nothing at all.
Ask us to look at your last review and count the removals
How we approach it

Four things that separate a working review from a completed one.

This is design work more than technical work. The systems can produce the data; the difficulty is turning it into something a busy manager will engage with honestly.

We build the translation layer, which is the actual job

Mapping every reviewable entitlement to a plain description of what it lets somebody do. This is unglamorous, it takes real effort, and it is the reason most reviews fail, because exporting group names is easy and translating them is not. Once built it is reusable every cycle, so the cost is front-loaded and the benefit recurs.

We scope down until reviewers will actually read it

A shorter review that gets genuine attention beats a comprehensive one that gets blanket approval, and we will argue for that even when a framework appears to push toward completeness. Privileged access, systems holding regulated or financial data, and anything externally reachable first. The rest can be annual, or sampled, or reasoned about rather than certified line by line.

We report removals, and we say when the answer is zero

If a cycle completes and nothing is removed, we tell you that plainly rather than presenting a completion rate. Access accumulates, so a genuine review across a real population always finds something. A clean sheet means the reviewers approved rather than assessed, and reporting that honestly is more useful than a green dashboard.

We fix leavers and movers first, so the net is mostly empty

A recurring review is a safety net, not the primary control. If removal at exit works and role changes trigger a check, the review should find little, and finding little for the right reason is the goal. Where we find leaver access persisting for months, that is the more urgent problem and we deal with it before designing a review cadence.

Who needs this

Six situations where a real review is required rather than optional.

In most of these something external drives the requirement, which is useful, because it means the review has an audience and a deadline rather than being an internal good intention.

A company whose external auditor samples access

ISA 315 names managing access to the IT environment as one of its three IT processes, so auditors test it, and they sample individual users rather than reading your policy. What they need is the review, the reviewer, the date and the outcome. A review performed but not recorded is indistinguishable to them from one never performed, which is a frustrating way to earn a finding.

A healthcare entity under ADHICS in Abu Dhabi

Access Control is one of the eleven control domains, and the standard is specific: access must be revoked within 24 hours of exit or termination, and there must be a security administration function with formal procedures for allocating access rights and monitoring use for unusual or unauthorised activity. Shared clinical logins sit awkwardly against all of that and are the recurring finding.

A payment provider or financial firm under CBUAE requirements

Article 13 requires a security administration function and formal access procedures, and sets out ten named controls for privileged and emergency IDs including restricting the number of privileged users, prohibiting shared privileged accounts, and logging and peer-reviewing privileged activity. These are testable items, which makes a designed review considerably easier to evidence than an informal one.

An organisation with long-serving staff and internal promotions

The mover problem in its purest form. People who have been through three roles in eight years hold the union of all three, nobody ever removed anything, and they are frequently the most trusted people in the business, which makes it socially awkward to raise. A designed review handles this impersonally, which is precisely why it works better than a conversation.

A business with high turnover

Hospitality, retail, logistics and construction, where people join and leave constantly and offboarding is often informal. Here the review is doing real work rather than acting as a safety net, and the first cycle usually removes a great deal. The durable fix is leaver process rather than review frequency, but the review is what demonstrates the scale of the problem.

A firm answering client or insurer questions about access control

Questions about how access is granted, reviewed and removed appear on almost every security questionnaire and insurance proposal now. These are answered on documents somebody signs, which makes accuracy more than good practice. A review that exists and removes nothing is difficult to describe honestly, and the honest description is worse than fixing it.

Three kinds of access review

Same activity, three entirely different outcomes.

The middle column is what most UAE organisations run, and it is the expensive one, because it consumes real management time across the business and changes nothing.
Entitlements described in business terms
Designed to be answerable
Rubber stamp
No review at allNot applicable
Reviewer knows the person and their job
Designed to be answerable
Rubber stampSometimes
No review at allNot applicable
Last-used information shown
Designed to be answerable
Rubber stamp
No review at all
Scope narrow enough to be read
Designed to be answerable
Rubber stamp
No review at allNot applicable
Access actually removed as a result
Designed to be answerableRegularly
Rubber stampAlmost never
No review at allNever
Privileged access on its own cycle
Designed to be answerable
Rubber stamp
No review at all
Movers trigger a check
Designed to be answerable
Rubber stamp
No review at all
Management time consumed
Designed to be answerableModerate
Rubber stampModerate
No review at allNone
Survives an auditor asking what changed
Designed to be answerable
Rubber stampAwkwardly
No review at all
Reported metric
Designed to be answerableRemovals
Rubber stampCompletion
No review at allNone
What the reviewer actually sees

The same entitlement, presented two ways.

The left column is what most access reviews send. The right is what makes a reviewer capable of answering. Nothing about the underlying access differs between them, only the presentation, and the difference in outcome is the whole subject of this page.
What is usually sentWhat the reviewer can act on
FIN-GL-POST-PRODCan post journal entries to the live general ledger
Domain AdminsFull control of every server, workstation and account
HR-SYS-ALLEMP-RWCan read and edit records for all employees, including salary
SP-SITE-LEGAL-OWNERCan manage and share the legal document library externally
AP-VENDOR-MAINTCan change supplier bank details, the invoice fraud path
Global ReaderCan read everything in the tenant, including all mailboxes
CRM-EXPORT-ALLCan export the entire customer database to a file
No usage informationLast used 14 months ago
No peer contextNobody else in this role has this access
No recommendationSuggested: remove. Accept or override with a reason
How we set it up

Five steps, and the first cycle is the expensive one.

The translation layer is front-loaded effort that pays back every cycle afterwards. Expect the first review to take real work and subsequent ones to be routine.
  1. 1

    Establish what is actually worth reviewing

    Privileged access first, then systems holding regulated, personal or financial data, then anything reachable by external parties. We scope down deliberately until the population is small enough that reviewers will read it, because a comprehensive review that gets blanket approval is worse than a narrow one that gets attention.

  2. 2

    Build the translation layer

    Every reviewable entitlement mapped to a plain description of what it permits, with last-used information where the system provides it and a note where an entitlement is unusual for that role. This is the substance of the engagement and it is reusable, so it is built once and maintained rather than recreated each cycle.

  3. 3

    Fix leavers and movers before the first cycle

    Check the last several leavers against removal dates, and establish whether anything triggers a review when somebody changes role. If leaver access is persisting, that is more urgent than any review design, and running a review over a population full of former employees wastes the reviewers first impression of the process.

  4. 4

    Run the first cycle with support

    Reviewers get a short briefing, a pre-populated recommendation they can accept or override with a reason, and someone available to answer questions during the window. Then removals are actioned promptly, because nothing teaches reviewers to disengage faster than marking access for removal and seeing it still there next quarter.

  5. 5

    Set the cadence and report removals

    Privileged access more frequently than general access, with the frequency set by risk rather than by convention. Reporting to leadership leads with entitlements removed rather than reviews completed, and where a cycle removes nothing we say so and look at why rather than presenting it as a clean result.

Straight answers

What organisations ask about access reviews.

Test your own review

Fifteen questions about the last access review you ran.

The first group tests whether it was real. The second is the design that determines whether the next one will be. The third is the surrounding process, because a review is a safety net and the net should mostly be empty.

Was the last one real

  • How many entitlements were removed as a result?
    The only question that matters. Zero means it did not work.
  • How long did reviewers spend on it, on average?
    If it was minutes for hundreds of lines, it was not read.
  • Did any reviewer ask a question during it?
    Silence across a whole cycle is a signal, not a success.
  • Were reviewers shown what each permission actually allows?
    Or a list of technical group names.
  • Can you produce the reviewer, date and outcome for each item?
    What an external auditor will sample.

Design of the next one

  • Is the reviewer someone who knows what the person does?
    Usually the line manager, not IT or a system owner.
  • Is the scope narrow enough that people will read it?
    Privileged, regulated and externally reachable access first.
  • Can you show last-used dates for entitlements?
    The single most useful field a reviewer can be given.
  • Do you pre-populate a recommendation to accept or override?
    Turns an open question into a decision.
  • Does anything actually happen when access is marked for removal?
    Reviews that produce no action teach reviewers not to bother.

The surrounding process

  • Is leaver access removed within 24 hours of exit?
    What ADHICS requires. Check your last ten leavers.
  • Does anything trigger a check when somebody changes role?
    Movers are the accumulation nobody reviews.
  • Is privileged access on a separate, more frequent cycle?
    It should not be buried in a general review.
  • Are shared privileged accounts eliminated?
    CBUAE Article 13 prohibits sharing them outright.
  • Do you report removals to leadership, or completion?
    Completion is the more misleading of the two.
Next step

Take your last access review and count the removals.

Tell us about the applications in scope, account sources, review owners and any upcoming audit. We will confirm the requirements and proposed scope with you.