Coverage

Review platform and integration coverage by category instead of one long catalog table.

Use these coverage pages to understand what evidence comes in, what the packs normalize, when collectors matter, and what caveats still apply before you trust source breadth claims.

Real VeridataOps data pack builder screenshot showing capability and semantic mapping controls.

Coverage Categories

Find the category that matches the buyer’s first integration-fit question.

Coverage - Cloud and Virtualization

Cloud and virtualization coverage that keeps ownership and lifecycle context visible. Use this page to evaluate cloud and virtualization source coverage, normalization scope, collector fit, and caveats. Open category

Coverage - Endpoint and Identity

Endpoint and identity coverage that explains what exists, who it belongs to, and where control gaps remain. Use this page to assess endpoint, directory, and identity coverage before security or onboarding decisions depend on it. Open category

Coverage - Network and Discovery

Network and discovery coverage that keeps source noise separate from approved estate truth. Use this page to assess network discovery, IPAM, and infrastructure coverage before records or relationships are trusted downstream. Open category

Coverage - Monitoring and Operations

Monitoring and operations coverage that helps teams understand service context before incidents force the question. Use this page to assess monitoring, operations, and infrastructure-state coverage with clear limits and next-step paths. Open category

Coverage - Destination Publishing

Destination publishing coverage that explains what reviewed estate data can be sent downstream and under what caveats. Use this page to evaluate destination publishing for CMDB, ITSM, ITAM, and DCIM targets without implying blind sync or universal parity. Open category

Priority Systems

Start with a named platform when the buyer already knows the estate question.

These pages answer system-specific evaluation questions for the sources and destinations that most often shape the first serious review.

System Coverage - AWS

Review AWS estate evidence before it turns into CMDB or audit truth. Use this page to assess AWS account, region, instance, network, and ownership evidence with explicit caveats. Open system page

System Coverage - Azure

Review Azure estate evidence before it becomes CMDB, onboarding, or audit-facing truth. Use this page to assess Azure subscription, resource, network, and ownership evidence with explicit proof limits. Open system page

System Coverage - VMware

Review VMware inventory and relationships before they are treated as operational truth. Use this page to assess VMware host, cluster, datastore, and VM evidence with explicit review and caveat boundaries. Open system page

System Coverage - Active Directory

Review Active Directory identity and ownership context before security or service workflows depend on it. Use this page to assess users, groups, devices, and ownership context from Active Directory with clear proof limits. Open system page

System Coverage - Okta

Review Okta identity and access evidence before security or onboarding workflows depend on it. Use this page to assess Okta users, groups, assignments, and ownership context with explicit caveats. Open system page

System Coverage - ServiceNow CMDB

Publish reviewed estate context into ServiceNow CMDB without treating raw sync as final truth. Use this page to assess reviewed publication into ServiceNow CMDB with destination caveats and approval boundaries. Open system page

Next Step

Move from category browsing to proof and fit review.

A coverage page should send the visitor toward the docs, proof artifacts, or scoped integration conversation that answers what source support really means.

Docs

Read the coverage caveats Use the supported coverage docs to review pack scope, source limits, and collector assumptions. Review Supported Coverage

Proof

Inspect the modeling surface Use the proof library when the visitor wants the artifact set behind the coverage story. Browse Proof Library

Contact

Route the integration-fit review Use the guided contact path once the buyer can name the system, caveat, and destination question that remains open. Review Integration Coverage