Security+ Flashcards: Ports, Acronyms and Key Concepts
Security+ flashcards work best for the parts of the exam you simply have to remember: port numbers, acronyms, attack names and which control solves which problem. Put the port or acronym on the front, and the meaning plus a one-line exam tip on the back. Study 20 to 30 a day with spaced review and those facts stop being the thing that costs you points.
Here's a quick round of sec+ flashcards from this page. Say your answer out loud, then flip:
🃏 Quiz yourself: 16 cards from this page
Read the front, say your answer, then tap the card to check.
Make, study & print this deck → Opens the free flashcard maker with all 16 cards ready to edit or print.One honest note before you start: CompTIA's official exam objectives are the source of truth for what's on the test. The current exam, SY0-701, launched in November 2023, and CompTIA refreshes Security+ every few years. Download the objectives PDF from CompTIA's site and check your deck against it, especially if a newer version has been announced.
What's on the Security+ exam?
SY0-701 has a maximum of 90 questions in 90 minutes, mixing multiple choice with a few performance-based questions (short hands-on tasks). The passing score is 750 on a scale of 100 to 900. The objectives are split into five domains:
| Domain | Weight | Good flashcard material |
|---|---|---|
| 1. General Security Concepts | 12% | CIA triad, control types, zero trust, PKI and crypto terms |
| 2. Threats, Vulnerabilities and Mitigations | 22% | Attack names, malware types, social engineering, indicators |
| 3. Security Architecture | 18% | Network design, cloud models, resilience, backups |
| 4. Security Operations | 28% | Ports and protocols, IAM, monitoring tools, incident response steps |
| 5. Security Program Management and Oversight | 20% | Risk math, policies, compliance, vendor and audit terms |
Domain 4 is the biggest slice, so if your time is short, that's where your cards should be thickest.
Security+ ports flashcards
Ports are the classic flashcard topic. The trick is to learn them in pairs: the old plain-text protocol and its secure version. The exam loves asking "which port should you allow for the secure version?"
| Front (port) | Back (protocol and tip) |
|---|---|
| 20 / 21 | FTP (data / control). Not encrypted. |
| 22 | SSH, SFTP, SCP. Secure remote access and file transfer. |
| 23 | Telnet. Plain text; replace it with SSH. |
| 25 | SMTP. Sending mail between servers. |
| 53 | DNS. Mostly UDP; TCP for zone transfers. |
| 67 / 68 | DHCP (server / client). |
| 69 | TFTP. No authentication at all. |
| 80 | HTTP. Plain web traffic. |
| 88 | Kerberos. Ticket-based authentication in Windows domains. |
| 110 | POP3. Secure version: 995. |
| 123 | NTP. Time sync, which matters for logs and Kerberos. |
| 143 | IMAP. Secure version: 993. |
| 161 / 162 | SNMP (queries / traps). Use SNMPv3 for encryption. |
| 389 | LDAP. Secure version: 636 (LDAPS). |
| 443 | HTTPS. HTTP over TLS. |
| 445 | SMB. Windows file sharing. |
| 514 | Syslog. |
| 587 | SMTP submission with STARTTLS (465 is also used for implicit TLS). |
| 1812 / 1813 | RADIUS (authentication / accounting). |
| 3389 | RDP. Remote Desktop. |
Make one card per port, not one card with the whole table. Small cards are faster to answer and easier to schedule. The minimum information principle explains why that matters so much.
Security+ acronyms you'll see everywhere
CompTIA's objectives include a long acronym list, and it's honestly the most flashcard-friendly part of the whole exam. Here are the ones worth carding first:
| Front | Back |
|---|---|
| AAA | Authentication, authorization, accounting |
| MFA | Multifactor authentication: two or more of something you know, have or are |
| PKI | Public key infrastructure: the system of CAs, certificates and keys |
| CRL / OCSP | Two ways to check if a certificate was revoked: a downloaded list, or a live lookup |
| IDS / IPS | Intrusion detection (alerts) vs. intrusion prevention (blocks) |
| WAF | Web application firewall: filters attacks like SQL injection and XSS |
| EDR | Endpoint detection and response on laptops and servers |
| DLP | Data loss prevention: stops sensitive data leaving |
| NAC | Network access control: checks a device before it joins the network |
| SAML | XML-based single sign-on between an identity provider and a service |
| RBAC / ABAC | Access by role vs. access by attributes (location, time, department) |
| MDM | Mobile device management |
| TPM / HSM | Chip on the motherboard that stores keys / dedicated hardware device for managing keys at scale |
| BIA | Business impact analysis: what breaks, and how badly, if a system goes down |
| MTTR / MTBF | Mean time to repair / mean time between failures |
| CVE / CVSS | A named, public vulnerability / the 0 to 10 score of how severe it is |
| OSINT | Open-source intelligence: info gathered from public sources |
| SPF / DKIM / DMARC | Email checks: allowed senders / signed messages / the policy that ties them together |
Concept cards: compare-and-contrast is where points hide
Many Security+ questions give you a scenario and two answers that both sound right. The fix is cards that force you to tell look-alike terms apart. Here are good ones to start with:
- Hashing vs. encryption. Hashing is one-way and proves integrity. Encryption is reversible with a key and protects confidentiality.
- Symmetric vs. asymmetric. Symmetric uses one shared key and is fast (AES). Asymmetric uses a public and private key pair (RSA, ECC) and helps with key exchange and signatures.
- Digital signature. The sender signs with their private key; anyone checks it with the sender's public key.
- RTO vs. RPO. RTO is how fast you need to be running again. RPO is how much data, measured in time, you can afford to lose.
- SLE, ARO and ALE. ALE = SLE x ARO. A $10,000 loss that happens twice a year gives an ALE of $20,000.
- Full, incremental and differential backups. Incremental backs up changes since the last backup of any kind; differential backs up changes since the last full one.
- Phishing family. Smishing is by text, vishing is by voice, whaling targets executives, and pretexting is a made-up story to get information.
Ordered lists make great cards too
Put the list name on the front and the steps on the back, or use cloze deletion to blank out one step at a time.
- Incident response: preparation, detection, analysis, containment, eradication, recovery, lessons learned.
- Order of volatility (collect the most fragile evidence first): CPU registers and cache, RAM, swap and temporary files, disk, remote logs, then backups and archives.
How to build your Security+ deck
- Open the free flashcard maker and name your deck "Security+ Ports" or similar. Separate decks for ports, acronyms and concepts make review easier.
- Go through the objectives one domain at a time. Every time you hit a term you couldn't explain to a friend, make a card.
- Keep the back short: the meaning plus one exam tip. If you need a paragraph, split it into two cards.
- Study on screen, then print a set for your commute. Wallet-size cards fit in a jacket pocket.
A simple Security+ flashcard study plan
| Weeks out | What to do with your cards |
|---|---|
| 6 to 8 | Build the deck as you work through your course. Add 20 to 30 new cards a day. |
| 3 to 5 | Keep adding, but spend more time on reviews. Retire cards you've answered right several times in a row. |
| 1 to 2 | No new cards except ones from practice-test mistakes. Drill the "not yet" pile daily. |
| Exam week | Short reviews only. Sleep matters more than one more late-night session. |
Not sure how many cards a day is realistic? How many flashcards per day has numbers for different schedules, and spaced repetition explained shows why reviewing just before you'd forget works so well.
Mistakes to skip
- Memorizing without the "why." The exam asks which control fits a scenario. A card that says "WAF: stops SQL injection at the web app" beats "WAF: web application firewall."
- Only studying flashcards. Performance-based questions need hands-on practice. Cards cover recall; labs and practice tests cover the rest.
- Studying an old version's objectives. Make sure your deck matches the exam code you're actually taking.
- Giant cards. One fact per card. Always.
If Security+ is your second CompTIA exam, the same method works for CompTIA A+ flashcards. Ready to start? Open the free flashcard maker and turn the first page of your objectives into cards tonight.
Frequently Asked Questions
Are flashcards good for studying for Security+?
Yes, for the memory-heavy parts: ports, acronyms, attack types and which control fits which problem. They won't teach you performance-based questions on their own, so pair them with hands-on practice and a practice test.
What ports do I need to know for Security+?
Start with the common ones: 22 (SSH), 25 (SMTP), 53 (DNS), 80 (HTTP), 443 (HTTPS), 389 and 636 (LDAP and LDAPS), 445 (SMB), 3389 (RDP), and the secure mail ports 993 and 995. Know which are secure and which are the old plain-text versions.
How many Security+ flashcards should I study a day?
About 20 to 30 new cards a day plus your reviews works for most people. Two or three short sessions beat one long one.
How long should I study for Security+ with flashcards?
It depends on your background. Many people with some IT experience study for 4 to 8 weeks. Flashcards are a daily 15 to 20 minute habit alongside your main course or book.
Which Security+ exam version is current?
SY0-701 launched in November 2023. CompTIA refreshes Security+ every few years, so check CompTIA's site for the current version and its official exam objectives before you build your deck.
Can I print these Security+ flashcards?
Yes. Open the deck in our free flashcard maker, add your own cards, and print 4 or 8 cards per page. No sign-up needed.



