Notifications
Clear all
Topic starter
23/06/2026 9:13 pm
TL;DR: IT asset discovery is no longer just about finding hardware and software, because SaaS sprawl, OAuth-connected AI agents, and unmanaged service accounts now create an identity layer that many tools cannot see, according to Zluri. Discovery only becomes useful when teams can map who and what has access, how it was granted, and whether it still belongs there.
NHIMG editorial — based on content published by Zluri: SaaS Management Top 9 IT Asset Discovery Tools in 2026
Questions worth separating out
Q: How should security teams govern SaaS discovery when access is fragmented across identities?
A: Security teams should treat SaaS discovery as an identity governance problem, not only an inventory task.
Q: Why do non-human identities complicate IT asset discovery?
A: Non-human identities complicate discovery because they create access paths that do not appear in traditional asset inventories.
Q: What breaks when discovery tools only report assets and not access?
A: When discovery tools only report assets, governance teams lose sight of entitlement risk, delegated access, and dormant identities.
Practitioner guidance
- Map identity to asset coverage Require every discovery workflow to show which human and non-human identities can access each SaaS app, cloud service, and on-prem system, including the grant source and ownership record.
- Inventory OAuth and AI app connections Track OAuth-consented applications, AI tools, and delegated integrations as first-class inventory objects so shadow AI does not sit outside review, offboarding, or risk scoring.
- Tie discovery to entitlement freshness Use continuous activity signals to flag dormant accounts, stale service identities, and privilege drift between review cycles instead of waiting for the next snapshot report.
What's in the full article
Zluri's full post covers the operational detail this post intentionally leaves for the source:
- A side-by-side breakdown of the nine discovery tools and the specific environments they fit best.
- Implementation detail on Zluri's Identity Visibility and Intelligence Product, including connector coverage and identity graph behavior.
- Practical examples of how discovery surfaces shadow IT, shadow AI, and OAuth-connected AI agents.
- Product-specific comparison points for teams that are past evaluation and need rollout detail.
👉 Read Zluri's analysis of IT asset discovery tools and identity visibility →
IT asset discovery and identity visibility: what teams are missing?
Explore further
25/06/2026 2:24 am
Asset discovery has an identity problem before it has a tooling problem. The article is right to separate asset presence from access visibility, because the real governance failure is treating inventory as if it were identity control. In SaaS and cloud environments, the relevant question is not only what is installed, but which identities can act on it and whether those entitlements still make sense. The practitioner conclusion is simple: discovery must be evaluated as an access governance capability, not a catalog feature.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to The 2026 Infrastructure Identity Survey.
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to The 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How can organisations tell whether discovery is actually improving governance?
A: Organisations should look for shorter time to identify owners, faster detection of stale access, and better visibility into OAuth grants and non-human identities. If discovery does not reduce unknown access paths or improve lifecycle decisions, it is just producing reports. Real governance improvement shows up in fresher identity data and fewer unowned entitlements.
👉 Read our full editorial: IT asset discovery now has an identity problem behind it
