As with other logs and trace files on the system, you can access these logs in several ways. If you have a need to customize roles or Group/Role assignments you will want to look at the “Standard Audit Log Administration” role to understand the level of access required for users/groups that need to look at audit logs.Īt this point, you have enabled audit logs for administrative tasks. Authorization levels are implemented via the Groups and Roles configuration objects. Depending on your particular operational model, you may have people with different levels of authorization.
Connect to Cisco Unified Serviceability on your CUCM cluster: 2. The following procedures can be used to accomplish this task:ġ. To access this feature, you will need to browse the audit log parameters from Cisco Unified Serviceability. In my lab, I tested this feature using a CUCM 7.1(3b)SU2 cluster.īy default, audit logs for administrative level tasks are enabled. The ability to enable auditing for administrative tasks was included in CUCM version 7.1(2) and later. There is also an accountability aspect as it is likely that senior support folks want to identify education gaps in their lower tier support teams. Basically, in large organizations there is a need to look at “what has changed” so that if there is an issue reported that is related to human error, the error can be quickly identified and fixed. To summarize, admins need a way to look at an audit trail for administrative changes that occur in their CUCM cluster. I will keep the background discussion to a minimum, because I am sure most readers of this blog understand the need for an auditing solution.
0 kommentar(er)
