An identity access review should follow the person and the permission
An identity access review audit examines whether access matches a legitimate purpose and whether changes in that purpose lead to appropriate access changes. Joiners, movers and leavers provide a practical way to trace the process. A new starter needs approved access, a role change may require removing old privileges, and a departure should trigger the relevant termination of access paths.
The difficult part is not counting directory accounts. It is connecting an authoritative business event with identities, entitlements, decisions and completed actions across the systems in scope. A central account can be disabled while a local application account remains; a role change can add new access without removing the old role. The audit should make those paths visible through evidence.
This guide describes document examination, interviews and authorised read-only assessment. It does not propose logging in as former workers, changing production access or attempting exploitation. Examples are hypothetical. For the broader engagement, see our cybersecurity audit service. The outcome is a traceable assessment of the lifecycle process and specific improvements the organisation can verify.
Reconcile people, accounts and applications
Build a population for the review period and compare it with the relevant identity and application inventories. One person can have several accounts, and one technical identity may not represent a person at all. Preserve those relationships instead of forcing every entry into a simple employee-to-account table.
Identify accounts outside the central identity platform. Local application users, privileged accounts, emergency identities and supplier portals may follow separate processes. The audit can include or explicitly exclude them, but should not imply that reviewing the central directory covers every access path. Record the systems and populations actually examined.
Investigate unmatched records. An account without a current personnel match might be a service identity, a valid contractor or an orphaned user. A person without an account might not require access. The assessor should resolve the category and purpose before presenting the mismatch as a security finding.
The CISA and NSA identity-management guidance describes identity governance and lifecycle events. Use that context to structure the review, while keeping each conclusion tied to the organisation’s own population, process and evidence. A framework reference does not establish that the implementation works.

Trace a joiner from request to justified entitlement
Select joiners from materially different groups, such as ordinary employees, contractors and privileged technical staff. Trace the business request, approval, account creation and entitlement assignment. The evidence should show why the person received the access, not merely that an account was successfully created.
Review how standard role access is defined. A role can make provisioning consistent, but its content still needs ownership and review. Ask who approves the role’s entitlements and how exceptions are handled. A broad default role can distribute unnecessary access efficiently, so automation alone is not evidence of a sound design.
Examine exceptional access separately. If a new starter receives additional privileges for a project, identify the approving owner, purpose and review or expiry condition. The audit should distinguish justified temporary access from an unexplained accumulation of permissions. Preserve the decision reference so the owner can revisit it later.
Check that the evidence reflects the actual implemented state. An approved request may differ from the final group membership or application role. Compare the relevant records at the appropriate time and explain any limitation in reconstructing history. Do not assume that the ticket’s requested access is exactly what the system granted.
Treat a role change as a removal question as well as an addition
Mover reviews often reveal accumulated access because the new role’s permissions are added while the previous role’s permissions remain. Select changes where responsibilities differ meaningfully, such as a move between departments or into a privileged function. Trace both the new access and the decision about what should be removed.
Identify who understands the old and new business requirements. The new manager may know what the person needs now but not what they no longer need from the former role. The process should obtain the relevant decisions without assuming that one generic approval covers every entitlement.
Review temporary overlap explicitly. A handover period may justify retaining some old access, but it should have an owner and end condition. Record whether that condition was reviewed and the access removed or reapproved. Temporary access that remains indefinitely is a lifecycle issue even if the original approval was reasonable.
Consider conflicting responsibilities where the organisation has defined them. The audit should examine the relevant access combination and owner decision rather than inventing universal segregation rules. A report is more useful when it identifies the specific business conflict and evidence than when it flags every combination of roles as suspicious.

Follow every relevant removal path
For selected leavers, trace the authoritative event through central identity, privileged identities and scoped application accounts. Identify the expected action for each path and the evidence of completion. A single central disablement record may be important but insufficient when the application allows local authentication or separately managed access.
Distinguish account state, sessions, tokens and application-specific access in the review questions. Product behaviour varies, so the assessor should use current documentation and read-only evidence for the actual environment. Avoid promising that one account action universally ends every session or integration. Record which paths were verified and which require further technical review.
Review the handling of owned resources and business continuity. Departures can affect shared mailboxes, documents, service ownership and approval workflows. The audit should not recommend deletion of information merely to simplify an account list. The organisation needs an approved process that removes unnecessary access while preserving legitimate records and operations.
Record late or incomplete actions against the organisation’s defined requirement and the evidence available. A delayed ticket closure does not always mean access remained active until that time, and an early closure does not prove removal. Examine the technical record where available and state uncertainty where it cannot be resolved.

