CompTIA Security+ guideHigh-value skills

Security+ Ports: Do You Need to Memorize Them?

Updated 4 min read3 official sources

Short answer

Not as a recited list. You need to reason about ports and protocols, not memorize an SY0-601-style port sheet. The current SY0-701 objectives mention open service ports, disabling ports and protocols, firewall rules that use ports and protocols, and implementation of secure protocols including port selection. They do not publish a table of numbers you must recite. It still helps to know the common assignments, such as SSH on 22, DNS on 53, HTTPS on 443, and RDP on 3389, and which secure protocol replaces a clear-text one. Learn what the protocol is for first, then the number.

What the current objectives actually say

The SY0-701 objectives, document version 6.0, talk about ports in context. They mention open service ports as a vulnerability, disabling ports and protocols as a mitigation, firewall rules that include ports and protocols, and “implementation of secure protocols” with protocol selection, port selection, and transport method. That is a decision skill.

They do not include a numbered list of ports to memorize. Older Security+ advice, including many SY0-601 writeups, treated a long port sheet as the assignment. CompTIA retired the English SY0-601 exam on July 31, 2024. Do not import that sheet as a SY0-701 requirement. A forum post that says “I saw port 22” is an anecdote. It does not amend the objectives. If the harder question is whether you need the Network+ credential before this exam, that decision is in do you need Network+ before Security+.

What is worth knowing

You should be able to do four things without a chart in your lap.

  1. Say what the protocol is for.
  2. Say whether a safer protocol is the usual replacement.
  3. Notice when a firewall rule allows a service the scenario never needed.
  4. Notice an exposed management service as a vulnerability, even if you are not asked for the number.

The port numbers below are the standard assignments in IANA’s port registry, checked October 16, 2026. They are common protocol knowledge so you can follow a flow. They are not an official SY0-701 answer key, and they are not a claim that these items will appear.

ProtocolUsual portWhat it is forThe reasoning, not a flashcard
SSHTCP 22Remote administration of a hostPrefer it when the alternative is a clear-text remote shell. An allow rule for administration from the whole internet is still a problem even if the protocol is SSH.
HTTPSTCP 443Web traffic protected with TLSAllowing it to a public site can be correct. The same allow does not inspect a SQL payload. That is a web-application question, not a port question.
DNS53, UDP and TCPName lookupA host that can browse the web and cannot resolve names is a different failure from a blocked web port.
RDPTCP 3389A graphical remote desktopConvenient for support, and a common thing to expose by mistake. Ask who needs it and from where before you treat the port as the whole answer.
SMTP with no protectionTCP 25Sending mail in the clearThe objectives care that you can choose a protected option. The number is secondary to “this path is readable.”

Clear-text protocols and their secure swap

Most port questions are really this question: the scenario uses a protocol that sends data in the clear, and you pick the protected one that does the same job. You will meet that choice again in the SSH, TLS, and firewall-rule questions in full Security+ prep.

Clear-text choiceUsual secure replacementWhat to keep straight
Telnet, TCP 23SSH, TCP 22Same job, a remote shell. Only SSH encrypts the session.
HTTP, TCP 80HTTPS, TCP 443HTTPS is HTTP inside TLS. Moving to 443 does not fix the application.
FTP, TCP 21SFTP, which runs over SSH on TCP 22, or FTPS on TCP 990SFTP and FTPS are different protocols. SFTP is not FTP with TLS added.
LDAP, TCP 389LDAPS, TCP 636Same directory lookups, protected by TLS.
POP3, TCP 110POP3 over TLS, TCP 995Mail retrieval.
IMAP, TCP 143IMAP over TLS, TCP 993Mail retrieval that keeps mail on the server.
Mail submission without TLSSubmission on TCP 587 with TLS, or submission over TLS on TCP 465Server-to-server mail still uses 25. The change is about protecting the client’s login and message.
SNMPv1 or v2c, UDP 161SNMPv3, still UDP 161The port does not tell you the version. The secure choice is a configuration, not a new number.

If a stem gives you the number and not the name, translate the number into the job, then decide. If a stem gives you the name, you may not need the number at all. When a translation goes wrong, Fix It in full Security+ prep saves that miss for a second try.

Quick check

Clear text or secure? 3 port-and-protocol calls

Choose the best answer for each port-and-protocol situation. You'll see why right after you answer.

Question 1 of 3

Network switches are still managed over Telnet on TCP 23. Which change keeps the remote-shell job and encrypts the session?

Your answers stay in this browser. Nothing is saved or sent.

How this check works

  • Every answer comes from this guide and the official sources it cites.
  • A short self-check, not a score prediction: it shows which points to reread.

A small practice habit

Read a one-line firewall rule and answer only this: what job did I just allow, and does this scenario need that job from the addresses in the rule? That habit matches “port selection” better than a nightly recital of forty numbers.

The PBQ guide uses the same habit on a rule list. Answer more port-and-protocol scenarios in full Security+ prep to practice that decision. They will not ask you to fill in a blank port from a dumped list.

Trust the source

Official sources

Exam policies can change. Use these primary sources for the most current details.