CompTIA Security+ (SY0-701)
The industry-standard baseline cybersecurity certification — vendor-neutral, DoD 8140/8570 approved, and the most common "you know security fundamentals" credential for analysts, admins, and anyone entering infosec. It validates core skills across threats, cryptography, architecture, operations, and governance/risk.
≤90 questions 90 minutes pass 750/900 MC + PBQs Valid 3 yearsPart 1 — High-Level Overview
What & Why
Security+ proves you can assess an organization's security posture, monitor and secure environments, understand threats and cryptography, and operate within governance/risk/compliance frameworks. It's often the first "real" security cert people earn and satisfies DoD baseline requirements — which is why it's so widely required in job postings.
Exam at a Glance
| Attribute | Value |
|---|---|
| Exam code | SY0-701 (objectives v5.0; launched Nov 2023) |
| Questions | Up to 90 — multiple choice/response + 3–6 performance-based questions (PBQs) |
| Time | 90 minutes |
| Passing score | 750 on a scale of 100–900 (scaled, not a straight 83%) |
| Cost | ~$404–439 USD voucher (discounted bundles exist); no free retake |
| Validity | 3 years — renew with 50 CEUs (+ maintenance fee) or a higher cert |
| Delivery / languages | Pearson VUE (test center or online); EN, JA, PT, ES, TH |
The 5 Domains
Security Operations (28%) is the biggest; together with Threats/Vulns/Mitigations (22%) it's half the exam. Weight your time accordingly.
| Domain | What it tests | Deep dive |
|---|---|---|
| 1 · Concepts 12% | Control types, CIA/AAA, zero trust, physical security, cryptography basics, change management. | → §2 |
| 2 · Threats 22% | Threat actors, vectors, vulnerabilities, indicators of attack, mitigation/hardening. | → §3 |
| 3 · Architecture 18% | Architecture models, securing infra, data protection, resilience/recovery. | → §4 |
| 4 · Operations 28% | Hardening, vuln management, monitoring/SIEM, IAM, automation, incident response, forensics. | → §5 |
| 5 · Program Mgmt 20% | Governance, risk management, third-party risk, compliance, audits, awareness. | → §6 |
Concept Snapshot
Foundations
CIA triad, non-repudiation, AAA, least privilege, defense in depth, zero trust. →Cryptography
Symmetric (AES) vs asymmetric (RSA/ECC), hashing (SHA-2), PKI, digital signatures, TLS. →Attacks
Phishing, DDoS, SQLi, XSS, on-path, privilege escalation, password attacks, malware. →IAM
MFA factors, SSO (SAML/OAuth/OIDC), access models (DAC/MAC/RBAC/ABAC), PAM. →Operations
SIEM, DLP, EDR/XDR, vuln mgmt (CVE/CVSS), incident response, forensics. →GRC
Risk (SLE/ALE/ARO), BIA (RTO/RPO/MTBF/MTTR), frameworks (NIST, ISO, CIS), audits. →Recommended Materials (community consensus)
Study Plan (Quick Version)
- Use the objectives PDF as a checklist; watch Professor Messer in order, taking notes per objective.
- Active recall: reinforce with Anki (acronym soup is real) and per-chapter quizzes in Gibson's book.
- Practice + PBQs: drill Dion exams; review every miss; practice PBQs (ports, log/firewall analysis, attack→mitigation matching).
- Gut-check: Messer's practice exams (closer to real difficulty), then book once consistently 80–85%+.
Part 2 — Thorough Study Guide
1 · Exam Details & PBQs
- Up to 90 questions in 90 minutes. Passing score is 750 / 900 — a scaled score, so it's not simply "get 83% right."
- Performance-based questions (PBQs): ~3–6 interactive simulations (drag-and-drop, configure a firewall/ACL, analyze a log or packet capture, match attacks to mitigations). They're presented first, are time-consuming, offer partial credit, and can be flagged/skipped.
- Strategy: glance at each PBQ, flag the heavy ones, clear all the multiple-choice quickly, then return to the PBQs with your remaining time. Never leave a PBQ blank — partial credit.
- Recommended experience: Network+ and ~2 years of security/admin work (not required). Valid 3 years; renew via 50 CEUs + maintenance fee, or by earning a higher CompTIA cert.
2 · General Security Concepts 12%
Security controls — two axes
| Category (how it's implemented) | Type (what it does) |
|---|---|
| Technical (tech/logical), Managerial (policy/risk), Operational (people/process), Physical (real-world) | Preventive, Deterrent, Detective, Corrective, Compensating, Directive |
Example: a firewall is a technical preventive control; a warning sign is physical deterrent; a backup is technical corrective.
| Control type | What it does | Examples |
|---|---|---|
| Preventive | Stops it before it happens | Firewall rules, locks, least-privilege ACLs |
| Deterrent | Discourages the attempt | Warning signs, visible cameras, login banners |
| Detective | Identifies during/after | IDS, log review, CCTV recording, SIEM alerts |
| Corrective | Fixes after the event | Restore from backup, patch after exploit, IR playbook |
| Compensating | Alternative when the primary control isn't feasible | Extra monitoring/segmentation for an unpatchable legacy system |
| Directive | Tells people what to do | Policies, procedures, AUP, signage ("authorized personnel only") |
Fundamental concepts
- CIA triad — Confidentiality, Integrity, Availability. Plus Non-repudiation (can't deny an action — provided by digital signatures).
- AAA — Authentication (who you are), Authorization (what you may do), Accounting (logging what you did). Applies to people and systems.
- Zero Trust — "never trust, always verify." Split into a Control Plane (adaptive identity, policy engine, policy administrator, threat-scope reduction) and a Data Plane (subject/system, policy enforcement point, implicit trust zones).
- Gap analysis; defense in depth; least privilege.
- Physical security — bollards, access-control vestibule (mantrap), fencing, lighting, cameras, guards, badges, sensors (infrared/pressure/microwave/ultrasonic).
- Deception tech — honeypot, honeynet, honeyfile, honeytoken.
Change management
Approval process, ownership, stakeholders, impact analysis, test results, backout plan, maintenance windows, SOPs; technical implications (allow/deny lists, restarts, downtime, dependencies, legacy apps); documentation & version control. (Cryptography basics are also introduced here — see the full treatment in §7.1.)
3 · Threats, Vulnerabilities & Mitigations 22%
Threat actors & motivations
- Actors: nation-state (APT), unskilled attacker (script kiddie), hacktivist, insider threat, organized crime, shadow IT.
- Attributes: internal/external, resources/funding, sophistication.
- Motivations: data exfiltration, espionage, service disruption, blackmail, financial gain, philosophical/political, revenge, war, chaos.
Threat vectors & social engineering
- Vectors/attack surfaces: message-based (email/SMS/IM), image/file/voice, removable media, vulnerable/unsupported software, unsecure networks (wireless/wired/Bluetooth), open ports, default credentials, supply chain (MSPs/vendors).
- Human/social engineering: phishing, vishing, smishing, pretexting, impersonation, business email compromise (BEC), watering hole, brand impersonation, typosquatting, mis/disinformation.
| Technique | Discriminator (how to tell them apart) |
|---|---|
| Phishing / spear phishing / whaling | Mass email / targeted at a specific person or group / targeted at an executive. |
| Vishing / smishing | Same con by voice call / by SMS text. |
| Pretexting | An invented scenario/identity ("IT here, I need your password to fix your account"). |
| BEC | Compromised or spoofed business email used to redirect payments/data — often after a real mailbox takeover. |
| Watering hole | Compromise a site the target group already visits and wait. |
| Typosquatting / brand impersonation | Look-alike domain (amaz0n.com) / fake brand identity in messages or sites. |
Vulnerabilities
Application (memory injection, buffer overflow, race condition/TOCTOU, malicious update); OS; web (SQLi, XSS); hardware (firmware, end-of-life, legacy); virtualization (VM escape, resource reuse); cloud; supply chain; cryptographic; misconfiguration; mobile (side-loading, jailbreaking); zero-day.
Malware — know the discriminators
| Type | Key behavior |
|---|---|
| Virus | Attaches to files/programs; needs user action to spread. |
| Worm | Self-replicates across the network — no user action needed. |
| Trojan | Malware disguised as legitimate software; RAT = trojan with remote control. |
| Ransomware | Encrypts data, demands payment. First move on detection: isolate/contain; recovery: offline/immutable backups. |
| Rootkit | Hides at OS/kernel (or firmware) level to conceal presence — hard to detect from inside the OS. |
| Logic bomb | Dormant until a trigger (date, event, account deletion) — classic disgruntled-insider scenario. |
| Keylogger / Spyware | Captures keystrokes / monitors activity & exfiltrates. |
| Bloatware | Unwanted pre-installed software widening the attack surface. |
Indicators of malicious activity
Attacks: DDoS (amplified/reflected), DNS/ARP poisoning, on-path (MITM), credential replay, injection, privilege escalation, directory traversal, password spraying/brute force, downgrade, collision/birthday. Account indicators: lockouts, impossible travel (login from two distant places in an hour), concurrent sessions, resource consumption spikes, out-of-cycle or missing logs (attackers clearing tracks), blocked-content alerts. (Full attack reference in §7.2.)
Mitigation & hardening
Segmentation, access control (ACL/permissions), application allow-listing, isolation, patching, encryption, monitoring, least privilege, configuration enforcement, decommissioning. Hardening: endpoint protection, host-based firewall/HIPS, disable unused ports/protocols, change default passwords, remove unnecessary software.
4 · Security Architecture 18%
Architecture models
- Cloud (shared responsibility matrix, hybrid, third-party), IaC, serverless, microservices, on-prem, centralized vs decentralized, containerization, virtualization, IoT, ICS/SCADA, RTOS, embedded, high availability.
- Design considerations: availability, resilience, cost, scalability, ease of deployment/recovery, risk transference, patch availability, power/compute.
- Network infra: physical isolation/air-gap, logical segmentation, SDN.
Securing the enterprise infrastructure
- Device placement, security zones, attack surface; fail-open (availability wins — traffic flows if the device dies) vs fail-closed (security wins — traffic blocked); inline (in the traffic path, can block) vs tap/monitor (copy of traffic, detect only).
- IDS vs IPS: IDS detects & alerts (passive/tap); IPS sits inline and blocks. Detection methods: signature-based (known patterns, misses novel attacks) vs anomaly/behavior-based (baselines, catches novel attacks, more false positives).
- Appliances: jump server (single hardened admin entry point into a secure zone), proxy (forward = controls user egress; reverse = fronts/protects servers), load balancer, sensors/collectors.
- Port security: 802.1X port-based network authentication with EAP + RADIUS — devices must authenticate before getting network access.
- Firewalls: WAF (protects web apps — SQLi/XSS), NGFW (deep packet inspection, application-aware, IPS built in), UTM (all-in-one bundle), Layer 4 (ports/IPs) vs Layer 7 (application content).
- Secure access: VPN — IPSec (AH integrity/auth, ESP adds encryption; tunnel vs transport mode) or TLS; site-to-site (network↔network, always-on) vs client/remote-access; full tunnel (all traffic through VPN — more secure) vs split tunnel (only corporate traffic — faster, less oversight).
- SD-WAN = software-defined WAN routing across links; SASE = SD-WAN + cloud-delivered security stack (SWG, CASB, ZTNA, firewall) as a service.
Protecting data
- Data states: at rest, in transit, in use. Classifications: public, private, sensitive, confidential, restricted, critical. Types: regulated, trade secret, IP, financial, PII/PHI.
- Data roles: owner (accountable), custodian/steward (handles day-to-day protection), controller (decides why/how processed) vs processor (processes on the controller's behalf).
| Method | What it does — and when it's the answer |
|---|---|
| Encryption | Reversible with the key; protects confidentiality in any state. |
| Hashing | One-way; verifies integrity (and stores passwords) — not for retrieval. |
| Masking | Hides part of the value for display (****-****-1234) — original intact underneath. |
| Tokenization | Replaces the value with a token; real value lives in a separate vault. No math relationship — common for card data (PCI). |
| Obfuscation / steganography | Makes data hard to interpret / hides data inside other files. |
| Segmentation + permissions | Limit where data lives and who reaches it; add geographic restrictions for sovereignty. |
Resilience & recovery
- High availability: load balancing (distribute across active nodes) vs clustering (nodes act as one system with failover); geographic dispersion, platform diversity (avoid vendor monoculture), multi-cloud.
- Site types: Hot = fully equipped + near-real-time data, minutes to switch, most expensive. Warm = equipment ready, data restored on activation, hours–days. Cold = space/power only, days–weeks, cheapest.
- Backup types: Full (everything; slow to make, fastest restore) · Incremental (changes since last any backup; fastest to make, restore needs full + every incremental) · Differential (changes since last full; restore needs full + latest differential only). Also: snapshots, replication, journaling, offsite/immutable copies for ransomware.
- Power: UPS (bridges seconds–minutes) → generator (long outages). Testing: tabletop (talk-through), simulation, failover test, parallel processing.
- Capacity planning covers people, technology, and infrastructure — not just servers.
5 · Security Operations 28% — biggest
Hardening & secure baselines
- Secure baselines: establish → deploy → maintain. Harden mobile, workstations, switches/routers, servers, cloud, ICS/SCADA, embedded, RTOS, IoT: disable unused ports/services, change defaults, patch, endpoint protection, host firewall/HIPS.
- Wireless: WPA3 uses SAE (replaces WPA2's crackable PSK 4-way handshake). Enterprise mode = 802.1X + RADIUS (per-user credentials) vs Personal (shared passphrase). EAP-TLS = certificate-based (strongest); PEAP wraps EAP in TLS. Site surveys/heat maps for placement.
- Mobile deployment: BYOD (user-owned — hardest to control), COPE (corporate-owned, personal use allowed), CYOD (user picks from an approved list). Manage all via MDM (enforce encryption, remote wipe, containerization).
- App security: input validation (the #1 defense against injection/XSS), secure cookies, static analysis (source code, pre-run) vs dynamic analysis (running app), code signing (proves integrity/origin), sandboxing.
Asset & vulnerability management
- Asset lifecycle: acquisition → assignment/classification → tracking/inventory → disposal. Sanitization: overwrite/wipe (reusable), degauss (destroys magnetic media), physical destruction (shred/pulverize) + certification of destruction. Deleting/formatting is not sanitization.
- Vulnerability management cycle: identify (scans, static/dynamic analysis, threat feeds/OSINT, pen tests, responsible disclosure / bug bounty) → analyze → respond (patch, segment, compensating controls, exceptions, insurance) → validate (rescan!) → report.
- CVE = the catalog ID of a vulnerability; CVSS = its 0–10 severity score — prioritize by CVSS plus exposure and environment (an internet-facing 7.5 can outrank an isolated 9.8).
- False positive = flagged but not real (wastes time); false negative = real but missed (dangerous). Confirm scanner findings before acting.
Monitoring & tooling
- Activities: log aggregation, alerting, scanning, reporting, archiving, quarantine, alert tuning (reduce false positives so real alerts aren't drowned out).
- SIEM = collect/correlate/alert on logs (detection); SOAR = automate the response with playbooks. EDR = endpoint detect & respond; XDR extends across endpoint + network + cloud. UBA flags abnormal user behavior.
- Also: antivirus, DLP (blocks sensitive data exfiltration — email/USB/uploads), SNMP traps, NetFlow (traffic metadata), vulnerability scanners, SCAP (automates config/vuln checking against benchmarks), FIM (alerts on changed system files), NAC (posture-check devices before admitting them), DNS/web filtering.
Email security — SPF vs DKIM vs DMARC
| Record | What it proves |
|---|---|
| SPF | The sending server/IP is authorized to send for the domain (DNS TXT list). |
| DKIM | The message is signed by the domain and unaltered (crypto signature in headers). |
| DMARC | Policy telling receivers what to do when SPF/DKIM fail (none/quarantine/reject) + reporting. Builds on the other two. |
Identity & Access Management
Provisioning/de-provisioning, identity proofing, federation, SSO (LDAP, OAuth, SAML), attestation; access-control models (MAC, DAC, RBAC, rule-based, ABAC); MFA factors; password policy & managers, passwordless; PAM (just-in-time, vaulting, ephemeral credentials). Full detail in §7.3.
Automation & orchestration
Use cases: user/resource provisioning, guardrails, ticket creation, escalation, CI/testing, APIs. Benefits: efficiency, baseline enforcement, faster reaction, workforce multiplier. Considerations: complexity, cost, single point of failure, technical debt.
Incident response & forensics
- IR process (7 steps): Preparation → Detection → Analysis → Containment → Eradication → Recovery → Lessons Learned.
- Testing: tabletop, simulation. Root cause analysis, threat hunting.
| Phase | "Which phase is this?" — the scenario clue |
|---|---|
| Preparation | Writing playbooks, training, deploying tooling before anything happens. |
| Detection / Analysis | Alert fires; determining scope, validity, and severity. |
| Containment | Isolate the infected host / disable the account / segment — stop the spread first, before cleanup. Almost always the answer to "what do you do FIRST?" |
| Eradication | Remove the malware/root cause, patch the hole. |
| Recovery | Restore systems/data, return to production, monitor closely. |
| Lessons Learned | Post-incident review; feed improvements back into Preparation. |
- Digital forensics: legal hold (preserve everything once litigation is anticipated), chain of custody (documented who-handled-what — breaks admissibility if broken), acquisition & preservation (image, hash the image to prove integrity, work on copies), e-discovery, reporting.
- Order of volatility — collect most-volatile first: CPU registers/cache → RAM → swap/pagefile → disk → remote logs → archived/backup media. A running machine's memory dies with the power — capture it before pulling the plug.
- Investigation data sources: firewall/application/endpoint/OS/IDS-IPS/network logs, metadata, vuln scans, dashboards, packet captures.
6 · Security Program Management & Oversight 20%
Governance
- Policies: AUP, information security, BCP, DRP, incident response, SDLC, change management.
- Standards (password, access control, encryption, physical) & procedures (onboarding/offboarding, playbooks).
- Governance structures (boards, committees), external considerations (regulatory/legal/industry), data roles (owner, controller, processor, custodian/steward).
Risk management
- Identification; assessment (ad hoc/recurring/continuous); analysis (qualitative vs quantitative).
- Quantitative formulas: SLE = AV × EF; ALE = SLE × ARO. BIA metrics: RTO, RPO, MTTR, MTBF.
- Risk register (KRIs, risk owners, thresholds); risk tolerance & appetite (expansionary/neutral/conservative); strategies: Accept, Avoid, Transfer, Mitigate.
Third-party risk
Vendor assessment (pen testing, right-to-audit clause, independent assessments, supply-chain analysis); due diligence & conflict-of-interest checks; ongoing monitoring & questionnaires; rules of engagement.
| Agreement | What it is — pick the right one |
|---|---|
| SLA | Measurable service levels (uptime %, response time) + penalties. |
| MOU | Informal statement of mutual intent — usually not binding. |
| MOA | More formal than MOU — specific responsibilities agreed. |
| MSA | Master agreement setting umbrella terms for a long relationship; individual jobs attach to it… |
| SOW / WO | …as a Statement/Work Order defining one specific project's deliverables. |
| NDA | Confidentiality — keep shared info secret. |
| BPA | Business partners agreement — profit/responsibility split between partners. |
Compliance & audits
- Compliance reporting (internal/external); consequences (fines, sanctions, reputational/contractual/license loss); privacy (data subject, controller vs processor, right to be forgotten, retention).
- Audits/assessments: attestation, internal (audit committee, self-assessment), external (regulatory, third-party), and pen testing (known/partially-known/unknown environment; passive vs active reconnaissance; offensive/defensive/physical).
Security awareness
Phishing campaigns & recognition, anomalous behavior recognition, user training (password mgmt, removable media, social engineering, operational security, remote/hybrid work), reporting & monitoring.
7 · High-Yield Reference
The topics below span multiple domains and appear constantly. Memorize them cold — much of the exam (and the PBQs) draws from here.
7.1 · Cryptography
| Type | Purpose | Examples |
|---|---|---|
| Symmetric | One shared key; fast; bulk data / confidentiality | AES (128/192/256), ChaCha20, 3DES; avoid DES/RC4 |
| Asymmetric | Public/private key pair; key exchange & digital signatures; slower | RSA, ECC/ECDSA (efficient, mobile/IoT), Diffie-Hellman (key exchange) |
| Hashing | Integrity; one-way; fixed length | SHA-2/256/512, SHA-3; avoid MD5 (collisions); HMAC = hash + key |
- Digital signature = hash of the message encrypted with the sender's private key → integrity + authentication + non-repudiation. Encrypt for confidentiality with the recipient's public key.
- Password protection: salt (defeats rainbow tables) + key stretching (bcrypt, PBKDF2, Argon2).
- PKI: CA, RA, CSR, X.509 certs, CRL (revocation list) vs OCSP (real-time status), root of trust, wildcard/SAN certs, key escrow. TLS/HTTPS is hybrid — asymmetric to exchange a symmetric session key.
- Other: TPM (on-device key storage), HSM (dedicated key hardware), secure enclave; obfuscation via steganography, tokenization, data masking; blockchain/open public ledger; key escrow (trusted third party holds a key copy); key stretching makes brute force slow by design.
- Certificate types: wildcard (
*.example.com— all first-level subdomains), SAN (multiple specific names in one cert), self-signed (free, but not trusted by browsers — internal use), third-party/CA-signed (publicly trusted). Getting one: generate a CSR (contains the public key + identity) → CA validates → issues the cert. Private key never leaves you. - Encryption levels (asked as "which scope?"): full-disk (FDE/SED) → partition → volume → file → database → record/column. Finer scope = protection stays while the system runs; FDE only protects data at rest on a powered-off device.
7.2 · Attacks
- Social: phishing / spear phishing / whaling / vishing / smishing / pharming, watering hole, typosquatting, BEC.
- Network: DDoS (amplified/reflected), on-path (MITM), DNS poisoning, ARP poisoning, replay, pass-the-hash.
- Application: SQL injection, XSS (stored/reflected/DOM), CSRF, buffer overflow, race condition (TOCTOU), directory traversal, privilege escalation.
- Password: spraying vs brute force vs dictionary; cryptographic: birthday, collision, downgrade.
7.3 · Identity & Access Management
- MFA factors: something you know (password), have (token/smart card), are (biometric), somewhere you are (geolocation), something you do (behavior). MFA = two or more different factors.
- SSO / federation protocols: SAML (enterprise web SSO), OAuth 2.0 (authorization), OpenID Connect (authentication on OAuth), Kerberos (tickets/TGT, port 88), LDAP/LDAPS. RADIUS vs TACACS+ (TACACS+ separates AAA, uses TCP, Cisco).
- Access-control models: DAC (owner decides), MAC (labels/clearance), RBAC (role), ABAC (attributes), rule-based, time-of-day.
- Principles: least privilege, separation of duties; PAM — just-in-time access, password vaulting, ephemeral credentials.
7.4 · Ports & Protocols (common on PBQs)
| Port | Service | Secure form |
|---|---|---|
| 20/21 | FTP | FTPS (989/990) / SFTP (22) |
| 22 | SSH / SCP / SFTP | (secure) |
| 23 | Telnet | → SSH (22) |
| 25 | SMTP | SMTPS / STARTTLS |
| 53 | DNS | DoH/DoT |
| 80 | HTTP | → HTTPS (443) |
| 88 | Kerberos | — |
| 110 / 143 | POP3 / IMAP | 995 / 993 |
| 161/162 | SNMP | SNMPv3 |
| 389 | LDAP | LDAPS (636) |
| 443 | HTTPS (TLS) | (secure) |
| 445 | SMB | — |
| 514 | Syslog | — |
| 1433 / 3306 | MS SQL / MySQL | — |
| 1812/1813 | RADIUS | — |
| 3389 | RDP | — |
7.5 · Risk, BC & Frameworks
- Quantitative risk: SLE = AV × EF; ALE = SLE × ARO. Risk strategies: Accept / Avoid / Transfer (insurance) / Mitigate.
- Business continuity metrics: RTO (max time to restore), RPO (max data loss), MTBF (mean time between failures — repairable), MTTR (mean time to repair), MTTF (non-repairable lifespan).
- Frameworks: NIST CSF = Identify, Protect, Detect, Respond, Recover (2.0 adds Govern); NIST RMF; NIST 800-53 (federal), 800-171 (CUI); CIS Controls (18)/Benchmarks; ISO 27001/27002; SOC 2; PCI DSS (cardholder data); MITRE ATT&CK, Cyber Kill Chain, Diamond Model; OWASP. Regs: GDPR, HIPAA, SOX.
8 · Study Materials (community consensus)
Averaged across 40+ r/CompTIA and r/SecurityPlus threads (pass write-ups & course debates). The consensus is remarkably consistent.
1 · Video courses
| Course | Why |
|---|---|
| #1Professor Messer (FREE, YouTube) | ~120 videos mapped objective-by-objective + free monthly live study group + free pop quizzes. The default backbone. Critique: terse ("straight to the point") — some beginners want more depth. |
| Jason Dion (Udemy, ~$15–25 on sale) | Narrative, scenario-based; the big draw is it bundles six 90-Q practice exams. The most-recommended paid supplement. |
| Mike Meyers (Udemy) | The go-to if Messer is too terse — fuller explainer, then review with Messer. |
| Mike Chapple (LinkedIn Learning) | Solid but secondary; mainly if you already have LinkedIn Learning. |
2 · Practice exams most important
3 · PBQ & hands-on practice
- Best PBQ prep: Dion's PBQ module and CompTIA CertMaster (Messer's practice exams are MC-only). Free PBQ drills at securityplus.training.
- Memorize for PBQs: ports, reading logs/packet captures, firewall/ACL rule ordering, matching attacks → defenses, basic Linux/networking commands.
4 · Free resources
- Professor Messer's ecosystem (videos + study group + pop quizzes) is the free backbone.
- Community Anki decks (free, often Messer-based) — the community favors grassroots/GitHub decks over paid ones. Great for acronyms.
- The official SY0-701 objectives PDF — use it as your master checklist; make your own notes keyed to it.
5 · Books / notes
- Book #1Darril Gibson & Joe Shelley — "CompTIA Security+ Get Certified Get Ahead: SY0-701 Study Guide" — plain-English, with a 50-Q pre-test, per-chapter quizzes, 300+ practice questions, and a full practice exam.
- Professor Messer's SY0-701 Course Notes PDF (~$20) — summarizes every objective.
Sources
- Official: CompTIA Security+ · Professor Messer resources · Get Certified Get Ahead (Gibson)
- Community: r/CompTIA pass threads (1bit5q6, 1g95zx2, 197lvk7, 191lzhz, 18982rw) · CompTIA brain-dump policy
9 · Study Plan (Retention-Based, ≈3–5 weeks)
Security+ is broad and acronym-heavy, which makes it the ideal candidate for spaced repetition (Anki) and retrieval practice. Cramming a vocabulary this large fails; distributed, self-tested review succeeds — and it's how you'll actually retain the concepts on the job.
| Principle | How to apply it to Security+ |
|---|---|
| Spaced repetition | Run an Anki acronym/concept deck daily from day one — the single highest-ROI habit for this exam. |
| Active recall | Use per-objective quizzes (Gibson's book, Messer's pop quizzes) instead of re-watching. Test, then review misses. |
| Interleaving | Mix domains in practice sets; the exam jumps between crypto, IAM, risk, and operations. |
| Elaboration | For each control/attack, explain why it fits and how it's mitigated — not just the definition. |
| Concrete practice | Do PBQ-style drills early (ports, logs, firewall rules) so the format isn't new. |
| Phase | Focus | Actions |
|---|---|---|
| Week 1 | Concepts + threats | Messer Domains 1–2 in order; start the Anki deck (run it daily forever after). Notes keyed to the objectives PDF. |
| Week 2 | Architecture + operations | Messer Domains 3–4 (Ops is 28% — go deep). Reinforce with Gibson chapter quizzes. Begin PBQ drills (ports, logs, firewall). |
| Week 3 | Program mgmt + first practice | Messer Domain 5. Take your first full Dion exam cold; review every miss and Anki the gaps. |
| Week 4 | Drill to readiness | Rotate through Dion's 6 exams + PBQ practice; interleaved review; push to consistent 80–85%. |
| Week 5 | Gut-check + taper | Messer's practice exams (closer to real). Final acronym/port sweep with the Cram Jam. Light review, good sleep, then sit it. |
Compress to 1–2 weeks with prior A+/Network+/IT experience; total beginners lean toward 4–6 weeks.
10 · Tips & Common Traps
- PBQs first, but do them last. Flag the heavy ones, clear the multiple-choice, then return. Never leave a PBQ blank (partial credit).
- Pick the BEST / MOST likely / FIRST answer — several options are often technically correct. Watch keywords FIRST, BEST, MOST, LEAST, NOT.
- Acronym soup — memorize the acronym list cold (that's what Anki is for).
- Symmetric vs asymmetric vs hashing — and what a digital signature provides (integrity + auth + non-repudiation).
- CRL vs OCSP, RADIUS vs TACACS+, DAC/MAC/RBAC/ABAC, IDS vs IPS, SIEM vs SOAR, EDR vs XDR.
- Risk math: SLE = AV×EF, ALE = SLE×ARO; know RTO/RPO/MTBF/MTTR.
- IR order: Preparation → Detection → Analysis → Containment → Eradication → Recovery → Lessons Learned.
- The real exam often feels less nitpicky than Dion's practice tests — don't panic if Dion scores feel low.