A non-human identity for an AI agent is a unique login for the agent itself, not a copy of yours. NIST 2026: own identifier, credentials, entitlements. If it uses your password, that is impersonation.
A non-human identity for an AI agent is a unique login for the agent itself, not a copy of yours. It has its own identifier, its own credentials, a named owner, a list of what it may touch, a log of what it did, and a way to revoke it without firing a person. If the agent uses your password, you do not have an NHI. You have impersonation.
I am Amelia S. Gagne, CEO of Kief Studio. I study behavioral psychology and I build AI applications. Diffusion of responsibility is the human version of a shared API key: when everyone could have done it, nobody did. This URL defines NHI in operator English. Sequence-level governance is the sibling: AI agent governance that checks the path, not only the click.
Put the agent on the org chart. A service account, a workload identity, a certificate, a short-lived token: those are NHIs when they name a thing that is not a person. An AI agent that can refund, post, or query production is one more of those things. NIST (Fisher and Galluzzo, 27 Aug 2026) wrote that credential sharing with agents creates accountability gaps, especially where non-repudiation matters.
Vendor surveys now quote NHI-to-human ratios in the tens to one. Treat those as direction, not your headcount. You do not need the ratio. You need an inventory: every key, bot, and agent that can act.
I study behavioral psychology because this is a responsibility design. Shared credentials feel efficient. They also spread blame until an incident has no author. That is not a scare story. It is how groups fail at boring tasks.
It is not a second MFA prompt on your laptop. It is not "we have Okta." It is not a long-lived API key in a markdown file. NIST's same post flags static and long-lived credentials as a pattern that already caused incidents, now scaled by agents. Short-lived, scoped tokens exist today: OAuth, SPIFFE, sender-constrained tokens. You do not wait for a new religion of identity.
Okta's NHI lifecycle explainer is a vendor page, but the lifecycle idea is right: create, review, retire. Humans get an HR offboarding ticket. Agents often do not. That is why keys outlive internships.
This sits next to data governance where to start and vendor security questions. If a vendor cannot issue the agent its own identity, you are renting impersonation. kief.dev is where we publish engineering hygiene. Brian's write-up on briansgagne.com is the deeper IAM architecture when you need it.
NIST also flags local agents running as the user's account: convenient for coding, fatal for non-repudiation. If the agent can open the terminal as you, the log is you. Sandbox it or give it a separate identity that cannot reach payroll. Consumer tools will keep making the insecure path easy. Your job is to make the named-agent path the default for anything that touches money, patients, or production.
OWASP's agentic application work (late 2025) put identity and privilege abuse in the top categories. You do not need the full top ten to start. You need "this bot is not me" in the directory. kief.studio will not sell you a new identity religion. We will put the agent on the chart the same week we put it in production.
It can be, if it is unique to the agent, owned, scoped, logged, and revocable. A shared "deploy" account used by people and bots is not an NHI. It is a group password.
Because the record will say you acted. NIST calls that an accountability gap. Refunds, health data, and money need a named actor.
No. Start with inventory, named owners, and stop using personal passwords in agents. Buy tooling after you know how many NHIs you already have.
Least privilege is how much access. NHI is who the access belongs to. You need both. Privilege on a borrowed human identity still impersonates.
Five Eyes agentic AI guidance for a small business is five moves: low-risk task, distinct identity, least privilege, human gate, logs plus a kill switch. CISA, NSA, and allies published Careful Adoption of Agentic AI Services on 1 May 2026.
AI pilots stall before production for boring reasons: no owner, no definition of done, no data path, no kill switch. CISA 1 May 2026: start low-risk. NIST AI RMF: Govern, Map, Measure, Manage.
AI agent governance fails when you approve each click and miss the path. Five in-policy refunds can still empty the drawer. Store intent, cap the run, gate pay/send/delete.
Work With Us
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe
