The security architect's first design question about any action is who the actor is, on whose behalf it acts and how the receiving system can tell. For people the identity provider gives a mature answer. For non-human actors the answer is usually credentials created for a project, copied into configuration and never retired, with an audit trail that names an account rather than a person. When an agent acts in production with such a credential, the organisation loses accountability as well as gaining attack surface, because nobody can say who decided that the action should happen.
This chapter concerns three of the four shifts. It belongs to Shift 1, from documents to code, because an identity is a versioned record that a broker reads and a policy point enforces. It belongs to Shift 2, from gatekeeper to boundary designer, because identity is the boundary that holds whatever an actor intends: the architect designs who may be an actor, what each may do and who answers for it, rather than approving each request. And it belongs to Shift 3, from periodic to continuous, at machine speed, because credentials that live for minutes and revocation within a minute replace the annual access review. Chapter 7 placed the boundaries around actors; this chapter owns who an actor is and how that is proved.
The chapter builds on the earlier volumes. AI Governance, Chapter 14, introduced the agent operator, who watches Mode 5 agents and may revoke their credentials, and its Chapter 19 concluded that the July 2026 OpenAI–Hugging Face incident failed through correlated controls (162, Nordqvist, 2026), the first of which, according to the incident reports, was a credential shared across many workloads (127, OpenAI, 2026) (128, Larcher et al., 2026). AI Platform and Security, Chapters 12 and 19, concluded that agents hold task-scoped credentials and no ambient authority (163, Nordqvist, 2026). AI Red Team, Chapters 6 and 14, concluded that every machine identity has an owner, operators and an authority who are named people, and that approvals are confirmed by call-back rather than by appearance (164, Nordqvist, 2026).
Primary topics explored
- Non-human actors outnumber people
- Workload identity
- Agents with their own identity or with a person's
- Delegated authority
- Owners, operators and authorities
- Approvals that resist synthetic media
About The Transformed Security Architect
The Transformed Security Architect is Book 6 of The Transformed Architecture. It describes how the security architect role is transformed when architecture is code, when AI drafts and acts, and when adversaries move at machine speed: the craft, the architect's own AI team, the role in the organisation, the competences and the career, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team and AI Threat.
Security architects, CISOs and heads of security architecture, enterprise, solution and AI architects, engineering leads, competence and hiring leads, procurement and programme leaders, and risk, compliance and audit.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 8: Identity Architecture for Non-Human Actors: Workloads, Agents and Delegated Authority in The Transformed Security Architect gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Craft” and is one of 31 drawn from the manuscript.