CRISC IT Risk Identification Practice Question
A company is adopting a DevSecOps approach and wants to conduct threat modeling early in the development lifecycle. Which threat modeling methodology is BEST suited for this environment due to its focus on agile and continuous integration?
⚠ Common exam trap
CRISC often tests the distinction between threat modeling methodologies by pairing an agile/DevSecOps keyword with the methodology that was purpose-built for that context — candidates who default to the more famous STRIDE or PASTA miss that VAST is the agile-native answer.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
VAST
VAST (Visual, Agile, and Simple Threat modeling) is the only methodology explicitly designed for agile and DevSecOps environments, integrating threat modeling into CI/CD pipelines and scaling across large development teams. It uses two model types — application threat models for developers and operational threat models for infrastructure — making it suitable for continuous delivery. This agile-native design is why VAST is the best fit when threat modeling must occur early and iteratively in the SDLC.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
TRIKE
Why it's wrong here
TRIKE centres on satisfying acceptable risk levels from each stakeholder's perspective, producing a requirements-driven model rather than per-sprint threat output. It is tempting because TRIKE's stakeholder risk framing suits compliance-heavy projects, and it would be correct where defensible risk acceptance documentation, not rapid iteration, is the priority.
- ✓
VAST
Why this is correct
VAST's Visual, Agile and Simple Threat modelling integrates into agile workflows and CI pipelines, producing scalable, automation-friendly outputs. This suits DevSecOps, where threat modelling must recur each sprint rather than as a one-off design-phase exercise.
- ✗
STRIDE
Why it's wrong here
STRIDE classifies threats into six categories but prescribes no integration with backlog items, sprint cadence or CI pipelines, so it does not deliver the continuous, per-story threat identification DevSecOps requires. It is tempting because STRIDE is lightweight and widely taught, and it would be correct for a one-off architectural review of a completed design.
- ✗
PASTA
Why it's wrong here
PASTA is a seven-stage, risk-centric methodology built around business impact analysis, which is too heavyweight to embed in short iterative sprints. It is tempting because PASTA's attacker-centric depth suits complex, high-assurance systems, and it would be correct where regulatory risk quantification across a long release cycle matters more than rapid iteration.
Go deeper
Related to this question
About these practice questions
This CRISC question is part of Courseiva's 1,062-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISACA exam blueprint
This CRISC practice question is part of Courseiva's free ISACA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CRISC exam.