TL;DR: As machine identities and AI agents increasingly retrieve data, execute workflows, and provision resources across enterprise systems, 1Password says it has acquired Apono to pair credential protection with just-in-time privileged access governance, according to 1Password. The shift matters because access review models built for stable human sessions do not fully fit non-deterministic actors that need governed access at the moment of action.
At a glance
What this is: 1Password’s acquisition of Apono is a governance move aimed at combining credential protection with just-in-time access control for humans, machines, and AI agents.
Why it matters: IAM teams need to rethink how access is granted and revoked when the actor can be a workload or agent, not just a person, because standing access and stable session assumptions no longer hold.
Context
Access governance is shifting from managing human logins to governing actions taken by machines and AI agents. In that model, the key question is no longer only who authenticated, but what the identity can do, for how long, and under what conditions.
1Password frames Apono as part of a broader move toward just-in-time privileged access and Zero Standing Privilege. The governance gap is that cloud workflows, service actors, and agentic systems operate continuously, while traditional access processes still assume access is stable enough to be reviewed after the fact.
That mismatch matters for NHI programmes because standing privilege, long-lived credentials, and delayed review cycles all become weaker controls when access must be granted at the moment of action.
Key questions
Q: What breaks when traditional vaults are used for AI agents and machine identities?
A: Vault models that assume infrequent human checkout break when agents and workloads consume secrets at machine speed. The result is either broad access that expands blast radius or per-secret vault sprawl that fragments governance. Identity teams need issuance, rotation and audit controls that follow the credential lifecycle, not a human checkout pattern.
Q: Why does just-in-time privileged access reduce risk for remote workers and administrators?
A: Just-in-time privileged access reduces risk because it replaces persistent credentials with temporary authorization that exists only for the task at hand. That means there are fewer leave-behind secrets to steal or share, less chance of misuse after access is no longer needed, and stronger control over who can reach sensitive systems. It also improves accountability through individual audit trails.
Q: How can teams tell whether access governance is actually working?
A: Look for short revocation times, low rates of stale entitlements, and repeatable access review outcomes across systems. If accounts remain active after role changes or offboarding, governance is not effective. Good measurement focuses on whether access is removed when it stops being justified.
Q: What is the difference between secret protection and privileged access governance?
A: Secret protection governs where credentials live and how they are released. Privileged access governance governs what an identity may do once access is granted, for how long, and under which conditions. Mature programmes need both because a secure vault does not by itself constrain downstream action.
How it works in practice
Why standing access breaks in dynamic enterprise workflows
Standing access means an identity keeps permissions continuously, even when it only needs them briefly. That model is workable for predictable human roles, but it becomes fragile in cloud systems where tasks are short-lived, resources are created on demand, and access needs change by step. Just-in-time access and Zero Standing Privilege reduce exposure by issuing permission only when the task starts and revoking it when the task ends. In identity governance terms, that shifts control from assignment time to use time, which is a material change in how privilege is managed.
Practical implication: move high-risk access from persistent assignment to task-scoped issuance and revocation.
How access brokering changes the secret-to-action path
The article separates two control points: where credentials are stored and how an identity is allowed to act once access is granted. That distinction matters because protecting a secret vault does not by itself govern what the requester can do in the target system. Access brokering adds a decision layer that checks the requester, the scope, and the duration before releasing a credential, token, or federated access. For NHIs and agents, that creates a control boundary around use, not just storage.
Practical implication: treat credential release and privileged action as separate control problems with separate audit trails.
Why AI agents and machine identities strain traditional access models
AI agents and machine identities do not behave like stable human users. They can retrieve data, execute workflows, and provision resources at runtime, which makes precomputed privilege models less reliable. The issue is not only volume, but non-determinism: the actor may need different access conditions depending on the task, context, or timing of execution. That means governance must account for ephemeral entitlement, policy decision points, and automatic revocation, rather than assuming an access review after the fact will capture the risk.
Practical implication: design controls for runtime entitlement decisions instead of relying on periodic recertification alone.
NHI Mgmt Group analysis
Just-in-time governance is becoming the baseline control for privileged NHI access. The article reflects a market shift away from persistent privilege toward task-scoped access for workloads and agents. That shift is not cosmetic: it acknowledges that cloud operations and AI-driven workflows now move faster than review cycles. Practitioners should treat standing privilege as the exception, not the default.
Access review assumptions break when the actor is a machine or agent. Access review processes were designed for access that persists long enough to be observed, certified, and removed later. That assumption fails when an identity acquires and discards access within the same operational task. The implication is that governance must move upstream to issuance time, not just certification time.
Credential protection and privilege governance are separate control planes. Protecting where secrets live does not solve what the recipient can do once a secret or token is released. The article usefully distinguishes secret custody from authorization scope, which is how mature NHI programmes should think about the problem. Practitioners should model both layers independently rather than collapsing them into one vault-centric control.
Zero Standing Privilege is now a governance pattern for non-human actors, not only for humans. As machine identities and AI agents become active participants in enterprise systems, the same access principles that limit human blast radius need to apply to software actors. This broadens the access-governance remit from HR-linked identities to runtime identities that may never have a stable user journey. The practical conclusion is that lifecycle and privilege governance must be unified across people, workloads, and agents.
Ephemeral access creates an identity blast-radius control problem. The named concept here is identity blast radius: how much damage an identity can do before access is revoked. In a world of dynamic workflows and autonomous execution, that blast radius is controlled less by broad role design and more by how narrowly access is issued, scoped, and terminated. Practitioners should judge programmes by how tightly they constrain the action window.
From our research library:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
- Read next: NHI Lifecycle Management Guide
What this signals
Identity blast radius: the useful question is no longer whether an identity can authenticate, but how far it can go before access expires or is revoked. That shifts programme design toward issuance-time controls, especially for workloads and agentic systems that act faster than human review cycles.
Access governance teams should expect more pressure to unify credential custody, task-scoped authorization, and auditability in one operating model. The organisations that treat machine identities and AI agents as first-class governed actors will have a clearer path to controlling privilege without slowing execution.
Only 44% of developers are reported to follow security best practices for secrets management, according to the State of Secrets in AppSec, which reinforces how much of the access problem still starts with everyday implementation behaviour rather than policy alone.
For practitioners
- Define task-scoped privilege boundaries Map every high-risk workflow to the minimum privileges needed at execution time, then remove persistent access where a task can be completed with just-in-time issuance.
- Separate secret custody from authorization Keep credential storage, release, and use under different controls so a protected vault does not become the only decision point for downstream privilege.
- Inventory machine and agent access paths Catalogue which workloads, bots, and AI agents can currently obtain standing permissions, and prioritise those with the broadest operational reach.
- Attach audit trails to access grants Require every privileged access grant to record requester, scope, duration, and revocation outcome so accountability survives beyond the session.
Key takeaways
- The core problem is not simply secret storage, but how access is granted and revoked when the actor is a workload or AI agent.
- The article ties the issue to a large and expanding actor set inside enterprises, where machine identities already outnumber human identities and non-deterministic access is becoming normal.
- The control that matters most is task-scoped privilege with automatic revocation, because persistent access creates unnecessary exposure for dynamic systems.
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 and MITRE ATT&CK define the specific risk controls and attack patterns relevant to this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | The article centers on replacing standing access with task-scoped privilege for non-human identities. |
| NHI-07 — Long-Lived Secrets | Credential Broker is positioned as a way to prevent long-lived secrets from spreading across systems. | |
| NHI-10 — Human Use of NHI | The article ties machine and agent access back to who is requesting and governing access, not just storage. | |
| Recommendation — Reduce persistent permissions and scope NHI access to the minimum required for each task. Shorten secret lifetime and control release so credentials are not broadly reusable across workflows. Separate human request paths from NHI execution paths and log each grant to the acting requester. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | Long-lived credentials and standing privilege expand paths for credential abuse and lateral movement. |
| Recommendation — Map standing privilege to credential-access and lateral-movement risk, then prioritise exposed access paths. | ||
Key terms
- Just-in-Time Access Request: Just-in-Time Access Request is a pattern that grants access only when it is needed and only for the duration required. It reduces standing privilege by making access temporary, policy driven, and task scoped. This approach is especially useful for contractors, sensitive systems, and short-lived operational work.
- Zero Standing Privilege: A control model in which an identity does not keep persistent access unless it is actively needed. For NHIs, this means credentials and permissions are issued for a narrow task and then removed. It reduces the time window and reuse value of stolen access.
- Credential Broker: A credential broker is a control layer that releases credentials, tokens, or federated access only after verifying the requester and the request context. It reduces secret copying by shifting access from static distribution to point-of-use delivery, which improves auditability and narrows exposure windows.
- Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
Published by the NHIMG editorial team on June 20, 2026.
Updated on October 10, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org