Perform configuration audits to maintain the integrity of configuration baselines.


Configuration audits confirm that the resulting baselines and documentation conform to a specified standard or requirement. Configuration item related records can exist in multiple databases or configuration management systems. In such instances, configuration audits should extend to these other databases as appropriate to ensure accuracy, consistency, and completeness of configuration item information. (See the definition of “configuration audit” in the glossary.)


Examples of audit types include the following:
  • Functional configuration audits (FCAs): Audits conducted to verify that the development of a configuration item has been completed satisfactorily, that the item has achieved the functional and quality attribute characteristics specified in the functional or allocated baseline, and that its operational and support documents are complete and satisfactory.
  • Physical configuration audits (PCAs): Audits conducted to verify that a configuration item, as built, conforms to the technical documentation that defines and describes it.
  • Configuration management audits: Audits conducted to confirm that configuration management records and configuration items are complete, consistent, and accurate

Example Work Products

  1. Configuration audit results
  2. Action items


1. Assess the integrity of the baselines.

2. Confirm that configuration management records correctly identify configuration items.

3. Review the structure and integrity of items in the configuration management system.

4. Confirm the completeness, correctness, and consistency of items in the configuration management system.

Completeness, correctness, and consistency of the configuration management system’s content are based on requirements as stated in the plan and the disposition of approved change requests.

5. Confirm compliance with applicable configuration management standards and procedures.

6. Track action items from the audit to closure.