Software Asset Management Fundamentals and Governance
Why SAM Is a Governance Discipline
Software Asset Management (SAM) is not a purchasing task; it is the governed control of software across its lifecycle from request through retirement. Candidates must know the difference between strategic SAM (aligning software spend with business value) and operational SAM (inventory, reconciliation, and license tracking). Governance supplies the decision rights: who approves entitlements, who owns the license record, who signs off on reconciliation results.
Core Concepts to Master
Know the SAM lifecycle stages (plan, acquire, deploy, manage, retire), the concept of the Effective License Position (ELP) as the gap between entitlements and consumption, and the role of a Software Review Board or SAM steering committee. Understand policy instruments: acceptable use policy, procurement policy, and reclamation policy. Distinguish roles: SAM manager, license analyst, IT asset owner, and procurement.
Traps in Exam Questions
Watch for questions that conflate asset management (hardware and software inventory) with configuration management (state control). Another trap: assuming SAM owns compliance risk; in mature governance, the business owner accepts risk while SAM provides evidence. Also beware answers that treat governance as a one-time project rather than a continuous control cycle.
Worked Rule of Thumb
Apply the "policy-owner-evidence" test to any governance scenario: name the policy that governs the activity, the role accountable for it, and the evidence the control produces. If any of the three is missing, the control is not auditable. For example, a reclamation program needs a policy (unused licenses return after 60 days), an owner (SAM manager), and evidence (reclamation report signed by the asset owner).