Auditing your SQL Compliance Manager implementation is called self-auditing. Self-auditing consists of regularly checking the integrity of the Repository databases. You can also audit the Repository databases. For example, you can audit specific events, such as logins, on the Repository. For more information, see Registering Your SQL Servers and Verifying Audit Data Integrity.
Tracking SQL CM activities is called monitoring. By default, the Collection Server gathers specific event data on the Repository databases. SQL CM automatically monitors change activity as well as SQLcompliance Agent events. SQL Compliance Manager lists these activities and events in the Activity and Change Logs. For more information, see Monitoring SQLcompliance Activities.
Using these built-in features, you can ensure your audit settings and data remain secure and uncompromised. You can also ensure your SQL CM implementation complies with your internal and external policies.