Home Security+ Prep
CompTIA Security+

The Security+ SY0-701 guide

Security+ is broad rather than deep. It tests vocabulary (control types, attack names, data states, agreement types), scenario judgment ("what's the BEST control here?"), and a few formulas. Most misses come from two similar terms, such as detective vs corrective, MOU vs MOA, or smishing vs vishing. This guide groups the look-alikes so you can tell them apart.

01 · Format

What you're walking into

750passing score on a 100–900 scale
≤ 90questions, multiple choice and performance-based
90 minexam time
SY0-701current exam version
  • Performance-based questions come first: match attacks to indicators, place controls, read logs, or configure firewall rules. Flag and return if needed.
  • Watch for BEST, MOST likely, and FIRST. Several answers may be true. Pick the one that most directly meets the scenario.
  • CompTIA refreshed the SY0-701 objectives in 2026 without changing the exam code. The core domains and weights below still apply. Check CompTIA's site for the latest objectives PDF.
  • This practice exam is 60 questions in 60 minutes, ending with a 5-question scenario set.
02 · Weighting

Domain map

DomainWeightFocus
1.0 General security concepts12%Control categories and types, CIA, zero trust, change management, cryptography and PKI.
2.0 Threats, vulnerabilities & mitigations22%Threat actors, vectors, social engineering, malware, attack indicators, mitigations.
3.0 Security architecture18%Cloud and infrastructure models, secure network design, data protection, resilience.
4.0 Security operations28%Hardening, vulnerability management, monitoring, IAM, automation, incident response, forensics.
5.0 Security program management20%Governance, risk analysis, third-party risk, compliance, audits, awareness.
03 · Schedule

A two-week study plan

Day 1

Baseline

Take the full practice exam timed. Note weak domains.

Days 2–5

Operations & threats

Together these are half the exam. Learn the attack names, IR phases, and IAM models.

Days 6–9

Program, architecture, concepts

Risk formulas, agreement types, data states, crypto, control types.

Days 10–13

Full exams

Full timed exams every other day with review. Flashcards daily, which suit this vocabulary-heavy exam.

Day 14

Light review

Look-alike terms and traps only.

04 · General concepts · 12%

General concepts cheat sheet

Control typePurposeExample
PreventiveStop an incident before it happensFirewall rule, lock, MFA
DeterrentDiscourage the attemptWarning sign, visible camera, login banner
DetectiveIdentify an incident as or after it happensIDS, log review, motion sensor
CorrectiveFix damage and restoreRestore from backup, patching after an exploit
CompensatingAlternative when the primary control isn't possibleSegmenting a system that can't be patched
DirectiveTell people what to doPolicy, "authorized personnel only" instruction

Control categories: technical (firewalls, encryption), managerial (policies, risk assessments), operational (guards, training, procedures done by people), physical (fences, locks).

Core principles

  • CIA: confidentiality (encryption, access control), integrity (hashing, signatures), availability (redundancy, backups).
  • Non-repudiation: proof someone did something. Provided by digital signatures.
  • AAA: authentication, authorization, accounting.
  • Gap analysis: compares current state to a desired framework or standard.

Zero trust

  • Control plane: adaptive identity, threat scope reduction, policy-driven access control, policy engine (decides) and policy administrator (communicates the decision).
  • Data plane: subject/system, policy enforcement point (allows or blocks), implicit trust zones.

Deception & physical

  • Honeypot (decoy system), honeynet (decoy network), honeyfile (decoy file), honeytoken (fake credential or record that alerts when used).
  • Physical: bollards, access control vestibule, fencing, lighting, guards, cameras, sensors (infrared, pressure, microwave, ultrasonic).

Change management

  • Approval process, owner, stakeholders, impact analysis, test results, backout plan, maintenance window, SOP.
  • Technical effects: allow/deny lists, downtime, service or app restarts, legacy apps, dependencies.
  • Update diagrams, policies, and version control after the change.

Cryptography

  • Symmetric (one shared key, fast: AES) vs asymmetric (public/private pair: RSA, ECC). Asymmetric is used to exchange symmetric keys (Diffie-Hellman, ECDHE).
  • Hashing (SHA-256) gives integrity, one-way. Salting adds random data before hashing passwords to defeat rainbow tables. Key stretching (PBKDF2, bcrypt) makes brute force slower.
  • Digital signature: hash signed with the sender's private key. Verified with their public key. Gives integrity, authentication, and non-repudiation.
  • To encrypt for someone, use their public key. They decrypt with their private key.
  • Obfuscation: steganography (hide data in other files), tokenization (replace data with a token, mapping stored elsewhere), data masking.
  • Hardware: TPM (in the device, stores keys, measured boot), HSM (dedicated appliance for keys at scale), KMS (key management service), secure enclave.

