uControlYour CMDB was accurate the day it went live. The estate hasn't stopped changing since.
Configuration changes constantly — new relationships form, components move, standards are broken. Without continuous validation, the CMDB drifts from reality and no one notices until it's wrong.
uControl Insights continuously discovers the estate, and uControl Core validates the model, detects drift and new relationship candidates, and alerts the owner — before anything is written back.
Executive summary
Discovery Drift Detection turns CMDB accuracy from a point-in-time snapshot into a continuously validated position. Insights provides continuous discovery; Core validates modelled components, detects drift and deviations from standard, and routes changes to owners for sign-off.
Drift is caught early, explained clearly, and corrected deliberately — with a full audit trail.
The business challenge
Drift is invisible until it causes harm:
- Configurations change without updating the CMDB
- New relationships form and go unrecorded
- Components deviate from your standard
- Stale and decommissioned assets linger
- Nobody is alerted when accuracy slips
So the model quietly diverges from reality and trust erodes.
The uControl approach
uControl validates continuously. Insights keeps discovering; Core's continuous validation (uAlert) checks that modelled components are still present and correct, detects configuration drift and new relationship candidates, and alerts owners with the evidence.
How it works
Continuous validation Core
Core continuously validates that modelled components are still present and correct.
Drift detection Core
Detects configuration drift and deviations from your modelled standard, and flags new relationship candidates.
Owner alerting Core
Routes drift to the owner — in the UI and on Microsoft Teams — with the supporting evidence.
Continuous discovery Insights
Insights supplies the up-to-date discovery that makes drift visible in the first place.
Sign-off before write-back Core
Owners confirm changes before the CMDB is updated; blackout windows respect change policy.
Reference architecture
Your enterprise Discovery populates your CMDB, while uControl Insights discovers independently. uControl Core takes feeds from your Discovery, your CMDB and Insights to do the analysis.
Customer journey
- Model Establish the validated baseline in Core.
- Watch Insights discovers continuously; Core validates against the model.
- Detect Drift, deviations and new relationships are flagged.
- Route Alerts go to owners with evidence, in-app and on Teams.
- Confirm Owners sign off; changes write back with an audit trail.
Key capabilities
Business benefits
Illustrative scenario
Change control depended on a CMDB that drifted between audits, undermining confidence in impact analysis.
uControl continuously validated the model and alerted owners the moment configurations drifted or new relationships appeared — turning CMDB accuracy into a continuously proven position and giving change management dependable data to work from.
Frequently asked questions
What counts as drift?
Configuration changes, new or removed relationships, and deviations from your modelled standard that affect accuracy.
Does it update the CMDB automatically?
Only with owner sign-off — and blackout windows respect your change policy.
How is this different from discovery?
Insights discovers; Core continuously checks that your model stays accurate over time and explains why it isn't.