GlossaryLast checked 16 October 2026 with AI-assisted research. Editor: Akshay Dubey.Corrections logEditorial policy
On this page
  1. Definition
  2. Relation to NHI and machine identity
  3. Why the term matters
  4. FAQ
  5. Sources

A non-person entity (NPE) is a term from US federal identity and security usage for anything with a digital identity that acts in cyberspace but is not a human: devices, software, services, processes and, in the formal definition, organisations and information artifacts. It is broader than the industry term non-human identity.

Definition

The NIST Computer Security Resource Center glossary gives this definition, sourced to CNSSI 4009-2022 (adapted from DHS OIG 11-121) and ICS 500-30:

An entity related to information technology with a digital identity that acts in cyberspace, but is not a human actor. This can include organizations, hardware objects (physical entities/devices), software objects (virtual/logical entities), and information artifacts.

The US Department of Defense Enterprise ICAM Reference Design (version 1.0, June 2020) uses the term for non-person entities that require access to resources, and states that "NPEs include physical devices, systems, and processes that are assigned identifiers". NIST SP 800-207, Zero Trust Architecture (August 2020), has a section titled "Use of Non-person Entities (NPE) in ZTA Administration".

Relation to NHI and machine identity

TermWhere it comes fromScope (as used on this site)
Non-person entity (NPE)US federal usage: CNSSI 4009, DoD ICAM, NISTAnything with a digital identity that is not a human, including organisations and information artifacts
Non-human identity (NHI)Industry and OWASP usageAn identity used by software, a workload, a device or an AI agent: service accounts, workload identities, cloud roles, agent identities
Machine identityPKI and analyst usageOn this site, the narrower part of NHI that is identified through certificates and keys (the PKI view); the certificates and keys themselves are credentials

In practice, most NPEs that an identity team governs are NHIs. The difference is at the edges: the federal definition also covers organisations and information artifacts, which an NHI programme would not normally inventory. If you work with US federal customers or answer to DoD or federal zero trust guidance, expect NPE in requirements and map it to your NHI inventory explicitly rather than assuming the two lists are the same.

One distinction holds in both vocabularies. The entity is not its credential. A device or service is the NPE; the certificate, key or token it presents is a credential it holds. That mirrors this site's rule that API keys, tokens, certificates and secrets are credentials held by identities, not identities themselves.

Why the term matters for governance

The same governance questions apply whatever the label: who owns the entity, what it may do, and how its access is revoked. See assigning an owner to every non-human identity and the full NHI glossary.

Frequently asked questions

What does NPE stand for in identity management?

NPE stands for non-person entity. In US federal usage, defined in CNSSI 4009-2022 and reproduced in the NIST glossary, it is an entity related to information technology with a digital identity that acts in cyberspace but is not a human actor, such as devices, software objects, organisations and information artifacts.

Is a non-person entity the same as a non-human identity?

They overlap heavily but are not identical. NPE is a US federal term that also covers organisations and information artifacts. Non-human identity, as used on this site, means identities used by software, workloads, devices and AI agents. Most NPEs an identity team governs are NHIs, but map the two lists explicitly.

Is a certificate a non-person entity?

No. The device, service or workload is the entity; the certificate, key or token it presents is a credential it holds. This site keeps the same distinction for non-human identities: credentials such as API keys, tokens, certificates and secrets are held by identities and are not identities themselves.

What does the CISA Zero Trust Maturity Model say about non-person entities?

CISA's Zero Trust Maturity Model version 2.0 (April 2023, guidance for US federal agencies) defines an identity as attributes that uniquely describe an agency user or entity, "including non-person entities". Its Identity pillar has four functions: Authentication, Identity Stores, Risk Assessments and Access Management. Its automation row starts with agencies manually onboarding, offboarding and disabling users and entities, and ends with automated orchestration of all identities. It names no specific service account control.

Does NIST SP 800-63-4 apply to service accounts or machines?

Not directly. NIST SP 800-63-4, Digital Identity Guidelines (final, dated July 2025), says in Section 1.1 that "person" refers only to natural persons, and that the guidelines do not explicitly address machine-to-machine authentication, IoT devices or API access on behalf of subjects. For service and device authentication, the closer NIST reference is SP 800-53, controls IA-3 and IA-9.

Sources

Monthly change log

Know when the NHI landscape changes.

One email a month from this reference: new deals, standards status changes and corrections. No sponsored content. Unsubscribe from any email.

We first email you a link to confirm. Privacy policy.