Privileged access audit, UAE

Count your administrators. Then count the service accounts, the vendor logins and the local accounts on every server.

A privileged access audit finds every path to elevated capability, not only the ones in the directory. The list that matters includes service accounts nobody owns, vendor accounts nobody reviews, local accounts nobody has changed, and the automation credentials sitting in a script somewhere.

Privileged access audit for UAE organisations
  • Every pathNot only directory administrators
  • CIS 5, 6 and 8Accounts, access control, audit logging
  • Service accountsThe population nobody has an owner for
  • Break-glassVerified by signing in, not by reading
What we examine

Seven privileged populations, and only the first is usually counted.

Account management is control 5 in the CIS Critical Security Controls at version 8.1, access control management is control 6, and audit log management is control 8. Between them they describe what a privileged access audit is measuring. The difficulty is never the standard, it is finding every population the standard applies to.

Directory administrators, which everybody counts

Global administrators, domain administrators, and the tiers below them. This is the population organisations can produce on request, and it is usually larger than the person producing it expects once nested groups are expanded. It is also the only population most organisations review, which is why the audit rarely stops here.

Service accounts, which almost nobody owns

Accounts created for an application, a backup job, an integration or a migration, frequently with more privilege than the task required and passwords that have not changed since creation. The audit question is not how many exist, it is how many have a named owner who can say what would break if the password were rotated.

Local accounts on servers and appliances

Local administrator accounts on Windows servers, root and sudo on Linux, and the built-in accounts on network devices, storage, hypervisors, backup systems and building management. They are outside the directory, so they are outside every directory-based review, and they are frequently the same password across a whole estate.

Vendor and support access

Accounts issued to a supplier for support, a remote access tool installed for a project, and the standing credentials somebody gave an integrator years ago. This population is usually undocumented, usually still active, and represents a privilege path through an organisation whose own controls you do not manage.

Cloud and platform privilege beyond the directory

Subscription owners, resource-level role assignments, key vault access, application registrations with high consent, service principals and managed identities with more permission than their workload needs. A directory administrator list says nothing about who can delete a production resource group, and increasingly that is the more consequential question.

Standing versus elevated on demand

The audit does not only count who has privilege, it records whether they hold it permanently or activate it when needed. Permanent assignment is the norm in most organisations and is the finding that most improves the risk position when changed, because it converts a persistent target into a time-bound one.

Whether any of it is logged and looked at

Audit log management is control 8, and privileged activity is the specific case where it matters most. The questions are whether privileged sign-ins and actions are logged, whether the logs are retained long enough to investigate, and whether anybody would notice an unexpected one. The third question is the one that usually fails.

The population nobody can name an owner for

Service accounts are the largest privileged population and the least governed.

Every organisation can produce a list of administrators. Very few can produce a list of service accounts with an owner against each.

  • They are created for a purpose, given the privilege that made the task work rather than the privilege the task required, and then never revisited because revisiting them risks breaking whatever they run.
  • They frequently have passwords that have not changed since creation, precisely because nobody can say with confidence what would stop working. That is the same asymmetry that stops firewall rules being removed, applied to credentials.
  • They are also the accounts least likely to be covered by multifactor authentication, most likely to be excluded from conditional access, and most likely to appear in a script, a scheduled task or a configuration file that somebody can read.
  • The audit output that changes this is not a count. It is a list with a named owner against each account, a statement of what it does, and a rotation plan for the ones where the owner can confirm the impact. Producing that list is most of the work and all of the value.
Ask us to inventory your service accounts
How we approach it

Four things that make this more than an administrator list.

Producing a list of directory administrators takes minutes and is the least useful version of this work. The value is entirely in the populations that are harder to enumerate and easier to ignore.

We inventory service accounts and chase every owner

This is the largest privileged population in most organisations and the least governed. The output that matters is not a count, it is a list with a named owner, a stated purpose and an assessment of what rotation would break. Producing that requires talking to application teams rather than querying a directory.