Review privileged identities as a distinct population
Identify administrators, emergency accounts and other identities with significant control over systems. Determine the business owner, assigned person or service, approval basis and review process. These identities may require a different sample and evidence depth from ordinary staff access because their potential consequences differ.
Check whether privileged access changes when the person’s employment or role changes. A separate administrator account can be missed if the lifecycle process tracks only the ordinary user identity. Reconcile the relationship and examine selected events. The finding should identify the missing linkage rather than merely recommending that the organisation buy another identity tool.
Review exceptional or emergency access governance. The audit can examine ownership, protection, use records and review without attempting to activate a production emergency account. If a controlled exercise is required, it should be separately authorised and designed with the system owner. Do not turn a read-only audit into an unplanned operational test.
Ask who reviews the reviewers’ own access. A process that relies entirely on self-approval for the most powerful roles has a different independence boundary from one with accountable oversight. Describe the actual arrangement and its rationale. Avoid suggesting that a particular organisational title automatically guarantees an independent decision.
Keep service identities out of the employee-only blind spot
Service accounts, application identities and automation credentials may not have a departure date, but they still need a purpose and owner. Identify which are in scope and how ownership changes when a person or team leaves. A service identity should not remain ungoverned because it does not appear in the HR population.
Review the evidence connecting the identity to an active workload or integration. Ask who can change its permissions, who manages its credential lifecycle and how its continued need is assessed. Do not collect the credential itself. The audit needs governance and configuration evidence, not possession of production secrets.
Examine a sample of retired or changed integrations. The old identity may retain permissions after the application has moved to another method. Trace the service change record to the access decision and implemented state. This provides a practical lifecycle question for non-human identities without pretending that they follow exactly the same process as employees.
Record shared ownership carefully. If several teams rely on one identity, the removal decision needs coordination, but responsibility should not dissolve into “everyone.” Name an accountable owner and the evidence needed before a change. The recommendation should preserve business continuity while reducing unexplained standing access.

Check whether periodic reviews produce meaningful decisions
A completed access-review campaign is not automatically evidence that reviewers understood the entitlements. Examine what information the reviewer saw, which population was included and how decisions were recorded. A list of cryptic group identifiers may encourage blanket approval even when the reviewer is acting in good faith.
Select approved, removed and exceptional decisions where available. Trace each to the implemented state or follow-up action. A removal decision that never reaches the application is an important handoff gap. The review process should include verification, not end when someone submits a spreadsheet.
Ask how reviewers handle uncertainty. They should be able to request context, escalate an unowned entitlement or defer a decision with a clear owner. A forced binary approval can hide missing information. Record whether the process supports a reasoned decision and how unresolved items are brought to closure.
Review the population completeness. The campaign may cover central groups but omit local roles, nested membership or application-specific privileges. Those exclusions may be intentional, but they should be visible. The report should not present a campaign’s completion percentage as coverage of every identity and entitlement in the organisation.
Build a chain from event to outcome
For each selected lifecycle case, preserve references to the business event, request, approval, system action and verification. Record the relevant times and system identifiers. This makes it possible to distinguish a process delay from a documentation delay and to identify which team owns a missing step.
Use interviews to explain the workflow and records to support conclusions about operation. The NIST control-assessment methodology offers a useful basis for planning evidence methods. In this engagement, keep the actual examine, interview and read-only boundaries clear and do not imply a formal certification result.
Document collection limitations. A current access export may not reconstruct the exact historical state. A ticket may omit the effective technical timestamp. If the evidence cannot answer the timing question, state that limitation rather than selecting whichever date supports the preferred conclusion.
Protect personal information throughout collection and reporting. Use pseudonymous references where practical and keep detailed records in a restricted evidence location. The management report can explain a lifecycle failure without naming a former employee. Traceability and privacy can coexist when the evidence design is deliberate.
Select cases that exercise different lifecycle paths
Define the review period and population first. Include meaningful differences such as employees and contractors, automated and manual applications, ordinary and privileged access, and role changes with temporary overlap. Explain why those groups matter. A sample selected only from the easiest central workflow may miss the process that needs attention most.
Target known exceptions or recent changes when they answer a specific question, and label that selection honestly. A targeted sample can reveal useful problems but does not support a claim about prevalence across the entire population. Avoid presenting a percentage of sample exceptions as a universal organisational failure rate.
Record replacements and unavailable evidence. If a selected case cannot be examined, preserve why and how the replacement was chosen. Silently substituting well-documented cases can make a weak process appear stronger. Missing records may themselves be relevant when the procedure requires an auditable trail.
Extend the sample only to resolve a defined uncertainty. If one application has an unlinked local-account process, examine additional cases from that path to understand whether the issue recurs. Document the extension and keep the conclusion bounded. The audit should adapt intelligently without pretending that its original plan proved everything.
Worked example: a mover keeps an old approval role
Consider a hypothetical employee moving from finance operations into a reporting team. The new role is approved and provisioned. During the audit, the current entitlement export still shows an old payment-approval role. The assessor traces the mover request and finds no recorded decision about removing the former role.
The business owner explains that a short handover overlap was intended. However, the record contains no end date or subsequent review. The assessor does not claim that the employee misused the role. The observed issue is an unbounded temporary-access decision with a current entitlement that no longer has clear justification.
The owner decides whether the role remains necessary, records the decision and implements the appropriate change. The audit follow-up reviews the resulting state and the revised mover workflow. A small sample of other role changes using the same process helps determine whether the missing end condition is a recurring design issue.
The report links the finding to the mover process, evidence and accountable owner. It avoids a generic instruction to remove all access immediately, which could disrupt legitimate handover work. The improvement is a defined decision and verification path that handles temporary overlap without allowing it to become permanent by default.
Use a lifecycle reconciliation worksheet
Create columns for event type, population, authoritative event reference, relevant identities, target systems, required action, approval, implementation evidence and verification result. Include the expected timing basis and any uncertainty. One row can represent a lifecycle case with linked sub-records for its different access paths.
Keep the business decision separate from the technical observation. An owner may approve retaining a particular entitlement, but the assessor should still confirm which state is implemented. Conversely, a technical removal may occur without a clear approval record. Both observations can matter, and the worksheet should not collapse them into one status.
Use a distinct result for not applicable, not examined and evidence unavailable. These are not interchangeable with passed or failed. Clear categories prevent gaps from disappearing into a green completion chart. They also help the organisation decide which follow-up work would materially improve confidence.
Ask an uninvolved authorised reviewer to trace one row to its supporting evidence. If they cannot understand the sequence, improve the references and explanation before finalising the report. This simple quality check keeps the audit usable for the people who must implement and verify the recommendations.

