Standing access is the thing every identity audit finds and no one remembers granting. An engineer gets a role for a migration, the migration ends, the role stays. A service account picks up a permission to unblock a deploy, and nobody removes it afterward. 1Password built Privileged Access, Credential Broker's move to public preview, and a pending Snowflake integration around a single mechanism for closing that gap: grant access at the moment of the task, and take it back the moment the task ends.

The company's own AI Agent Governance survey puts a number on the problem the products target. Forty percent of developers grant AI agents persistent access to systems or credentials, meaning access that is never revoked once the task that required it is finished. That statistic is not a marketing flourish. It describes the exact failure mode Privileged Access is engineered to close, and it gives a chief information officer a concrete baseline to measure against once the product is running.

1Password Privileged Access extends the company's Unified Access platform into privileged access management, provisioning permissions directly in a target system's native policy layer rather than replacing the tools a security team already runs. It is built on Apono, the just-in-time access startup 1Password acquired in June. Chief Executive Officer David Faugno framed the goal plainly: "access must be granted for a specific task," with permissions revoked automatically once that task ends (1Password, 2026).

How the product works matters more than the positioning. Discovery scans cloud, database, and Kubernetes environments for access that has accumulated and gone unreviewed. Provisioning happens at request time, scoped to the task. Every request, approval, and access event logs with attribution sufficient for SOC 2, HIPAA, PCI-DSS, ISO 27001, and GDPR evidence. Just-in-time access and zero standing privilege are established ideas in privileged access management. The difference here is applying them from the start to identities that are not human, with agents named alongside employees and service accounts in the product's own framing.

1Password Credential Broker addresses a narrower but related gap: credentials that get copied into pipelines instead of requested at runtime. It exited private beta and entered public preview for GitHub Actions, issuing credentials scoped to a single workflow run rather than leaving long-lived static secrets sitting in configuration files. GitHub's Ben De St. Paer-Gotch, Director of Product Management, called the goal eliminating secrets from pipeline configurations to reduce the risk of credential theft (1Password, 2026).

Public preview is not general availability.

Teams evaluating the product today can only test what is currently available. Credential Broker supports GitHub Actions and custom OpenID Connect configurations, with the roadmap for machine workloads and AI agents still ahead. A team piloting the product should scope the test to what is shipping, GitHub Actions credential delivery, rather than the fuller cross-agent vision the product name implies.

The Snowflake integration applies the same access model to a different problem: third-party agents reaching into Snowflake's environment from outside it. 1Password named the integration alongside its own July launch, with general availability scheduled for the second half of 2026. Snowflake's own Black Hat 2026 announcement places the work inside a broader effort called Cortex AI Gateway, where most of the new agent governance controls, including the third-party identity integrations, are listed at private preview rather than general availability (Snowflake, 2026). Snowflake Chief Security and Trust Officer Mayank Upadhyay described the goal as establishing a secure foundation for agent interoperability (1Password, 2026). That direction is necessary as more vendors' agents begin calling into shared data platforms without a common trust layer between them.

Enterprises running both platforms have reason to track that roadmap now. A partnership scheduled for future delivery answers a different evaluation question than a product already provisioning access in production.

The survey's sample, 500 information technology and security professionals and 500 developers at United States firms with at least 250 employees, is large enough to support its headline figures but says nothing about whether the 40 percent persistent-access finding holds at smaller companies or outside the United States. 1Password has not published a breakdown by company size. Whether Credential Broker's public preview converts to general availability on a fixed timeline, or how quickly the Snowflake integration extends beyond its initial scope, is also not yet disclosed.