Notifications
Clear all
Topic starter
23/06/2026 7:17 pm
TL;DR: Slack now has to be governed like any other high-value identity surface, not treated as a separate collaboration island, as Unosecur’s Slack Connector feeds people, guest accounts, bots and OAuth tokens into a unified identity fabric, with flags for dormant access, non-MFA use, SSO bypass and privilege drift, according to Unosecur.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should security teams govern Slack bots and OAuth tokens alongside user access?
A: Security teams should treat Slack bots and OAuth tokens as governed identities, not app settings.
Q: Why do collaboration platforms create identity risk even when the workspace looks tidy?
A: They accumulate access over time through guest accounts, dormant bots, inherited roles and app permissions.
Q: What breaks when Slack access is reviewed like ordinary application access?
A: Ordinary app reviews often miss bots, tokens, nested admin paths and privilege drift.
Practitioner guidance
- Inventory Slack non-human identities alongside human users Include bots, guest accounts, app integrations and OAuth tokens in the same entitlement inventory so the workspace is reviewed as an identity system, not a chat application.
- Trace nested roles before access reviews close Review inherited admin rights, delegated workspace roles and app-added permissions before recertification.
- Automate remediation for dormant privileged access Set a control process that can disable, revoke or downgrade Slack privileges with a logged evidence trail.
What's in the full announcement
Unosecur's full product announcement covers the operational detail this post intentionally leaves for the source:
- The Slack Connector’s field-level inventory of users, guest accounts, bots and OAuth tokens across workspaces.
- The exact posture checks used for dormancy, non-MFA access, SSO bypass and privilege drift.
- How one-click remediation records disable, revoke or downgrade actions with exportable evidence.
- The deployment model for read-only OAuth connection without endpoint agents.
👉 Read Unosecur's announcement on the Slack Connector for identity governance →
Slack Connector: what it means for identity teams and access control?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
25/06/2026 3:14 am
Slack identity governance is now part of the broader NHI problem, not an application exception. Once bots, OAuth tokens and guest accounts are treated as first-class identities, Slack exposes the same governance failures that show up in cloud and SaaS estates. The operational implication is that collaboration platforms need the same lifecycle discipline as other non-human identities, including inventory, review and revocation.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, with 38% having no or low visibility and a further 47% having only partial visibility, according to The State of Non-Human Identity Security.
- Only 19.6% of security professionals express strong confidence in their organisation's ability to securely manage non-human workload identities, according to The 2024 Non-Human Identity Security Report.
A question worth separating out:
Q: Which frameworks are most relevant for Slack identity governance?
A: NIST Cybersecurity Framework 2.0 is useful for organising govern, identify, protect and detect activities, while NHI-focused controls help teams manage tokens, bots and other non-human identities. The practical test is whether your framework maps Slack access ownership, review cadence and remediation evidence to a repeatable governance process.
👉 Read our full editorial: Slack identity governance now extends to bots, tokens and guest access
