Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › How Configuration Audit and Control Facility Works › Verification Policy Prioritization by Sequence Number

Verification Policy Prioritization by Sequence Number

When multiple policies match an attribute update, CACF chooses the policy with the lowest sequence number. Consider the following policies and their sequence numbers.

• Policy name(Policy1) sequence(1000) CI(prod*)
• Policy name(Policy2) sequence(2000) CI(prod-NY*)

When an update to CI(prod1) occurs, Policy1 manages the transaction. When an update to CI(prod-NY-1) occurs, Policy1 still manages the transaction because it has a lower sequence number. In this example, Policy2 never takes effect.

We recommend that you change the sequence numbers so that the most specific policy has the lower sequence number, as shown in the following example policies:

• Policy name(Policy1) sequence(2000) CI(prod*)
• Policy name(Policy2) sequence(1000) CI(prod-NY*)

When an update to CI(prod1) occurs, Policy1 manages the transaction. When an update to CI(prod-NY-1) occurs, Policy2 manages the transaction because it has a lower sequence number.