Details

Without establishing where events occurred, 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, it is essential for security personnel to know where events occurred, such as switch components, modules, device identifiers, node names, and functionality.

Associating information about where the event occurred within the network provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured switch.

Solution

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

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Cisco_IOS_Switch_Y21M07_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Cisco.

References

• 800-53|AU-3
• CAT|II
• CCI|CCI-000132
• Rule-ID|SV-220437r622190_rule
• STIG-ID|CISC-RT-000210
• STIG-Legacy|SV-110721
• STIG-Legacy|V-101617
• Vuln-ID|V-220437

Source

• Tenable.com/audits