A bank in Mauritius began with a license review and risk assessment across seven publisher portfolios. It then moved to a managed SAM service with a license compliance review every quarter, and has since renewed that service for two more years.
Every figure from the engagement is set out in our license review case study for this client.
| Publisher portfolios with a trusted license position | Quarterly compliance reviews in year two | In-scope software recognized and normalized | Managed service renewed |
|---|---|---|---|
| 7 | 4 | 100% | 2 more years |
| Client | A bank in Mauritius |
|---|---|
| Portfolios in scope | Microsoft (including Microsoft 365), Oracle database, middleware and applications, VMware, Red Hat, IBM, Adobe and security software |
| Sites | License use analyzed across the data center (DC) and the disaster recovery site (DR) |
| Engagement | License review and risk assessment, then managed SAM on the Euladox platform, in three phases |
| Outcome | A trusted Effective License Position for every portfolio, IBM ILMT issues resolved, cost avoided on Oracle licensing, and SAM processes and license policies documented |
The challenge: A transformation program and an unreliable IBM position
The bank’s licenses spanned seven portfolios: Microsoft, including Microsoft 365; Oracle database, middleware and applications; VMware; Red Hat; IBM; Adobe; and its security software. Three issues shaped the work:
- A transformation program was under way, which raised questions about the bank’s contract rights, its obligations and novation.
- Reporting issues in IBM License Metric Tool (ILMT) had exposed the bank’s IBM sub-capacity licensing.
- The bank wanted a trusted license baseline first, and continuous compliance after that.
How we ran it: From a trusted baseline to continuous compliance
- Discover. We installed Euladox on site and combined four discovery methods: agentless scans, stand-alone agents, scripts and license-portal adaptors.
- Reconcile. We loaded contracts, purchase orders and entitlements into Euladox and matched them to deployments at both the DC and the DR site.
- Baseline. For each publisher we produced an Effective License Position, a risk assessment and a cost-optimization plan.
- Document. We analyzed the contracts and novation questions, and wrote the bank’s license policies and SAM process documentation.
The engagement ran in three phases:
- Phase 1, 2025. A license review and risk assessment, with a baseline Effective License Position for every in-scope publisher.
- Phase 2, one year. Continuous compliance, with a license compliance review every quarter.
- Phase 3, the next two years. The bank renewed for two more years, and this phase is now under way.
The results: A trusted baseline, then compliance every quarter
- Trusted license positions for all seven publisher portfolios, with every piece of in-scope software recognized and normalized.
- IBM. The ILMT issues were resolved, protecting the bank’s sub-capacity licensing. Read more about IBM license compliance.
- Cost avoidance on Oracle licensing.
- Novation. Contract novation analysis for the transformation project.
- SAM process. SAM processes and license policies documented for the bank.
Is your license position ready for the next vendor audit?
A license review is often the right first step. Tell us which publishers you license, and a senior advisor will walk you through what a review would cover and how a managed SAM service could follow it.
Talk to an advisor or read about our managed SAM services.
More managed SAM case studies: 16,300+ assets and 25 publishers at a fast-growing bank; a private-sector bank, on-premises and on AWS; a Red Hat audit defense for a Kenyan SACCO.
See more of our analysis in Google: add Rythium as a preferred source
