A network administrator is creating an inbound IPv4 extended Access Control List (ACL) on a router interface to filter traffic from the internal management subnet () heading toward a DMZ web server (). The policy requires allowing secure HTTPS access specifically for management workstation , allowing general HTTP traffic from the entire internal subnet to the web server, logging any other blocked attempts from the internal subnet to the DMZ subnet (), and relying on standard firewall drop behavior for remaining traffic. Arrange the following ACL entries in the correct top-to-bottom sequence to ensure proper evaluation without rule shadowing.
- 1access-list 105 permit tcp host 192.168.10.45 host 172.16.50.10 eq 443
- 2access-list 105 permit tcp 192.168.10.0 0.0.0.255 host 172.16.50.10 eq 80
- 3access-list 105 deny ip 192.168.10.0 0.0.0.255 172.16.50.0 0.0.0.255 log
- 4access-list 105 deny ip any any
Answer
The correct sequence places the specific host HTTPS permit rule first, followed by the subnet HTTP permit rule, then the logged subnet-to-DMZ deny rule, and finally the catch-all deny rule.
Access Control Lists evaluate rules sequentially from top to bottom until the first matching rule is found. To function correctly, rules must be organized from most specific to most general: first the host-specific permit rule, then the subnet-wide permit rule for specific ports, followed by an explicit subnet deny with logging, and ending with the default catch-all deny rule.
Step-by-Step Solution
Key Concept
Access Control List (ACL) sequential rule order and rule shadowing prevention