Skip to main content

← Back to glossary

Term · 10. Account Types

Non-Human Identity NHI

A non-human identity (NHI) is any credential that authenticates a machine rather than a person — service accounts, API keys, OAuth client secrets, machine certificates, workload identities (AWS IAM roles, Azure managed identities, GCP service accounts) and AI agents. NHIs outnumber human identities roughly 45:1 and need their own governance, lifecycle and offboarding, codified by the OWASP NHI Top 10 (2025).

IDM/IGA Domain
Identity Security NHI DORA NIST OWASP Introduced by: Gartner Introduced by: KuppingerCole Introduced by: Big4 (Deloitte / PwC / EY / KPMG)

Definition

Identities for service accounts, API keys, OAuth client secrets, machine certificates, workload identities (AWS IAM roles, Azure managed identities, GCP service accounts), AI agents, IoT devices — anything without a human employment lifecycle. Outnumber human identities 45:1 in typical enterprises (CyberArk 2024 research). Subject to OWASP NHI Top 10 (2025) risk catalogue.

Application
MidPoint: Non-human identity (NHI) is an identity that represents entity that is not human (physical person).

SailPoint: Service Account aggregation + custom Application onboarding for NHI types
Sources
FAQ

Frequently asked questions

What is a non-human identity (NHI)?

A non-human identity authenticates a machine or workload rather than a person — service accounts, API keys, OAuth secrets, certificates, cloud workload identities and AI agents. Unlike employees, NHIs have no joiner-mover-leaver lifecycle, so they need a separate governance model.

Why are non-human identities a security risk?

NHIs outnumber humans about 45:1, are often over-privileged, and rarely get offboarded when their workload ends — leaving long-lived credentials. The OWASP NHI Top 10 (2025) catalogues the main risks, from secret leakage to improper offboarding.

How do you govern non-human identities?

Inventory every NHI and assign an owner; rotate and vault secrets instead of embedding them in config; apply least privilege; and offboard NHIs when the workload retires. An IGA platform extends joiner-mover-leaver controls to service and workload identities.