Join our Newsletter — 33% off our NHI Course

Why does MDM and CASB discovery still leave shadow IT unowned?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Discovery can identify unmanaged SaaS apps, but Zluri says that visibility still leaves approval, ownership, and offboarding unresolved. SaaS governance has to turn that catalog into lifecycle work or shadow IT stays in place after detection.

Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How Zluri’s Discovery Engine Works?”.

Key questions

Q: Why do hidden SaaS apps create access governance risk?

A: Hidden SaaS apps create risk because governance depends on knowing what exists, who owns it, and which accounts still have active access.

Q: How do teams know when SaaS discovery is producing actionable results?

A: They should look for a catalog that is both broad and clean, with accepted applications carrying enough metadata to support policy and licensing actions.

Q: What breaks when SaaS discovery finds apps but no one owns them?

A: Discovery without ownership breaks governance because the organisation can identify an application but cannot prove who approved it, who should review it, or who is responsible for offboarding.

Practitioner guidance

  • Map discovery signals to lifecycle owners Require every discovered SaaS application to be assigned to a business owner, technical owner, and review cadence so visibility becomes accountable governance.
  • Reconcile finance data with sanctioned app inventory Compare expense records and reimbursement data against approved SaaS inventories to identify employee-purchased tools that bypass procurement.
  • Treat browser telemetry as evidence of active use Use browser extension and CASB signals to identify SaaS that is actively in use even when it is missing from central app records.

Bottom line: SaaS discovery helps organisations find unmanaged applications, but that visibility does not by itself establish control.

Glossary terms: SaaS Discovery, Shadow IT, Lifecycle Governance, Identity Surface

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Discovery is only the first half of SaaS control: finding an application does not prove that the organisation can govern it. The article shows how multiple telemetry sources improve visibility, but visibility alone does not establish approval, access ownership, or retirement discipline. In identity programmes, that means discovery must be treated as an input to governance, not a substitute for it.

A few things that frame the scale:

  • Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: What is the difference between SaaS configuration and SaaS governance?

A: SaaS configuration is the on or off state of a feature. SaaS governance is the policy, ownership, monitoring, and cleanup process that determines whether the feature can be used safely. A disabled setting may reduce exposure, but only governance ensures identities, content, and exceptions are managed over time.

👉 Read our full editorial: SaaS discovery engines expose the identity gap behind shadow IT



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.