Topic starter
22/06/2026 10:08 am
TL;DR: Long-lived secrets copied into apps, pipelines, repositories, and agent workflows create governance and audit problems that credential brokering is meant to reduce, according to 1Password. The deeper issue is that access review and secret governance assume credentials persist long enough to be reviewed, but brokered access shifts control to the moment of use.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “1Password Introduces Credential Broker, Building a Secure Credentialing Layer for Humans, Machines, and AI Agents”.
Key questions
Q: What breaks when credentials are copied into apps and pipelines instead of brokered at use time?
A: Copied credentials create persistence, leakage and audit problems because the secret exists in too many places for governance to follow.
Q: Why does brokered credential delivery change IAM and PAM accountability?
A: Because the decision to release a credential becomes a distinct control event from the decision to allow privileged action in the target system.
Q: How do organisations know brokered access is actually under control?
A: Organisations know brokered access is under control when every connected provider account has an owner, a defined scope, an auditable reauthorization path, and a documented revoke process.
Practitioner guidance
- Define brokered credential issuance policies Specify which humans, workloads and AI agents may request credentials, which identity signals are required, and which artifact types can be released for each trust relationship.
- Remove copied secrets from pipelines and repositories Inventory where credentials currently live in apps, build systems, configuration files and environment variables, then replace those copies with brokered delivery where runtime access is needed.
- Separate issuance from downstream privilege Keep the credential broker focused on trusted delivery while downstream systems enforce least privilege, session scope and privileged task boundaries.
Bottom line: Credential sprawl remains the underlying risk when secrets are copied into runtime environments, pipelines and agent workflows.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/06/2026 10:54 am
Credential brokering exposes the limits of secret-centric governance. The central shift is from managing where credentials sit to managing when and to whom they are released. That matters because copied secrets create audit blind spots across apps, pipelines and agent workflows, while brokered access creates an issuance record that is easier to govern. Practitioners should read this as a control-model change, not just a new distribution method.
A few things that frame the scale:
- Only 44% of organisations are currently using a dedicated secrets management system, according to the 2024 State of Secrets Management Survey.
A question worth separating out:
Q: What is the difference between credential brokering and downstream privileged access control?
A: Credential brokering governs whether a trusted requester receives a credential or token. Downstream privileged access control governs what that identity can do inside the target system after the credential is presented. They are complementary controls, but they solve different governance problems.
👉 Read our full editorial: Credential brokering for humans, machines and AI agents