Clarity, control, and confidence for your CMDB

See the full blast radius of every ServiceNow change - and prove CMDB fixes stick.

CMDBx turns your ServiceNow CMDB into deterministic change-impact evidence, sync-to-sync drift history, and remediation that is verified against the next sync - so you can approve changes with confidence and improve CSDM alignment from real data.

View plans
  • Read-only ServiceNow access
  • No agents, no schema changes
  • Built for CSDM-aligned CMDBs
Explore CMDBx through real product views and ServiceNow CMDB data
ServiceNow ingestion — no agents installed
Read-only
Findings close only after CMDBx checks the CI again
Verified
Write-back with a full audit trail
Governed
Service model validation built in
CSDMv5
Platform

One platform to understand, govern, and fix CMDB risk

Four capabilities, one workflow - from the combined impact of a change to modeling CSDM services and proving that each fix holds after the next sync.

Approve changes without crossing your fingers

Analyze one CI or every affected CI on a ServiceNow change as a single graph. CMDBx follows outage-propagating relationships to the services that depend on them, shows the paths, and flags shared impact, redundancy, and single points of failure - with a ready-to-post work note for CAB.

Features

Everything needed to operate the CMDB with confidence.

ServiceNow manages the CMDB. CMDBx adds a deterministic evidence layer on top of it - change impact and resilience, drift history, exposure review, CSDM modeling, and remediation that is independently verified.

Change impact and resilience

Know what a change touches before CAB approves it.

Analyze a single CI or every affected CI on a ServiceNow change as one graph. CMDBx follows outage-propagating relationships to the CIs and services that depend on them, records which changed CI reaches each impact, and keeps alternate paths.

Evidence surfacedDeterministic impact paths, shared impact across changed CIs, and ServiceNow work-note, PDF, and CSV evidence
  • Blast Radius Simulator
  • Multi-CI change impact
  • Alternate paths and redundancy
  • Single-point-of-failure detection
Evidence you can trust

Know when the answer itself is incomplete.

Every analysis reports how fresh the topology is, which relationships it excluded, and whether a depth, size, or time limit stopped it early. Stale or partial evidence lowers confidence instead of looking complete.

Evidence surfacedConfidence reported separately from risk, so a high score built on stale data never looks certain
  • Evidence confidence
  • Topology freshness
  • Completeness and truncation
  • Saved, immutable results
CMDB activity and drift

See what drifted, and whether a change request covered it.

Compare completed syncs to see added, removed, changed, and reclassified CIs and relationships. Rebuild topology before and after, and flag CMDB drift with no overlapping change request.

Evidence surfacedSync-to-sync change evidence with optional change-request coverage from ServiceNow
  • CMDB Activity ledger
  • Time Machine before and after
  • Relationship deltas
  • Uncovered-change detection
Exposure analysis

Review what a compromised or risky CI can reach.

Exposure Analysis follows CMDB relationships in both directions, including relationships that do not carry outage impact, for security and tabletop reviews. It shows CMDB relationship reachability, not a verified exploit path.

Evidence surfacedDistinct outage and exposure models, so each question uses the right relationship semantics
  • Exposure Analysis
  • Bidirectional traversal
  • Separate rules from outage impact
  • Exportable evidence
Verified remediation

A closed change is not proof that the CMDB is fixed.

Findings track recurring CMDB problems with owners, severity, and history. Review owner, support contact, and operational status corrections through an approved ServiceNow change request. CMDBx closes a finding only after it checks the CI again.

Evidence surfacedApproval tied to an exact preview, tracked ServiceNow change requests, and a later sync that re-runs the original rule
  • Findings with ownership
  • Governed change reviews
  • Approval-bound change requests
  • Post-sync verification
Health and service modeling

Measure CMDB quality and model services from real evidence.

Score each CI and the whole CMDB across completeness, relationships, freshness, ownership, CSDM alignment, and operational status. Validate CSDM 5 patterns, propose service boundaries from existing topology, and model services before governed write-back.

Evidence surfacedDeterministic, versioned health rules and CSDM checks with per-CI evidence
  • CI Health scoring
  • CSDM Validator
  • CSDM Workbench
  • AI Discovery
Outcomes

Operational results, not dashboard theater.

Reduce change risk, improve CMDB quality, and move from reactive troubleshooting to controlled operational decisions — so teams can investigate, validate, and act without waiting on specialist intervention.

Safer change approvals

See the combined impact of every CI on a change, including shared services and single points of failure, before CAB decides.

