What Is Configuration Management?
Configuration Management is the ITIL v4 practice of ensuring that accurate and reliable information about the configuration of services and the configuration items (CIs) that support them is available when and where it is needed. The Configuration Management Database (CMDB) is the system of record for this information.
Most organizations don't truly know what they have. Servers, applications, licenses, network devices, and their interdependencies exist in spreadsheets, tribal knowledge, or nowhere at all. When something breaks, teams waste hours figuring out what's connected to what.
Griffin IT Group builds and maintains CMDBs that give you complete visibility into your IT estate — every asset, every relationship, every dependency — enabling faster incident resolution, better change planning, and accurate cost allocation.
Key Capabilities
CMDB Design & Implementation
We design and deploy CMDB solutions tailored to your environment using industry-leading platforms and ITIL v4 data models.
Relationship Mapping
Automated discovery and mapping of dependencies between servers, applications, networks, and services.
Automated Discovery
Continuous automated scanning ensures your CMDB reflects the actual state of your environment — not an outdated snapshot.
Configuration Compliance
Baseline configurations and drift detection ensure systems remain in their approved state and unauthorized changes are flagged.
Service Mapping
Map business services to their underlying infrastructure so you understand the blast radius of any CI change or failure.
Impact Analysis
Before making changes, query the CMDB to understand exactly which services and users will be affected.
How We Deliver
- Discovery & Inventory: We deploy automated discovery tools to scan your environment and build a comprehensive inventory of all configuration items.
- Data Model Design: We define CI types, attributes, and relationship models aligned to ITIL v4 and your specific operational needs.
- CMDB Population: Discovered data is normalized, deduplicated, and loaded into the CMDB with proper categorization and ownership assignment.
- Relationship Mapping: Dependencies between CIs are mapped automatically and validated manually to create accurate service topology views.
- Ongoing Maintenance: Continuous discovery, reconciliation, and governance processes keep your CMDB accurate and trustworthy over time.
Understanding Configuration Management in Depth
Configuration management is the connective tissue of IT service management. Every other ITSM practice — incident, problem, change, release, and asset management — depends on accurate configuration data. When a server goes down, incident management needs to know which services and users are affected. When a change is proposed, change enablement needs to understand the blast radius. The CMDB provides this intelligence.
The CMDB data model defines what types of configuration items (CIs) are tracked, what attributes are recorded for each type, and what relationships exist between CIs. Common CI types include servers (physical and virtual), network devices, applications, databases, storage arrays, and cloud resources. Relationships include "runs on," "depends on," "connects to," and "is part of" — creating a multi-dimensional map of your IT environment.
Federation is a critical concept for large or complex environments. Rather than duplicating data from existing systems (monitoring tools, cloud consoles, virtualization platforms), a federated CMDB connects to authoritative sources and aggregates data in real-time. This approach reduces data staleness, eliminates reconciliation overhead, and ensures the CMDB reflects the actual state of the environment.
Configuration baselines define the approved state of a CI — its configuration settings, installed software, patch level, and security policies. Drift detection continuously compares the actual state against the baseline and flags unauthorized or accidental deviations. This capability is essential for security compliance and change validation.
The biggest challenge in configuration management is not building the CMDB — it's keeping it accurate. Without governance processes (who can create/modify/delete CIs, how changes are verified, when reconciliation runs), CMDBs decay rapidly. Within six months of deployment, an ungoverned CMDB can be less than 50% accurate, making it worse than useless because teams make decisions based on incorrect data.
How Griffin IT Group Implements Configuration Management
Griffin IT Group deploys and maintains CMDBs as a foundational service for all managed clients. Our approach combines automated discovery tools with manual validation to achieve and maintain accuracy rates above 95%. We use platforms including ConnectWise, ServiceNow, Device42, and IT Glue depending on client environment complexity and existing tooling.
Our CMDB implementation follows a crawl-walk-run approach. Phase 1 focuses on hardware and network infrastructure — the physical and virtual CIs that are easiest to discover and validate. Phase 2 adds application and service relationships. Phase 3 introduces service mapping, business service views, and integration with change and incident management workflows.
Ongoing CMDB maintenance is built into our operational model. Weekly reconciliation runs compare discovered state against recorded state. Monthly governance reviews address data quality issues. Quarterly service mapping reviews ensure business service dependencies remain accurate as environments evolve.
- Automated Discovery: Agentless and agent-based scanning tools continuously discover CIs across on-premises, cloud, and hybrid environments.
- Service Topology Views: Visual maps showing how infrastructure components connect to deliver business services — invaluable for impact analysis and change planning.
- CMDB-Integrated Change Management: Change requests automatically pull affected CIs from the CMDB, ensuring impact assessments are based on current, accurate data.
- Drift Detection & Alerting: Continuous baseline comparison flags unauthorized configuration changes, supporting security compliance and operational stability.
- Multi-Tenant Architecture: Our CMDB infrastructure supports strict data isolation for multi-tenant clients while enabling cross-client pattern analysis for our operations team.
Value-Added Benefits of Configuration Management
- Faster Incident Resolution: When incidents occur, technicians immediately see what's connected to the affected CI — reducing investigation time by 40-60%.
- Accurate Impact Analysis: Before making changes, teams can see exactly which services, users, and business processes will be affected — preventing unexpected outages.
- Compliance Readiness: Auditable configuration records with change history satisfy SOC 2, ISO 27001, HIPAA, and regulatory requirements.
- Cost Optimization: Visibility into your full IT estate reveals underutilized resources, redundant systems, and optimization opportunities.
- Security Posture Improvement: Configuration baseline enforcement and drift detection identify unauthorized changes and potential security vulnerabilities.
- Strategic Planning Support: Accurate infrastructure data enables better capacity planning, technology refresh scheduling, and architecture decisions.
Do You Really Know Your IT Environment?
Griffin IT Group builds the CMDB foundation your operations need.
Frequently Asked Questions
- What is a CMDB?
- A Configuration Management Database (CMDB) is a centralized repository that stores information about your IT assets (configuration items) and the relationships between them. It serves as the single source of truth for your IT environment.
- How is a CMDB different from an asset inventory?
- An asset inventory lists what you own. A CMDB goes further — it maps relationships and dependencies between assets, showing how servers, applications, networks, and services connect and depend on each other.
- How do you keep the CMDB accurate?
- We use automated discovery tools that continuously scan your environment, reconciliation processes that compare discovered data with CMDB records, and governance procedures that ensure changes are reflected in the CMDB.
- What platforms do you use for CMDB?
- We work with ServiceNow, ConnectWise, Freshservice, Device42, and other ITSM platforms. We recommend the platform that best fits your environment size, complexity, and budget.
- How long does CMDB implementation take?
- Initial discovery and population typically takes 4-8 weeks depending on environment complexity. Relationship mapping and service topology may take an additional 2-4 weeks. Ongoing maintenance is continuous.