Topic starter
06/06/2026 11:26 am
TL;DR: Disconnected apps force manual joiner-mover-leaver workflows that consume thousands of hours, delay access changes, weaken auditability, and leave orphaned accounts active, according to Cerby and customer examples from monday.com and ClickUp. The real issue is not inconvenience but a structural lifecycle gap that keeps governance from reaching critical applications.
Editorial analysis by NHI Mgmt Group, based on content published by Cerby: “Modernizing identity lifecycle management: The consequences of disconnected apps”.
By the numbers:
- Manual identity lifecycle work consumed 3,300+ hours per year at monday.com, the equivalent of more than two full-time employees.
- Cerby says monday.com used its coverage to identify unused and overprovisioned licenses, and fully 20% of licenses were unnecessary.
Key questions
Q: What breaks when joiner-mover-leaver workflows stop at disconnected apps?
A: Lifecycle control becomes partial, so access changes depend on tickets, emails and scripts instead of enforceable automation.
Q: Why do disconnected apps increase identity and access risk?
A: Disconnected apps increase risk because they break the chain between authentication, entitlement management, and offboarding.
Q: How do security teams know if manual lifecycle work is becoming a control issue?
A: Look for persistent deprovisioning lag, repeated spreadsheet-based access reviews, accounts that remain active after departures, and applications whose permissions cannot be reconciled centrally.
Practitioner guidance
- Map disconnected app coverage gaps Inventory every application that cannot be governed through standard identity workflows, then classify each one by whether provisioning, deprovisioning and access review are manual, scripted or fully integrated.
- Measure deprovisioning lag by application Track the time between leaver events and actual account deactivation for each disconnected app, then prioritise the systems where access persists longest or where shared accounts are present.
- Require audit evidence for each lifecycle step Make access creation, change and removal evidence available for every disconnected app so compliance teams are not forced to reconstruct control operation from spreadsheets and local logs.
Bottom line: Disconnected apps turn joiner-mover-leaver work into a structural governance gap because identity controls stop at the app boundary.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 12:14 pm
Disconnected apps create a lifecycle governance gap, not just an operations burden. When identity workflows stop at the boundary of standards-compliant systems, joiner-mover-leaver control becomes partial by design. That means governance is only as strong as the apps it can reach, and disconnected applications become the weak link in the control chain. Practitioners should treat lifecycle reachability as a core governance requirement, not a convenience feature.
A few things that frame the scale:
- Organisations that rely heavily on static credentials reported a 20-percentage-point increase in security incidents compared with those with low reliance, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should organisations prioritise first in disconnected app governance?
A: Start with the applications that carry the highest access risk and the poorest visibility, especially where deprovisioning is manual and audit evidence is fragmented. The first goal is not full perfection. It is closing the longest-lived access windows and making the highest-risk lifecycle events provable in one place.
👉 Read our full editorial: Disconnected apps turn identity lifecycle gaps into security cost