ISC · Security and Confidentiality and Privacy · 6 practice questions
When to Use Vulnerability Scanning vs Penetration Testing
Use vulnerability scanning to identify known weaknesses without attempting exploitation. Below, sort requests for testing a company's portal servers by whether they identify weaknesses or attempt exploitation.
Try one first
Hint
Focus on the type of test that finds known technical weaknesses without primarily trying to exploit them.
Answer D. A vulnerability scan is designed to identify known technical weaknesses, missing patches, insecure configurations, and outdated software, across systems in a repeatable, low-disruption way. It typically does not attempt active exploitation or simulate a full attacker campaign, which matches management's stated constraints.
Why not A: Penetration testing attempts to exploit vulnerabilities to demonstrate attack paths and impact; it is more intrusive and often unsuitable for frequent, low-disruption, repeatable checks.
Why not B: Business continuity testing evaluates an organization's ability to continue or recover operations after disruptions and does not focus on finding technical vulnerabilities on servers.
Why not C: Red-team exercises simulate realistic attacker campaigns across people, processes, and technology and are broader and more intrusive than the narrow, repeatable identification of known technical weaknesses.
Sort it
Identify known weaknesses without attempting to exploit them, using credentials when deeper patch and configuration visibility is needed.
Under explicit authorization, attempt to exploit weaknesses to demonstrate access or impact.
| Item | Goes to |
|---|---|
| Use supplied administrator credentials to check the portal servers for missing patches; do not attempt exploits. | Vulnerability scanningAuthenticated scanning provides patch visibility without requiring exploitation. |
| Under an approved test scope, attempt to exploit an outdated portal service to demonstrate unauthorized access. | Penetration testingThe objective is to demonstrate access through an exploit, not merely report outdated software. |
| After a portal software update, scan all supporting hosts for known vulnerabilities without exploiting findings. | Vulnerability scanningThe update prompts a broad check for known weaknesses, not an exploitation exercise. |
| From outside the network, identify exposed portal-server ports and services without attempting entry. | Vulnerability scanningUnauthenticated probes identify externally visible exposure without exploiting it. |
| With explicit approval, attempt privilege escalation through a reported portal-server weakness. | Penetration testingTrying to gain greater privileges through a weakness is attempted exploitation. |
| Use supplied credentials to inspect weak TLS settings and outdated software across the portal servers. | Vulnerability scanningCredentialed inspection identifies configuration and software weaknesses; supplied credentials do not make it an exploit. |
| Despite a clean portal scan, management separately authorizes exploit attempts to test whether access can be gained. | Penetration testingA clean scan does not prove security. The new objective requires attempted exploitation. |
| Run an approved recurring production scan for missing patches, with exploit attempts disabled. | Vulnerability scanningProduction use and repetition do not change the classification; the procedure identifies weaknesses without exploitation. |
| Replace an external-only scan with credentialed checks of portal-server patch status; exploitation remains prohibited. | Vulnerability scanningCredentials improve visibility into patch status without changing the no-exploitation objective. |
| Under explicit authorization, exploit a reported portal flaw to demonstrate access to a designated test record. | Penetration testingDemonstrating access through the flaw validates impact rather than merely identifying a potential weakness. |
| Within approved change controls, scan the live portal servers and report known weaknesses without validating exploits. | Vulnerability scanningThis supports a vulnerability assessment. Live production targets do not turn scanning into penetration testing. |
| Before portal go-live, use authenticated checks to identify insecure configurations across its servers and prioritize remediation. | Vulnerability scanningBroad identification and remediation prioritization fit scanning when proof of compromise is not required. |
Key points
- Remember: Looking for weaknesses is scanning; trying to exploit them is penetration testing.
- Authenticated scans use valid credentials to inspect patch and configuration details unavailable to external probes.
- Production scans still require authorization and change control.
- Scan findings identify potential weaknesses; they do not prove exploitability.
How the exam traps you
- Calling a scan a penetration test because it targets production servers. Classify the work by attempted exploitation, not the environment tested.
- Treating an authenticated scan as an attempt to break in. Using supplied credentials to inspect settings is not exploiting a weakness.
- Treating a clean scan as proof that compromise is impossible. A scan checks for known weaknesses; it does not establish that the servers cannot be breached.
Question 2
Hint
Focus on which tests are permitted without disruption and which combination both identifies technical weaknesses and demonstrates operating effectiveness of confidentiality/access controls to auditors.
Answer B. Because active exploit attempts are prohibited and administrative credentials plus configuration and access lists are available, an authenticated vulnerability scan combined with a configuration review and privileged-account recertification best balances non‑disruption and coverage. Authenticated scans reveal vulnerabilities and misconfigurations visible only with valid credentials and reduce false positives; reviewing configurations and recertifying privileged access directly evaluates confidentiality/access controls and produces evidence auditors need of operating effectiveness.
Why not A: Penetration testing can demonstrate exploitability and provide strong assurance, but the stem explicitly prohibits active exploit attempts that could affect availability and the short window raises outage risk, so a full exploit-focused pentest is not appropriate.
Why not C: Log and incident-review are safe and may detect past or ongoing incidents, but they are primarily detective and, within a two-day window, do not proactively identify unexploited vulnerabilities or demonstrate the operating effectiveness of configuration and privileged-access controls for auditors.
Why not D: An unauthenticated external scan is low risk and useful for exposed services, but without credentials it misses issues visible only to legitimate users and cannot assess privileged-account or configuration controls central to confidentiality, so it provides incomplete evidence for the compliance review.
Question 3
Hint
Focus on which option stays within authorization to find weaknesses without actively trying to compromise the environment.
Answer C. Management explicitly prohibited exploit attempts, escalation, credential harvesting, and any activity that could disrupt production. A vulnerability assessment is designed to identify and report weaknesses without actively exploiting them, so it fits the stated authorization and minimizes risk to live personal data and availability. Penetration tests and red-team exercises typically include exploitation or simulated attacks that exceed the allowed scope.
Why not A: This is tempting because narrowing the scope to external services sounds safer, but penetration testing usually involves attempting exploitation to validate risk. Since exploit attempts were not authorized, a penetration test exceeds the stated limits even if the target surface is reduced.
Why not B: Though targeting people can reveal important weaknesses, this choice involves credential harvesting and active deception that were explicitly disallowed and would increase confidentiality and privacy risks in a live production environment.
Why not D: Red-team exercises are typically broader and more intrusive, often including exploitation, lateral movement, or disruptive actions to test detection and response. That scope conflicts with the management limitations in the stem.
Question 4
Hint
Focus on whether the team is only identifying weaknesses or is actually trying to exploit them.
Answer B. This is vulnerability scanning because the team is using automated tools to identify known weaknesses (missing patches, weak settings) without attempting to exploit them. The explicit instruction not to exploit findings distinguishes it from penetration testing or red-team activities.
Why not A: Tempting because penetration tests search for weaknesses, but they typically include attempts to exploit vulnerabilities to confirm whether unauthorized access or impact is possible. The stem explicitly forbids exploitation, so penetration testing is not the best classification.
Why not C: Red-team exercises simulate an adversary with stealthy, objective-based attacks that often involve exploitation and lateral movement. The described activity is a narrower, tool-driven scan without exploitation, so it better fits vulnerability scanning.
Why not D: A configuration baseline review compares system settings against a standard or benchmark and focuses on compliance and hardening. While it can reveal weak settings, the stem emphasizes an automated search for known vulnerabilities across servers, which aligns more closely with vulnerability scanning.
Question 5
Hint
Match the testing method to the stated objective: broad identification of known weaknesses is different from attempting exploitation.
Answer A. An authenticated vulnerability scan is the best fit when the goal is to broadly identify known weaknesses such as missing patches and insecure configurations. It is generally more efficient and cost-effective than a penetration test when exploitation is not required. The facts point to detection and remediation of common technical issues, not proof of compromise.
Why not B: This is tempting because penetration tests are a well-known security testing method and often feel like the strongest choice. However, the stated objective is not to exploit systems or demonstrate impact; it is to broadly identify known configuration and patching issues. A penetration test is usually narrower, more intensive, and less aligned with the requested scope.
Why not C: This is tempting because access reviews are important for protecting confidential data. Still, an access recertification is an administrative control activity, not the testing action that best identifies missing patches and insecure server configurations in the new environment. It addresses a different risk than the one described.
Why not D: This can sound reasonable because the portal was recently migrated and management may want broad assurance before go-live. But a disaster recovery test addresses availability and recoverability, not whether internet-facing servers have known vulnerabilities or weak configurations. It does not match the specific testing objective in the stem.
Question 6
Hint
Focus on the method that identifies technical weaknesses broadly without trying to break in through them.
Answer B. Vulnerability scanning is an automated method designed to discover known weaknesses such as missing patches, open ports, and outdated software without attempting to exploit them. It typically runs with minimal disruption and produces a report for remediation, matching management's stated goals.
Why not A: This is tempting because penetration testing assesses security by attempting to exploit vulnerabilities to demonstrate impact. However, penetration tests are typically manual or targeted and involve exploitation, which management specifically said to avoid.
Why not C: This may attract candidates who focus on the word "testing," but disaster recovery testing evaluates whether systems and operations can be restored after a disruption. It does not identify technical configuration issues like missing patches or open ports on live servers.
Why not D: Social engineering testing targets human behavior and controls and can reveal people-related risks. It does not directly scan or identify technical server vulnerabilities such as outdated software or unnecessary open ports.
Common questions
When should I use vulnerability scanning instead of penetration testing?
Use scanning when the goal is to identify known weaknesses without exploiting them. Use a separately authorized penetration test when management wants testers to attempt exploitation and demonstrate impact.
Why use an authenticated vulnerability scan?
Valid credentials let the scanner inspect internal patch and configuration details. An external, unauthenticated scan has less visibility into those details.
Does a clean vulnerability scan mean the servers are secure?
No. A clean scan means the scan reported no findings, not that compromise is impossible or that exploitability was tested.
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
- Vulnerability Scan vs. Penetration Test: Which to Use?
- 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.