We look outside the directory, where the estate actually lives

Server local accounts, Linux sudoers, network device credentials, hypervisor and storage consoles, backup systems, database logins and building management. None of these appear in a directory review, all of them confer privilege, and several of them confer more privilege than any directory role because they sit beneath it.

We test the break-glass accounts by using them

Microsoft guidance for emergency access accounts is specific: two or more, cloud-only on the onmicrosoft.com domain, phishing-resistant authentication different from normal administrative accounts, permanent active rather than eligible in Privileged Identity Management, excluded from blocking Conditional Access policies, alerted on, and validated at least every ninety days. We check by signing in rather than by reading the configuration.

We ask whether anybody would notice, not only whether it is logged

Audit log management is control 8, and privileged activity is where it matters most. Logging privileged sign-ins is common. Retaining those logs long enough to investigate is less common. Having somebody who would notice an unexpected privileged sign-in at three in the morning is rare, and it is the question that separates a control from a record.

Where this matters most

Six UAE situations where a privileged access audit changes the picture.

Privileged access is the shortest path between an attacker and everything that matters, which is why it is the population attackers target and the population organisations most consistently under-count.

A regulated firm asked to evidence privileged access control

Most regulatory frameworks expect privileged access to be restricted, justified, monitored and periodically reviewed. Answering that with a directory administrator list covers a fraction of the privileged estate. A full audit produces the answer for every population, which is what the question actually asks even when it does not say so.

A group that has grown by acquisition

Each acquisition brings its own directory, its own service accounts, its own vendor relationships and its own local account conventions. Integration typically adds cross-domain trust or synchronisation without anybody auditing what privilege that grants. The combined privileged picture is almost never assembled unless somebody deliberately does it.

An organisation with heavy supplier and integrator involvement

Vendor accounts, support access and remote access tools installed for projects accumulate steadily and are removed rarely. Each represents privilege in your environment held by an organisation whose own controls you do not manage, which makes it both a security question and a third-party risk question at the same time.

An operator with technology outside the IT estate

Building management, access control, plant systems and facilities technology are networked, privileged over things that matter physically, and almost never in scope for an identity review. They frequently run default credentials because nobody in IT considers them their responsibility and nobody in facilities considers them a security asset.

An organisation that has just had an identity incident

After a compromise, the immediate question is what that account could reach. The broader question is what else has similar reach, and answering it requires the full privileged inventory rather than the administrator list. That work is usually commissioned after an incident and is far cheaper before one.

A business implementing just-in-time privileged access

Moving from standing to on-demand privilege requires knowing what standing privilege exists first, including the populations that cannot be moved because they are service accounts or appliance logins. The audit is the necessary predecessor, and it usually reveals that the human administrators are the easy part of the problem.

Three positions

How UAE organisations understand their privileged access.

The middle column is the common one and it is genuinely better than nothing. It answers the question for the directory and leaves every other privileged path unexamined.
Directory administrators known
Full privileged access auditYes
Directory administrators reviewedYes
No privileged access reviewNo
Service accounts inventoried with owners
Full privileged access auditYes
Directory administrators reviewedNo
No privileged access reviewNo
Local and appliance accounts covered
Full privileged access auditYes
Directory administrators reviewedNo
No privileged access reviewNo
Vendor access documented
Full privileged access auditYes
Directory administrators reviewedNo
No privileged access reviewNo
Cloud resource privilege included
Full privileged access auditYes
Directory administrators reviewedRarely
No privileged access reviewNo
Standing versus on-demand recorded
Full privileged access auditYes
Directory administrators reviewedNo
No privileged access reviewNo
Credential age known
Full privileged access auditYes
Directory administrators reviewedPartly
No privileged access reviewNo
Break-glass accounts tested
Full privileged access auditYes
Directory administrators reviewedNo
No privileged access reviewNot applicable
Privileged activity monitored
Full privileged access auditYes
Directory administrators reviewedLogged only
No privileged access reviewNo
Answer to who could do the most damage
Full privileged access auditYes
Directory administrators reviewedPartial
No privileged access reviewNo
The questions per account