Write findings around a broken handoff or unclear decision
Describe the intended lifecycle requirement, observed evidence, affected path and practical consequence. “Access management needs improvement” gives an owner little direction. A finding that a manual application does not receive contractor departure events identifies a specific integration or process decision to resolve.
Distinguish design gaps from operating exceptions. If no owner exists for local-account removal, the process needs a design decision. If the owner and process are clear but a selected case was missed, the action may involve monitoring and execution. The recommendation should address the mechanism behind the observation rather than prescribing the same solution for every issue.
Set a verification outcome. The organisation might demonstrate that new lifecycle events reach the application owner, that removal is recorded and that a selected completed case reconciles to current state. The auditor should explain what evidence would support closure without dictating an unnecessary product purchase.
Keep accepted risk separate from correction. If the business temporarily retains access for a justified reason, record the owner, boundary and review condition. That decision can be legitimate, but it is not evidence that the original process gap has been eliminated. The report should preserve both facts.
Verify the new process with fresh cases
Follow-up should examine the affected path after the change, not only the updated procedure. Select a relevant new joiner, mover or leaver case where available and trace the revised handoff. If insufficient time has passed to observe operation, state that the design has changed while operating effectiveness remains to be reviewed.
Recheck the original affected entitlement or account where appropriate through read-only evidence. Confirm that the implemented state matches the owner’s decision. Avoid declaring closure solely because a remediation ticket is marked complete. The conclusion should rest on the evidence relevant to the original finding.
Preserve the relationship between the finding, change and follow-up observation. Future reviewers should understand what was corrected and which limitation remains. This prevents repeated audits from starting the same discussion without recognising prior decisions or changes.
Use periodic reconciliation to maintain the improvement. A lifecycle process can drift as applications, suppliers and teams change. The organisation should know who reviews unmatched identities, unowned roles and overdue decisions. An audit can establish the baseline, but continued ownership keeps the process useful.

Scope an identity access review around the paths you need to trust
Provide the identity platforms, important applications, workforce categories and review objective. Identify known manual processes and recent migrations. Ask the assessor to propose a proportionate population and sample, with clear evidence requirements and read-only boundaries. This makes the engagement more useful than a generic account-counting exercise.
Ask for a synthetic example of a finding that traces a lifecycle event across several systems. The report should show the business requirement, observed access and practical action without unnecessary personal data. A buyer should be able to see how an administrator would locate and verify the issue.
Use our audit scoping planner or discuss an identity access review with Atlant Security. Share high-level system and process information first. Personnel records, account exports and other sensitive evidence should use an agreed secure exchange after scope and handling requirements are established.
Reviewed 25 October 2026. This article describes an evidence-led audit method, not a certification or a claim that particular accounts are compromised. Product-specific access behaviour and organisational requirements must be verified in context. The strongest result is a clear chain from business event to justified access, implemented action and documented verification.
Published by Atlant Security. Sources, editorial policy and corrections.

