PracticeISCFree practice exam

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.

The ruleUse authenticated vulnerability scanning to identify known missing patches and insecure configurations without attempting exploits. Use a separately authorized penetration test when the objective is to attempt exploitation and demonstrate impact.

Try one first

An entity is planning routine security testing of its internet-facing servers. Management wants a repeatable, low-disruption procedure that can be run regularly to identify known issues such as missing patches, default passwords, and outdated software versions. Assume the entity does not want the test to actively exploit weaknesses or simulate a full attacker campaign. Which is the best conclusion?
Hint

Focus on the type of test that finds known technical weaknesses without primarily trying to exploit them.

Sort it

Vulnerability scanning

Identify known weaknesses without attempting to exploit them, using credentials when deeper patch and configuration visibility is needed.

Penetration testing

Under explicit authorization, attempt to exploit weaknesses to demonstrate access or impact.

ItemGoes 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.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

An internal audit team must test security, confidentiality, and privacy controls over a cloud-hosted customer database that stores sensitive personally identifiable information. Management needs evidence of control operation to support an upcoming external compliance review. Constraints: the team has a two-day testing window, must avoid service disruption, and IT policy prohibits active exploit attempts that could affect availability. IT will provide administrative credentials for testing and access to configuration documentation and current user-access lists. Which of the following testing approaches is the most appropriate given these constraints?
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.

Question 3

A company wants to test a customer-facing billing system that processes live personal data. Management approved a security assessment but did not authorize exploit attempts, privilege escalation, credential harvesting, or any activity that could reasonably disrupt the production environment. Assuming the objective is to identify security weaknesses within those limits, which testing approach is most appropriate?
Hint

Focus on which option stays within authorization to find weaknesses without actively trying to compromise the environment.

Question 4

An organization asks its security team to use an automated tool to examine its internet-facing servers for missing patches, weak settings, and other known technical weaknesses. The team is specifically instructed not to exploit any findings or attempt to gain unauthorized access. This activity is best classified as which of the following?
Hint

Focus on whether the team is only identifying weaknesses or is actually trying to exploit them.

Question 5

A company has moved its customer portal, which stores confidential customer data, to a new hosting environment. Before go-live, management wants a cost-effective security test that will broadly identify known missing patches and insecure configurations across the internet-facing servers. Management does not need the tester to exploit weaknesses or prove data exfiltration. Assuming change approvals are already complete, which action is most appropriate?
Hint

Match the testing method to the stated objective: broad identification of known weaknesses is different from attempting exploitation.

Question 6

A company asks its CPA to recommend a security testing approach for its annual review. Management wants an automated test that identifies missing patches, unnecessary open ports, and outdated software on its internet-facing servers, causes minimal disruption, and does not attempt to exploit any weaknesses. Which type of testing best addresses the company's primary issue?
Hint

Focus on the method that identifies technical weaknesses broadly without trying to break in through them.

Drill all 138 Testing questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Testing practice →

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.