Alter Any Login permission is a SQL Server server-level permission that allows a principal to create, change, or drop logins. It controls authentication identities at the instance level and can indirectly affect access by resetting passwords, enabling logins, or changing login attributes.
What the permission actually changes
Alter Any Login Permission is not just a metadata flag, it is authority over instance-level authentication identities. A principal with this permission can create, modify, or remove logins, which means it can change who can connect, how they authenticate, and whether an existing login remains usable. In practice, it sits close to the control plane for SQL Server access.
Because logins are the top-level entry point into an instance, this permission can have effects that feel larger than its name suggests. Resetting a login password, enabling a disabled login, or changing login attributes can immediately reopen access paths that were previously blocked, even when the database objects themselves are unchanged.
Why it matters for access control
This permission is dangerous because it can alter the boundary between a valid identity and a blocked one. If an operator can create or change logins without strong oversight, they can potentially restore access for an account that should remain disabled, widen access by introducing a new login, or interfere with account controls that other teams rely on for segregation of duties.
The core security concern is not just privilege depth, but privilege scope. A seemingly narrow server-level right can affect many downstream permissions if the login is mapped into roles, databases, or applications that trust that instance identity.
Where misuse becomes a security problem
In SQL Server environments, this permission becomes especially sensitive when administrative duties are split across teams or when login changes are used as an operational shortcut. A mistaken or malicious change can create unauthorized access, break application connectivity, or hide the fact that an account has been re-enabled outside normal approval.
It also matters because login management is often reviewed less frequently than database permissions. That gap can leave identity changes unnoticed until an unexpected connection, a failed audit, or a post-incident review reveals that a login was altered without proper control.
For broader context on the risks of overprivileged and poorly governed identity material, OWASP Non-Human Identity Top 10 is a useful reference point even though this SQL Server permission is a native database control, not a dedicated NHI topic.
How it is typically governed and reviewed
Organisations usually treat this as a highly restricted administrative permission, ideally assigned only where login lifecycle work is a genuine job requirement. The practical question is who is allowed to change authentication identities at the instance layer, under what approvals, and with what logging or change record.
Reviewing who holds the permission, when it was granted, and whether it is still needed is more important than the label itself. A stale assignment can be as risky as an active misuse path, because the permission remains usable even when it is forgotten.
For a control-oriented view of least-privilege and access management, NIST SP 800-53 Rev 5 Security and Privacy Controls provides the broader access-control and audit patterns that this permission should fit within, while NIST Cybersecurity Framework 2.0 frames the governance and protective functions around managing privileged access.
Risk and Threat Considerations
This permission creates a direct abuse path because a holder can change the identity that others rely on to authenticate to the database instance. If it is misassigned, stolen, or used outside approved change control, an attacker or insider may be able to restore access, create a new foothold, or interfere with account state in a way that looks like routine administration.
Failure mechanism: The permission lets a principal manipulate login state and attributes at the instance boundary, so abuse can bypass expected account disablement, re-enable dormant access, or introduce a new trusted login path.
Impact: Unauthorized login changes can lead to privilege escalation, persistence, loss of accountability, and unexpected access to databases and connected applications that trust the altered login.
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 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Covers lifecycle control over credentials and login authentication material. |
| AC-2 — Account Management | Defines governed creation, modification, and disabling of accounts and logins. | |
| AU-12 — Audit Record Generation | Supports traceability for privileged login changes and account-state modifications. | |
| Recommendation — Manage login credentials and reset processes so instance access changes stay controlled. Review who can create, alter, or disable logins and remove unnecessary account authority. Log login creation, modification, and removal events for review and investigation. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions | Addresses least-privilege access and permission governance for privileged actions. |
| DE.CM-09 — Monitoring for Unauthorized Behavior | Supports monitoring for unexpected changes to authentication identities and admin activity. | |
| Recommendation — Limit this permission to the smallest role set that genuinely needs instance-level login control. Alert on unusual login changes and review them as privileged-account activity. | ||
Practitioner Guidance
Why practitioners should care: Treat this permission as a high-risk administrative capability, not a routine server right. Its effect is indirect but immediate, because login changes alter the authentication surface that every dependent database and application may inherit.
Governance implication: Assign it only to roles that truly manage login lifecycle, and make sure every grant is reviewable, time-bound where possible, and tied to an explicit operational need. Where login changes are rare, the permission should be even more tightly constrained.
Practitioner takeaway: If you would not want someone to create or revive instance access without scrutiny, they should not hold this permission outside a controlled admin process.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
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.
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