Quick Answer
The answer is Data Execution Prevention (DEP). DEP is the correct choice because it is a hardware and software security feature that marks memory pages as non-executable unless they explicitly contain executable code, directly stopping code injection attacks that attempt to run shellcode from data regions like the heap or stack. On the Systems Security Certified Practitioner SSCP exam, this concept tests your understanding of memory protection mechanisms and how they prevent malware from hijacking legitimate processes, often appearing in questions about buffer overflows or privilege escalation. A common trap is confusing DEP with Address Space Layout Randomization (ASLR); remember that DEP blocks execution, while ASLR randomizes memory addresses. Memory tip: DEP stands for “Don’t Execute Pages”—if the page isn’t marked for code, it won’t run.
This SSCP practice question tests your understanding of systems and application security. 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.
An organization experiences malware that injects code into legitimate processes. Which security feature should be enabled to prevent code execution in memory pages?
Encrypted File System (EFS)
Why wrong: EFS encrypts files, not memory.
Address Space Layout Randomization (ASLR)
Why wrong: ASLR makes exploitation harder but does not prevent code execution.
Mandatory Access Control (MAC)
Why wrong: MAC restricts access but not memory execution.
Data Execution Prevention (DEP)
DEP prevents execution from non-executable memory regions.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Data Execution Prevention (DEP)
Data Execution Prevention (DEP) is a hardware and software security feature that marks memory pages as non-executable unless they explicitly contain executable code. By preventing code execution in data-only memory regions (such as the heap and stack), DEP stops malware that attempts to inject and run shellcode within legitimate processes, even if the process is compromised.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Encrypted File System (EFS)
Why it's wrong here
EFS encrypts files, not memory.
Address Space Layout Randomization (ASLR)
Why it's wrong here
ASLR makes exploitation harder but does not prevent code execution.
Mandatory Access Control (MAC)
Why it's wrong here
MAC restricts access but not memory execution.
Data Execution Prevention (DEP)
Why this is correct
DEP prevents execution from non-executable memory regions.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse ASLR with DEP, thinking randomization alone prevents code execution, but ASLR only makes addresses unpredictable while DEP actively blocks execution from non-executable pages.
Detailed technical explanation
DEP leverages the NX (No-Execute) bit on modern CPUs, which allows the operating system to mark memory pages with a flag that the processor checks before executing any instruction. When a process attempts to execute code from a page marked as non-executable (e.g., the stack or heap), the CPU raises an access violation exception, and the OS terminates the offending process. In real-world scenarios, DEP is critical against buffer overflow attacks that inject shellcode into writable memory regions, as even if the attacker overwrites a return address, the injected code cannot run.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A SOC analyst notices unusual lateral movement in the network at 2 AM. The IR playbook dictates: identify and contain (isolate the affected machine), then eradicate (remove the malware), then recover (restore from backup), then document. Skipping containment before eradication risks the attacker regaining access. Questions like this test the sequence and rationale of incident response phases.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Systems and Application Security — study guide chapter
Learn the concepts, then practise the questions
Systems and Application Security practice questions
Targeted practice on this topic area only
All SSCP questions
504 questions across all exam domains
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Practise SSCP questions linked to Network and Communications Security.
Practise SSCP questions linked to Systems and Application Security.
Practise SSCP questions linked to Security Operations and Administration.
Practise SSCP questions linked to Incident Response and Recovery.
Practise SSCP questions linked to Access Controls.
Practise SSCP questions linked to Cryptography.
Practise SSCP questions linked to SSCP fundamentals.
Practise SSCP questions linked to SSCP scenario.
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Systems and Application Security — This question tests Systems and Application Security — Read the scenario before looking for a memorised answer..
The correct answer is: Data Execution Prevention (DEP) — Data Execution Prevention (DEP) is a hardware and software security feature that marks memory pages as non-executable unless they explicitly contain executable code. By preventing code execution in data-only memory regions (such as the heap and stack), DEP stops malware that attempts to inject and run shellcode within legitimate processes, even if the process is compromised.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
This SSCP 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 SSCP 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.