PKI & certificates

  • CSR (certificate signing request) → CA signs → certificate. A chain of trust ends at the root CA.
  • Revocation: CRL (published list) or OCSP (real-time query). OCSP stapling: the server attaches the response.
  • Wildcard (*.contoso.com, one level of subdomains), SAN (multiple names in one certificate), self-signed (not trusted by default).
  • Key escrow: a trusted third party holds keys for recovery.
  • Blockchain / open public ledger: tamper-evident, distributed record.
05 · Threats, vulnerabilities & mitigations · 22%

Threats cheat sheet

Threat actors

  • Nation-state: most resources and sophistication, long-term espionage (APTs).
  • Organized crime: financial motive (ransomware, fraud).
  • Hacktivist: ideological or political motive (defacement, DDoS, leaks).
  • Insider threat: already has access. Can be malicious or careless.
  • Unskilled attacker: uses others' tools and scripts.
  • Shadow IT: staff using unapproved systems or services.

Social engineering

  • Phishing (email), spear phishing (targeted), whaling (executives), vishing (voice), smishing (SMS).
  • Business email compromise: impersonated or compromised executive or vendor email requests payments.
  • Pretexting: invented scenario to get information. Impersonation.
  • Watering hole: compromise a site the targets visit. Typosquatting: lookalike domains. Brand impersonation.
  • Misinformation (false, unintentional) vs disinformation (false, deliberate).

Malware

  • Ransomware encrypts data for ransom. Trojan pretends to be legitimate. Worm self-replicates over the network. Virus needs a host file and user action.
  • Rootkit hides deep in the OS (kernel). Logic bomb triggers on a condition. Keylogger captures keystrokes. Spyware collects data. Bloatware: unwanted preinstalled software.
  • Fileless malware runs in memory using legitimate tools such as PowerShell.

Application attacks

  • SQL injection: input changes a database query. Fix: parameterized queries, input validation.
  • XSS: injected script runs in other users' browsers. Fix: output encoding, input validation, CSP.
  • CSRF: tricks a logged-in user's browser into sending a request. SSRF: tricks the server into making requests to internal resources.
  • Buffer overflow, memory injection, race condition (TOC/TOU), directory traversal (../), privilege escalation, replay.

Network & credential attacks

  • DDoS, including amplification and reflection (spoofed requests to open DNS/NTP servers).
  • On-path (MITM), DNS poisoning, credential replay, wireless (evil twin, deauthentication).
  • Password spraying: a few common passwords across many accounts (avoids lockouts). Brute force: many passwords on one account.
  • Crypto attacks: downgrade (force weaker protocol), collision (two inputs, same hash), birthday.
  • Physical: RFID cloning of badges, brute force of locks.

Indicators of compromise

  • Impossible travel (sign-ins from distant places minutes apart), concurrent session usage, account lockouts.
  • Unusual resource consumption, resources becoming inaccessible, blocked content alerts.
  • Out-of-cycle logging (logs at unusual times) and missing logs (an attacker covering tracks).

Vulnerability types

  • Zero-day: unknown to the vendor, no patch yet.
  • Virtualization: VM escape, resource reuse. Mobile: sideloading, jailbreaking/rooting.
  • Supply chain: compromised vendor, MSP, software update, or hardware.
  • Misconfiguration, default credentials, open ports, EOL/legacy systems that can't be patched.

Mitigations

  • Segmentation, isolation, access control lists, application allow lists.
  • Patching, encryption, monitoring, least privilege, configuration enforcement, decommissioning.
  • Hardening: EDR, host firewall, HIPS, disable unused ports and protocols, change default passwords, remove unnecessary software.
06 · Security architecture · 18%

Architecture cheat sheet

Infrastructure models

  • Shared responsibility: in IaaS you secure OS and up. In PaaS, apps and data. In SaaS, mainly data and access.
  • Serverless, microservices, containers (share the host kernel) vs VMs (separate OS).
  • Air-gapped networks are physically isolated. Logical segmentation uses VLANs and ACLs. SDN centralizes control.
  • ICS/SCADA, RTOS, embedded, and IoT devices are often hard or impossible to patch. Isolate them and use compensating controls.
  • Infrastructure as code: consistent, reviewable deployments.

