Coverage - Cloud and Virtualization

Cloud and virtualization coverage that keeps ownership and lifecycle context visible.

Cloud and virtualization coverage should show what resources exist, who owns them, what service or lifecycle context they belong to, and where scope still depends on credentials or collector reach.

Start with source fit, caveats, and collector requirements for this coverage category.

Diagram showing cloud hosting scenarios and deployment ranges.
Sources Cloud and VM APIs
Normalize Estate meaning
Review Caveats and gaps
Publish Approved context

Coverage Category

What this category is meant to answer

This category helps buyers assess whether AWS, Azure, Google Cloud, VMware, Hyper-V, OpenStack, Kubernetes, or Nutanix evidence can be reviewed with the context needed for estate baselines and downstream publication.

What data comes in Account, subscription, project, host, cluster, VM, storage, network, and workload evidence from cloud and virtualization platforms.
What the pack normalizes Identity, ownership hints, lifecycle, relationships, platform metadata, and estate-ready context instead of one source system's shape.
When collectors matter Collectors matter when private APIs, internal virtualization managers, or customer-network-only systems are not reachable from the SaaS plane.
Coverage caveats Coverage still depends on source permissions, enabled APIs, network position, and the specific pack behavior installed for that source.

Coverage Model

Cloud and virtualization deployment context

Cloud and virtualization coverage needs source access, ownership context, and review before it becomes trusted estate data.

Diagram showing cloud hosting scenarios and deployment ranges.
Coverage Hub Browse all categories
Data Packs See pack catalog
Docs Read collector guidance
Contact Send a message

Next Step

Turn this coverage page into a fit decision.

A detailed coverage page should route the visitor to the broader hub, the caveat docs, and the exact integration-review conversation needed to confirm fit.

Hub

Compare the rest of the coverage model Move back to the coverage hub when the reviewer needs adjacent categories or named-system context. Open Coverage Hub

Docs

Read the modeling caveats Use the supported coverage docs to confirm how data-pack scope, credentials, and collectors shape this category. Review Supported Coverage

Contact

Scope the integration review Route the next conversation only after the exact system, data shape, and destination question are clear. Review Integration Coverage