Web UI configuration command accounting in TACACS+ server
A Web UI configuration command audit is a security feature that
-
records configuration changes executed through the controller's GUI
-
logs audit information to a TACACS+ server for centralized tracking, and
-
includes details such as the executed command, the user responsible, and session parameters.
The Cisco Catalyst 9800 series wireless controller configuration is stored in databases.
Feature history for Web UI configuration command accounting in TACACS+ server
This table provides release and related information for the feature explained in this module.
This feature is also available in all the releases subsequent to the one in which they are introduced in, unless noted otherwise.
|
Release |
Feature |
Feature Information |
|---|---|---|
|
Cisco IOS XE Cupertino 17.9.1 |
Logging Web UI-Based Configuration Changes in TACACS+ Server |
This feature logs all configuration changes made in controller web UI. Support for logging configurations done in IOS console in TACACS+ server is already available. |
Guidelines for Web UI configuration command accounting in TACACS+ server
-
By default, configuration commands are not logged to the TACACS+ server unless command accounting is configured.
-
All commands are accounted for only when AAA default command accounting is configured for privilege level 15.
-
If AAA default command accounting is not configured, and you want commands to be logged to the TACACS+ server, use these methods:
-
The HTTP named method list command accounting.
-
The AAA named method list (same as the one configured in Step 1) command accounting.
-
Configure AAA accounting using default method list (CLI)
Before you begin
-
Confirm that AAA is enabled on the device.
Procedure
|
Step 1 |
Enter global configuration mode. Example:
|
|
Step 2 |
Create an accounting method list and enables accounting. Example:
|
|
Step 3 |
Return to privileged EXEC mode. Example:
|
The controller records user command activities according to the configured accounting method.
Configure HTTP command accounting using named method list (CLI)
Before you begin
-
Ensure AAA accounting is enabled on your device.
-
Have a predefined AAA accounting method list (if not, configure one).
Procedure
|
Step 1 |
Enter global configuration mode. Example:
|
|
Step 2 |
Configure HTTP command accounting using the named method list. Example:
|
|
Step 3 |
Return to privileged EXEC mode. Example:
|
The device records user command activities in accordance with the configured accounting method.
Feedback