Secure network design

  • Fail-open (keeps traffic flowing on failure, availability) vs fail-closed (blocks traffic, security).
  • Inline devices (IPS, firewall) can block. Tap/monitor devices (IDS) only see copies.
  • Firewalls: layer 4 (ports), layer 7 / NGFW (application aware), WAF (protects web apps from SQLi and XSS), UTM (all-in-one).
  • Jump server for admin access. Proxy for web filtering. Load balancer.
  • 802.1X with EAP for port-based network access control.
  • Secure tunnels: IPsec (site-to-site, tunnel mode), TLS VPNs, SD-WAN, SASE.

Data protection

  • Data states: at rest (disk encryption), in transit (TLS, IPsec), in use (memory, secure enclaves).
  • Classifications: public, private, sensitive, confidential, restricted, critical. Types: regulated, PII, PHI, financial, trade secret, intellectual property.
  • Data sovereignty: data is subject to the laws of the country it's stored in. Use geographic restrictions.
  • Methods: encryption, hashing, masking, tokenization, obfuscation, segmentation, permission restrictions.

Resilience & recovery

  • Load balancing (active-active) vs clustering (failover).
  • Sites: hot (fast, expensive), warm, cold (slow, cheap). Geographic dispersion. Platform diversity and multi-cloud avoid single points of failure.
  • COOP: continuity of operations plan. Capacity planning covers people, technology, and infrastructure.
  • Testing: tabletop, failover, simulation, parallel processing.
  • Backups: onsite and offsite, encrypted, snapshots, replication, journaling. Power: UPS bridges to generators.
07 · Security operations · 28%

Security operations cheat sheet

Access control modelWho decidesExample
DAC (discretionary)The owner of the resourceFile owner sets NTFS permissions
MAC (mandatory)The system, using labels and clearancesMilitary classification (Secret, Top Secret), SELinux
RBAC (role-based)Permissions assigned to job rolesHelp desk role can reset passwords
Rule-basedSystem-wide rulesFirewall rules, time-of-day restrictions
ABAC (attribute-based)Policies on attributes (user, resource, environment)Allow if department = Finance AND device = managed AND location = US

Incident response

  1. Preparation
  2. Detection
  3. Analysis
  4. Containment
  5. Eradication
  6. Recovery
  7. Lessons learned

Digital forensics

  • Legal hold: preserve relevant data. Overrides normal retention and deletion.
  • Chain of custody: document who handled evidence, when, and why.
  • Order of volatility (collect first → last): CPU registers and cache, RAM, swap/page file, disk, remote logs, backups/archives.
  • Acquire forensic images and verify them with hashes. Work on copies.
  • E-discovery: identifying and producing electronic evidence for legal cases.

Vulnerability management

  • Find: vulnerability scans (credentialed find more), SAST (static code) and DAST (running app), package monitoring, threat feeds (OSINT, ISACs, dark web), pen tests, bug bounties.
  • False positive: reported but not real. False negative: real but missed (worse).
  • Prioritize with CVSS scores and CVE IDs, plus exposure, environment, and business impact.
  • Respond: patch, segment, compensating controls, insurance, documented exceptions. Then rescan to validate.

Monitoring & tools

  • SIEM: aggregates and correlates logs, alerts. SOAR: automates response playbooks.
  • EDR (endpoints) and XDR (endpoints, network, cloud, email together). UBA/UEBA: user behavior analytics.
  • DLP: blocks sensitive data from leaving. FIM: file integrity monitoring.
  • SCAP and benchmarks (CIS) for automated configuration checks. Agent vs agentless.
  • Email: SPF (authorized sending servers), DKIM (signature), DMARC (policy for failures and reporting).
  • DNS filtering, web filtering (URL categories, reputation), NAC, secure protocols (replace Telnet, FTP, HTTP with SSH, SFTP, HTTPS).

Identity & access

  • Lifecycle: provisioning, deprovisioning (disable at termination), identity proofing, attestation (periodic access review).
  • SSO and federation: SAML (web SSO), OAuth (delegated authorization), OpenID Connect (authentication on top of OAuth), LDAP.
  • MFA factors: something you know, have, are, and somewhere you are. Two passwords isn't MFA.
  • Passwordless: FIDO2 security keys, passkeys, biometrics.
  • PAM: just-in-time permissions, password vaulting, ephemeral credentials.

