Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Reset Password Extended Right
Governance, Ownership & Risk

Reset Password Extended Right

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

Reset Password Extended Right is an access control permission that lets one account reset another account's password without knowing the existing password. It is used in directory and IAM systems to support help desk recovery or delegated administration, and it can bypass normal authentication if granted too broadly.

What the permission does and why it matters

Reset Password Extended Right is a delegated administrative permission, not a recovery feature in itself. It changes who can set a new secret for another account, which is powerful because it can restore access quickly, but also dangerous because it can override the account owner’s normal authentication path if granted too broadly.

In practice, the right is usually intended for a constrained help desk or admin role. The security problem is not the existence of reset capability, it is whether the permission is scoped to the smallest feasible set of operators, objects, and administrative boundaries. When that scope is loose, the right becomes an easy path to account takeover inside the directory.

Where it shows up in directory administration

This permission appears in directory and IAM designs that support delegated help desk work, break-glass recovery, or tiered administration. It is often attached through ACLs, OU inheritance, or other delegation models, which means the effective access can be broader than the person who granted it originally expects.

Because the right is evaluated by the directory itself, the practical question is not only who can use it, but where it is inherited and whether protected objects are excluded. A reset right on the wrong container can reach far more accounts than a team intended, especially in environments with complex group nesting or legacy delegation.

For design and hygiene patterns around dangerous directory permissions, the Active Directory ACL and Delegation Hygiene Guide is the most direct reference point, and the broader Active Directory Delegation guide shows how to structure help desk delegation more safely.

How exposure is checked and constrained

Exposure review starts with inventorying where the permission exists, then tracing inheritance, explicit ACEs, and delegated admin groups that can exercise it. Organisations should also check whether the permission is reachable on internet-facing identity surfaces, exposed through cloud sync bridges, or embedded in legacy delegation that no one actively owns.

Vendor guidance and directory documentation should be used to confirm the intended delegation model, but the most important control is local evidence: which accounts have the right, on which objects, under which inheritance path. In mature environments, the review is paired with change logging so that new grants, reassignments, and accidental broadening are visible quickly.

Operational impact when the right is abused

If an attacker or malicious insider gains this permission, they may reset a target account and immediately move into that identity’s mailbox, applications, or admin console without needing the previous password. That is why the permission is often treated as a privilege-escalation primitive rather than a simple convenience for support staff.

After a reset, the security consequence depends on what else was tied to the account: active sessions, MFA enrolment state, recovery options, and downstream application tokens may still need to be invalidated. If the reset was part of a compromise, the affected account and any sibling administrative paths should be reviewed for persistence, not just the password value itself.

What good control looks like

The safest pattern is narrow delegation, explicit ownership, and routine review of who can reset which classes of account. Help desk staff should have the minimum practical delegation, with protected administrator accounts, sensitive groups, and break-glass accounts excluded wherever possible.

Where password reset is part of a broader recovery process, organisations should pair the permission with strong verification, alerting, and logging so that each reset is attributable and reviewable. The Account Recovery and Help Desk Security Guide covers the surrounding verification controls, while the Help Desk Social Engineering Incident Playbook shows how reset abuse is investigated and contained.

Risk and Threat Considerations

A reset right is valuable to defenders because it restores access quickly, but that same speed makes it attractive to attackers who can social-engineer support staff, abuse overbroad delegation, or compromise an admin with reset authority. The main risk is that one permission can bypass the normal password-based control plane and turn a directory recovery function into an account takeover path.

Failure mechanism: Broad inheritance, weak caller verification, or excessive delegation lets a malicious actor reset a target account and then pivot into sessions, email, SaaS apps, or administrative workflows linked to that identity.

Impact: The result can be privilege escalation, persistence, lateral movement, and loss of trust in the directory, especially when high-value admin accounts or help desk operators are in scope.

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, NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeReset rights are privileged access that should be narrowly delegated.
IA-5 — Authenticator ManagementThe term concerns resetting account secrets and related credential lifecycle handling.
AU-12 — Audit Record GenerationDirectory reset grants and reset events need auditable traceability.
Recommendation — Restrict password reset delegation to the smallest necessary admin roles. Manage password reset authority as part of credential lifecycle control. Log reset-right grants and password reset events for review.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication and Access ControlDelegated reset authority is an access-control decision for identities.
Recommendation — Apply identity and access controls to constrain reset privileges.
CIS Controls v8CIS-6 — Access Control ManagementThe subject is a high-risk access delegation that must be governed.
Recommendation — Review and revoke unnecessary reset permissions across directory roles.

Practitioner Guidance

Governance implication: Treat this permission as a high-risk delegated privilege, not a routine support setting. Define exactly which roles may hold it, which account classes it may affect, and which objects must never inherit it.

What to watch for: Repeated resets by the same operator, resets on privileged accounts, or unexpected changes to delegation paths often indicate either process drift or abuse. Pair the permission with alerting on directory permission changes and with post-reset session review so that the reset itself does not become the end of the investigation.

Practitioner takeaway: If you cannot explain why a given group needs this right, and on which objects, it is already too broad.

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