ISC · Security and Confidentiality and Privacy · 9 practice questions
Vulnerability Scan vs. Penetration Test: Which to Use?
Vulnerability scans identify possible weaknesses; authorized penetration tests attempt exploitation to show whether sensitive data can be reached. Below, sort customer portal testing activities by what testers actually attempt.
Try one first
Hint
Focus on the difference between a test that identifies possible weaknesses and one that shows whether those weaknesses can actually be exploited.
Answer C. A penetration test attempts controlled exploitation of identified weaknesses to determine whether they are actually exploitable and could lead to unauthorized access. The stem explicitly says testing is authorized and controlled, which is the appropriate context for a penetration test. A vulnerability scan alone only identifies potential issues and does not prove exploitability.
Why not A: Policy and access reviews are important for governance and may identify control gaps, but they are not technical tests that show whether vulnerabilities can be exploited to gain unauthorized access to the portal.
Why not B: Repeating the scan may help verify or reduce false positives, but scans only identify potential weaknesses and do not demonstrate that an attacker can exploit them to access data. Management specifically asked whether the weaknesses can be used to gain unauthorized access, which requires exploitation testing.
Why not D: Backup restoration testing validates recoverability and availability, not whether the portal's technical weaknesses permit unauthorized access or data exfiltration. It does not answer management's question about exploitability.
Sort it
The activity identifies or reports potential weaknesses without attempting exploitation.
Within approved boundaries, testers attempt controlled exploitation to determine whether unauthorized access is achievable.
| Item | Goes to |
|---|---|
| An automated tool reports outdated software and exposed services on Ridge Co.'s customer document portal without attempting exploitation. | Vulnerability scanningThe tool identifies potential weaknesses but does not try to use them to access customer documents. |
| Under written authorization, defined scope, and approved rules of engagement with stop conditions, testers try to combine predictable document IDs and broad file permissions to retrieve another customer's document. | Penetration testingThe testers attempt a controlled attack path to determine whether unauthorized document access is possible. |
| Using an ordinary portal account, a scanner flags potentially excessive permissions but makes no attempt to retrieve restricted documents. | Vulnerability scanningCredentials improve visibility, but they do not turn weakness identification into exploitation testing. |
| Within the approved scope, testers change a document ID while signed in as an ordinary customer to attempt access to another customer's document. | Penetration testingThe testers actively challenge the portal's authorization logic rather than merely flagging a possible weakness. |
| A report titled 'Portal Penetration Test' lists scanner findings, but the engagement prohibited all exploitation attempts. | Vulnerability scanningThe label does not control classification. The actual work only identified potential weaknesses. |
| Authorized testers use automated tools to attempt selected portal exploits that could expose customer documents. | Penetration testingAutomation does not make the work scanning. Controlled exploitation is the deciding fact. |
| Weekly portal scans report no critical findings. The team performs no exploitation attempts. | Vulnerability scanningFrequent, clean scans remain scans. They do not demonstrate whether document-access weaknesses can be exploited or chained. |
| Testers receive a portal diagram and an ordinary account, then attempt approved exploits against document-access controls. | Penetration testingPartial internal information supports the work, but attempted exploitation is what distinguishes it from scanning. |
| A second scanning tool reports the same suspected document-access weakness, without trying to retrieve a restricted document. | Vulnerability scanningRepeated findings can support identification of a potential issue, but repetition does not prove exploitability. |
| Under the approved rules, testers attempt the document-access exploit in a test environment that mirrors the production portal. | Penetration testingControlled exploitation can occur in a production-like environment. Testing live production is not what defines a penetration test. |
Key points
- Remember: Finding a weakness is not the same as trying to use it to reach customer data.
- Classify the work by what testers attempt, not the engagement label or whether they use automated tools.
- Before exploitation, establish written authorization, defined scope, rules of engagement, and stop conditions.
How the exam traps you
- Treating frequent or clean scans as proof that customer data cannot be reached. Scan frequency and results do not replace controlled attempts to exploit attack paths.
- Calling an engagement a penetration test even though testers only list weaknesses. Look for attempted exploitation, not the report's title.
Question 2
Hint
Think about the difference between identifying possible weaknesses and proving how an attacker could actually use them.
Answer D. Vulnerability scans are useful for finding known technical weaknesses such as missing patches, open services, and common misconfigurations, but they do not attempt to exploit those findings or demonstrate whether vulnerabilities can be chained into a real attack. Penetration testing (or red-team exercises) performs exploit attempts and attack-path validation, providing evidence about real-world exploitability and control effectiveness that scans alone do not provide.
Why not A: Although both are types of security assessment, they serve different purposes: scans identify potential vulnerabilities, while penetration testing attempts to exploit them to show whether they can be used in realistic attack paths. They are not equivalent.
Why not B: This is tempting because a clean scan report can create a false sense of assurance. However, scans detect many issues but do not prove that all controls operate effectively, nor do they validate exploitability or compensating controls; they can also produce false negatives.
Why not C: This traps candidates who think only manual testing can find configuration issues. Properly configured vulnerability scanners are specifically designed to detect many missing patches and insecure configurations; penetration testing is not required to discover those categories of weaknesses.
Question 3
Hint
Classify the engagement by two dimensions: how much the testers know before they start, and whether they may only identify weaknesses or also try to exploit them.
Answer A. This is a gray-box penetration test because the testers have meaningful but incomplete internal knowledge (network ranges, an architecture diagram, and a standard user credential) rather than full access. They are also authorized to actively exploit discovered weaknesses to evaluate whether those weaknesses can be chained into broader compromise in a production-like environment. The combination of partial prior knowledge plus permitted exploitation distinguishes a gray-box penetration test from black-box testing or a vulnerability assessment.
Why not B: White-box testing implies extensive or near-complete internal knowledge (for example, source code, detailed configs, or admin credentials). The engagement provides only partial information and no administrative privileges, so it is gray-box rather than white-box.
Why not C: Black-box testing starts with little or no internal knowledge to simulate an external attacker. Because the testers are given network ranges, an architecture diagram, and a user credential, they have insider context, so black-box is not the best fit.
Why not D: A vulnerability assessment focuses on identifying and prioritizing weaknesses and typically stops short of active exploitation. Because testers here are authorized to attempt exploitation and escalation to determine impact and extent of compromise, the engagement is a penetration test, not merely an assessment.
Question 4
Hint
Focus on the difference between evidence that a known weakness was specifically fixed and evidence that the whole environment is generally secure.
Answer C. A targeted retest directly verifies that the specific chained access exploit has been closed by attempting the same scenario under controlled conditions, which is the strongest evidence for that known finding. Broader authenticated scans or later full-scope penetration tests address wider assurance objectives but do not specifically prove that this particular authorization and permission configuration now prevents the original exploit.
Why not A: This is tempting because authenticated scans provide broad coverage and are repeatable, but they may not reproduce the exact chained authorization logic and permission combination that allowed document retrieval. A clean enterprise scan is useful but weaker evidence for that specific exploit path than a focused retest.
Why not B: Candidates may view full-scope pen tests as the gold standard, but waiting for an unscripted engagement needlessly delays assurance about a known, remediated weakness. A focused retest is sufficient and more appropriate to validate remediation of this specific finding.
Why not D: Documentation and approvals show a change process occurred, but they do not demonstrate that the technical control now prevents the previously exploited confidentiality risk. Technical validation (a retest) is required to confirm effective remediation.
Question 5
Hint
Classify the test by its primary objective and scope, not by the first technique used.
Answer C. The engagement's primary objective was to determine whether a realistic attack path could reach a specified database within a defined, preapproved scope and two-week timebox, this aligns with penetration testing. Penetration tests validate impact by actively exploiting and chaining weaknesses; by contrast, vulnerability assessments stop at identification, and red-team exercises emphasize stealth and measuring defender detection and response.
Why not A: Red-team engagements are plausible distractors since they use adversary-like tactics, but they typically aim to test long-term stealth, detection, and response across a broader mission. The stem explicitly limits scope and timebox and says the engagement was not designed to measure long-term stealth or defender maturity, which makes penetration testing the better fit.
Why not B: This distractor is tempting because the testing occurred in production and weaknesses were found, but vulnerability assessments center on discovering and prioritizing flaws rather than exploiting and chaining them to demonstrate end-to-end reach to a protected asset. Here, exploiting and proving an attack path to the target was the central objective.
Why not D: Phishing as an initial vector might suggest a social engineering test, but that type of assessment focuses primarily on human manipulation and access techniques. In this scenario phishing was one tactic within a broader, exploit-focused exercise intended to chain technical weaknesses to reach a database, so social engineering alone is too narrow.
Question 6
Hint
Which testing methods actually exercise application logic and APIs introduced by the recent release versus those that mainly detect host/network misconfigurations or provide broad attestation?
Answer D. The deployment introduced application logic and new API endpoints that are not covered by host/network vulnerability scans or by an infrastructure-focused penetration test performed before the change. Targeted application-layer (dynamic/manual) penetration testing is necessary to identify business-logic and API vulnerabilities, and reviewing change-management and firewall artifacts corroborates that controls were implemented and effective after the release.
Why not A: Tempting because automated scans and an external penetration test provide systematic evidence, but wrong because the weekly scans focus on host/network issues and the vendor's pen test occurred before the release and excluded the new module, so neither provides assurance about application-layer or business-logic vulnerabilities introduced by the deployment.
Why not B: Tempting because SOC 2 reports and management inquiry are efficient sources of assurance, but wrong because a SOC 2 report may not cover the newly developed module or recent deployment and inquiry alone is insufficient corroboration; direct, targeted testing of the changed application components is required.
Why not C: Tempting because configuration and access controls are important, but wrong because those reviews do not exercise application logic or API behavior. Vulnerabilities in the new authentication logic or API endpoints are primarily detected through application-layer dynamic/manual testing, not just configuration review or access sampling.
Question 7
Hint
Which approach actually tries to break the controls (active, demonstrative evidence) rather than only checking settings, records, or alerts?
Answer A. A controlled penetration test actively attempts to exploit vulnerabilities and bypass protections under realistic attack conditions, so it directly demonstrates whether an attacker could gain access, providing the strongest direct evidence of operating effectiveness. The other approaches mainly identify weaknesses, confirm configuration, or verify procedure adherence and therefore offer indirect or detective evidence rather than an active test of defenses.
Why not B: Tempting because scans and logs are continuous and surface vulnerabilities or suspicious activity, but wrong because they are diagnostic/detective; they do not attempt exploitation or prove that MFA or privilege controls cannot be bypassed in an attack.
Why not C: Tempting because configuration inspection verifies technical implementation and can find misconfigurations, but wrong because it is a static review that cannot demonstrate whether controls will hold up against active exploitation or sophisticated bypass techniques at runtime.
Why not D: Tempting because walkthroughs and reperformance provide evidence that procedures are followed and can show operating effectiveness for specific processes, but wrong because they rely on sampled representations and do not simulate an attacker trying to bypass controls, making them weaker than an active penetration test for proving resilience.
Question 8
Hint
Focus on the primary purpose of each testing method, not on what merely raises overall risk or provides background assurance.
Answer C. The governing factor is the testing objective. Vulnerability scans identify known weaknesses broadly, while penetration tests are used when management needs to know whether those weaknesses can actually be exploited, chained, or used to bypass confidentiality and access controls. Because the identity federation, role-mapping, and API changes affect authentication and authorization paths, evidence of real-world exploitability should drive the choice.
Why not A: This distractor plays on over-reliance on third-party assurance. A SOC 2 report can inform the risk assessment regarding provider-managed controls, but it does not replace testing of the entity's own configuration, role mapping, federation logic, or application-specific attack surfaces.
Why not B: This is tempting because regulated data increases risk, but data sensitivity affects the overall risk assessment and testing frequency/depth; it does not automatically mandate a penetration test absent a specific legal or contractual requirement.
Why not D: This is appealing as a shortcut, but prior low-severity scan results do not answer whether recent design or access-path changes created exploitable vectors. Historical scan findings are informative background, not the primary determinant when exploitability of new changes is in question.
Question 9
Hint
Ask whether the procedure is only identifying weaknesses or actually trying to use them.
Answer D. A penetration test goes beyond identifying weaknesses and involves an authorized attempt to exploit them. Here, the specialist is actively trying to use known weaknesses to gain unauthorized access in a controlled, non-production environment, which is characteristic of penetration testing rather than a passive assessment.
Why not A: A disaster recovery test evaluates the ability to restore systems and operations after a disruption. It is not concerned with exploiting security vulnerabilities, even if performed in a test environment.
Why not B: This is tempting because the scenario began with an automated scan that identified vulnerabilities. However, a vulnerability assessment focuses on finding and prioritizing weaknesses, while a penetration test attempts to exploit them to demonstrate whether they can be used to compromise the system.
Why not C: A controls walkthrough traces processes and confirms that controls are implemented and operating; it does not simulate an attacker or attempt unauthorized access to exploit technical vulnerabilities.
Common questions
When should I use a vulnerability scan instead of a penetration test?
Use scanning to identify potential weaknesses, such as outdated portal software or broad permissions. Use authorized penetration testing when the objective is to determine whether weaknesses can be exploited to reach customer data.
Does a clean vulnerability scan eliminate the need for penetration testing?
No. A clean scan does not prove that an attacker cannot exploit application logic or combine weaknesses to reach customer documents.
Is an authenticated vulnerability scan a penetration test?
Not merely because testers receive a user account. If they only identify weaknesses, it remains scanning; controlled attempts to exploit weaknesses distinguish penetration testing.
Watch it solved
A full CPA ISC task-based simulation on Testing, worked step by step.
ITGC Testing: Procedures, Samples & Exceptions | CPA ISC TBS on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Testing
- When to Use Vulnerability Scanning vs Penetration Testing
- Penetration Test Authorization and Cloud Scope Rules
- PII in Test Environments: Masked vs. Unmasked Data
- Testing Automated Access Controls Across the Audit Period
- Penetration Test Limits: Point in Time and Scope
- What Drives Security Testing Scope and Frequency?
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.