Faster incident triage

Trace the dependency paths to affected services from CMDB evidence, not guesswork.

Improved CMDB health

Prioritize stale, orphaned, and weakly modeled areas, then confirm each fix against the next sync.

CSDM alignment at scale

Validate service structures continuously instead of periodic clean-up projects.

Security

Built for enterprise security and compliance

CMDBx is architected from the ground up with the security and data governance standards that regulated enterprise environments demand.

Token & credential controls

All integration tokens are time-bound and automatically expire. Credential encryption is fail-safe with zero plaintext fallback paths.

Data minimization by default

Only required CI metadata is retained; raw upstream payload over-collection is prevented. Automated retention and token hygiene jobs continuously enforce lifecycle policy.

Auditable chain of custody

Security-sensitive actions are captured in an append-only tenant-scoped compliance audit stream. Generated impact and remediation reports include verifiable provenance metadata.

Consistent session enforcement

Session policy controls are enforced consistently across protected UI and API flows. Token misuse and authorization-denied paths are captured as explicit compliance events.

ServiceNow OAuth controls for short-lived tokens, public keys, IP restrictions, and allowed scopes
Process

From raw CMDB data to usable insight after the first sync

A simple execution loop your ops teams can actually use day to day.

  1. STEP 01

    Connect

    Secure, read-only connection to your ServiceNow instance. No agents. No production risk.

  2. STEP 02

    Analyze

    CMDBx builds a dependency graph, calculates health metrics, and surfaces CSDM and relationship issues automatically.

  3. STEP 03

    Act

    Assess change impact, route corrections through governed change requests, and let the next sync verify the result.

Frequently asked questions

Common questions about ServiceNow CMDB dependency mapping, blast radius analysis, and CMDB health with CMDBx.

What is a CMDB dependency map in ServiceNow?

A CMDB dependency map visualizes how configuration items (CIs) in your ServiceNow CMDB relate to and depend on each other - which applications run on which servers, which services depend on which infrastructure. CMDBx builds this map automatically from your existing ServiceNow relationship data, so you can see real dependencies without manually tracing records.

What is blast radius analysis for change management?

Blast radius analysis identifies the CIs and services that could be affected if a configuration item fails or changes. CMDBx follows outage-propagating relationships from the changed CI to everything that depends on it, using deterministic rules rather than AI guesses, and shows the paths, excluded relationships, and how complete and fresh the evidence is.

Can CMDBx analyze a change request with more than one affected CI?

Yes. CMDBx can analyze every affected CI on a ServiceNow change request as one graph. It removes duplicate impacts, records which changed CI reaches each impacted CI or service, keeps alternate paths, and flags redundancy and single points of failure. ServiceNow receives a summary and a ready-to-post work note for the change request.

Does CMDBx require write access to ServiceNow?

No. CMDBx ingests your CMDB using read-only ServiceNow access by default - no agents and no schema changes. Governed write-back to ServiceNow (for CSDM modeling and remediation) is a separate, explicitly enabled capability that uses a dedicated write credential. Every write is permission-gated, audited, and read back.

How does CMDBx measure CMDB health?

CMDBx scores each configuration item with deterministic, versioned rules across completeness, relationships, freshness, ownership, CSDM alignment, and operational status, and rolls those into per-environment CMDB health metrics you can track over time. This turns CMDB quality into operating signals you can act on rather than a one-time audit.

How does CMDBx know a CMDB fix actually worked?

CMDBx does not treat a closed change request as proof. For fixes made through a change request, the finding waits for a later complete sync, which re-runs the exact rule that found the problem. The finding closes only when that check passes, and it reopens if the problem returns.

What is CSDM validation and does CMDBx support CSDM 5?

CSDM (Common Service Data Model) validation checks that your service model follows ServiceNow's prescribed structure and relationships. CMDBx validates against CSDM 5, including the Service Instance and Technology Management Service model, and its CSDM Workbench lets you design and commit compliant service models from real CMDB evidence.

How quickly can we see value after connecting?

You see a first dependency graph and CMDB health baseline as soon as the first sync completes. Sync time depends on the size of your CMDB, the CI classes in scope, and your ServiceNow API capacity: a small CMDB can sync in minutes, and a very large CMDB can take several hours for its first full sync. There is no data migration and no schema change - CMDBx reads the CMDB you already have.

Ready to trust
your CMDB again?

Eliminate CMDB blind spots, approve changes with confidence, and keep CMDB health on track - without turning every fix into a project.