Topic starter
06/06/2026 2:15 am
TL;DR: Disconnected apps are creating a governance gap that leaves access removal incomplete, audit records fragmented, and business-critical accounts tied to individuals rather than corporate identity, according to Ponemon Institute research commissioned by Cerby. The real problem is not just inconvenience: identity programmes built around connected apps still fail when shared passwords, MFA handoffs, and offboarding gaps dominate the marketing stack.
Editorial analysis by NHI Mgmt Group, based on content published by Cerby: “Our Company Was Worth $6 Billion. We Shared Passwords Over Slack.”.
By the numbers:
- 68% of organizations report delayed or incomplete access removal after an employee leaves.
- 77% of organizations experienced at least one cybersecurity incident in the past two years caused by their inability to secure disconnected apps.
- 34% of incidents involving disconnected apps specifically included social media platforms like Meta, LinkedIn, X, and Instagram.
Key questions
Q: What breaks when marketing apps are not connected to corporate identity systems?
A: Access removal, ownership transfer, and audit evidence break first.
Q: Why do disconnected apps create so many audit problems?
A: Because auditors need proof that access was granted, reviewed, and revoked consistently, not just a statement that policy exists.
Q: How do you know if disconnected app governance is actually working?
A: Look for complete application inventory, documented ownership, timely revocation after departure, and audit-ready evidence for each critical account.
Practitioner guidance
- Map disconnected apps by business criticality Inventory marketing, social, and ad platforms that sit outside SSO and SCIM, then rank them by business impact and manual access dependence.
- Replace shared access with named corporate identities Remove spreadsheet passwords and Slack-based MFA sharing by assigning each account to a named employee or controlled admin role.
- Build offboarding checks for non-integrated platforms Add disconnected-app access revocation to leaver workflows so admin rights are removed even when the platform does not support native deprovisioning.
Bottom line: Disconnected marketing tools can become governance blind spots when access depends on shared credentials, manual MFA handoffs, and individual memory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 3:49 am
Disconnected app access is a lifecycle governance failure, not an application quirk. The core issue is that access to business-critical marketing systems is being managed outside the corporate identity plane, so joiner-mover-leaver controls never fully reach the app. That means access removal, ownership transfer, and audit evidence all depend on manual memory rather than governed state. Practitioner implication: disconnected apps need lifecycle treatment equal to any other privileged access surface.
A few things that frame the scale:
- 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Who is accountable when a marketing platform is left outside identity governance?
A: IAM, security, and the business owner are jointly accountable, because disconnected apps fail at the boundary between technical control and operational ownership. If the platform is business-critical, someone must own access lifecycle, recovery, and evidence. Without that ownership, the account becomes a shared risk that no team can fully explain to auditors.
👉 Read our full editorial: Disconnected app access is breaking identity governance in marketing