{
  "examSlug": "security-plus",
  "examCode": "SY0-701",
  "examName": "CompTIA Security+",
  "outline": {
    "title": "Field Guide study notes for the public CompTIA Security+ SY0-701 outline",
    "effective": "SY0-701 objectives as published by CompTIA; Field Guide notes are original and not affiliated with CompTIA",
    "url": "https://www.comptia.org/certifications/security"
  },
  "domains": [
    { "id": "concepts", "name": "General Security Concepts", "weight": 12 },
    { "id": "threats", "name": "Threats, Vulnerabilities, and Mitigations", "weight": 22 },
    { "id": "architecture", "name": "Security Architecture", "weight": 18 },
    { "id": "operations", "name": "Security Operations", "weight": 28 },
    { "id": "governance", "name": "Security Program Management and Oversight", "weight": 20 }
  ],
  "topics": [
    {
      "slug": "exam-format",
      "domainId": "concepts",
      "outlineRef": "Exam characteristics",
      "question": "How is the Security+ SY0-701 exam structured, and what does Field Guide practice cover?",
      "answer": "CompTIA publishes Security+ SY0-701 as a single exam of up to 90 questions in 90 minutes, with a passing score of 750 on a scale of 100 to 900. The sitting mixes multiple-choice items with performance-based questions. The five domain weights on the public outline are General Security Concepts 12%, Threats, Vulnerabilities, and Mitigations 22%, Security Architecture 18%, Security Operations 28%, and Security Program Management and Oversight 20%. Field Guide wrote these notes and the practice items on this site. They are original drafts, not retired CompTIA questions, and Field Guide is not affiliated with CompTIA. This draft bank does not include performance-based questions and has not had a Crosscheck pass.",
      "citation": {
        "label": "CompTIA Security+ certification page (public exam facts)",
        "url": "https://www.comptia.org/certifications/security"
      }
    },
    {
      "slug": "cia-zero-trust",
      "domainId": "concepts",
      "outlineRef": "Domain 1 — fundamental concepts",
      "question": "What is the CIA triad, and how does zero trust differ from trusting the corporate LAN?",
      "answer": "Confidentiality keeps data from unauthorized disclosure, integrity keeps it from unauthorized change, and availability keeps it reachable when it is needed. Authentication, authorization, and accounting (AAA) are access functions, not a replacement for CIA. Zero trust refuses implicit trust based on network location. Each request is authenticated, authorized, and preferably encrypted, and the design assumes an attacker may already be inside. NIST SP 800-207 describes that model. A locked-down LAN with no per-request check is the older castle-and-moat approach.",
      "citation": {
        "label": "NIST SP 800-207, Zero Trust Architecture",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-207/final"
      }
    },
    {
      "slug": "crypto-building-blocks",
      "domainId": "concepts",
      "outlineRef": "Domain 1 — cryptographic solutions",
      "question": "How do symmetric encryption, asymmetric encryption, hashing, and a digital signature differ?",
      "answer": "Symmetric ciphers such as AES use one shared key for encryption and decryption and are the usual choice for bulk data. Asymmetric algorithms such as RSA and elliptic-curve cryptography use a key pair and are slower, so they wrap keys and support signatures rather than encrypting large files alone. A hash such as SHA-256 is one-way and detects change; it does not hide the file. A digital signature is a hash encrypted with the sender’s private key. Checking it with the public key shows integrity, authentication, and non-repudiation. Confidentiality still requires encrypting the body. A salt makes identical passwords hash differently. OCSP or a certificate revocation list answers whether a certificate is still trustworthy.",
      "citation": {
        "label": "NIST Computer Security Resource Center — cryptography publications",
        "url": "https://csrc.nist.gov/projects/cryptographic-standards-and-guidelines"
      }
    },
    {
      "slug": "threat-actors",
      "domainId": "threats",
      "outlineRef": "Domain 2 — threat actors",
      "question": "How should a study set separate hacktivists, insiders, nation-states, and unskilled attackers?",
      "answer": "Separate motive from skill. A hacktivist acts for a political or social cause, often with a visible effect such as a defacement. An insider already has authorized access and abuses it; the control problem is least privilege, monitoring, and offboarding, not a missing firewall rule. A nation-state or advanced persistent threat pursues strategic intelligence or disruption and can spend time staying quiet. An unskilled attacker reuses other people’s tools. Shadow IT is an employee using unsanctioned systems, which is a governance problem as well as a threat. One person can sit in more than one of these descriptions, so the exam stem’s motive and access are the clues.",
      "citation": {
        "label": "CISA, cybersecurity best practices and threat topics",
        "url": "https://www.cisa.gov/topics/cybersecurity-best-practices"
      }
    },
    {
      "slug": "social-engineering",
      "domainId": "threats",
      "outlineRef": "Domain 2 — social engineering",
      "question": "What is the difference between phishing, spear phishing, whaling, vishing, smishing, tailgating, and piggybacking?",
      "answer": "Phishing is a broad fraudulent message. Spear phishing is aimed at a specific person or role. Whaling aims at a senior executive, often a payment or credential request. Vishing is voice. Smishing is SMS. Pretexting invents a story that justifies the request. Tailgating is following someone through a physical control without that person’s consent. Piggybacking is when the authorized person knowingly lets the other person through. A watering-hole attack compromises a site the group already visits. Typosquatting uses a lookalike domain. Training plus a simple report path is the people control; technical filters do not replace it.",
      "citation": {
        "label": "CISA, Avoiding Social Engineering and Phishing Attacks",
        "url": "https://www.cisa.gov/news-events/news/avoiding-social-engineering-and-phishing-attacks"
      }
    },
    {
      "slug": "malware-and-injection",
      "domainId": "threats",
      "outlineRef": "Domain 2 — vulnerabilities and malicious activity",
      "question": "How do common malware families and injection bugs differ on SY0-701?",
      "answer": "A virus needs a host file and usually a user action. A worm spreads on its own. A trojan looks legitimate. Ransomware extorts, often by encrypting files. A rootkit hides. A logic bomb waits for a condition such as a date. SQL injection concatenates untrusted input into a query; parameterized queries are the fix. Stored cross-site scripting saves a script that later runs in other browsers. Cross-site request forgery uses an existing signed-in session. An on-path attacker relays or changes traffic. A zero-day has no vendor patch yet. CVE names a vulnerability. CVSS scores it.",
      "citation": {
        "label": "OWASP, SQL Injection",
        "url": "https://owasp.org/www-community/attacks/SQL_Injection"
      }
    },
    {
      "slug": "cloud-responsibility",
      "domainId": "architecture",
      "outlineRef": "Domain 3 — architecture models",
      "question": "Who patches what in IaaS, PaaS, and SaaS?",
      "answer": "In infrastructure as a service the provider runs facilities, hardware, and the hypervisor, and the customer patches the guest operating system, identity, and data. In platform as a service the provider also runs the operating system and runtime, and the customer owns the application and its data. In software as a service the provider runs the application, and the customer still decides who may sign in and how data is classified. A shared-responsibility chart is the exam tool: do not assign guest-OS patching to the provider on an IaaS stem, and do not assign physical power to the customer. IoT and industrial systems often cannot take the same agent or patch cadence, so they are segmented instead.",
      "citation": {
        "label": "NIST SP 800-145, The NIST Definition of Cloud Computing",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-145/final"
      }
    },
    {
      "slug": "resilience-objectives",
      "domainId": "architecture",
      "outlineRef": "Domain 3 — resilience and recovery",
      "question": "What is the difference between RPO and RTO, and between hot, warm, and cold sites?",
      "answer": "Recovery point objective is how much data loss is acceptable, measured in time back from the failure. Recovery time objective is how long the service may stay down. Swapping those two is a common miss. A hot site is equipped and kept close to production so it can take over quickly. A warm site is partially built. A cold site is space and power with little or no equipment. A full backup in the same rack fails with the site. Incremental backups copy changes since the last backup. Differential backups copy changes since the last full backup. A business impact analysis is what sets the objectives.",
      "citation": {
        "label": "NIST SP 800-34 Rev. 1, Contingency Planning Guide",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-34/rev-1/final"
      }
    },
    {
      "slug": "segmentation",
      "domainId": "architecture",
      "outlineRef": "Domain 3 — enterprise infrastructure",
      "question": "What do microsegmentation, a jump server, 802.1X, and an air gap each accomplish?",
      "answer": "Microsegmentation places policy close to each workload so east-west traffic is not wide open after one breach. A jump server, or bastion, is the hardened host administrators must pass through. IEEE 802.1X keeps a switch port closed until the endpoint authenticates, typically with RADIUS. An air gap has no routine network path; removable media then becomes the thing to control. A honeypot is a decoy, not a production control. A site-to-site VPN joins two networks at the gateways. A remote-access VPN joins a user client to a network. Data loss prevention watches sensitive data leaving, which is a data-protection control rather than a routing design.",
      "citation": {
        "label": "NIST SP 800-207, Zero Trust Architecture (segmentation and policy enforcement)",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-207/final"
      }
    },
    {
      "slug": "incident-response",
      "domainId": "operations",
      "outlineRef": "Domain 4 — incident response",
      "question": "What incident-response order does Security+ expect, and what is containment for?",
      "answer": "The sequence tested for SY0-701 follows the classic lifecycle in NIST SP 800-61 Revision 2: preparation, detection and analysis, containment, eradication, recovery, and post-incident lessons. Containment stops the spread before cleanup. Quarantine a confirmed host instead of emailing the sample to the whole company. A tabletop exercise is a discussion and does not stop production. A full interruption test does. Capture volatile memory before powering a host off if keys may be in RAM, and keep a chain of custody if the image may be used as evidence. A playbook is the incident procedure. A runbook is the operational procedure for a routine task.",
      "citation": {
        "label": "NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-61/rev-2/final"
      }
    },
    {
      "slug": "identity-and-mfa",
      "domainId": "operations",
      "outlineRef": "Domain 4 — identity and access",
      "question": "What does least privilege change, and which MFA resists a real-time phishing proxy?",
      "answer": "Least privilege gives only the access the current role needs. Recertification is the periodic check that those rights are still needed. Offboarding disables the account and revokes sessions at departure; deletion can wait for retention. Federation lets a company identity provider sign users into a relying application, commonly with SAML or OpenID Connect. SMS one-time codes can be relayed through a lookalike site. A FIDO2 or WebAuthn key signs a challenge bound to the real origin, so the lookalike cannot replay it. Privileged access management vaults admin credentials, limits the checkout, and rotates them. Something you know, something you have, and something you are are the factor classes; two passwords are still one class.",
      "citation": {
        "label": "NIST SP 800-63B, Digital Identity Guidelines: Authentication and Lifecycle Management",
        "url": "https://pages.nist.gov/800-63-3/sp800-63b.html"
      }
    },
    {
      "slug": "vulnerability-operations",
      "domainId": "operations",
      "outlineRef": "Domain 4 — vulnerability management and tools",
      "question": "How do a vulnerability scan, a credentialed scan, and a penetration test differ?",
      "answer": "A vulnerability scan lists likely weaknesses. A credentialed scan signs in and sees patch level and configuration, which reduces guesswork. A non-credentialed scan sees the outside view. A false positive is a finding that is not real. A false negative is a real flaw the test missed. A penetration test tries to exploit findings under written rules of engagement. A SIEM aggregates and correlates logs. SOAR runs response playbooks from those events. Endpoint detection and response records behavior and can isolate a host. An application allow list permits only approved programs. A firewall’s implicit deny blocks what was not explicitly allowed. Log sources need a shared clock or the timeline will not line up.",
      "citation": {
        "label": "NIST SP 800-115, Technical Guide to Information Security Testing and Assessment",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-115/final"
      }
    },
    {
      "slug": "risk-math",
      "domainId": "governance",
      "outlineRef": "Domain 5 — risk management",
      "question": "How are SLE and ALE calculated, and what are the four risk responses?",
      "answer": "Single loss expectancy is asset value times exposure factor. Annualized loss expectancy is that single loss times the annualized rate of occurrence. Qualitative analysis uses scales such as high, medium, and low instead of dollars. The four responses are avoid (stop the activity), mitigate (reduce likelihood or impact), transfer (insurance or a contract shifts the financial impact), and accept (live with what remains). A risk register records the risk, the owner, the rating, the treatment, and the status. Risk appetite is how much risk leadership will take on. A business impact analysis identifies critical processes and feeds recovery objectives.",
      "citation": {
        "label": "NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments",
        "url": "https://csrc.nist.gov/publications/detail/sp/800-30/rev-1/final"
      }
    },
    {
      "slug": "compliance-map",
      "domainId": "governance",
      "outlineRef": "Domain 5 — compliance and privacy",
      "question": "Which program covers HIPAA, PCI DSS, GDPR, and SOX?",
      "answer": "HIPAA is U.S. law for protected health information. PCI DSS is the card-brand standard for cardholder data; it is contractual, not a statute. GDPR is the European Union’s personal-data law, including the idea of a controller who decides purposes and a processor who acts for that controller. SOX is U.S. public-company financial reporting, including the IT controls that support those reports. Privacy decides why personal data is collected and how long it is kept. Security provides confidentiality, integrity, and availability. Encryption supports privacy and is not a substitute for a purpose limitation. Field Guide is not a law firm and these notes are study labels, not legal advice.",
      "citation": {
        "label": "HHS, HIPAA for Professionals",
        "url": "https://www.hhs.gov/hipaa/for-professionals/index.html"
      },
      "citations": [
        {
          "label": "PCI Security Standards Council",
          "url": "https://www.pcisecuritystandards.org/"
        }
      ]
    },
    {
      "slug": "policy-and-vendors",
      "domainId": "governance",
      "outlineRef": "Domain 5 — governance and third parties",
      "question": "How do policy, standard, procedure, and guideline differ, and what should a vendor review include?",
      "answer": "A policy is mandatory management intent. A standard is a mandatory specific requirement. A procedure is the step-by-step. A guideline is recommended and not required. An acceptable use policy is what people acknowledge for company systems. A non-disclosure agreement is the confidentiality promise. A service-level agreement sets service targets. Before a SaaS vendor is connected to production identity, review its reports (such as a SOC 2), the contract’s breach notice and right to audit, and whether it supports single sign-on and multifactor authentication. A control exception is written, owned, dated, and paired with a compensating control. The data owner classifies the data. The custodian implements the handling.",
      "citation": {
        "label": "NIST Cybersecurity Framework",
        "url": "https://www.nist.gov/cyberframework"
      }
    }
  ]
}
