A reference diagram showing how a Configuration Management Database models dependencies between configuration items — the hub-and-spoke relationship structure that makes impact analysis possible.
A CMDB is a map of dependencies, not a flat asset list — knowing that this application runs on this server, over this network, backed by this storage, is what makes impact analysis and root-cause work possible.
Last reviewed 2026-09-30
What this shows
How configuration items (servers, applications, network devices, services) relate to each other in a CMDB, and why that relationship map — not just an asset list — is what enables real change-impact and root-cause analysis.
Intended audience
IT operations and ITSM practitioners evaluating or designing a configuration-management approach.
Methodology
Reflects standard ITSM/CMDB modeling concepts (as codified in ITIL 4 service-configuration-management practice), illustrated generically rather than tied to any specific CMDB product’s schema.
Limitations
A conceptual relationship model, not a specific CMDB tool’s data schema or implementation guide. Real CMDB deployments vary significantly by tooling and organizational scale.
Citing this resource
To reference this resource, link directly to this page — e.g. “IT KORR’s CMDB Configuration Item Relationships, itkorr.com/technical-resources/cmdb-configuration-item-relationships.” This page may be linked to and quoted from with attribution; republishing or redistributing the diagram itself requires separate permission.
IT KORR helps regulated and growth-stage businesses operate, secure, and prove the systems this resource describes. Learn about Operational Governance →
