hardMultiple ChoiceObjective-mapped
SSCP Practice Question: A medium-sized financial services company has…
A medium-sized financial services company has recently deployed a new web application that processes sensitive customer data, including Social Security numbers and account balances. The security team implemented network segmentation, a web application firewall (WAF) from a reputable vendor, and quarterly vulnerability scans. The developers assert that they use parameterized queries for all database calls in the main application code. During a recent penetration test, testers successfully exploited a SQL injection vulnerability, extracting the entire customer database. Further investigation reveals that the main application indeed uses parameterized queries, but a third-party reporting module, integrated to generate compliance reports, constructs SQL queries by concatenating user-supplied date range inputs directly into SQL strings. The WAF is configured with a generic rule set and has not been tuned to the application's specific traffic patterns. What is the most effective course of action to remediate this vulnerability and prevent future occurrences?
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
✓
Replace the third-party reporting module with an alternative that uses parameterized queries.
The root cause is the third-party module's insecure query construction. Replacing it with a module that uses parameterized queries directly eliminates the vulnerability at its source. Input validation (A) is a defense-in-depth measure but not sufficient if concatenation is still used. Increasing scan frequency (C) does not fix the underlying issue. Configuring the WAF (D) provides a layer of defense but can be bypassed and is not as reliable as eliminating the vulnerable code.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Replace the third-party reporting module with an alternative that uses parameterized queries.
Why this is correct
This directly removes the vulnerable coding practice (concatenation) and replaces it with a secure method, permanently fixing the SQL injection flaw.
- ✗
Implement strict input validation to sanitize user-supplied date inputs.
Why it's wrong here
Input validation reduces risk but cannot fully prevent SQL injection if concatenation is still used; blacklist-based validation can be bypassed.
- ✗
Increase the frequency of vulnerability scans from quarterly to monthly.
Why it's wrong here
More frequent scans detect vulnerabilities sooner but do not remediate the existing issue; the vulnerability remains exploitable until fixed.
- ✗
Configure the WAF to block SQL injection patterns with custom rules.
Why it's wrong here
WAF rules provide a reactive defense and can be bypassed by sophisticated attacks; the most effective approach is to eliminate the vulnerability in the code.
Go deeper
Related to this question
About these practice questions
This SSCP question is part of Courseiva's 920-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 →
Same concept, more angles
2 more ways this is tested on SSCP
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. A company deploys a web application that processes credit card payments. The development team uses parameterized queries for all database interactions. However, during a penetration test, the tester successfully injects malicious code into a search field and retrieves sensitive customer data. Which of the following is the most likely cause?
medium- ✓ A.The application uses dynamic SQL despite parameterized queries for some fields.
- B.The web server is misconfigured to allow directory traversal.
- C.The database server has weak permissions allowing direct query execution.
- D.The search field output is not sanitized, allowing stored XSS.
Why A: The use of parameterized queries prevents SQL injection, but if dynamic SQL is constructed elsewhere in the application (e.g., for the search field), it can still be vulnerable. Option B is incorrect because directory traversal exploits file system access, not database query injection. Option C is incorrect because direct query execution would require explicit permissions beyond the application's context. Option D is incorrect because XSS affects client-side execution, not direct data retrieval from the database.
Variation 2. A web application processes user-supplied data in SQL queries. Which practice best prevents SQL injection?
medium- ✓ A.Parameterized queries
- B.Escaping all user input
- C.Using stored procedures exclusively
- D.Input length validation
Why A: Parameterized queries (also known as prepared statements) separate SQL logic from user data by using placeholders (e.g., `?` in MySQLi or `:name` in PDO). The database engine treats the user input strictly as data, never as executable SQL code, which inherently prevents SQL injection regardless of the input content.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.