Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Impersonate Any Login Permission
Governance, Ownership & Risk

Impersonate Any Login Permission

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

Impersonate Any Login permission is a SQL Server server-level permission that allows a principal to impersonate any login. It enables execution under another login’s security context through EXECUTE AS, which can expand access to databases and server-level actions if granted too broadly.

What this permission actually does

Impersonate Any Login is a server-level SQL Server permission that lets a principal run actions under another login’s security context. In practice, it is a powerful delegation capability, because the impersonated context can inherit access that the original principal does not normally hold.

This matters because SQL Server permissions are evaluated against the current execution context, not just the caller’s original identity. When impersonation is permitted, the boundary between “who issued the request” and “which rights are now in force” becomes much thinner, so small configuration mistakes can become broad access expansions.

Why it is dangerous when overgranted

When this permission is assigned too broadly, it can become a privilege-amplification path. A login with limited direct rights may be able to pivot into more privileged database access, server actions, or application pathways that were supposed to remain separated.

The core security issue is not impersonation itself, but the trust placed in the impersonation boundary. If a high-value login can be impersonated widely, then any flaw, misuse, or compromise of that permission can erase the value of normal role separation and make server-level authorization much less meaningful.

For that reason, audit the login and service-account landscape around SQL Server, including linked logins, orphaned users, and sysadmin membership, because impersonation risk is usually clearer when mapped against the broader account inventory. See How to audit SQL Server service accounts and logins for a practical review approach.

How it is checked and governed

Exposure assessment starts with knowing which principals hold the permission, whether it is granted directly or via role membership, and which logins those principals can impersonate. The practical question is not only “does the grant exist?” but “what effective access can this create across databases, linked servers, and server-level operations?”

Good governance also requires a clear ownership model for the privileged login set, because impersonation can hide excessive access behind a normal-looking execution path. Vendors and administrators should review whether the permission is necessary for a specific administrative pattern, or whether a narrower design would meet the same operational need.

External guidance on least privilege and control boundaries can help frame that review. The NIST SP 800-53 Rev 5 Security and Privacy Controls catalog supports access control, audit, and account management decisions, while the NIST Cybersecurity Framework 2.0 provides a broader governance lens for identifying and protecting privileged access paths.

Containment, detection, and response

If the permission cannot be removed immediately, reduce the blast radius by limiting who can invoke the affected context, tightening server-role membership, and monitoring for unusual execution patterns under impersonated identities. The goal is to make misuse visible before it becomes durable access expansion.

Detection should focus on abnormal context switching, unexpected privilege use, and privileged actions that do not align with the normal business function of the original login. Post-incident review should also ask whether impersonated sessions were used to create persistence, alter permissions, or stage later access through other trusted logins.

For adversary tradecraft mapping, MITRE ATT&CK Enterprise Matrix is useful for understanding privilege escalation and credential-access style behaviour, and the OWASP Non-Human Identity Top 10 helps frame overprivilege and secret-handling problems when SQL Server logins are tied to service or automation accounts.

Standards & Framework Alignment

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

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementServer-level impersonation directly affects access enforcement and effective permissions.
AU-2 — Event LoggingImpersonation risk depends on logging and review of context changes and privileged actions.
Recommendation — Enforce least-privilege authorization paths for principals that can impersonate other logins. Log impersonation-related context switches and review them for unexpected privileged activity.
CIS Controls v8CIS-5 — Account ManagementThis permission is governed through privileged account inventory and access review.
Recommendation — Inventory and review privileged SQL Server logins and permissions that enable impersonation.
OWASP ASVSV8 — AuthorizationThe permission is an authorization concern because it changes what actions a caller may perform.
Recommendation — Verify that delegated execution paths cannot expand authorization beyond intended roles.
MITRE ATT&CKT1078 — Valid AccountsImpersonation abuses trusted account context to perform actions under a different identity.
Recommendation — Map suspicious impersonation activity to valid-account abuse and hunt for privilege escalation.

Practitioner Guidance

Why practitioners should care: This permission is legitimate in some administrative designs, but it should be treated as a high-trust exception rather than a routine grant. If the same outcome can be achieved with a narrower role split or a more specific impersonation target, the broader permission usually creates unnecessary exposure.

Common misunderstanding: Teams sometimes assume that server-level impersonation is harmless because it is “only for admin convenience.” In reality, convenience is exactly what makes it dangerous, because a permission meant for controlled delegation can quietly erase privilege boundaries if it is inherited too widely or left unreviewed.

Practitioner takeaway: Review this permission alongside the full login inventory, then confirm that every principal holding it has a documented business need and a bounded impersonation scope.

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 November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org