IAM Audit: Access Rights Review & Controls
Understanding IAM Audit
Definition
An IAM Audit is a structured technical review of Identity and Access Management controls, focusing on access rights, role assignments, privilege levels, and authentication mechanisms across an organization's systems. The IAM Audit process examines who holds access to what resource, under which conditions, and whether that access is still justified by a current business need. It covers user accounts, service accounts, privileged identities, group memberships, and federation configurations. Key verification points include dormant accounts that retain active permissions, role accumulation (also known as privilege creep) where users collect entitlements over time without formal review, and misconfigured Separation of Duties (SoD) policies that allow a single identity to perform conflicting operations. IAM Audits also validate whether authentication factors are correctly enforced, whether conditional access policies match the defined security baseline, and whether delegated admin rights in directories such as Active Directory or Azure AD are scoped appropriately. The outcome feeds directly into compliance frameworks including SOC 2, ISO 27001, and NIST 800-53, and provides concrete evidence for access recertification campaigns.
Detection (Blue Team / SOC)
From a Blue Team and SOC perspective, continuous IAM Audit monitoring relies on correlating identity-related events across multiple log sources. In Active Directory environments, Windows Security Event IDs 4720 (account created), 4732 (member added to privileged group), 4756 (member added to universal security group), and 4672 (special privileges assigned at logon) are primary indicators of unauthorized privilege changes. Azure AD logs surfaced through Microsoft Entra ID Audit Logs and Sign-in Logs expose role assignments, guest account provisioning, and conditional access policy bypasses. SIEM platforms such as Splunk, Microsoft Sentinel, or Elastic SIEM should run scheduled queries to detect accounts with no recent logon activity still holding high-privilege roles, service accounts authenticating interactively, and admin accounts without MFA enforcement. Identity Governance platforms like SailPoint IdentityNow or Saviynt generate access review campaigns and flag out-of-policy entitlements automatically. Key IOCs include sudden addition of accounts to Domain Admins or Global Administrators groups, use of stale service account credentials, and delegation of password reset rights to non-admin users. UEBA rules that baseline normal access patterns and alert on deviations are particularly effective for detecting insider privilege abuse before it escalates.
Exploitation & countermeasures (Red Team)
From a Red Team and pentest perspective, IAM Audit findings represent some of the highest-value attack paths available during an engagement. Privilege creep discovered during an audit translates directly into lateral movement opportunities: a compromised standard user account that has accumulated unnecessary rights to sensitive file shares or administrative consoles can bypass the need for explicit privilege escalation. Attackers routinely target dormant service accounts because their passwords often predate current rotation policies and their activity generates fewer baseline alerts. Techniques such as Kerberoasting (requesting TGS tickets for SPNs registered to service accounts) or AS-REP Roasting (targeting accounts with Kerberos pre-authentication disabled) are effective precisely because these misconfigurations are common IAM Audit failures. Tools such as BloodHound with SharpHound collectors map Active Directory ACL paths and group membership chains to visualize the shortest route from a low-privilege account to Domain Admin. Hardening measures derived from IAM Audit results include enforcing just-in-time (JIT) privileged access via solutions like CyberArk PAM or Microsoft PIM, removing standing admin rights, implementing time-bound role assignments, and enforcing access recertification on a quarterly cycle. Automated SoD enforcement within the IAM platform prevents conflicting entitlement combinations from being provisioned in the first place.
Articles about IAM Audit
IAM wildcards, unconstrained assumable roles, unrotated root keys: how these misconfigs lead to full AWS account takeover.
Application Administrator, Helpdesk Administrator… these roles look harmless. Here's how they can be chained to reach Global Administrator.