CompTIA launched Security+ V8, exam code SY0-801, on November 17, 2026. The exam objectives are CompTIA's official list of what the exam can test: 27 objectives in five domains. This page gives every objective number and title, explains each one in plain English, and shows what changed from SY0-701.
SY0-801 at a glance
| SY0-801 | |
|---|---|
| Exam name | CompTIA Security+ V8 |
| Launch date | November 17, 2026 |
| Retirement | Estimated about three years after launch |
| Questions | Up to 90, multiple choice and performance-based |
| Time | 90 minutes |
| Passing score | 750 on a scale of 100–900 |
| Languages | English at launch |
| Recommended experience | Security administrator with two years of hands-on experience |
| Objectives | 27 across five domains |
Sources: the CompTIA Security+ V8 page and the official SY0-801 exam objectives (PDF). The PDF also includes CompTIA's acronym list and a sample list of hardware and software for building a practice lab. CompTIA notes that the examples under each objective are not a complete list, so treat them as a guide to scope rather than a checklist.
The five domains and their weights
The weight is the share of the exam each domain makes up. It is the single most useful number for planning study time: Security Operations alone is more than a quarter of the exam.
| Domain | Share of the exam | Objectives |
|---|---|---|
| 1.0 General Security Concepts | 16% | 3 |
| 2.0 Threats, Vulnerabilities, and Attacks | 24% | 6 |
| 3.0 Security Architecture | 19% | 4 |
| 4.0 Security Operations | 27% | 8 |
| 5.0 Security Program Management and Oversight | 14% | 6 |
All 27 objectives explained
Each table lists CompTIA's objective number and title, then what the objective covers in plain words. Objectives that start "Given a scenario" are tested with realistic situations: you apply the idea rather than just define it. 9 of the 27 objectives are worded that way. For the full list of examples under each one, see the objectives PDF.
1.0 General Security Concepts (16%)
| Objective | CompTIA title | What it means |
|---|---|---|
| 1.1 | Explain security concepts and controls | The vocabulary the rest of the exam builds on: the CIA triad, AAA, non-repudiation, zero trust, least privilege and defense in depth. It also covers how to label a control by category (technical, managerial, operational, physical) and by type (preventive, detective, corrective and the rest). |
| 1.2 | Given a scenario, demonstrate the impact of change management processes on security | How approvals, impact analysis, testing, backout plans and maintenance windows stop a change from causing an outage or a security gap, and what has to be updated afterward, such as diagrams, procedures and version history. |
| 1.3 | Explain the importance of using appropriate cryptographic solutions | PKI and certificates (authorities, revocation checks, signing requests, wildcards), symmetric and asymmetric encryption at every level from a whole disk down to a single record, and the related tools: hashing, salting, digital signatures and obfuscation. |
2.0 Threats, Vulnerabilities, and Attacks (24%)
| Objective | CompTIA title | What it means |
|---|---|---|
| 2.1 | Explain characteristics of threats and vulnerabilities | How a threat is judged (threat feeds, intelligence sources, likelihood and impact) and how a vulnerability is scored and ranked, using CVE identifiers and CVSS scores to decide what to fix first. |
| 2.2 | Describe common threat actors and motivations | Who attacks and why, from unskilled attackers and hacktivists to organized crime, insiders, competitors and state-sponsored groups, compared by funding, skill and whether they sit inside or outside the organization. |
| 2.3 | Describe threat vectors and sources | The routes an attack can take: messages, images and QR codes, attachments, the browser, the network, remote access, endpoints, the supply chain, USB media, people, IoT and OT devices, physical entry and wireless signals. |
| 2.4 | Explain types of vulnerabilities and attack surfaces | Where weaknesses come from: unsupported or unpatched systems, open ports, application and code flaws such as race conditions and hardcoded secrets, misconfiguration, stale credentials, shadow IT, public repositories and storage buckets, and large language models. |
| 2.5 | Given a scenario, analyze indicators of malicious activity | Spot the signs of malware, physical, network, social engineering, application and credential attacks in a scenario, and read indicators of compromise such as impossible travel, unexpected lockouts or tampered logs. |
| 2.6 | Summarize threats and vulnerabilities associated with artificial intelligence (AI) usage | The ways AI systems can be attacked or go wrong: prompt injection, jailbreaking, poisoning and model manipulation, hallucinations, bias and explainability, data loss and privacy, and the ethical questions around them. |
3.0 Security Architecture (19%)
| Objective | CompTIA title | What it means |
|---|---|---|
| 3.1 | Compare and contrast security implications of different architecture models | The security trade-offs of cloud (including serverless and multicloud), on-premises, hybrid, infrastructure as code, microservices, OT and air-gapped designs, weighed against cost, ease of recovery, data sovereignty and who is responsible for what. |
| 3.2 | Given a scenario, manage the security architecture to best protect the infrastructure | Place devices and security zones sensibly, apply zero trust architecture, secure remote access and communication (VPNs, tunnelling, security service edge), manage service and privileged accounts, and decide how systems should behave when they fail. |
| 3.3 | Summarize concepts and strategies used to protect data | Data types, states (at rest, in transit, in use) and classification levels; the methods that protect data, such as encryption, masking and tokenization; the roles from data owner to subprocessor; and handling data through its life cycle and under compliance rules. |
| 3.4 | Explain the importance of resilience and recovery in security architecture | Keeping services running and getting them back: hot, warm and cold sites, redundancy and power, backups (including immutable ones and restore tests), failover testing, capacity planning, and recovery metrics such as RTO, RPO, MTTR and MTBF. |
4.0 Security Operations (27%)
| Objective | CompTIA title | What it means |
|---|---|---|
| 4.1 | Given a scenario, apply mitigating controls, techniques, and solutions to secure the environment | The broadest objective on the exam. Choose and apply defences: segmentation, hardening, sandboxing, deception (honeypots, honeytokens), firewalls and IDS/IPS, DLP and content filtering, EDR/XDR, network access control, secrets scanning, application security and email authentication (SPF, DKIM, DMARC). |
| 4.2 | Explain the security implications of proper hardware, software, and data asset management | Track hardware, software and data from planning and purchase, through assignment and monitoring, to secure disposal. |
| 4.3 | Given a scenario, perform tasks associated with vulnerability management | Find vulnerabilities (scanning, cloud security posture management, code review), prioritize them, fix them, confirm the fix worked, and report them internally or through bug bounty and disclosure programs. |
| 4.4 | Explain security alerting and monitoring concepts and tools | Watch systems, applications and infrastructure: gather and tune logs and alerts in a SIEM, use agents, benchmarks and scanners, and know the monitoring protocols, such as NetFlow, SNMP, syslog and SCAP. |
| 4.5 | Given a scenario, apply concepts related to identity and access management | Create and remove accounts, assign permissions, use federation and single sign-on (SAML, OAuth, LDAP), choose MFA methods and access control models, including just-in-time access, and apply current password practice such as passkeys and passwordless sign-in. |
| 4.6 | Given a scenario, apply automation and orchestration solutions to secure operations | Use automation and scripting for provisioning, baselines, anomaly detection and tickets; weigh the guardrails and risks; and know where AI (agentic tools, chatbots, predictive analysis) and CI/CD pipelines fit into security operations. |
| 4.7 | Summarize concepts associated with incident response activities | The incident response cycle, from preparation and tabletop exercises through detection, investigation and forensics, containment, eradication and recovery, to notification and lessons learned. Negotiation is listed as a topic of its own. |
| 4.8 | Given a scenario, use data, artifacts and sources to support a security investigation | Pick the log, data source or artifact that answers an investigation question, preserve evidence such as memory dumps and disk images, protect log integrity, and know who to bring in, from HR to legal. |
5.0 Security Program Management and Oversight (14%)
| Objective | CompTIA title | What it means |
|---|---|---|
| 5.1 | Explain the importance of governance, risk, and compliance artifacts | The documents that run a security program: guidelines, standards and baselines, procedures and runbooks, continuity and recovery plans, and policies such as acceptable use, BYOD and incident response. |
| 5.2 | Explain the impact of risk management processes on the security of the organization | Identify, assess and analyze risks, record them in a register, choose a treatment (transfer, accept, avoid or mitigate), and use business impact analysis, risk appetite and loss figures (SLE, ALE, ARO). |
| 5.3 | Explain the assessment and management processes associated with third-party risk | Choosing vendors (RFPs, due diligence), the agreements that bind them (SLA, MOU, MSA, SOW and others), monitoring them with audits and assessments, and the limits you work within, such as lock-in or jurisdiction. |
| 5.4 | Summarize elements of effective security compliance | Compliance training and monitoring, what non-compliance costs, privacy rights such as the right to be forgotten, and legal duties like legal holds and data retention. |
| 5.5 | Explain concepts associated with audit and assessment activities | How audits and assessments are scoped and run, internal and external engagement types, penetration testing approaches, and reference models such as MITRE ATT&CK, the Cyber Kill Chain and the Diamond Model. |
| 5.6 | Given a scenario, apply security awareness concepts to improve organizational security | Plan and deliver security awareness training, measure whether it works, and cover topics such as social engineering, business email compromise, remote work and removable media. |
What changed from SY0-701
These differences come from comparing the official SY0-801 objectives with the SY0-701 objectives. The format, time limit and passing score are the same on both.
| Domain | SY0-701 weight | SY0-801 weight | Change | Objectives (SY0-701 → SY0-801) |
|---|---|---|---|---|
| General Security Concepts | 12% | 16% | +4 pts | 4 → 3 |
| Threats, Vulnerabilities, and Mitigations → Threats, Vulnerabilities, and Attacks | 22% | 24% | +2 pts | 5 → 6 |
| Security Architecture | 18% | 19% | +1 pts | 4 → 4 |
| Security Operations | 28% | 27% | -1 pts | 9 → 8 |
| Security Program Management and Oversight | 20% | 14% | -6 pts | 6 → 6 |
- AI gets its own objective. Objective 2.6 covers threats and vulnerabilities from AI use, such as prompt injection, jailbreaking, poisoning and hallucinations. AI also shows up in 2.4 (large language models as an attack surface) and 4.6 (AI in automation). SY0-701 had no AI objective.
- Domain 2 is renamed and restructured. "Threats, Vulnerabilities, and Mitigations" becomes "Threats, Vulnerabilities, and Attacks". It gains a new opening objective (2.1) on judging threats and scoring vulnerabilities, and the SY0-701 objective on mitigation techniques (2.5) is gone from this domain. Defensive controls now sit in Security Operations.
- Domain 1 drops from four objectives to three. The core ideas from SY0-701 1.2 (the CIA triad, AAA, zero trust) now share objective 1.1 with control types. Deception technology such as honeypots now appears in 4.1, and gap analysis in 5.5.
- Security Operations goes from nine objectives to eight. The new 4.1 is a single, broad scenario objective on mitigating controls. It covers ground that SY0-701 split across hardening computing resources (4.1), modifying enterprise capabilities (4.5) and mitigation techniques (2.5).
- More objectives are scenario-based. 9 objectives start "Given a scenario", up from 7. Change management (1.2), vulnerability management (4.3) and automation (4.6) are the new ones, so expect to apply them rather than just define them.
- Governance carries less weight. Security Program Management and Oversight falls from 20% to 14%, while General Security Concepts rises from 12% to 16%. Domain 5 keeps six objectives, with reworded titles such as governance, risk, and compliance artifacts (5.1).
For dates, a version picker and advice on which exam to book, see SY0-701 or SY0-801.
How to study from the objectives
The objectives are the best checklist you have, because CompTIA builds the exam from them. A simple way to use them:
- Turn them into a tracker. List the 27 objectives, and mark each one as not started, shaky or solid. Review the shaky ones every week.
- Spend time by weight. Security Operations at 27% and Threats, Vulnerabilities, and Attacks at 24% are over half the exam between them. Give them the most hours.
- Practise the scenario objectives. For the 9 "Given a scenario" objectives, knowing the definitions is not enough. Work through examples where you choose a control, read a log or pick the right access model.
- Learn the acronym list. It is at the back of the objectives PDF, and questions use those abbreviations without spelling them out.
If you are sitting SY0-701 before it retires, our SY0-701 objectives guide explains all 28 objectives with the concepts to know and the common traps. The study plan generator builds a week-by-week schedule weighted by domain, and you can check where you stand with the free SY0-701 practice test, no account needed.