Here's what to check to identify and remediate CMDB gaps in ServiceNow:
1. Use Built-In CMDB Health Tools First
CMDB Health Dashboard (Configuration > CMDB Health Dashboard) — gives out-of-box scores for completeness, correctness, compliance, and duplicates
CMDB Query Builder / CI Class Manager — to inspect class structure and CI counts
If not already active, activate the CMDB Health plugin if it isn't already
2. Key Gap Categories to Check
Completeness — CIs missing mandatory fields (owner, support group, environment, location, etc.)
Correctness — CIs with stale data (not updated/discovered recently), broken relationships, orphaned CIs with no parent/relationships
Compliance — CIs not following your CMDB data policies (e.g., missing classification rules, incorrect class assignment)
Duplicates — Same asset represented as multiple CI records (common with multiple discovery sources or manual entry)
Stale/Inactive CIs — CIs not touched by Discovery/Service Mapping in X days but still marked operational
Orphaned Relationships — Relationships pointing to deleted or inactive CIs
Reconciliation Gaps — Conflicting data from multiple data sources (Discovery, manual, integrations) without a proper reconciliation authority set
3. Check Your Data Sources
Review the Identification & Reconciliation Engine (IRE) — is it configured correctly for each CI class and source?
Confirm each data source (Discovery, Service Mapping, integrations, manual entry) has proper reconciliation rules so authoritative sources aren't overwritten by less reliable ones
4. Check CSDM Alignment
Since ServiceNow pushes the Common Service Data Model (CSDM), check if your CI classes, relationships, and service mapping align with CSDM layers (Foundation, Design, Manage Technical Services, etc.) — misalignment is a common source of "gaps" flagged in audits
5. Coverage Gaps
Compare your CMDB against your asset inventory — are there assets in Asset Management or discovered infrastructure with no matching CI?
Check Discovery schedules — are all subnets/domains actually in scope, or are some environments (like the SQL pilot servers from your other question) missing from Discovery coverage?
6. Remediation Approach
Prioritize gaps by business impact (start with CIs tied to critical services/CMDB-dependent processes like Change, Incident)
Set up Data Certification jobs to have CI owners periodically confirm/correct data
Automate what you can via Discovery/Service Mapping rather than relying on manual updates
Establish governance: CI class ownership, mandatory field enforcement, and scheduled housekeeping (deactivating stale CIs, merging duplicates)
Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Bharat Chavan