Nine questions, asked of every privileged account we find.

The audit produces an answer to each of these per account. Most organisations can answer the first two comfortably and struggle from the third onwards.
QuestionWhy it matters
Who is the named owner?An account with no owner cannot be reviewed, changed or retired
What is it for?Purpose determines whether the privilege level is proportionate
Does the privilege match the purpose?Most over-privilege is historic rather than deliberate
Is it standing, or activated on demand?Standing privilege is a persistent target
How does it authenticate?Phishing-resistant, multifactor, password only, or a key in a file
When did the credential last change?And does anybody know what rotation would break
When was it last used?Unused privileged accounts are the cheapest thing to remove
Is its activity logged?Audit log management is control 8, and privilege is the case that matters
Would anyone notice unexpected use?Logging without review is storage, not detection
How an engagement runs

Five steps, and step two takes longer than everything else.

Typically three to six weeks. Enumeration is fast where systems are accessible. Attributing ownership to service accounts is what determines the timeline, because it requires people rather than queries.
  1. 1

    Enumerate every privileged path, not only the directory

    Directory roles with nested groups expanded, server local administrators, Linux root and sudoers, database logins, network device accounts, hypervisor and storage consoles, backup systems, cloud subscription and resource roles, application registrations and service principals, and any facilities or operational technology in scope.

  2. 2

    Attribute ownership, especially for service accounts

    Working with application and platform teams to put a named owner and a stated purpose against every account. This is the slowest step and the one that determines whether the audit produces a decision list or a census. Accounts that end this step with no owner are themselves a finding.

  3. 3

    Assess proportionality, standing privilege and credential hygiene

    Whether the privilege level matches the purpose, whether it is held permanently or activated on demand, how it authenticates, when the credential last changed, and when the account was last used. Unused privileged accounts are the cheapest possible remediation and consistently the largest single category.

  4. 4

    Test break-glass and check monitoring

    Signing in to each emergency access account rather than reading its configuration, and verifying the alert fires. Then whether privileged sign-ins and actions are logged, retained long enough to investigate, and reviewed by somebody who would notice an unexpected one. That last question is the one that usually fails.

  5. 5

    Deliver a prioritised remediation plan with owners

    Unused accounts removed, over-privileged accounts scoped down, standing privilege converted to on-demand where the account type allows, credentials rotated where the owner can confirm impact, and vendor access documented and time-bounded. Each item with an owner, because a privileged access report without owners produces no change.

Straight answers

What organisations ask about privileged access audits.

Preparing for the audit

Fifteen sources of privileged access to include in scope.

Scoping to the directory alone produces a comfortable report. These are the places privilege actually lives, and the ones after the first five are where the findings are.

The obvious ones

  • Directory administrative roles
    With nested groups expanded.
  • Server local administrators
    Outside the directory, outside most reviews.
  • Linux root and sudo
    Including sudoers entries.
  • Database administrative accounts
    Frequently separate from the directory.
  • Network device accounts
    Often shared, often unchanged.

The ones that get missed

  • Service accounts across all platforms
    The largest population.
  • Application registrations and service principals
    Consent can exceed any human role.
  • Cloud subscription and resource roles
    Not visible in a directory role list.
  • Hypervisor and storage consoles
    Privileged over everything they host.
  • Backup system accounts
    Able to read or destroy everything.

The ones nobody mentions

  • Vendor and integrator accounts
    Usually standing, usually undocumented.
  • Remote access tools installed for projects
    Frequently still running.
  • Break-glass accounts
    Verified by signing in, not by reading.
  • Building and facilities systems
    Privileged, networked, and unowned.
  • Credentials in scripts and config files
    Machine secrets scanning finds these.
Next step

Ask for a list of your service accounts with an owner against each.

Tell us about administrator accounts, service identities, vendor access and critical system dependencies. We will confirm the requirements and proposed scope with you.