Hardening, mobile & apps

  • Secure baselines: establish, deploy, maintain. Use CIS benchmarks.
  • Mobile: MDM. Deployment models: BYOD, COPE (corporate-owned, personally enabled), CYOD (choose your own device).
  • Wireless: WPA3, RADIUS/802.1X, site surveys and heat maps.
  • App security: input validation, secure cookies, code signing, sandboxing, static analysis.
  • Asset management: inventory, ownership, classification, tracking, sanitization or destruction with certification at disposal.
  • Automation: user and resource provisioning, guard rails, ticketing. Watch for complexity, single points of failure, and technical debt.
08 · Program management · 20%

Program management cheat sheet

AgreementWhat it is
SLAService level agreement: measurable performance commitments (uptime, response time)
MOUMemorandum of understanding: intent to work together, usually not legally binding
MOAMemorandum of agreement: more formal than an MOU, specific responsibilities
MSAMaster service agreement: overall terms for future work
SOW / WOStatement of work / work order: specific deliverables under an MSA
NDANon-disclosure agreement: protects confidential information
BPABusiness partners agreement: how partners share profits, losses, and responsibilities

Risk analysis

  • SLE = asset value (AV) × exposure factor (EF).
  • ALE = SLE × ARO (annualized rate of occurrence).
  • Qualitative (high/medium/low) vs quantitative (dollar values).
  • Risk register: risks, owners, key risk indicators, thresholds.
  • Risk appetite (how much risk to pursue: expansionary, conservative, neutral) vs risk tolerance (acceptable variation).
  • BIA (business impact analysis) sets RTO, RPO, and identifies critical functions. Also MTTR and MTBF.

Risk strategies

  • Mitigate: add controls to reduce it.
  • Transfer: shift it to someone else (cyber insurance, outsourcing).
  • Avoid: stop the risky activity.
  • Accept: acknowledge it, possibly with a documented exception or exemption.

Governance & roles

  • Policies (high-level what and why: AUP, IR, BC/DR, SDLC, change management) → standards (mandatory specifics) → procedures (step-by-step how) → guidelines (recommendations).
  • Data roles: owner (accountable, sets classification), controller (decides why and how personal data is processed), processor (processes for the controller), custodian/steward (day-to-day handling).
  • Privacy: data subject rights, right to be forgotten (GDPR), data inventory and retention.

Third parties, audits & awareness

  • Vendor assessment: right-to-audit clause, independent assessments, questionnaires, supply chain analysis, due diligence, conflict of interest checks.
  • Pen testing environments: known (white box, full info), partially known (gray box), unknown (black box). Reconnaissance: passive (OSINT, no contact) vs active (scanning).
  • Rules of engagement: scope, timing, and limits for testing.
  • Audits: internal (self-assessment, audit committee) and external (regulators, independent third parties). Attestation.
  • Compliance consequences: fines, sanctions, reputational damage, loss of license, contract impacts.
  • Awareness: phishing simulations, insider threat training, removable media policy, reporting suspicious activity.
09 · Recall

Formulas & ports

Formula or itemValue
Single loss expectancySLE = AV × EF
Annualized loss expectancyALE = SLE × ARO
Example: $200,000 asset, 25% EF, once every 4 yearsSLE $50,000; ALE $12,500
SSH / SFTP22
DNS53
Kerberos88
HTTPS / LDAPS443 / 636
SMTPS / IMAPS / POP3S465 or 587 / 993 / 995
RADIUS1812 / 1813
RDP3389
Syslog514 (TLS 6514)
10 · Traps

Classic traps

Category vs type. Technical, managerial, operational, and physical are categories. Preventive, detective, corrective, and so on are types. A camera is physical (category) and detective or deterrent (type).
Encrypt with the recipient's public key; sign with your private key.
Hashing isn't encryption. It can't be reversed and gives integrity, not confidentiality.
Password spraying vs brute force: spraying tries few passwords on many accounts to avoid lockouts.
Smishing = SMS, vishing = voice, whaling = executives.
Containment comes before eradication in incident response. Lessons learned is last.
RAM before disk in the order of volatility. Don't power off a running system before capturing memory.
Insurance is risk transference, not mitigation.
MOU isn't legally binding; an SLA defines measurable service levels.
A false negative is worse than a false positive: a real issue was missed.
Tokenization keeps no mathematical link to the original data; encryption can be reversed with a key.
DMARC needs SPF and/or DKIM to work. It sets the policy for failures.