Join our Newsletter — 33% off our NHI Course

Did SAM tools resolve SaaS lifecycle governance gaps?

 

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

TL;DR: SAM tools help organisations discover applications, track renewals, and optimise licence spend, according to Zluri. Software governance still depends on access lifecycle enforcement, because app inventory alone does not remove the identities attached to those apps.

Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “13 Best Software Asset Management Tools in 2026”.

Key questions

Q: Why does application discovery alone not solve software governance?

A: Discovery tells you what exists, but it does not tell you who approved it, who owns it, or whether access was ever removed.

Q: Why do SaaS management gaps often turn into access governance problems?

A: Because the same blind spots that hide rogue apps also hide who can use them.

Q: How should IAM and SaaS teams share responsibility for app offboarding?

A: IAM should own the lifecycle logic for access removal, while SaaS operations should supply the usage and contract context that proves whether access is still needed.

Practitioner guidance

  • Strengthen SaaS discovery coverage Validate that your discovery stack pulls from SSO, finance, APIs, and optional endpoint signals so unsanctioned apps do not stay invisible.
  • Tie app requests to identity lifecycle Ensure approval, assignment, and revocation are triggered by joiner, mover, and leaver events rather than handled as standalone admin work.
  • Separate spend optimisation from access decisions Use licence usage and renewal data to prioritise review, but confirm entitlement ownership before terminating or retaining an application.

Bottom line: SAM tools help organisations see and rationalise software spend, but they do not on their own govern the identities that use those applications.

Glossary terms: SaaS Discovery, Identity Lifecycle Governance, License Optimisation, Shadow IT

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
 

Software asset management has become a proxy layer for identity governance in SaaS estates. The article shows that the operational value of SAM now depends on whether it can connect discovery, requests, approvals, assignment, and revocation. That is an identity lifecycle problem wearing an asset-management label. Practitioners should stop treating SAM and IGA as separate domains when the control failure emerges in the same application path.

A question worth separating out:

Q: How do software asset management and IGA work together in practice?

A: SAM should supply application discovery, usage, and renewal context, while IGA should enforce ownership, approvals, recertification, and removal. Used together, they create a closed loop from request to revocation. Used separately, they leave gaps where applications can be purchased, assigned, and forgotten without a durable governance record.

👉 Read our full editorial: Software asset management tools show why app inventory is not enough


This post was modified 1 week ago by NHI Mgmt Group

   
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.