Detections
Analytics

1.21 CISC-RT-000340

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

The Cisco perimeter switch must be configured to filter egress traffic at the internal interface on an inbound direction.

GROUP ID: V-221094
RULE ID: SV-221094r999703

Access lists are used to separate data traffic into that which it will route (permitted packets) and that which it will not route (denied packets). Secure configuration of switches makes use of access lists for restricting access to services on the switch itself as well as for filtering traffic passing through the switch.

Inbound versus Outbound: It should be noted that some operating systems default access lists are applied to the outbound queue. The more secure solution is to apply the access list to the inbound queue for three reasons:

 - The switch can protect itself before damage is inflicted.
 - The input port is still known and can be filtered upon.
 - It is more efficient to filter packets before routing them.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Configure the switch to use an inbound ACL on all internal interfaces as shown in the example below:

SW1(config)# int e2/4
SW1(config-if)# ip access-group EGRESS_FILTER in
SW1(config-if)# end

See Also

https://workbench.cisecurity.org/benchmarks/22581

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-7a., CAT|II, CSCv7|14.6, Rule-ID|SV-221094r999703_rule, STIG-ID|CISC-RT-000340, Vuln-ID|V-221094

Plugin: Cisco

Control ID: 8aef2de284db08833a6d68f0d4f7400bccb2603421e2eaaa86207acc484ec2cf