CIS – Software Asset Management (CIS-SAM)

Domain 1: Software Asset Core Overview & Fundamentals — 14%

Software asset management starts with one important distinction: installation data isn’t the same thing as license entitlement.

You’ll need to understand the software asset lifecycle, major application records, user roles, implementation considerations, and the relationship between discovery, normalization, entitlement, allocation, and compliance. These steps work together, but they don’t serve the same purpose. Follow the lifecycle from acquiring software rights through discovering installations, normalizing evidence, calculating license position, remediating gaps, and maintaining the result. Don’t memorize individual tables without understanding how they contribute to the overall process. A defensible software asset program can explain what was purchased, where software is installed, how it’s licensed, and whether current usage is compliant.

Domain 2: Data Integrity – Attributes and Sources for the Data — 28%

Data integrity determines whether reconciliation produces a compliance position anyone can trust.

You’ll work with discovery sources, imports, normalization content, software models, publishers, products, versions, installations, and unrecognized software. Raw discovery data must be mapped to consistent software identities before it can support reliable entitlement or compliance calculations. More records don’t automatically mean better evidence. Duplicate installations, stale discovery data, inconsistent publisher names, and weak normalization can distort both consumption and remediation results. Understand which sources collect software evidence, how normalization content processes that evidence, and where administrators resolve exceptions. Trustworthy compliance begins with repeatable, traceable data processing rather than a manual cleanup performed shortly before an audit.

Domain 3: Practical Management of Software Compliance — 30%

Software compliance is calculated from entitlements, license metrics, product-use rights, allocations, installations, and normalized discovery evidence.

You’ll need to understand software models, entitlements, rights, metric attributes, suites, upgrades, downgrades, allocations, reconciliation, and remediation options. Don’t assume that one discovered installation always consumes one license. Device, user, processor, subscription, and other license metrics can produce very different consumption results. Follow the calculation closely enough to explain why a product is compliant, underlicensed, or overlicensed. Then choose a remediation action that addresses the real cause. Buying more licenses won’t fix incorrect normalization, and removing software won’t help when the entitlement record itself is incomplete. The goal is a license position that can be explained and defended.

Domain 4: Operational Integration of Software Processes — 13%

Software asset management depends on clean integration with procurement, contracts, catalog requests, discovery, change activity, reclamation, and operational fulfillment.

You’ll need to understand how purchases create or support entitlements, how requests can create allocations, how usage data identifies reclamation opportunities, and how remediation work reaches the teams responsible for uninstalling or reassigning software. Common failures include contracts that aren’t linked, catalog requests that bypass approval, reclamation tasks closed without verification, and renewal decisions based on stale information. Don’t stop when a dashboard reports potential savings. Track whether the operational action actually occurred and whether the next reconciliation reflects the change. Strong integration turns compliance findings into repeatable work instead of leaving them as static recommendations.

Domain 5: Extending SAM — 15%

Extending SAM applies the core software asset model to broader optimization, specialized licensing, lifecycle management, reporting, and ongoing program improvement.

You’ll need to understand software model lifecycle, retirement, reclamation, optimization, dashboards, scheduled processing, content updates, and capabilities that broaden compliance coverage. Watch for scenarios where custom development is offered even though configuration, content services, or an established workflow already supports the requirement. A one-time cleanup isn’t the same as a sustainable process. Choose approaches that preserve normalized data, repeatable reconciliation, clear ownership, and supportable upgrades. Before adding scripts or custom tables, understand the product’s intended extension points and operational dependencies. Good extensions increase coverage without creating a second, disconnected software asset system.