A Configuration Management Database provides an early foundation for changing a reactive IT culture into a proactive service provider.
Improved Security Deployment and Assessment of Risk. When assessing a known vulnerability on a server, CMDB information can be used to assess risk based on both the severity of a patch, as well as the business context of the vulnerability. This capability allows IT organizations to prioritize patches that support the business and ensure that critical systems are secured first.
More Accurate and Streamlined Compliance. To better facilitate Sarbanes-Oxley and HIPAA initiatives, IT organizations can tap into the CMDB data model to ensure that asset information is accurate and complete. Additionally, the CMDB coupled with the assignment of accountable CI owners and auditors can better enable IT organizations to demonstrate better internal controls. Tracking CIs, relationships and validating their accuracy through continuous monitoring can provide a higher level of assurance that IT systems and related components are controlled and managed in accordance with legislative requirements.
Other advantages of deploying and optimizing a standard CM process and supporting CMDB toolset may include:
Implementing a CMDB
Deployment of a CMDB can only be accomplished in parallel with a Configuration Management process. Therefore, IT organizations need to establish goals, create a baseline and foster an environment of continuous improvement. In turn, related activities will help IT management and supporting personnel to gain momentum and demonstrate the value of standard policies, processes and supporting procedures.
In order to establish an effective Configuration Management process, process stakeholders need to ensure that any data associated with core IT operational processes is appropriately stored and managed. Guaranteeing the integrity, validity, accuracy and completeness of CM data is no small task, and requires certain levels of accountability and ownership in order to properly manage the data.
Therefore, deployment of a CMDB requires careful consideration of who owns and is accountable for the operational components of the repository itself. At a minimum, the following Key Goal Indicators (KGI) should be reviewed, established and/or communicated to all stakeholders prior to commencing any CM strategy or CMDB implementation:
Bottom Line: For many organizations, simply establishing a starting point for a CMDB can greatly help facilitate effective awareness and maturity of the Configuration Management process. However, incorporating too much detail during an initial CMDB deployment can add significant cost to the process and exceed the actual (or perceived) value it provides. In the end, early adopters of CMDB tools that take a tactical, realistic approach to deployment will be rewarded with more rapid realization of IT service support and delivery efficiencies.
