A community-driven list of the most important security risks affecting non-human identities such as service accounts, API keys, OAuth apps, and AI agents. It gives security teams a common language for prioritising controls, comparing weaknesses, and building a structured NHI programme around the risks most likely to drive real exposure.
What the OWASP NHI Top 10 is for
The OWASP NHI Top 10 is a prioritisation model, not a product or a control standard. Its value is that it gives teams a shared vocabulary for the most consequential risks in non-human identity estates, so security work can be ordered by exposure rather than by whichever issue is easiest to spot first.
Because it is risk-led, the framework helps organisations compare very different failure modes on the same page: leaked secrets, excessive privilege, weak offboarding, risky third-party integrations, and other conditions that can turn machine access into an entry point.
The project is most useful when an NHI programme needs a common reference point for security leadership, platform teams, and operations teams to agree what “good” should look like.
How the OWASP NHI Top 10 structures NHI risk
The model works by grouping recurring patterns of NHI weakness into a short list that practitioners can remember and act on. That makes it easier to identify whether a problem is really about discovery, authentication, privilege, secret handling, lifecycle, or trust boundaries, rather than treating every incident as a one-off event.
That structure matters because NHI exposure often spreads across service accounts, API keys, OAuth apps, workload identities, and automation. A single weakness can therefore affect many systems, and Top 10 NHI Risks is a useful companion for understanding how those risk patterns appear in real breaches and what the first control usually needs to address.
For readers comparing related material, the external project page for the OWASP Non-Human Identity Top 10 remains the canonical public reference for the list itself.
Why this list matters in operational security
The practical value of the Top 10 is that it converts a broad governance problem into a repeatable security conversation. Teams can use it to decide what to inventory first, where to add ownership, which secrets need stronger handling, and which permissions are too broad for the system’s real function.
It also helps separate symptoms from root cause. For example, a leaked token is not just a secret-management issue if the underlying problem is poor lifecycle ownership, weak rotation, or an integration that keeps old credentials alive long after they should have been revoked. Ultimate Guide to NHIs — Key Challenges and Risks is useful here because it connects visibility gaps, over-privilege, and unmanaged credentials to the same operational picture.
The same framework also helps security teams align on where NHI security overlaps with broader identity governance, especially when human and non-human access patterns are mixed in the same workflow.
How practitioners should read and apply the list
Practitioners should treat the OWASP NHI Top 10 as a prioritisation lens for design reviews, backlog planning, and security assessments, not as a checklist to complete once and file away. Its best use is to keep attention on the risks that most commonly drive real exposure in production environments.
That means reading each item against actual estate conditions, such as shared ownership, long-lived secrets, third-party integrations, missing inventory, and high-impact automation. The list is especially helpful when used alongside NHI discovery, ownership, and rotation work, because those controls determine whether a risk can be reduced in practice or merely documented.
A strong programme uses the Top 10 to force specificity: which identities exist, who owns them, how they authenticate, what they can reach, and how quickly they can be removed or rotated when something changes.
How the OWASP NHI Top 10 relates to other security work
The Top 10 sits between strategy and implementation. It is broad enough to inform executive prioritisation, but concrete enough to shape engineering decisions about secrets, access, and lifecycle management.
That makes it a useful bridge to adjacent work such as machine identity governance, authentication design, and access review. For teams building a deeper operating model, Non-Human Identity (NHI) Guide provides the broader context, while NHI Authentication Guide explains the mechanisms that often sit behind the risks the Top 10 highlights.
The point is not that every organisation needs a separate framework for every control family. The point is that this list gives NHI work a stable risk vocabulary so controls, ownership, and remediation can be discussed against the same priorities.
Risk and Threat Considerations
The main risk is that teams treat NHI exposure as an inventory problem when it is often an attack-path problem. A leaked key, an overprivileged service account, or a poorly governed OAuth app can give an attacker durable access that is harder to detect than a human login.
Failure mechanism: weak offboarding, excessive privilege, long-lived secrets, or poor third-party governance lets compromise persist after the original misuse should have been stopped.
Impact: attackers can reuse non-human access for lateral movement, data access, token theft, or repeated abuse across connected systems, turning a single exposed identity into a broader compromise.
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 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Directly addresses leaked secrets, a core OWASP NHI risk pattern in this term. |
| NHI-05 — Overprivileged NHI | Directly maps to excessive privilege, one of the central NHI risk patterns named by the term. | |
| NHI-01 — Improper Offboarding | Supports lifecycle risk in non-human identities when unused or orphaned access persists. | |
| Recommendation — Detect and eliminate exposed NHI secrets, then rotate and revoke any credentials that may have leaked. Reduce NHI entitlements to the minimum needed and remove standing excess privilege. Revoke and disable dormant NHI access paths promptly when the identity is no longer needed. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | NHI risk often turns on secret issuance, rotation, revocation, and lifecycle management. |
| Recommendation — Manage NHI authenticators through controlled issuance, rotation, and revocation. | ||
| CIS Controls v8 | CIS-5 — Account Management | The term is fundamentally about governing machine and application accounts across their lifecycle. |
| Recommendation — Inventory and govern non-human accounts so access can be reviewed and removed on time. | ||
Practitioner Guidance
Why practitioners should care: the OWASP NHI Top 10 is most valuable when it becomes the organising structure for ownership and remediation, not just a slide in a security presentation. Teams should use it to decide which NHI risks deserve first attention in backlog planning and risk reviews.
Common misunderstanding: many organisations assume the hardest problem is finding every NHI, when the more important issue is understanding which of those identities can still do damage if they are leaked, reused, or forgotten. The list helps keep attention on exposure, not just count.
Practitioner takeaway: use the Top 10 to anchor one shared remediation conversation across security, platform, and application owners, so the same risk language drives discovery, privilege reduction, and cleanup.
Related resources from NHI Mgmt Group
- How should security teams use the OWASP NHI Top 10 to prioritise risk reduction across service accounts, API keys, and OAuth apps?
- What are the core risks identified by the OWASP Agentic Top 10?
- How should IAM and AppSec teams work together on OWASP Top 10 findings?
- How should security teams evaluate MCP runtimes against the OWASP Top 10?
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 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org