From Perimeter Router Security Technical Implementation Guide Cisco
Part of Management traffic is not blocked by egress ACL.
Associated with IA controls: ECSC-1
The management network must still have its own subnet in order to enforce control and access boundaries provided by Layer 3 network nodes such as routers and firewalls. Management traffic between the managed network elements and the management network is routed via the same links and nodes as that used for production or operational traffic. Safeguards must be implemented to ensure that the management traffic does not leak past the managed network’s premise equipment such as using egress ACLs.
The gateway router of the managed network must be configured with an ACL or filter on the egress interface to block all outbound management traffic. Review router configuration to verify that any traffic destined to the management network is blocked. The configuration example below is blocking all traffic with a destination address from the 10/8 prefix which is being used as the address block for the management network. IOS interface Serial0/0 description to_NIPRNet ip address 188.1.20.3 255.255.255.0 ip access-group 100 in ip access-group 101 out interface Fastethernet 0/0 description to_our_PrivateNet ip address 192.168.1.1 255.255.255.0 ! access-list 101 deny ip any 10.0.0.0 0.255.255.255 log access-list 101 permit ip … … access-list 101 deny ip any any log
Configure the gateway router of the managed network with an ACL or filter on the egress interface to block all outbound management traffic.
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer