CISSP Security Assessment and Testing Practice Question
A company's security team uses a tool that instruments the application at runtime to monitor and block attacks. This is an example of:
⚠ Common exam trap
CISSP often tests the distinction between testing tools (SAST, DAST, IAST) and runtime protection (RASP) — the trap is selecting IAST because it also instruments the application, but IAST is used during testing, not for blocking attacks in production.
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
✓
RASP
RASP (Runtime Application Self-Protection) instruments the application at runtime, embedding security checks inside the application to detect and block attacks in real time. It operates within the application's execution context, allowing it to monitor data flow, method calls, and user input.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
IAST
Why it's wrong here
IAST (Interactive Application Security Testing) instruments the application during dynamic testing to observe its internal behavior, data flow, and execution paths. This hybrid approach combines elements of static and dynamic analysis to identify vulnerabilities with high accuracy. However, IAST's primary function is to find security flaws during development or quality assurance phases, not to provide continuous, real-time protection against active attacks in a production environment.
- ✓
RASP
Why this is correct
RASP (Runtime Application Self-Protection) directly integrates with the application's runtime environment, actively monitoring its execution, data inputs, and outputs in real-time. By instrumenting the application, RASP can detect and immediately block malicious requests or anomalous behavior that indicates an attempted exploit, such as SQL injection or cross-site scripting. Its core purpose is to provide continuous, self-contained protection against attacks in live production systems.
- ✗
SAST
Why it's wrong here
SAST (Static Application Security Testing) analyzes an application's source code, bytecode, or binary code without executing it. This "white-box" testing method identifies potential security vulnerabilities, coding errors, and design flaws early in the software development lifecycle. Since SAST operates exclusively on static code, it cannot provide any form of runtime protection or respond to active threats against a deployed application.
- ✗
DAST
Why it's wrong here
DAST (Dynamic Application Security Testing) operates by executing a running application and simulating external attacks, much like a malicious actor would. It identifies vulnerabilities by observing the application's responses to various inputs and attack vectors from the outside. While DAST tests a live application, its role is strictly for vulnerability discovery during testing phases, not for providing continuous, active protection against ongoing threats in a production environment.
Go deeper
Related to this question
About these practice questions
This CISSP question is part of Courseiva's 816-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 ISC2 exam blueprint
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.