Week 10 · Lesson 7

Extended ACLs

When you need to say “let this exact server accept HTTPS from this exact client and nothing else”, a standard ACL is helpless — it cannot even see a port. The extended ACL is the precision tool: it matches source and destination address, the protocol, and the port numbers. This lesson covers the syntax, the operands you must know cold (eq, host, any), and the place such a filter must live: close to the source.

CCNA 200-301 Domain 5.0 Security Fundamentals Verified 2026-10-11
Learning objectives
Part 1

What an extended ACL matches

An extended ACL evaluates packets against four dimensions that a standard ACL never sees:

That single sentence is why extended ACLs can express precise security policy — “permit host A to reach host B on port 443” — whereas a standard ACL is stuck at “permit source A”. The price is longer lines and the discipline to write them correctly.

Definition — extended ACL An ACL that can match on the source address, destination address, protocol field, and (for TCP/UDP) the source and destination port numbers. Because it can see where traffic is headed, it is placed as close to the source as possible to stop unwanted traffic early.
In this lesson · select a part to jump

Key ideas & exam traps · select one

Part 2

Numbered ranges: 100-199 and 2000-2699

Numbered extended ACLs live between 100 and 199, with the later expansion 2000 to 2699. The exam throws these ranges at you in two ways: identifying the type of an existing ACL, and spotting invalid statements. When a question refers to “ACL 150”, it is extended by definition; when it writes a port filter inside ACL 10, it is invalid because ACL 10 is standard range.

Exam tip — the four ranges Standard 1-99 / 1300-1999, extended 100-199 / 2000-2699. Many questions only test this: label the range, and you immediately know whether a given statement is legal syntax for that ACL.
Part 3

Reading the full syntax

Here is the complete template for a numbered extended ACL, followed by three realistic examples:

! Template: access-list NUMBER permit|deny PROTOCOL SRCHOST DSTHOST [eq PORT]
R1(config)# access-list 100 permit tcp 192.168.1.0 0.0.0.255 host 203.0.113.10 eq 443
R1(config)# access-list 100 deny tcp any host 203.0.113.10 eq 23
R1(config)# access-list 100 permit ip any any

Decode the first line, from left to right:

Note where eq sits: it always refers to the nearest preceding address. In this line it is the destination port. Placing eq www after the source would match the source port, which is almost never what a server-side rule wants and is a favourite reading trap.

Protocol name and port words are both real IOS: eq 80 and eq http mean the same thing; eq 443 and eq https too. The well-known ports from Week 3 come right back: TCP 22 SSH, 23 Telnet, 80 HTTP, 443 HTTPS, 25 SMTP, 110 POP3, and for UDP, 53 DNS and 123 NTP.

Part 4

eq, host, and any

Three keywords dominate extended-ACL questions:

KeywordMeaningExample
eq <port>“Port must equal this value”eq 443
host <ip>Exactly one addresshost 203.0.113.10
anyAny address at allany

The full family of comparison operators deserves a mention because the exam likes one of them: eq (equal), neq (not equal), gt (greater than), lt (less than), and range <start> <end>. In practice eq and range are what you will configure; gt 1023 occasionally appears for “unprivileged ports”.

Analogy Assembling an extended ACL is like writing a guest list with three answers per person: where they come from (source), which room they may enter (destination), and which event ticket they hold (port/protocol). Only when all three facts match the rule does the guest get in.
Client A 192.168.1.10 R1 Web Server HTTPS 443 permitted tcp any host .10 eq 443 Telnet 23 denied
An extended ACL on R1 (near the source) sees every fact it needs: source, destination, protocol, and port. HTTPS to the web server is permitted; Telnet to the same server is dropped.
Reference table · select a row

Part 5

Place close to the source

The extended ACL’s reward for seeing the destination is that it can be safely deployed near the source: it filters a packet at the first router it meets, so unwanted traffic never crosses the network core. That is both the placement rule and the security benefit:

Compare this with the standard ACL’s “near the destination” rule and you have the two placement bookends every CCNA question expects: standard → destination, extended → source.

Warning Placing an extended ACL outbound near the destination still works functionally, but wastes bandwidth: the denied traffic has already consumed the whole path. The blueprint expects the placement answer based on the ACL type, so answer source — for extended — unless the scenario explicitly justifies otherwise.
Part 6

Named extended ACLs

Named extended ACLs use ip access-list extended and then the same statement grammar in a sub-prompt. Sequence numbers give you surgical editing:

R1(config)# ip access-list extended WEB-ONLY
R1(config-ext-nacl)# 10 permit tcp 192.168.1.0 0.0.0.255 host 203.0.113.10 eq 443
R1(config-ext-nacl)# 20 deny tcp any host 203.0.113.10
R1(config-ext-nacl)# 30 permit ip any any
R1(config-ext-nacl)# exit

With sequence numbers, an administrator can drop statement 20 alone (no 20) or add a new line between 10 and 20 without rewriting the list — something a numbered ACL cannot do cleanly. Named lists are the default choice in modern IOS documentation.

Part 7

Configuration and verification

Putting it together: block Telnet and FTP attempts from the whole network to the web server, allow HTTPS, and leave everything else untouched. The filter belongs close to the clients, so apply it inbound on the router that faces them:

! Build the numbered extended ACL
R1(config)# access-list 100 deny tcp any host 203.0.113.10 eq 23
R1(config)# access-list 100 deny tcp any host 203.0.113.10 eq 21
R1(config)# access-list 100 permit tcp any host 203.0.113.10 eq 443
R1(config)# access-list 100 permit ip any any

! Bind it inbound on the interface facing the users
R1(config)# interface gigabitEthernet0/0
R1(config-if)# ip access-group 100 in
R1(config-if)# end

R1# show access-lists
Extended IP access list 100
    10 deny tcp any host 203.0.113.10 eq telnet (8 matches)
    20 deny tcp any host 203.0.113.10 eq ftp (2 matches)
    30 permit tcp any host 203.0.113.10 eq https (150 matches)
    40 permit ip any any (42 matches)
R1# show ip interface gigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
  Inbound  access list is 100
  Outgoing access list is not set

The counters tell the whole story: Telnet and FTP attempts are being dropped at the edge, HTTPS is flowing, and the catch-all catches the rest. When troubleshooting, zero on a deny with suspected traffic means the rule is not where the traffic passes — check direction and interface before touching the list.

Part 8

Exam traps

Exam tip — answer grammar If an option says “deny a client from using Telnet to a server but allow HTTPS”, look for the two rules: a deny tcp ... eq 23 before a permit ... eq 443, then the final permit ip any any. The deny must precede the broad permit, or first-match wins undoes it.
Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 9 · Your turn

Review

Check what you have learned with these review questions.

Review · 5 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.