Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › Change Verification

Change Verification

Change verification helps ensure that Change Orders execute according to change specifications. Verification occurs after a Change Order enters a change management state such as Verification In Progress and when any kind of CI update occurs. At this time, when data from any MDR or web client user imports into the CMDB, CACF compares the incoming attribute data with active change specifications. If the CI attribute data matches, CACF verifies the change. If the inbound data does not match the Change Order specifications, actions to remediate the variance can occur based on policy.

Executed policies can any of the following actions:

• Rejects a single attribute update from the transaction.
• Rejects the entire transaction, including all attribute and value pairs.
• Loads the entire transaction to the TWA for deferred processing after approval and verification of the transaction.
• Creates an Incident that describes each variance.

  Note: This action can trigger existing notification and automation. To prevent multiple incident creation, rogue change detection only creates a single incident for all rogue changes to a single CI.

• Accepts the transaction unconditionally when accepting data from authorized source MDRs.

For example, the CMDB Administrator can define a policy that creates an Incident when a change to a production server executes incorrectly. When imported data from an authorized MDR does not match a pending change specification, CACF creates an Incident. The policy can allow or reject a CI update by the nonmatching import data. In addition, the Change Manager can have the opportunity to accept the newly discovered value, even if the value does not match the planned change specification exactly.

Note: If multiple discoveries occur during change specification verification, discovery data can invalidate a previously verified change. At the end of verification, the CI is in the state that all the change specifications want.