Join our Newsletter — 33% off our NHI Course
Governance, Ownership & Risk

Scope Creep

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

Scope creep is the gradual expansion of what a delegated application can do beyond its original purpose. In OAuth environments, it usually appears as broader permissions, extra APIs, or added administrative reach that increase the blast radius of a compromise.

What Scope Creep Means in OAuth and Delegated Access

Scope creep is not just “more access.” In delegated OAuth setups, it is the gradual widening of what an app, integration, or agent can do after the original grant, through broader scopes, extra APIs, or administrative privileges. The result is a larger trust boundary than the one the business originally approved.

That expansion matters because delegated access often starts narrow and then accretes exceptions. A report exporter becomes a data reader, a workflow tool becomes a writer, and a support integration becomes a privileged admin path. The security problem is not the first permission, but the accumulated reach.

How Scope Creep Develops

Scope creep usually appears when teams add functionality faster than they review permissions. New API calls get bundled into an existing app, a vendor requests a wider consent prompt for convenience, or a service account is reused for multiple purposes. Each change may look small, but together they change the original security posture.

In practice, this often reflects missing ownership of the permission baseline. If nobody periodically asks what the integration actually needs, the granted scope tends to grow with product features, troubleshooting shortcuts, and informal approvals. That is why scope creep is often gradual and easy to miss.

Why Scope Creep Increases Blast Radius

Every additional scope can expose more data, more actions, or more administrative reach if the delegated app is compromised. In OAuth environments, that can mean reading mail, modifying files, pulling customer records, or invoking management APIs that were never necessary for the original use case. The blast radius grows because the token is now accepted in more places.

This is especially dangerous when the delegated principal can act across systems or tenants. A compromise is no longer limited to a single function, because the token reflects accumulated trust rather than a tightly bounded purpose. Scope creep therefore turns convenience into concentration risk.

How to Control and Review It

Scope creep is controlled by continuously comparing granted permissions with actual business need. The useful question is simple: does this app still need every scope it has, and does each permission still match a documented function? If not, the permission set should be reduced, split, or reapproved.

Teams should also treat consent reviews, app inventories, and privilege recertification as routine work rather than one-time setup tasks. Where a permission is only needed for a special workflow or an exception, it should be isolated instead of becoming the default operating model. For a practitioner-focused view of how permission drift expands across delegated systems, see Agent Permission Drift. For a broader external reference on non-human identity risk patterns, compare that with the OWASP Non-Human Identity Top 10.

Risk and Threat Considerations

Scope creep creates a larger attack surface because a single compromise can inherit every permission that was added over time. It also makes consent prompts and admin grants easier to overlook, which helps attackers abuse trusted integrations, replay stolen tokens, or pivot into systems that were never part of the original use case.

Failure mechanism: Permissions expand quietly, review cycles lag behind functional changes, and the delegated app ends up with broader token rights than the operator intended. Once an attacker obtains the app, token, or consented integration, they can use those accumulated scopes to move laterally or extract more data than the original workflow required.

Impact: The compromise of one delegated application can become a multi-system incident, with data exposure, unauthorized actions, and harder incident containment because the permission set no longer reflects a single clear purpose.

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 API Security Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-05 — Overprivileged NHIScope creep is the gradual move into overprivileged delegated access.
NHI-09 — NHI ReuseScope creep often grows when one app or credential is reused for multiple purposes.
Recommendation — Review and shrink delegated permissions to enforce least privilege. Separate trust boundaries instead of reusing one integration for multiple jobs.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationExtra scopes often grant functions the caller should not perform.
Recommendation — Map each delegated action to explicit function-level authorization checks.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeScope creep is a least-privilege failure in delegated access.
IA-5 — Authenticator ManagementExpanded delegated access often depends on credential and token lifecycle control.
Recommendation — Limit each integration to the minimum permissions required for its purpose. Rotate and revoke tokens and secrets when delegated access changes.

Practitioner Guidance

Governance implication: Scope creep is best managed as a lifecycle problem, not a one-time configuration choice. Owners should be named for every delegated integration, and permission changes should follow the same approval discipline as new access requests.

What to watch for: Watch for apps that accumulate broad scopes, unused permissions, repeated “temporary” exceptions, or administrator consent granted to solve a short-term issue. Those are the clearest signs that delegated access has drifted beyond its intended purpose.

Practitioner takeaway: The safest delegated app is usually the one whose permissions still look boring six months later.

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