Managing Configuration Items › Configuration Audit and Control Facility (CACF) › CACF Administration and Policy Definition › How Configuration Audit and Control Facility Works

How Configuration Audit and Control Facility Works

CACF governs inbound CI data before loading the data into the CMDB. This verification helps ensure that each requested Change Order executes correctly, and detects and manages rogue changes automatically. The Configuration Administrator (CMDB Administrator) defines verification policies to determine how CA SDM responds when any deviation or variance from the requested change occurs.

The following diagram shows how CACF works:

1. Inbound CI data loads from Web Services, GRLoader, MDR, or the Web Interface to request an attribute update for a CI in the CMDB.
2. Based on the verification policies established by your Configuration Administrator, CACF completes one or more the following actions:
   • CACF accepts the update and modifies the CI data in the CMDB.
   • CACF defers the update to the TWA for further processing.

     For example, your Change Manager handles transactions in the TWA.

   • CACF creates an Incident and lets you manage the ticket.

     For example, your Incident Management process requires managing the Incident for reporting purposes.

   • CACF rejects the update and the CI data is not changed in the database.