1Password Developers

Grateful for the opportunity to speak with our friends at @lightspeedvp about our journey at @1Password .

This is becoming clear. Reduce blast radius. Harden credential security. Find standing access and exposed credentials. Treat agents as privileged actors with scoped, traceable access. Do it now.

Every day now seemingly brings another breach, and the postmortem almost always ends the same way. A credential was compromised, and it could reach far more than it should have. We spend enormous energy trying to prevent the breach. Prevention matters, but I think we ask the wrong question afterward. The question is not only how did they get in. It is why did one stolen credential open so much. Breaches are inevitable. Blast radius is a choice. Every standing credential in your environment is pre-authorized damage. The API key on a hard drive that never expires. The token sitting in a config file. The agent running with persistent access to systems it touches once a month. When one of them leaks, and one of them will, the damage was decided by choices made months earlier. So what can we do? Secure exposed credentials. Give every identity, human or agent, only the access it needs, only for as long as it needs it. Know where every credential lives, who owns it, and how to revoke it. Agents make this urgent. Handing an agent your credentials is not automation. It is delegation without accountability. You cannot shrink a blast radius you cannot see. Start by looking. How much standing access do you have? Most teams I speak with cannot answer that today. That gap is the risk. Breaches are inevitable. What happens next is up to us.