CMDB
The asset record your compliance and risk run on.
A three-level hierarchy — assets, IT services, business solutions — with ownership, criticality, environments and structural relationships. Processes stay contextual, never orphaned.
- Online paymentsBusiness solution · Payments team · 2 IT servicesCritical
- Payment gateway APIIT service · 3 assets · 1 providerHigh
- api-gw-01Server · Production · verified 3 d ago
- pg-primaryDatabase · Production · backup tested
- Acme Cloud B.V.Third party · ICT provider · LEI on fileLinked
- Card tokenisationIT service · 2 assetsCritical
- Chargeback handlingBusiness process · Contextual link
Payment gateway API
- Type
- IT service
- Owner
- Platform team
- Lifecycle
- Production
- Criticality
- High
- Supports
- Online payments
- Provider
- Acme Cloud B.V.
- Verified
- 3 days ago
2 compliance links · 1 open risk
Capabilities
What the module does
- 01
Three-level hierarchy
Assets roll up into IT services, IT services into business solutions. Structural links are validated: no shortcuts, no orphans, no accidental cycles.
- 02
Asset types across categories
28 asset types across 13 categories — endpoint, compute, network, security, identity, application, data, cloud, SaaS, integration, certificates & secrets, external dependencies — with the attributes each one needs.
- 03
Ownership & criticality
Technical, business and team owners from your company directory; criticality, environment and lifecycle on every record.
- 04
Topology explorer
Walk the structural graph from a business solution down to the servers it depends on — and back up when something fails.
- 05
Imports & connectors
A CSV import wizard (upload → map fields → preview & resolve → result; unknown types are never silently mapped) plus a connector platform with encrypted credentials, scheduled runs and per-record run history — Entra ID directory sync is live today, further connectors are in build.
- 06
Data quality workspace
Health score, missing ownership, incomplete classification, unlinked objects and duplicate detection with inline merge — because a CMDB is only useful while it is true.
One data model
How it connects to the rest of the workspace
Compliance →
Assets are the targets requirements and controls attach to; posture is computed per solution and service.
Risk →
Every risk names the assets it threatens; criticality feeds the assessment.
Third parties →
Vendors and suppliers live in the same registry and link to the assets they provide.
Questions we get asked
Do we need a complete CMDB before we start?
No. Start with the business solutions that matter and the services under them; the quality workspace tells you what is still missing.
Can we import from existing tools?
Yes — the CSV import wizard with saved mapping templates covers assets and company users, and the connector platform runs scheduled syncs, Entra ID first. New connectors plug into the same configuration, secrets and run-history machinery.
How are business processes modelled?
As context, not hierarchy. An IT process links to IT services, a business process to business solutions — so a process never becomes an orphan asset.
See it on your own frameworks
A walkthrough on a workspace set up for your sector. No trial sign-up, no credit card.