Software Asset Management and License Compliance
What the exam tests
Software Asset Management and License Compliance tests entitlement management, license metrics, reconciliation, and audit readiness across on-premises and subscription software.
Core rules
- An entitlement is the right to use software, defined by a contract and a license metric: per device, per user, per core, per processor, per instance, or consumption-based.
- The Effective License Position (ELP) equals entitlements minus consumption, adjusted for license rules such as downgrade rights, second-use rights, and virtualization.
- Reconciliation matches installed and accessed software to entitlements. Deployment counts alone misstate consumption whenever the metric is user- or core-based.
- ISO/IEC 19770-2 (software identification tags) and 19770-3 (entitlement schema) support automated, verifiable SAM data.
- Audit readiness means the evidence exists before the publisher asks: purchase records, contract terms, deployment data, and a documented methodology.
Worked example
A company has 1,000 employees, 850 managed devices, and a per-user subscription for 900 seats. Discovery shows the application on 870 devices, accessed by 940 named users - including 60 contractors never added to the contract. Because the metric is per user, the shortfall is 40 seats, not the device gap. The analyst then checks the contractor clause: if contractors need separate entitlements, true exposure is 60 seats. Remediation buys 60 seats and adds a joiner/mover/leaver control so contractor accounts are counted at onboarding.
Traps that cost marks
- Comparing install counts to seat counts when the metric is per user or per core.
- Ignoring virtualization and core-factor rules.
- Treating OEM or bundled licenses as freely transferable.
- Forgetting SaaS subscriptions, trials that convert, and developer environments.