The Cisco switch must be configured to audit the execution of privileged functions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-220495	CISC-ND-000940	SV-220495r961362_rule		Medium

Description
Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.

Description

Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.

STIG	Date
Cisco NX OS Switch NDM Security Technical Implementation Guide	2024-06-06

Details

Check Text ( C-22210r539206_chk )
Review the Cisco switch configuration to verify that it is compliant with this requirement. The configuration example below will log all configuration changes. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to log all configuration changes, this is a finding.

Check Text ( C-22210r539206_chk )

Review the Cisco switch configuration to verify that it is compliant with this requirement. The configuration example below will log all configuration changes.

Step 1: Verify that account records will be sent to an AAA server as shown in the example below:

aaa accounting default group RADIUS_SERVERS

Step 2: Verify that the referenced group name has defined AAA servers that are online.

aaa group server radius RADIUS_SERVERS
server 10.1.48.10
server 10.1.48.12

Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server.

If the Cisco switch is not configured to log all configuration changes, this is a finding.

Fix Text (F-22199r539207_fix)
Configure the Cisco switch to log all configuration changes as shown in the following example: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

Fix Text (F-22199r539207_fix)

Configure the Cisco switch to log all configuration changes as shown in the following example:

Step 1: Configure the AAA servers as shown in the example below:

SW1(config)# radius-server host 10.1.48.10
SW1(config)# radius-server host 10.1.48.12

Step 2: Configure an AAA server group as shown in the example below:

SW1(config)# aaa group server radius RADIUS_SERVERS
SW1(config-radius)# server 10.1.48.10
SW1(config-radius)# server 10.1.48.12
SW1(config-radius)# exit

Step 3: Enable AAA accounting as shown in the example below:

SW1(config)# aaa accounting default group RADIUS_SERVERS
SW1(config)# end