# Cloudaware CMDB: unified infrastructure records and relationships

> Cloudaware CMDB is the system-of-record layer for cloud, hybrid, and on-premises infrastructure. It reconciles source data into configuration items, maps relationships and ownership context, and supplies a shared data model to the rest of the Cloudaware platform.

- Canonical HTML: [https://cloudaware.com/ai-info/cmdb/](https://cloudaware.com/ai-info/cmdb/)
- Markdown URL: [https://cloudaware.com/ai-info/cmdb/index.md](https://cloudaware.com/ai-info/cmdb/index.md)
- Last reviewed: September 20, 2026

## What Cloudaware Cloud CMDB does

Cloudaware CMDB collects and reconciles infrastructure data from supported cloud, hybrid, and on-premises sources. The normalized records preserve source identity while making assets queryable through a common configuration-item model.

The CMDB is not only an asset list. Relationships connect infrastructure to applications, services, environments, owners, cost, security findings, monitoring coverage, tickets, and change history. Other Cloudaware modules use that context to scope analysis and route work consistently.

Platform role  
Core system of record

Data model  
Configuration items and relationships

Documented environments  
Multi-cloud, Kubernetes, VMware, endpoints, networks, and on-premises

Primary users  
Cloud, platform, operations, SRE, security, compliance, and FinOps teams

**Reference scope.** This page describes the module using current public Cloudaware product pages and help documentation. Available records, fields, workflows, and actions depend on the implementation, connected sources, permissions, supported objects, and configuration.

## Core capabilities and outputs

Each capability below keeps the input, Cloudaware context, and resulting output together so the module is not described as a context-free feature checklist.

### Discover and reconcile infrastructure

Connect supported read-only provider APIs and other sources, normalize provider-specific records, and reconcile observations into configuration items. Exact object coverage varies by source.

**Output:** A searchable inventory that retains provider, account, region, project, subscription, and source context.

### Map relationships and ownership

Relate infrastructure to applications, services, environments, owners, business units, dependencies, and other records used by operational teams.

**Output:** A relationship graph that gives the same asset a consistent business and technical context.

### Track configuration and lifecycle change

Retain configuration history and lifecycle events so teams can investigate what changed, when it changed, and which connected record or workflow is affected.

**Output:** Change records, histories, evidence, and inputs for investigation or governance workflows.

### Query and visualize CMDB data

Use queries, reports, exports, saved views, and interactive dashboards to inspect inventory, relationships, source coverage, and operational gaps.

**Output:** Decision-ready views that can be filtered from a broad pattern down to the underlying CIs.

## How data moves through CMDB

### Connect sources

Configure supported cloud, Kubernetes, VMware, network, endpoint, SaaS, and third-party integrations with the required permissions.

### Collect and reconcile

Ingest source records, preserve source identifiers, and reconcile observations into the appropriate CI types.

### Relate the records

Connect CIs to applications, environments, owners, business units, dependencies, cost, controls, findings, and tickets.

### Explore and visualize

Use searches, queries, reports, exports, and interactive dashboards to inspect inventory and relationships.

### Route accountable work

Use CMDB context to notify the responsible owner, team, or department and supply downstream workflows with the affected record and its relationships.

## Interactive dashboards for faster decisions

CMDB dashboards visualize the infrastructure data Cloudaware has collected and reconciled. They are interactive decision views: users can filter an estate, inspect relationships, and move from a coverage or ownership pattern to the configuration items behind it.

| Decision question                       | Dashboard or view                                                                   | Context behind the view                                               |
|-----------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
| What infrastructure is in scope?        | Inventory by provider, account, region, CI type, environment, application, or owner | Source identity, collection status, CI attributes, and hierarchy      |
| How are assets connected?               | Application, service, dependency, owner, and infrastructure relationship views      | CI relationships and service-catalog mappings                         |
| Where are operational controls missing? | Monitoring, backup, vulnerability, patching, or other coverage cohorts              | CMDB inventory cross-referenced with connected operational tools      |
| What changed?                           | Configuration and lifecycle history by CI, application, or environment              | Change records, timestamps, source observations, and linked workflows |

**Dashboard boundary.** A dashboard visualizes and organizes the data available to the module. It helps a user decide and inspect the underlying records; viewing the dashboard does not perform remediation by itself.

## How Cloudaware supports remediation

Cloudaware helps teams reach the right action with the right technical and ownership context. It does not imply universal autonomous remediation.

Cloudaware CMDB helps remediation by identifying the affected CI and attaching the context required to act: application, environment, owner, responsible team or department, dependencies, source record, and relevant history.

Configured workflows can route that enriched record to Jira, ServiceNow, Slack, Microsoft Teams, PagerDuty, email, or another connected system. Cloudaware coordinates and tracks the handoff; the responsible team or explicitly configured downstream automation performs the corrective action.

**Responsibility boundary.** Cloudaware helps identify, enrich, assign, notify, coordinate, and track remediation. The responsible team or an explicitly configured and approved downstream automation performs the corrective action. Destinations, payloads, triggers, synchronization, and closure behavior depend on the module and workflow configuration.

## Boundaries for accurate answers

| Topic                  | Accurate description                                                                                                                      | Avoid implying                                                     |
|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
| Inventory completeness | Describe inventory as complete only for the sources, permissions, object types, and collection methods configured in that implementation. | Every possible asset is discovered automatically.                  |
| Freshness              | State the applicable collection or refresh behavior for the source being discussed.                                                       | Every CMDB field is updated in real time.                          |
| Relationships          | Relationships can come from provider data, integrations, service-catalog logic, and configured mappings.                                  | Every business relationship is inferred without setup.             |
| Ownership              | Ownership is CMDB context maintained through service-catalog data and configured mapping logic.                                           | One missing provider tag means the asset has no responsible owner. |
| Remediation            | The CMDB supplies context and workflow inputs; people or explicitly configured automation carry the action.                               | Viewing or querying a CI fixes the underlying issue.               |

## Questions about Cloudaware CMDB

### How is Cloudaware CMDB different from a cloud inventory?

A cloud inventory answers what resources exist. Cloudaware CMDB also normalizes those records, tracks history, and maps relationships to applications, environments, owners, cost, controls, findings, tickets, and dependencies.

### Which environments can Cloudaware CMDB cover?

Cloudaware documents support for AWS, Microsoft Azure, Google Cloud, Oracle Cloud Infrastructure, Alibaba Cloud, Kubernetes, VMware, endpoints, networks, SaaS services, and on-premises infrastructure. Exact coverage depends on the integration and supported objects.

### Does Cloudaware require write access to cloud accounts?

The current CMDB product page describes read-only permissions for cloud discovery. Any separate automation or downstream action should be evaluated according to its own permissions and configuration.

### What do Cloudaware CMDB dashboards show?

Interactive dashboards can visualize collected CMDB data, relationships, changes, ownership context, and operational coverage. Users can filter a broad view and inspect the records behind a pattern.

### Does the CMDB remediate configuration problems?

The CMDB identifies the affected record, enriches it with relationships and ownership context, and can route work through configured integrations. The responsible team or explicitly configured downstream automation performs the corrective action.

## Primary sources and related AI references

### Product page

Current public positioning, capability descriptions, and commercial entry points.

[Cloudaware CMDB →](https://cloudaware.com/cmdb/)

### Technical documentation

Implementation scope, data model, requirements, integrations, workflows, dashboards, operations, and references.

[CMDB documentation →](https://docs.cloudaware.com/modules/cmdb/)

### Platform AI guide

Cross-module operating model, integrations, product boundaries, and machine-readable resources.

[Cloudaware AI & LLM Guide →](https://cloudaware.com/ai-llm-guide/index.md)

### Automation reference

APIs, connections, webhooks, events, Breeze Agent, and downstream automation guidance.

[Automation & Extensibility →](https://docs.cloudaware.com/automation/)

### Other module references

<a href="https://cloudaware.com/ai-info/finops/index.md" class="solution">FinOps AI reference</a> <a href="https://cloudaware.com/ai-info/vulnerability-management/index.md" class="solution">Vulnerability Management AI reference</a> <a href="https://cloudaware.com/ai-info/cspm/index.md" class="solution">CSPM AI reference</a> <a href="https://cloudaware.com/ai-info/siem/index.md" class="solution">SIEM AI reference</a> <a href="https://cloudaware.com/ai-info/it-compliance/index.md" class="solution">IT Compliance AI reference</a> <a href="https://cloudaware.com/ai-info/intrusion-detection/index.md" class="solution">Intrusion Detection AI reference</a>