STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Cisco IOS Switch NDM Security Technical Implementation Guide

V-220581

CAT II (Medium)

The Cisco switch must produce audit records containing information to establish where the events occurred.

Rule ID

SV-220581r960897_rule

STIG

Cisco IOS Switch NDM Security Technical Implementation Guide

Version

V3R7

CCIs

CCI-000132

Discussion

To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as device hardware components, device software modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the network device provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured device.

Check Content

Review the deny statements in all interface ACLs to determine if the log-input parameter has been configured as shown in the example below.
Note: log-input can only apply to interface bound ACLs.

ip access-list extended BLOCK_INBOUND
 deny icmp any any log-input

If the switch is not configured with the log-input parameter after any deny statements to note where packets have been dropped via an ACL, this is a finding.

Fix Text

Configure the log-input parameter after any deny statements to provide the location as to where packets have been dropped via an ACL:

SW1(config)#ip access-list extended BLOCK_INBOUND
SW1(config-ext-nacl)#deny icmp any any log-input