Topic starter
12/05/2026 2:33 pm
TL;DR: OAuth tokens stolen from Drift let attackers use an AI chat integration to access Salesforce data at scale, according to Entro Security, turning a third-party connection into a shared non-human identity blast radius across many tenants. OAuth apps need the same lifecycle, ownership, and revocation discipline as any other NHI.
Editorial analysis by NHI Mgmt Group, based on content published by Entro Security: “Abusing OAuth at Scale: How Drift’s Breach Opened Salesforce to Attackers”.
Key questions
Q: What breaks when an OAuth-connected AI chat app is not governed like an identity?
A: The app can inherit delegated access that outlives the original approval, which turns a convenience integration into a reusable entry point.
Q: Why do stolen OAuth tokens create disproportionate risk in cloud-connected business systems?
A: Stolen OAuth tokens are dangerous because they inherit the permissions already granted to the connected app, so the attacker often does not need to authenticate again.
Q: What are the signs that a connected app has become overprivileged?
A: Look for apps that can reach more data than their stated business purpose, generate repeated high-volume API calls, or remain connected long after the original use case has changed.
Practitioner guidance
- Inventory every OAuth-connected app Build a complete register of connected apps, their owners, scopes, and downstream systems so no AI chat integration sits outside governance.
- Enforce short token lifetimes and rapid revocation Reduce the period in which stolen bearer tokens remain valid and make revocation a standard incident-response action for delegated access.
- Review privileged OAuth scopes quarterly Recertify high-risk app scopes against actual business need, especially where the integration can read customer or HR records.
Bottom line: OAuth-connected AI chat apps can function as delegated non-human identities and therefore need explicit ownership, scope review, and revocation control.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/05/2026 2:33 pm
OAuth-connected AI chat apps are now identity assets, not optional integrations. Once a third-party app can request tokens and reach production data, it sits inside the identity governance model whether teams acknowledge it or not. The governance question shifts from vendor management to delegated authority, lifecycle ownership, and revocation speed. Practitioners should classify these integrations as first-class NHIs.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: Should teams treat SaaS-to-SaaS integrations as privileged access?
A: Yes. A connected app can function like a privileged service identity if it can read, write, or export business data through APIs. Treating it as ordinary application plumbing leaves no clear place for certification, offboarding, or incident revocation, which is exactly where shared blast radius emerges.
👉 Read our full editorial: OAuth token abuse shows how AI chat integrations widen NHI risk