The administrator must bind the ingress ACL filtering packets entering the network to the external interface on an inbound direction.

From Perimeter Router Security Technical Implementation Guide

Part of Bind ingress filters to correct interface

SV-3968r1_rule The administrator must bind the ingress ACL filtering packets entering the network to the external interface on an inbound direction.

Vulnerability discussion

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 routers makes use of access lists for restricting access to services on the router itself as well as for filtering traffic passing through the router. 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 3 reasons:•The router 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.

Check content

Base Procedure: The administrator will bind the ingress ACL filtering packets entering the network to the external interface in an inbound direction. Note: All filters must be applied to the appropriate interfaces on an inbound direction. Ingress filtering is applied to all traffic entering the enclave. The ingress filter would be bound to all external interfaces.

Fix text

Bind the ingress ACL to the external interface (inbound) and the egress ACL to the internal interface (inbound).

Pro Tips

Powered by sagemincer