Managing Configuration Items › Configuration Audit and Control Facility (CACF) › Planning and Implementing Change Verification › Prevent Rogue Changes to the Attribute

Prevent Rogue Changes to the Attribute

You want to prevent rogue changes to the IP Address attribute to help ensure CMDB data integrity and require a Change Order for the update. The Change Order must specify the CI and a change specification is not required for the IP Address in order for the change to occur. Change verification occurs at the CI/Change Order level but not at the attribute level. For example, prevent any rogue updates to and Use Incident creation to track the users that request these changes.

Follow these steps:

1. Set Policy1.1 and Policy2.1 to Inactive to disable these policies so that they are not in effect.
2. Create Policy 3.1 with the following information:
   • Enter 3100 as the Sequence.
   • Enter Prevent rogue changes without any Change Order as the description.
   • Select Rogue Update as the alignment.
   • Enter test* as the CI Name and NY as the Location and Any Managed Attribute and an asterisk for all other patterns.
   • Select the Always Cancel Entire Transaction action.
3. Click Save.
4. Create Policy3.2 with the following information:
   • Enter 3200 as the Sequence.
   • Enter Require a Change Order for IP address changes as the description.
   • Select 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 Allow Attribute Update as the action.
5. Click Save.

   This policy eliminates rogue changes because Change Orders must accompany the change.

   The Configuration Manager sees that data not defined in the Change Order is also getting updated since change specifications are not required for changes at the attribute level. For example, requesting a change to increase Memory Installed while changing the IP Address at the same time, would not be considered a rogue change because there is a Change Order. They also would like the Change Orders to be automatically be verified and promoted and determine they want verification at the attribute level.