|Audit Logs on CUCM Part 2|
In April I wrote a blog: Audit Logs on Cisco Unified Communications Manager. This blog focused on new audit features available with Cisco Unified Communications Manager (CUCM) 7.1(2) and later. Recent Netpro discussions around a similar topic provided a reminder that there were other aspects of the CUCM system that can be audited, such as database transactions, operating system events, and remote support account activities.
Simply stated, audit logging is a process on the Cisco UC appliance which is responsible for logging certain events to log files used specifically for auditing. With CUCM, there are several audit logs:
The above sources are tracked in separate log files written to the common partition.
The application audit log can be used to track configuration changes and activities for the following applications/services:
The application log was the focus of a previous blog article: Audit Logs on Cisco Unified Communications Manager.
This log focuses on tracking database changes. It can track changes to the schema, database updates, and database reads. You actually can select administrative changes here, which will increase the level of audit information available for auditing admin level information. So, clearly a little overlap between functions.
Database logging is configured using the Unified Serviceability pages. This is same location used to configure the application audit log parameters. These logs can be accessed from RTMT using the "Cisco Audit Logs/informixauditlogs" subfolder:
If you are looking for these files from the CLI:
admin:file list activelog audit/informixauditlogs/*
Operating System Log
The CUCM appliance OS, like any other, performs functions and runs routines in the background. The activities of these functions and routines can be tracked via the system's audit logging. Interestingly enough, this audit log can only be enabled or disabled. Further, you have to enable or disable it from the CLI. For example:
admin:utils auditd enable
The OS audit log will show you when a process executes, what was executed, the process ID, and other, somewhat cryptic information.
These logs can be accessed from RTMT using the "Cisco Audit Logs/vos" subfolder or from the CLI:
admin:file list activelog audit/vos/*
Remote Support Accounting Log
So, there is a feature which allows Cisco TAC to logon to your OS platform and do some low level magic. TAC can access the root shell and look/touch/modify things that standard admins cannot. Remote support accounting tracks the CLI commands that are issued by the technical support teams. You cannot enable/disable this auditing feature. It is engaged automatically when the remote support account is enabled.
The logs themselves are stored in the same location as the operation system logs.