Managing Configuration Items › Configuration Audit and Control Facility (CACF) › Planning and Implementing Change Verification › Require Change Specifications when Updating the Attribute

Require Change Specifications when Updating the Attribute

The Configuration Manager shows concern that data in the CMDB receives multiple updates for changes not specified in the Change Order. For example, a user changes the value of Memory Installed (phys_mem) and IP Address (ip_address) at the same time. In the previous phase, CACF does not consider this request as a rogue change because a Change Order exists.

The Configuration Manager wants to enforce change verification at the attribute level. The Configuration Administrator creates a policy that requires the use of change specifications when updating IP Address and to create an Incident if no rogue update is attempted..

Follow these steps:

1. The Configuration Manager contacts Change Analysts that changes to IP Address must contain a change specification.
2. Set Policy3.1 and Policy3.2 to Inactive to disable these policies so they are not in effect.
3. Create Policy4.1 with the following information:
   • Enter 4000 as the Sequence.
   • Enter Require Change Specifications for IP Address changes as the description.
   • Select Rogue Insert, Rogue Update, and Change Orders Without Specifications as the alignment.
   • Enter test* as the CI name and NY as the Location, and an asterisk for all other patterns.
   • Select IP Address from the Managed Attribute drop-down list.
   • Select Always Cancel Entire Transaction as the action.
4. Click Save.
5. Create Policy4.2 with the following information:
   • Enter 4100 as the Sequence.
   • Enter Require Change Specifications for IP Address changes as the description.
   • Select Change Orders With Specifications as the alignment.
   • Enter test* as the CI Name and NY as the Location pattern.
   • Select IP Address from the Managed Attribute drop-down list.
   • Select Allow Update only if Matches Change Specification as the action.
6. Click Save.

You have successfully completed the appropriate example phases to implement change verification in your environment. You can expand the change verification strategy to include more attributes, CIs, MDRs, and tenants.