You don’t have to, but there are some reasons you should consider it:
Reason Nr. 1: because the ITIL Manuals state: What is an Incident? ”An unplanned interruption to an IT Service or reduction in the Quality of an IT Service. Failure of a Configuration Item that has not yet affected Service is also an Incident. ” (more…)
This process makes sure that the content of your Configuration Management System (CMS) / Configuration Management Database (CMDB) is verified and audited to guarantee the required level of data content accuracy. That goal is reached by executing a set of different procedures searching for discrepancies and raising incidents when difference can not be explained (e.g. some discrepancies can be explained by open changes, that means the TO BE State is already defined, but the change has not been deployed yet, so that the AS IS (discovered state) is not YET correct. (more…)
Below you see picture with an example of a process flow diagram for Configuration Verification & Audit. (more…)