CompTIA SecurityX guideStudy & preparation
CompTIA SecurityX Threat Modeling: Choose the Right Framework
Short answer
Choose the framework by the output the SecurityX scenario requests: threat categories, common attack patterns, observed adversary behaviors, or intrusion stages. CompTIA's CAS-005 objective 1.4 lists STRIDE, CAPEC, ATT&CK, and the Cyber Kill Chain. Match the requested deliverable to each framework's organizing purpose; do not treat design work or incident analysis as an exclusive territory belonging to only one framework.
What output does the scenario need?
Choose the framework by the requested output: threat categories, common attack patterns, observed adversary behaviors, or intrusion stages. CompTIA's CAS-005 objective 1.4, checked November 11, 2026, names STRIDE, CAPEC, ATT&CK, and the Cyber Kill Chain.
Before comparing those names, finish this sentence: “The team needs a ___ that will help it ___.” A categorized threat list, a pattern-based abuse case, a behavior mapping, and a stage-based intrusion account answer different requests, even when they concern the same service.
“Review the design” alone does not settle the choice. A review might need threat categories, pattern-based abuse cases, or adversary behaviors to examine defensive coverage. Identify the specific deliverable.
Use the SecurityX exam-content guide for the wider objective map; here, write down the required output. For practice across that map, CompTIA SecurityX prep at launch plans 1,600 questions in four domains.
What does each named framework organize?
The distinctions below come from the official framework resources checked November 11, 2026. The sample deliverables are editorial examples of how to use those distinctions.
| Framework | What the official resource organizes | Example deliverable |
|---|---|---|
| STRIDE | Six threat categories: spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege | A categorized list of threats and questions for a system review |
| CAPEC | Common attack patterns describing how weaknesses are exploited, with mitigation guidance | An abuse-case worksheet connecting a relevant pattern to a design assumption and mitigation to evaluate |
| ATT&CK | Adversary tactics and techniques grounded in real-world observations | A mapping between supported observations and adversary behaviors, with evidence gaps identified |
| Cyber Kill Chain | Seven stages of an intrusion | A stage-organized account of an intrusion, showing what is known and where evidence is missing |
Microsoft provides the STRIDE category definitions; MITRE maintains CAPEC and ATT&CK; Lockheed Martin describes the Cyber Kill Chain. These are organizing resources, not interchangeable names for a finished security assessment.
A category is not a complete attack description. An attack pattern does not establish that it occurred. A behavior mapping needs supporting evidence, and a stage model does not prove that you observed every stage. Decide what the requested artifact must contain before filling it in.
How does one service lead to different artifacts?
This is an original preparation exercise, not a recalled or predicted exam item.
Brief: A project portal lets contributors upload revised drawings. Reviewers may read only their assigned projects, and administrators manage accounts. The team wants to review a proposed expansion. A separate exercise report records two fictional observations from the existing portal: an unauthorized drawing change and a download of a project file by an unassigned account. The report does not explain how either account obtained its access.
Keep those facts fixed. Change only the requested deliverable.
Request 1: Categorize threats for the review
Choose STRIDE to organize questions such as these:
| Category | Question for this fictional portal |
|---|---|
| Spoofing | Could someone act using another contributor's identity? |
| Tampering | Could someone alter a drawing without authorization? |
| Repudiation | Could a contributor deny an action that the team needs to attribute? |
| Information disclosure | Could an unassigned reviewer read a project's files? |
| Denial of service | Could a user prevent others from using the upload service? |
| Elevation of privilege | Could a contributor obtain administrator authority? |
These questions are a review checklist, not findings that all six conditions exist. Mark the unauthorized change and unassigned download as observations supplied by the brief; keep the other questions open pending evidence.
Request 2: Develop a pattern-based abuse case
Choose CAPEC when the team asks for common attack patterns, the weaknesses they exploit, and mitigation guidance relevant to the portal.
Start a worksheet with the observed unauthorized change. Record: “Relevant pattern to identify; weakness the pattern requires; evidence that the portal has that weakness; mitigation guidance to evaluate.” The missing access explanation is a gap to investigate, not permission to invent a cause.
The useful deliverable is a justified connection between a cataloged pattern and this design. Merely writing “tampering” supplies a threat category but leaves the requested pattern, weakness, and mitigation work unfinished.
Request 3: Map observed adversary behavior
Choose ATT&CK when the requested artifact maps supported observations to adversary tactics and techniques.
For the fictional download, record the account, file, authorization mismatch, and evidence supplied by the report. Keep “how the account obtained access” in an unknowns field. Consult ATT&CK for a supported mapping; do not invent a technique identifier from the word “download” alone.
This output organizes behavior and its evidence. The same resource may also inform a design discussion, so “the service is being designed” does not automatically eliminate ATT&CK. The decisive point here is the requested behavior mapping.
Request 4: Organize the intrusion by stage
Choose the Cyber Kill Chain when the team asks for an account organized around intrusion stages.
The two observations are insufficient to establish a complete sequence: the brief supplies neither their order nor how access began. Start the artifact with those known actions, request timing and access evidence, and identify which stage assignments still need support. Do not insert a story about earlier activity merely to fill every stage.
A useful stage-based account can expose gaps. A confidently completed sequence built from missing facts would misrepresent this brief.
Which plausible framework fails the requested task?
Test an alternative by describing the artifact it would produce:
- If the request is for common attack patterns and mitigation guidance, a STRIDE category list leaves the pattern analysis incomplete.
- If the request is to categorize threats, a chronological account does not supply the six-category review structure.
- If the request is to map observed tactics and techniques, a list of hypothetical abuse cases does not establish what the observations support.
- If the request is for intrusion stages, an unordered list of techniques leaves the stage-oriented account unfinished.
These are mismatches to the stated deliverable, not universal restrictions on framework use. In the same project, several outputs may be useful. For a selection exercise, justify the framework that directly answers the current request. At launch, the rationale planned for each CompTIA SecurityX practice answer lets you check that justification.
If you keep choosing by a familiar keyword, use the SecurityX scenario-reading method to separate the requested action, evidence, and constraints.
How can you practice without memorizing labels?
Cover the framework column and write a four-line response for each request:
- Name the required deliverable.
- Choose the framework and explain its organizing purpose.
- List the facts available and the important unknowns.
- Explain what the closest alternative would leave unfinished.
Then change the request while preserving the portal facts. If your answer stays the same, check whether you are responding to the service's name instead of the output. At launch, missed CompTIA SecurityX questions are planned to come back in Fix It for this kind of retry. Next, try a different system, such as the deployment review in the SecurityX AI-controls guide.
Apply this explanation method to the 20 free SecurityX practice questions, then add the distinction you could not explain to your free SecurityX study plan. Your next study task should name the missing skill: categorizing a threat, justifying a pattern, supporting a behavior mapping, or identifying gaps in a stage-based account.
Trust the source
Official sources
Exam policies can change. Use these primary sources for the most current details.