Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Credential brokerage
Threats, Abuse & Incident Response

Credential brokerage

← Back to Glossary
By NHI Mgmt Group Updated October 23, 2026 Domain: Threats, Abuse & Incident Response

Credential brokerage is the unauthorized resale, sharing, or trading of stolen login details, tokens, or access keys between actors. In identity security, it creates a secondary market for compromised human and non-human identities, enabling account takeover, lateral movement, and abuse of cloud, application, and infrastructure access.

What Credential Brokerage Means in Practice

Credential brokerage is more than simple theft. It is the secondary market that forms after compromise, where access material is repackaged, resold, swapped, or bundled so other actors can use it without breaching the original target themselves.

That market can involve human accounts, service accounts, API keys, session tokens, and cloud access keys. The security significance is that the value of a stolen secret increases when it can be transferred, tested, and monetised across multiple criminal workflows, rather than being used once and discarded.

Why Credential Brokerage Is Dangerous

Brokered credentials extend the lifetime and reach of a compromise. A single leaked login or token can become repeated access for different buyers, which makes containment harder and increases the chance of lateral movement, cloud abuse, and follow-on fraud.

It also breaks the assumption that only the original intruder has access. Once a credential is circulating, an organisation may face several unknown users of the same access path, each with different timing, infrastructure, and intent. That makes the compromise harder to attribute and easier to re-exploit.

For non-human identities, the impact is often amplified because stolen API keys, service credentials, or tokens can be automated at scale. NHIMG’s Ultimate Guide to NHIs — What are Non-Human Identities is a useful reference point for understanding why machine-facing access material is so attractive in this market.

How Organisations Expose Themselves to Brokerage

Credential brokerage usually becomes possible after credential collection, token theft, secret leakage, or session capture. The most common exposure paths are weak secret handling, poor rotation discipline, overlong token lifetime, and broad reuse of the same credential across environments or services.

Discovery matters because organisations cannot protect what they cannot inventory. A complete view of where credentials live, where they are duplicated, and which systems accept them is essential to understanding whether a stolen secret can still be used outside the intended context.

When the credential in question is an API key or bearer secret, lifecycle controls become especially important. NHIMG’s API Key Management Guide and Guide to the Secret Sprawl Challenge both map directly to the control gaps that create brokerable access material.

Detection, Containment, and Recovery

Brokered credentials are often detected indirectly, through anomalous geographies, unusual user agents, impossible travel, odd API usage, or access to systems that the original user would not normally touch. Because the actor using the credential may not be the original thief, the indicator set can look like routine valid logins until correlated across identity, endpoint, and cloud telemetry.

Containment should focus on revocation, not just password resets. If a token, key, or session has already entered a resale ecosystem, organisations need to treat it as potentially copied multiple times and assume that reuse may continue until every valid form of the secret is invalidated and downstream trust is reset.

Post-incident review should also look for secondary compromise. Once a brokered secret is used, attackers often pivot to mailbox access, cloud consoles, CI/CD systems, and administrative interfaces. NHIMG’s The State of NHI & AI Agent Breach Report 2026 illustrates how stolen secrets often become the first step in broader identity abuse.

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 OWASP API Security Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-02 — Secret LeakageCredential brokerage depends on leaked secrets, tokens, and access keys being traded or reused.
NHI-07 — Long-Lived SecretsBrokered access is more valuable when credentials and tokens remain valid for long periods.
NHI-05 — Overprivileged NHIBrokered non-human credentials become more damaging when they carry excessive access rights.
Recommendation — Detect leaked secrets early and revoke brokerable credentials before they circulate. Shorten credential lifetime and replace long-lived secrets with time-bound access. Reduce privilege on machine credentials so stolen access cannot spread broadly.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementAuthenticator lifecycle controls govern issuance, rotation, and revocation of credentials used in brokerage.
IA-9 — Service Identification and AuthenticationBrokered machine and service credentials fall under service-to-service authentication controls.
AU-6 — Audit Record Review, Analysis, and ReportingDetecting brokered credential use depends on reviewing anomalous authentication and access records.
Recommendation — Manage authenticators with strict rotation and revocation processes. Authenticate services with tightly scoped credentials that can be invalidated quickly. Correlate authentication logs to spot reused credentials and unusual access paths.
OWASP API Security Top 10API2 — Broken AuthenticationBrokered API keys and tokens turn authentication failure into reusable unauthorized access.
API9 — Improper Inventory ManagementYou cannot control brokerable credentials without knowing where APIs, keys, and consumers exist.
Recommendation — Harden API authentication so stolen tokens cannot be replayed successfully. Inventory all APIs and credentials so exposed access material can be found and revoked.

Practitioner Guidance

Why practitioners should care: Credential brokerage changes a one-time compromise into a reusable access commodity. That means the defensive goal is not only to stop theft, but to make stolen material short-lived, scoped, and easy to invalidate.

Governance implication: Ownership for secrets, tokens, and keys should be explicit, with clear rotation, revocation, and recovery responsibility. NHIMG’s Secrets Management Guide is relevant because it frames the operational shift from scattered secrets to controlled lifecycle management.

Practitioner takeaway: If a secret can be copied, sold, and used elsewhere without immediate detection, it is already functioning as a brokerable asset, not a controlled credential.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 23, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org