openskills.info
Course catalog
Course Preview

Configuration Management Databases

A Configuration Management Database (CMDB) is a repository that stores information about IT assets and their relationships. It tracks hardware, software, services, and dependencies so that change, incident, and problem management processes operate with accurate knowledge of the environment.

itIT service management and support

Configuration Management Databases

An incident reaches the service desk: customers cannot check out. The web application looks healthy. The database is responding. A certificate changed an hour ago. Which component supports checkout, and what depends on that certificate?

A configuration management database, or CMDB, helps you answer those questions. It records configuration items and the relationships that connect them. A configuration item, or CI, is a component you choose to manage as one entity. A CI can represent hardware, software, an application, a service, or another resource that matters to service delivery.

The central mental model is a service map backed by governed records.

customer service
      |
      v
 application -> database -> server -> network device
      |              |
   owner          version
      |
 incidents, changes, risks, and controls

The records tell you what exists. The relationships tell you why it matters. Governance keeps both trustworthy enough for decisions.

Why a CMDB exists

Technical information usually begins in many systems. Cloud platforms know about virtual machines. Endpoint tools know about laptops. Deployment systems know about applications. Monitoring tools know about live behavior. Procurement systems know about purchases and contracts.

A CMDB does not need to replace every source. It creates a managed view of selected CIs, their important attributes, and their relationships. That view supports work across service management.

You can use it to:

  • trace a service interruption through technical dependencies;
  • estimate which services a proposed change may affect;
  • connect incidents, problems, changes, and requests to the same CI;
  • identify owners and support groups;
  • find stale, duplicate, missing, or unexpected components;
  • support inventory, security, audit, and continuity decisions.

NIST requires a system-component inventory to reflect the system accurately, include the necessary components, avoid duplicate accounting, use suitable granularity, and support accountability. A CMDB can help meet those goals when its scope and controls match the organization.

A CMDB is more than an asset list

Continue the course

This section is part of the paid course.

See pricing to subscribe, or log in if you already have access.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources