Why Broadcom SAM Is Different
Software Asset Management for Broadcom products requires a different strategic posture than SAM for most other enterprise software vendors. With Oracle, SAP, or Microsoft, SAM is primarily a compliance discipline — track your deployments, ensure they are within licence entitlements, and manage audit risk. With Broadcom, SAM is simultaneously a compliance discipline, a cost management function, and a strategic input to major infrastructure decisions.
The reason is Broadcom's acquisition-driven business model. Every major software company Broadcom has acquired — CA Technologies in 2018, Symantec's enterprise security business in 2019, VMware in 2023 — has experienced the same post-acquisition pattern: elimination of low-margin products, conversion of perpetual licences to subscriptions, aggressive support cost increases of 3 to 5 times, and heightened licence compliance enforcement. Enterprises running software across all three Broadcom product families face this pattern simultaneously, compounding the complexity.
SAM for Broadcom must therefore address not just compliance but also the financial implications of a vendor that is actively redesigning its commercial relationship with every customer in its installed base.
Understanding the Three Broadcom Portfolios
Effective SAM requires understanding how each Broadcom product family is structured, what licence models apply, and where compliance risk concentrates.
VMware: The Subscription Transition
VMware represents the most immediate and most financially material SAM challenge for most enterprises. Following Broadcom's acquisition in November 2023, VMware's entire product portfolio was transitioned from perpetual + support to subscription-only licensing. All VMware perpetual licences were discontinued in 2024, with Broadcom actively contacting perpetual licence holders to negotiate conversion to subscription.
From a SAM perspective, this creates several distinct obligations. First, inventory management: organisations must know exactly which VMware products they deploy, at which version, on how many physical cores, across all locations. This is harder than it sounds because many VMware deployments have grown organically without central tracking — test environments, branch office deployments, and non-production infrastructure frequently accumulate unlicensed or under-licensed deployments.
Second, telemetry awareness: cloud-connected VMware products now report usage telemetry to Broadcom. VMware vSphere+ and VCF with cloud-connected management send core count and deployment information back to Broadcom in real time. This means Broadcom has visibility into your deployment that it did not have under perpetual licensing. SAM teams must understand which products are cloud-connected and what data is being reported.
Third, subscription management: unlike perpetual licences which survive indefinitely once purchased, subscriptions lapse if not renewed by the anniversary date. Broadcom has introduced a 20 percent late renewal penalty for subscriptions that are not renewed on time, creating a new financial risk that perpetual licence holders never faced. SAM systems must track VMware subscription expiry dates and trigger renewal processes with sufficient lead time.
Symantec: Enterprise Security Under Broadcom's Ownership
Broadcom acquired Symantec's enterprise security business in 2019, applying the same post-acquisition playbook it had used with CA Technologies. The Symantec enterprise security portfolio — which includes endpoint protection, data loss prevention, network security, and identity management — was rebranded as Broadcom's Enterprise Security Group and consolidated with Carbon Black following the VMware acquisition.
For SAM teams managing Symantec products, the key challenges are product discontinuation risk and licence model evolution. Broadcom has consistently eliminated Symantec products that do not meet its margin thresholds, forcing customers to either migrate to remaining Symantec products or find alternatives. Endpoint protection products that organisations have relied on for years have been repositioned, rebranded, or replaced within Broadcom's consolidated security portfolio.
The licence model for Symantec enterprise products has shifted toward user-based subscription licensing, with enterprise agreements structured to cover defined seat counts for defined terms. Compliance risk for Symantec products concentrates around user count accuracy — deployments that have grown beyond the licensed user count without corresponding entitlement expansion represent the primary audit exposure. Broadcom's compliance enforcement for Symantec has historically been less aggressive than for Oracle or IBM, but this has changed as Broadcom has strengthened its licence compliance capabilities post-acquisition.
CA Technologies: Mainframe and DevOps Legacy
CA Technologies, acquired by Broadcom in 2018, brought a portfolio of mainframe software (including CA IDMS, CA Datacom, CA 7, and CA 11), DevOps and development tools (CA Agile Central, CA Automic Automation), and IT management tools (CA Service Management, CA Performance Management). This portfolio serves customers with deep mainframe dependencies, many of whom have been running CA tools for decades.
SAM for CA Technologies products presents unique challenges compared to VMware or Symantec. Mainframe licensing in particular involves MIPS-based or MSU-based metrics that require integration with mainframe capacity planning systems, not just standard desktop SAM tools. Organisations running CA mainframe tools need SAM processes that cover both distributed infrastructure and mainframe environments, which requires specialist capability that many SAM teams lack.
The risk of product discontinuation is also significant for CA customers. Broadcom has progressively narrowed the CA Technologies portfolio to focus on products with the largest and most profitable installed bases. Products serving smaller customer segments have been discontinued or placed in maintenance-only mode, requiring customers to migrate. SAM teams managing CA tools must maintain close awareness of Broadcom's CA product roadmap to anticipate discontinuations and plan migrations before they are forced.
Managing SAM across all three Broadcom portfolios?
We provide independent Broadcom SAM assessments and optimisation programmes.Broadcom SAM Framework: Six Core Disciplines
A robust SAM programme for Broadcom software must address six core disciplines, each of which interacts with the others and requires both technical implementation and governance process.
1. Licence Inventory and Normalisation
The foundation of any SAM programme is an accurate inventory of licences owned and software deployed. For Broadcom, this starts with extracting your current entitlement data from Broadcom's licence management portal (accessible through the Broadcom Support Portal for registered customers) and normalising it against your deployment data from discovery tools.
VMware environments should be inventoried using vCenter's built-in capacity reporting, supplemented by a SAM discovery tool that can enumerate ESXi host core counts, deployed products, and versions across all vCenter instances. For Symantec, endpoint protection deployment counts should be reconciled against Active Directory user counts and device inventories. For CA mainframe tools, MIPS and MSU data must be extracted from mainframe performance monitoring systems.
A common gap in Broadcom SAM is the failure to include non-production environments. Test and development VMware deployments frequently run untracked, and Broadcom's subscription model does not automatically provide a discount for non-production use — unless this is explicitly negotiated in the subscription agreement.
2. Compliance Position Assessment
Once inventory and entitlement data are normalised, the compliance position — the delta between what you own and what you deploy — must be calculated. This is not a one-time exercise; it is a continuous process because deployment counts change and entitlements evolve.
For VMware, the compliance position must account for the core-count minimum (72 cores from April 2025) and the counting rule that each physical CPU is counted as a minimum of 16 cores. An organisation that has inventoried its environment based on actual core counts may find that the effective licensed core count under Broadcom's rules is significantly higher.
Compliance shortfalls — deployments that exceed entitlements — must be remediated before Broadcom conducts a licence review. Broadcom's licence review processes have become more systematic post-acquisition, and organisations that allow compliance shortfalls to persist face both back-licence fees and the risk of a formal audit with financial penalties.
3. Cost Optimisation Identification
SAM is not only a compliance function; it is also a cost reduction function. For Broadcom, cost optimisation opportunities arise in three primary areas: right-sizing, product rationalisation, and subscription term management.
Right-sizing involves identifying VMware deployments that are over-licensed — environments where the licensed core count exceeds the deployed core count, allowing for a reduction in subscription scope at renewal. In the pre-acquisition VMware era, this was less time-sensitive; perpetual licences did not expire, so over-licensing was an opportunity to deploy more infrastructure without additional cost. Under subscription, over-licensed cores represent direct ongoing cash waste.
Product rationalisation involves identifying Symantec or CA tools that are deployed but no longer actively used, or that duplicate capabilities available in other parts of the enterprise's stack. In environments that have been through mergers and acquisitions, duplicate security tools and legacy CA automation products are common. Rationalising these reduces subscription cost and simplifies the compliance position.
Subscription term management involves ensuring that renewal dates are aligned where possible to create a unified Broadcom renewal event — a single negotiation with more aggregate leverage — rather than multiple disconnected renewals that Broadcom can address at different times with different account teams.
4. Renewal and Negotiation Strategy
SAM data is the foundation of a successful renewal negotiation. Enterprises that approach Broadcom renewals with accurate deployment data, documented right-sizing opportunities, and competitive alternative pricing have consistently achieved better outcomes than those that respond reactively to Broadcom's proposed renewal terms.
The key SAM outputs for a VMware renewal negotiation are: current deployed core count by product (VCF versus VVF versus standalone), the delta between current entitlements and current deployment (right-sizing opportunity), and a modelled alternative cost for Nutanix or Azure VMware Solution covering the same workloads. This creates a negotiating brief that Broadcom's account team must respond to commercially rather than simply defending the list price.
For Symantec products, the equivalent inputs are: current user and device counts by product, upcoming contract anniversary dates, and pricing for equivalent capabilities from competitors (CrowdStrike, SentinelOne, Palo Alto, Zscaler as relevant). For CA mainframe tools, the equivalent is: current MIPS or MSU usage, upcoming contract dates, and any migration analysis for CA capabilities that overlap with more modern tooling.
5. Migration Planning Integration
SAM for Broadcom must integrate directly with migration planning in a way that SAM for other vendors typically does not. Because a significant proportion of VMware customers are actively considering migration to Nutanix, Azure VMware Solution, or other platforms, and because Symantec customers face ongoing product discontinuation risk, the SAM programme must feed directly into infrastructure planning and architecture decisions.
Concretely, this means SAM data should drive the migration sequencing decision: which VMware workloads are the strongest candidates for early migration based on their licensing cost, operational simplicity, and application portability? Workloads with the highest per-core cost relative to their technical migration complexity should be prioritised.
For Symantec, SAM data should identify which products are most exposed to discontinuation risk and which have the strongest replacement candidates. For CA, SAM data should identify which mainframe tools are most strategic to the organisation's long-term infrastructure direction and which are legacy tools that can be decommissioned as part of a rationalisation programme.
6. Governance and Continuous Control
Broadcom SAM governance must be embedded in the processes that govern infrastructure provisioning, application deployment, and vendor management. The risk of ungoverned VMware deployment is higher under subscription than under perpetual licensing: every new ESXi host that is provisioned without updating the subscription count creates a compliance shortfall that accumulates until the next renewal.
SAM governance for Broadcom should include: a mandatory vCenter change process that triggers licence count review whenever new hosts are added, a quarterly compliance reconciliation process comparing entitlements to deployment data, an annual cost optimisation review aligned to the Broadcom renewal calendar, and a vendor management protocol that ensures Broadcom account communications are routed through SAM and procurement rather than being handled by IT operations directly.
SAM Tools for Broadcom Products
Standard SAM platform tools handle VMware discovery reasonably well through vCenter API integration and network scanning. The major SAM platforms — ServiceNow HAM, Flexera One, Snow Software, Certero — all support VMware licence management with varying degrees of sophistication. Key capability requirements for VMware SAM include: vCenter API integration for ESXi host and core count discovery, VMware licence metric normalisation (per-core counting with 16-core minimum), and subscription expiry date tracking and alerting.
For Symantec endpoint products, SAM tools rely on endpoint agents and directory integration. For CA mainframe tools, most SAM platforms lack native mainframe capability, requiring either custom integration or specialist mainframe SAM tooling. Organisations with significant CA mainframe footprints should evaluate whether their existing SAM platform has adequate CA mainframe support before relying on it for compliance management.
The Nutanix and Azure VMware Solution Factor
No CIO playbook for Broadcom SAM is complete without addressing the platform migration question, because the strategic trajectory for many organisations is away from VMware — and SAM data is a critical input to that decision. Nutanix and Azure VMware Solution (AVS) are the two primary alternative destinations.
Nutanix offers a native AHV hypervisor included at no additional cost as part of the Nutanix subscription. For organisations where the SAM analysis reveals that VMware subscription costs have increased 3 to 5 times and the workload migration complexity is manageable, the Nutanix economic case is often compelling. Nutanix's migration tooling (Move) supports live migrations from VMware environments without downtime for most workload types.
Azure VMware Solution provides a VMware-native environment managed by Microsoft. The SAM implication of choosing AVS is significant: organisations that move to AVS exit the Broadcom commercial relationship for VMware entirely. Microsoft manages all VMware licensing as part of the AVS service, and the customer's procurement relationship is with Microsoft, not Broadcom. For CIOs who want to reduce Broadcom commercial risk while maintaining VMware operational familiarity, AVS is a structurally clean solution.
The SAM decision framework for platform migration should weigh the annual cost delta (current VMware subscription versus Nutanix subscription or AVS consumption cost), the one-time migration cost (project labour, migration tooling, downtime risk), and the ongoing operational impact (retraining, tooling changes, integration work). SAM data provides the "current VMware subscription cost" variable; infrastructure architecture provides the migration complexity variable.
Action Plan for CIOs: Next 90 Days
For CIOs who have not yet implemented a structured Broadcom SAM programme, the following 90-day action plan provides a prioritised starting point.
- Days 1–30: Conduct a full Broadcom entitlement audit. Extract all licence and entitlement data from the Broadcom Support Portal. Map it against current deployment data from vCenter, endpoint management, and mainframe capacity tools. Identify the compliance position for each product family.
- Days 31–60: Build the Broadcom cost model. Calculate the total annual Broadcom subscription cost across VMware, Symantec, and CA. Identify right-sizing opportunities. Model the cost delta if VMware workloads were migrated to Nutanix or AVS. This data becomes the foundation for the next renewal discussion.
- Days 61–90: Establish Broadcom governance controls. Implement a change process that requires licence count review for new VMware host provisioning. Set up subscription expiry alerting in your SAM or ITSM platform. Align Broadcom renewal dates where possible for consolidated negotiation leverage. Assign a named commercial owner for the Broadcom vendor relationship.
For independent support executing any of these steps, the Broadcom advisory specialists provides SAM assessment, cost modelling, and renewal negotiation services. Our Broadcom negotiation guide contains the frameworks and templates referenced in this playbook.
Common SAM Failures with Broadcom and How to Avoid Them
Based on our advisory engagements across more than 150 Broadcom customer organisations, these are the SAM failures that most frequently create financial exposure.
Treating perpetual licences as permanent entitlements. Many organisations that purchased VMware perpetual licences assumed those licences were an indefinite asset that required no ongoing management. Under Broadcom's post-acquisition model, perpetual licence holders are actively being transitioned to subscription. Organisations that have not engaged with Broadcom's conversion programme risk finding themselves in a conversation where Broadcom has documented their deployment status via telemetry while they lack comparable documentation of their perpetual entitlements. Maintain a clear register of perpetual licence certificates, purchase records, and entitlement documents independent of Broadcom's portal.
Allowing IT operations to provision VMware infrastructure without SAM involvement. In most enterprises, the team that provisions new ESXi hosts is not the team that manages VMware licences. When new hosts are provisioned without triggering a licence review, the licence count falls behind the deployment count. Under subscription, this creates a compliance shortfall that must be resolved at renewal, typically by purchasing additional subscription at then-current rates. Implementing a change control gate that requires licence review for new host provisioning prevents this accumulation.
Managing Broadcom portfolios in silos. VMware, Symantec, and CA are managed by separate IT teams in most enterprises — infrastructure, security, and applications respectively. But from a commercial and compliance perspective, they are all Broadcom. Organisations that consolidate Broadcom management into a unified vendor relationship — with a single commercial owner and a coordinated renewal strategy — consistently achieve better commercial outcomes than those that address each product family in isolation.
Neglecting subscription renewal date management. The 20 percent late renewal penalty Broadcom introduced for VMware subscriptions is a direct consequence of enterprises failing to track and act on renewal dates. Implement calendar alerts, SAM platform notifications, and procurement workflow triggers at 90 and 30 days before every Broadcom subscription anniversary to prevent penalty exposure.