Notifications
Clear all
Topic starter
12/06/2026 1:23 am
TL;DR: As SaaS adoption expands, manual discovery, onboarding, offboarding, approvals, and review processes become slower, more error-prone, and harder to govern, increasing shadow IT, security, and compliance risk, according to Zluri. The real issue is not automation for its own sake, but whether identity and access controls can keep pace with a fragmented SaaS estate.
NHIMG editorial — based on content published by Zluri: Automation 4 Signals that it's Time to Automate SaaS Management in Your Organization
Questions worth separating out
Q: How should security teams automate SaaS access without losing governance control?
A: Start with authoritative app discovery, then automate only the access paths that are policy-defined and lifecycle-triggered.
Q: Why do SaaS sprawl and shadow IT create IAM risk?
A: Because IAM cannot govern what it cannot see.
Q: What breaks when onboarding and offboarding stay manual in SaaS environments?
A: Manual lifecycle handling breaks consistency.
Practitioner guidance
- Build a complete SaaS inventory first Use discovery signals from SSO, finance systems, integrations, browser activity, and desktop agents to establish a single authoritative app view before automating access decisions.
- Automate lifecycle-triggered access changes Connect onboarding and offboarding events to provisioning and deprovisioning workflows so access changes occur through repeatable policy rather than manual ticket handling.
- Curate the app catalogue for self-service Limit the employee app store to approved applications, define approval rules explicitly, and review catalogue changes on a fixed governance cadence.
What's in the full article
Zluri's full blog post covers the operational detail this post intentionally leaves for the source:
- Discovery method breakdown across SSO or IDP, finance systems, direct integrations, browser extensions, and desktop agents
- Renewal calendar and licence right-sizing detail for teams managing SaaS contracts and subscriptions
- Step-by-step onboarding and offboarding playbook behaviour inside the Employee App Store model
- Risk and compliance monitoring features used to evaluate SaaS applications and control access
👉 Read Zluri's analysis of when SaaS management should be automated →
SaaS sprawl and onboarding automation: are controls keeping up?
Explore further
12/06/2026 11:17 am
SaaS automation is really an identity control problem, not an IT efficiency project. The article correctly identifies that manual administration cannot keep up once app count, access volume, and renewal activity scale. In practice, the governance question is whether the organisation can still prove who has access, why they have it, and when it should be removed. That makes SaaS automation a control plane issue, not a productivity shortcut.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- The same research found that only 44% of developers are reported to follow security best practices for secrets management, which shows how quickly governance assumptions diverge from daily behaviour.
A question worth separating out:
Q: Who is accountable when a self-service app store grants the wrong access?
A: Accountability stays with the organisation that defines the catalogue and approval policy, not with the user who clicks the request button. If the catalogue includes the wrong apps, if approvals are too loose, or if offboarding is not enforced, the governance failure sits with the access model.
👉 Read our full editorial: SaaS sprawl and access automation: the governance gap teams miss
