1Password: the factory infographic
Passwords and secrets for 150,000 businesses, now including the AI agents that log in on their behalf.
What the company does
In normal terms
Secures every identity, from people to AI agents: passwords, passkeys and secrets for over 150,000 businesses, and a security layer for how agents authenticate and connect to the internet.
1Password is building a security layer for how agents authenticate and connect, so agent credentials are held and handed out like human ones.
In lay terms
1Password is a safe for keys. Now it also hands keys to AI assistants, so they can open the doors they need without anyone writing passwords on sticky notes.
The risks it faces, especially from AI agents
In normal terms
- A key that opens too much. An agent given a vault item or broad token inherits everything that credential can reach, far beyond its task.
- Credentials outlive the task. Long-lived secrets issued to agents stay valid after the work ends or the agent is replaced.
- Who used the key?. Shared or delegated credentials blur attribution between the person, the agent and the session.
In lay terms
- A key that opens too much. Give the assistant the office key and it can open the finance room too.
- Credentials outlive the task. The temp left, but their key still works.
- Who used the key?. If three people share one badge, the log can't say who went in.
How RiskMandate helps
- Reachwhat it can actually access or affectWhich secrets and vault items each agent can retrieve, and what they unlock.
- Mandatewhat the business authorisedThe few credentials the agent's job actually needs.
- Gapthe difference: the riskSecrets in reach but outside the mandate: the first thing to cut.
- Barrierswhat really stands in the wayScoped, short-lived credentials from 1Password as technical evidence.
- Provenancewho owns it, who reviewed it, which versionThe person who granted each credential and when it was reviewed.
In normal terms
RiskMandate turns 'what can this agent unlock' into a reviewed record per agent, so 1Password's controls map to a stated mandate. Customers get a reason for each grant, and a gap list to close.
In lay terms
1Password hands out the keys; RiskMandate keeps the list of which keys each assistant should have, and spots the spare ones.
A first line for the conversation: You hand agents their keys. We write down which keys each agent should have, and show the gap. Could we map one of yours?
Sources and method
The facts in grey (what it does) are from the company map, which cites:
- websummit.com, read 2026-11-01: LIS26 appearance page: name, country, industry, website
- websummit.com, read 2026-11-01: listed on the 2026 event partners list with its elevator pitch (the "what" field)
- websummit.com, read 2026-11-01: Developer Summit track page names 1Password (Nancy Wang) among featured speakers; may be a past-edition highlight
The risks and how RiskMandate helps are our analysis, written by dev@web-summit.indi on 3 November 2026 from those facts and RiskMandate's model as this site explains it (Reach, Mandate, Gap; an Agent Behaviour Policy in practice). They are not the company's own statements and name no incident. A person reviews each before it is used.