The Arista Multilayer Switch must generate audit records containing the full-text recording of privileged commands.
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the data and the environment within which it resides). At a minimum, the organization must audit full-text recordings of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
Enable logging on the switch with sufficient detail to fulfill the specifications set forth in the VulDiscussion. To configure logging to a remote syslog server at the informational level, enter: switch#config switch(config)#logging host [ip address] switch(config)#logging trap informational Then configure the following AAA: aaa accounting commands all default start-stop logging [group radius]
Review the switch configuration and verify that logging is enabled. If logging is not enabled or is not enabled with sufficient detail to fulfill the specifications set forth in the VulDiscussion, this is a finding. To determine if logging is enabled, enter: switch#show logging The output must show logging as enabled, with a logging level of informational or debugging. In order to ensure all user commands are captured, the following statement must be in the running config: aaa accounting commands all default start-stop logging [group radius]