
CompTIA SecurityX (CAS-005) is CompTIA's expert-level security certification, the new name for CASP+. It is meant for security architects and senior security engineers who design and run security for a whole organisation: governance and risk, security architecture for cloud and zero trust, security engineering with automation and advanced cryptography, and security operations from threat hunting to incident response. The current version launched on 17 December 2024.
This guide follows CompTIA's official SecurityX page: the four domains with weights, what each one expects at architect level, how it differs from Security+ and CySA+, a 10-week plan and 15 original scenario questions.
Quick facts (CompTIA, November 2026)
| Item | Detail |
|---|---|
| Exam code | CAS-005 (V5), launched 17 December 2024 |
| Retirement | Usually about three years after launch; estimated 2027 |
| Questions | Maximum 90, multiple choice and performance-based |
| Duration | Maximum 165 minutes |
| Scoring | Pass/fail only; there is no scaled score |
| Recommended experience | At least 10 years of hands-on IT experience, including 5 years of hands-on security, plus Network+, Security+, CySA+, Cloud+ and PenTest+ or equivalent knowledge |
Read the official CompTIA SecurityX page and download the exam objectives before you book.
Domains and weights
| Domain | Weight | Key topics (from CompTIA) |
|---|---|---|
| Security Engineering | 31% | Automation (scripting, IaC, SOAR, generative AI); vulnerability management (scanning, SCAP); advanced cryptography (post-quantum, homomorphic encryption, forward secrecy); tokenisation, code signing, digital signatures |
| Security Architecture | 27% | Cloud capabilities and cloud data security; cloud control strategies; network architecture and security boundaries; deperimeterisation (SASE, SD-WAN, software-defined networking); zero trust |
| Security Operations | 22% | Monitoring and data analysis (SIEM, behaviour baselines); vulnerabilities and attack surface; threat hunting (threat intelligence, IoC sharing, detection rule languages); incident response (malware analysis, reverse engineering, root cause analysis) |
| Governance, Risk and Compliance | 20% | Security programme documentation and management; frameworks (COBIT, ITIL, NIST CSF, CSA); GRC tools; data governance; risk management and threat modelling; attack surface analysis; compliance (PCI DSS, ISO/IEC 27000) |
How SecurityX differs from Security+ and CySA+
| Certification | Level | The question it asks |
|---|---|---|
| Security+ | Core | What is this control and when do you use it? |
| CySA+ | Analyst | What is happening in these logs, and how do you respond? |
| PenTest+ | Offensive | How would an authorised tester find and prove this weakness? |
| SecurityX | Expert / architect | Given the business, its risks and its rules, what is the best design, and what trade-off are you accepting? |
SecurityX questions usually have several technically correct answers. The best answer is the one that fits the stated constraint: cost, regulation, latency, legacy systems or the organisation's risk appetite. Read the last sentence of each question first.
What each domain expects
- Security engineering (31%): automate security with scripts, infrastructure as code and SOAR playbooks; know where generative AI helps and where it adds risk; run a vulnerability programme with SCAP content; choose cryptography for the use case, including post-quantum algorithms, forward secrecy, tokenisation and code signing.
- Security architecture (27%): design cloud controls (CASB, key management, data protection), segment networks, and move from a perimeter model to SASE and zero trust, where every request is verified by identity, device posture and context.
- Security operations (22%): build SIEM detections from behaviour baselines, hunt threats with intelligence and IoCs, write detection rules, and lead incident response through to root cause.
- Governance, risk and compliance (20%): write and run the security programme, pick frameworks, quantify and treat risk, threat-model new systems, and map controls to PCI DSS, ISO/IEC 27001 and local law such as India's DPDP Act, 2023.
Cryptography choices to know
| Need | Typical choice |
|---|---|
| Recorded traffic must stay secret even if the server key leaks later | Forward secrecy (ephemeral Diffie-Hellman key exchange) |
| Protect long-lived data against future quantum attacks | Post-quantum algorithms (NIST's ML-KEM for key exchange, ML-DSA for signatures), often in hybrid mode |
| Analytics on data without decrypting it | Homomorphic encryption (accepting a large performance cost) |
| Keep card numbers out of most systems | Tokenisation, with the vault in a tightly controlled zone |
| Prove software came from you and wasn't changed | Code signing with keys held in an HSM |
10-week study plan
| Week | Focus | Practice |
|---|---|---|
| 1–2 | GRC: programme documents, frameworks, risk analysis, threat modelling (STRIDE), compliance mapping | Write a one-page risk register and a threat model for a web app |
| 3–4 | Architecture: cloud security controls, segmentation, SASE, SD-WAN, zero trust | Draw a zero trust design for a hybrid company and justify each control |
| 5–7 | Engineering: IaC and SOAR automation, vulnerability management, PKI and advanced cryptography | Scan your IaC with a policy tool; automate one alert-to-ticket playbook |
| 8–9 | Operations: SIEM baselines, detection rules, threat hunting, incident response, malware analysis basics | Write three detection rules in your lab SIEM; run a tabletop exercise |
| 10 | Performance-based question practice and full mocks | Two timed mocks; book the exam |
15 scenario questions with answers
These are original scenarios written for this guide, not exam questions.
1. A bank must keep customer records confidential for 20 years. Attackers may be collecting encrypted data now to decrypt later. What do you plan?
A migration to post-quantum (or hybrid) key exchange and signatures for long-lived data, starting with a cryptographic inventory.
2. Remote staff use SaaS directly from home, and traffic currently hairpins through the head-office VPN. Which architecture fits?
SASE: cloud-delivered secure web gateway, CASB and zero trust network access close to the user.
3. The board asks which risks to fund first. What do you present?
A risk register ranked by likelihood and impact, with treatment options (mitigate, transfer, accept, avoid) and cost.
4. A new payments service will store card numbers. How do you shrink PCI DSS scope?
Tokenise card numbers so only the tokenisation vault holds real data.
5. Developers keep deploying storage buckets without encryption. What stops it before deployment?
Policy-as-code checks on the infrastructure-as-code templates in the CI pipeline.
6. The SOC drowns in repetitive phishing alerts. What helps most?
A SOAR playbook that enriches, scores and auto-closes or escalates them.
7. A user logs in from Hyderabad and, ten minutes later, from another continent. Which detection approach flags it?
Behaviour baselining (impossible travel) in the SIEM or UEBA.
8. A threat intel report lists hashes and domains from a campaign against your sector. What do you do?
Hunt for those IoCs in your logs and endpoints, then turn them into detection rules and share findings through your sharing community.
9. You need to prove a firmware update is genuine and unaltered. What control?
Code signing, with signature verification before install.
10. A legacy app can't support MFA or modern authentication. What is the best compensating design?
Put it behind an identity-aware proxy or ZTNA gateway that enforces MFA and device checks, and segment it.
11. Which framework would you use to describe IT service management processes alongside security?
ITIL (with COBIT for governance of enterprise IT).
12. After an incident, the same malware returns a week later. What was probably skipped?
Root cause analysis and full eradication (for example, a persistence mechanism or the initial access path was not closed).
13. The data team wants to analyse encrypted health data without seeing it. Which technique, and what is the trade-off?
Homomorphic encryption; the trade-off is heavy compute cost and limited operations.
14. Scan reports differ between tools and can't be compared. What standard helps?
SCAP (with CVE, CVSS and CPE identifiers) for consistent, machine-readable results.
15. A team wants to use a public generative AI tool on internal code. What controls do you set?
An acceptable-use policy, an approved enterprise tool with data-retention controls, DLP on prompts, and review of generated code before merge.
After SecurityX
- Go deeper in cloud with AWS Security Specialty, SC-500 or Google Cloud Security Engineer.
- Read the cyber security career roadmap.
- See live security jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches cyber security, cloud security and AI security with hands-on labs. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is CompTIA SecurityX?
CompTIA's expert-level security certification for security architects and senior engineers. It replaced the CASP+ name; the current exam is CAS-005.
When did CAS-005 launch?
17 December 2024. CompTIA estimates retirement in 2027.
How is SecurityX scored?
Pass/fail only; there is no scaled score.
How long is the SecurityX exam?
Up to 165 minutes, with a maximum of 90 multiple-choice and performance-based questions.
Which SecurityX domain has the most weight?
Security Engineering at 31%, followed by Security Architecture at 27%.
What experience does CompTIA recommend for SecurityX?
At least 10 years of hands-on IT experience, including 5 years of hands-on security.



