Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Impersonation
Governance, Ownership & Risk

Impersonation

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

Impersonation is a controlled administrative action that lets an authorised operator assume a user context for debugging or support. In a well-governed setup it preserves audit logging, limits exposure of credentials, and keeps production authentication separate from local troubleshooting.

What impersonation is used for

Impersonation is a controlled break-glass style administrative capability, not a user-facing login shortcut. It exists so support staff can inspect a problem in the same context the user experiences, while preserving separation between production authentication and local troubleshooting.

The key design choice is that the operator borrows the user context without quietly becoming the user in an uncontrolled way. That means the action should be intentionally invoked, bounded, and traceable, because it changes what the operator can see and do during the session.

How impersonation differs from ordinary access

Impersonation sits between direct administrative access and full delegation. Direct access uses the operator's own privileges; delegation lets someone act on behalf of another identity through an explicit protocol or token flow; impersonation temporarily adopts the target context for a defined operational purpose.

That distinction matters because the security properties are different. A normal admin action should be attributed to the admin, while an impersonated action should be attributed to both the operator and the assumed context, with audit records showing who initiated the switch and why.

In practice, the difference is often visible in how the system handles session state, authorization checks, and evidence of approval. If those controls are weak, impersonation can become an informal back door rather than a governed support function.

Why impersonation needs tight control

Impersonation is powerful because it can reveal the same data, workflows, and permissions that a user sees. That makes it useful for troubleshooting, but also dangerous if the operator can overreach, export sensitive information, or silently bypass normal segregation of duties.

Well-run environments keep the scope narrow, usually by limiting when impersonation is allowed, which roles may invoke it, and how long the borrowed context remains active. Pretexting Guide is relevant here because real-world impersonation abuse often begins with social engineering of the help desk or support process.

Impersonation also creates a trust problem if the organisation cannot prove that a legitimate support reason existed. Without strong logging and approval trails, the action can blur into account takeover behaviour, especially when the operator is viewing or changing recovery settings, MFA state, or other identity controls.

Operational signals and safe use patterns

Healthy impersonation programs are explicit about context switching. They preserve original operator identity, record the reason for the session, and avoid mixing production credentials with troubleshooting credentials or local test accounts.

They also rely on consistent verification of who is asking for the action and whether the request matches an approved support scenario. That discipline reduces the chance that an attacker can use the same mechanism to pose as a user, a vendor, or an executive. Entra ID actor token flaw (CVE-2025-55241) is a useful reminder that context or token abuse can turn what looks like legitimate identity handling into privilege escalation if validation is flawed.

Where impersonation is implemented well, it becomes a diagnostic control with a clear end state: the session ends, the borrowed context is revoked, and the operator returns to their own account. That keeps support work distinct from standing access and reduces the risk of unintended persistence.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 provides the primary governance reference for this term.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementImpersonation depends on governed account use, approvals, and controlled activation of access context.
AU-2 — Event LoggingImpersonation must be auditable so operators and assumed context are both visible in logs.
AC-6 — Least PrivilegeImpersonation should only grant the minimum context needed for a support task.
Recommendation — Restrict impersonation to approved account-management workflows and record each activation with a traceable business reason. Log every impersonation start, stop, target, initiator, and justification in an immutable audit trail. Limit impersonation scope and duration to the smallest privilege set needed for the approved troubleshooting action.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org