STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Cisco IOS Switch RTR Security Technical Implementation Guide

V-220438

CAT II (Medium)

The Cisco switch must be configured to produce audit records containing information to establish the source of the events.

Rule ID

SV-220438r622190_rule

STIG

Cisco IOS Switch RTR Security Technical Implementation Guide

Version

V3R3

CCIs

CCI-000133

Discussion

Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. To compile an accurate risk assessment and provide forensic analysis, security personnel need to know the source of the event. In addition to logging where events occur within the network, the audit records must also identify sources of events such as IP addresses, processes, and node or device names.

Check Content

Review the switch configuration to verify that events are logged containing information to establish the source of the events as shown in the example below: 

ip access-list extended INGRESS_FILTER 
 permit tcp any any established 
 permit tcp any host x.11.1.5 eq www 
 permit icmp host x.11.1.1 host x.11.1.2 echo 
 permit icmp any any echo-reply 
… 
 … 
 … 
deny ip any any log-input 

Note: When the log-input parameter is configured on deny statements, the log record will contain the Layer 2 address of the forwarding device for any packet being dropped. 

If the switch is not configured to produce audit records containing information to establish the source of the events, this is a finding.

Fix Text

Configure the switch to log events containing information to establish where the events occurred as shown in the example below: 

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