The abuse of a legitimate user approval sequence so an attacker can bind their session to a valid identity. In practice, the attacker does not need to steal a password if they can control the page, timing, or context that leads the user to approve access.
Expanded Definition
Approval-path hijacking is a workflow attack against identity assurance, not a password attack. The attacker manipulates a legitimate approval sequence so a user, reviewer, or administrator approves a request that binds the attacker to a valid session, account, token, or delegated permission. In NHI environments, the “approval path” may include consent screens, device enrollment, admin grants, ticket-based authorization, chatops approvals, or just-in-time elevation flows.
Definitions vary across vendors, but the security boundary is consistent: the attacker must influence the context in which the approver decides, rather than defeating the authentication mechanism itself. This makes the attack especially relevant where agents, service accounts, and API-driven workflows rely on human sign-off or out-of-band verification. Guidance from NIST SP 800-53 Rev 5 Security and Privacy Controls is useful here because approval integrity, separation of duties, and auditability are core control expectations even when the approval path is implemented outside a classic IAM console. The most common misapplication is treating any signed-off request as trustworthy, which occurs when approvers cannot reliably verify origin, intent, or the exact resource being approved.
Examples and Use Cases
Implementing approval workflows rigorously often introduces friction, because stronger verification steps can slow access grants and increase reviewer burden, requiring organisations to weigh speed against assurance.
- A cloud admin receives a realistic prompt to approve an application consent request, but the request was routed through a spoofed domain that captures the resulting grant.
- A helpdesk technician approves a JIT elevation ticket after seeing a familiar incident title, while the attacker has already altered the underlying target identity.
- An AI agent is allowed to connect to a repository only after owner approval, yet the approval page is manipulated so the agent is bound to a broader scope than intended.
- A service account rotation request is “approved” in chatops, but the message thread has been hijacked and the approver is authorizing the wrong credential change.
These patterns are closely related to the governance failures described in NHI Mgmt Group research such as GitHub Personal Account Breach and the SpotBugs Token GitHub Supply Chain Attack, where trust in a legitimate workflow became the attacker’s entry point. When the term maps to access governance, NIST SP 800-53 Rev 5 Security and Privacy Controls helps frame approval logging, authorization, and accountability expectations.
Why It Matters in NHI Security
Approval-path hijacking matters because NHIs often inherit trust from the process that created them. If an attacker can steer a legitimate approval, they may obtain an API key, token scope, delegated access, or agent permission set without ever cracking a secret directly. That turns workflow integrity into a primary control surface for NHI security, especially in environments using SSO, SaaS admin approvals, secret distribution, or delegated automation.
NHI Mgmt Group data shows how severe this exposure can be: 97% of NHIs carry excessive privileges, and 79% of organisations have experienced secrets leaks, with 77% of those incidents causing tangible damage. Those figures matter here because approval-path hijacking often results in permissions that are broader than intended and harder to unwind after the fact. This is also why zero trust and least privilege are not enough on their own if the approval channel itself is weak. Organisations typically encounter the consequences only after an anomalous grant, token abuse, or lateral movement event, at which point approval-path hijacking becomes operationally unavoidable to investigate and contain.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST SP 800-63, NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-05 | Covers workflow abuse and unauthorized NHI authorization paths. |
| NIST SP 800-63 | Identity assurance guidance applies when approvals substitute for stronger verification. | |
| NIST CSF 2.0 | PR.AA-1 | Identity proofing and authorization integrity are directly implicated by hijacked approvals. |
| NIST Zero Trust (SP 800-207) | Zero trust requires continuous validation of trust decisions, including approval workflows. | |
| OWASP Agentic AI Top 10 | LLM-06 | Agentic systems can be tricked into unsafe actions through manipulated approval paths. |
Require explicit scope checks and human-verifiable approvals before agents execute privileged actions.
