Cloud and Virtual Asset Management
What the exam tests
Cloud and Virtual Asset Management tests how you extend ITAM into elastic, API-driven environments where assets appear and disappear without a purchase order.
Core rules
- Cloud assets are provisioned, not received. Inventory must come from provider APIs, infrastructure-as-code state, and cloud security posture tools, not from goods-in.
- A tagging standard is the cloud equivalent of an asset record: owner, cost center, environment, application, data classification. Untagged resources are unmanaged resources.
- Virtual machines, containers, and serverless functions have different lifecycles. Containers may exist for minutes; the image and its entitlements still need governance.
- Bring-your-own-license (BYOL) and license mobility rules determine whether on-premises entitlements can be applied in the cloud. Check publisher terms rather than assuming portability.
- The shared responsibility model splits security and configuration duties between provider and customer; ITAM owns the customer side of the inventory.
Worked example
A team runs 400 virtual machines. Tag analysis shows 28% missing an owner tag and 15% idle (CPU below 5% for 30 days). The analyst cannot simply delete them: two are domain controllers for a legacy application, identified through the CMDB relationship map. After owner confirmation, 42 VMs are rightsized and 18 decommissioned, saving roughly 12% of monthly compute. The durable fix is a policy blocking production deployment without mandatory tags.
Traps that cost marks
- Assuming the cloud bill is an asset inventory - it is a cost record, not a configuration record.
- Ignoring ephemeral and containerized workloads.
- Applying on-premises license rules to cloud deployments without checking portability.
- No tag enforcement, so ownership and cost allocation decay.