The answer is spidering and fuzzing. Spidering, also known as crawling, systematically maps an application’s structure by following links and discovering hidden endpoints, which is a foundational DAST technique for identifying the attack surface. Fuzzing then tests runtime behavior by injecting malformed or unexpected inputs to trigger unhandled exceptions, crashes, or security vulnerabilities, making it a core dynamic testing method. On the CISSP exam, these two techniques are often paired together because spidering reveals what to test, while fuzzing executes the actual attack simulation. A common trap is confusing fuzzing with static analysis, but remember that DAST always examines the application while it is running. For a memory tip, think of a spider building a web to map the terrain, then a fuzzer shaking the web to see what breaks.
CISSP Security Assessment and Testing Practice Question
This CISSP practice question tests your understanding of security assessment and testing. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO of the following are common techniques used in dynamic application security testing (DAST)?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Fuzzing
Fuzzing is a DAST technique that involves sending malformed or unexpected input to an application to trigger unhandled exceptions, crashes, or security vulnerabilities. It tests the runtime behavior of the application, making it a dynamic testing method.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Fuzzing
Why this is correct
Fuzzing is a dynamic testing technique that inputs malformed data to trigger faults.
Related concept
Read the scenario before looking for a memorised answer.
✗
Static analysis
Why it's wrong here
Static analysis examines source code without execution, not dynamic.
✓
Spidering
Why this is correct
Spidering (crawling) is a dynamic technique to map application pages.
Related concept
Read the scenario before looking for a memorised answer.
✗
String search
Why it's wrong here
String search is typically a manual or static code review technique.
✗
Code review
Why it's wrong here
Code review is a manual static analysis technique, not dynamic.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ISC2 often tests the distinction between static and dynamic testing techniques, and candidates may mistakenly associate code review or string search with dynamic testing because they are security assessment activities, but they are not performed against a running application.
Detailed technical explanation
How to think about this question
DAST tools like OWASP ZAP or Burp Suite use spidering to automatically crawl an application's endpoints and map its attack surface by following links and submitting forms. Fuzzing in DAST often targets input fields with payloads such as SQL injection patterns or cross-site scripting strings, observing the application's response for anomalies or error messages that indicate vulnerabilities.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CISSP question in full detail.
Security Assessment and Testing — This question tests Security Assessment and Testing — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Fuzzing — Fuzzing is a DAST technique that involves sending malformed or unexpected input to an application to trigger unhandled exceptions, crashes, or security vulnerabilities. It tests the runtime behavior of the application, making it a dynamic testing method.
What should I do if I get this CISSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An organization is conducting a security assessment of a new web application. Which testing technique would best identify cross-site scripting (XSS) vulnerabilities?
easy
A.Manual code review
B.Static application security testing (SAST)
C.Interactive application security testing (IAST)
✓ D.Dynamic application security testing (DAST)
Why D: DAST (Dynamic Application Security Testing) tests the running application by simulating external attacks, including injecting malicious scripts into input fields and observing the response. This directly identifies reflected, stored, and DOM-based XSS vulnerabilities because it exercises the application's runtime behavior, where XSS payloads are executed in the browser. Unlike static analysis, DAST does not require source code access and can detect vulnerabilities that only manifest during execution.
Last reviewed: Jun 30, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CISSP practice question is part of Courseiva's free ISC2 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 CISSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.