PracticeISCFree practice exam

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.

The ruleUse a scoped, authorized penetration test when management needs evidence of exploitability or attack paths to sensitive data. Vulnerability scans alone do not prove exploitability.

Try one first

An organization has launched a new web portal that stores customer personal information. IT has already run an automated vulnerability scan and received a list of possible weaknesses. Management now wants to know whether those weaknesses can actually be used to gain unauthorized access to customer data. Assuming the testing is authorized and controlled, which action is most appropriate?
Hint

Focus on the difference between a test that identifies possible weaknesses and one that shows whether those weaknesses can actually be exploited.

Sort it

Vulnerability scanning

The activity identifies or reports potential weaknesses without attempting exploitation.

Penetration testing

Within approved boundaries, testers attempt controlled exploitation to determine whether unauthorized access is achievable.

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

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

A company performs quarterly automated vulnerability scans on its internet-facing applications. It does not perform penetration testing. Assume the scans are properly configured and current. What is the most likely consequence of relying only on vulnerability scans?
Hint

Think about the difference between identifying possible weaknesses and proving how an attacker could actually use them.

Question 3

A CPA assisting management with security oversight reviews the scope of a planned third-party security engagement. The testers will receive the organization's network ranges, a current architecture diagram, and one standard employee credential, but they will not receive source code, administrator credentials, or a list of known vulnerabilities. They are authorized to attempt to exploit weaknesses they discover to determine whether broader access can be obtained in a production-like environment; social engineering and physical intrusion are out of scope. Assume standard security-testing terminology. How should this engagement be classified?
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.

Question 4

A limited-scope penetration test showed that an authenticated low-privilege employee could retrieve other customers' stored documents by combining predictable document IDs in URLs with overly broad file permissions. Management corrected the URL access check and tightened folder permissions 10 days later. Before quarter-end, management wants the strongest evidence that this specific confidentiality weakness has actually been remediated, but does not want to overstate that it has re-tested the entire environment. Assume change management approval, developer testing, and updated policies are already complete. Which testing approach is most appropriate?
Hint

Focus on the difference between evidence that a known weakness was specifically fixed and evidence that the whole environment is generally secure.

Question 5

After a major migration of confidential customer data, an entity hired an external security firm. Under written rules of engagement, the firm could send phishing emails, exploit discovered weaknesses, move laterally within a defined production subnet, and attempt to reach one specified database that stored confidential customer records. The exercise was time-boxed to two weeks, the in-scope assets were preapproved, and management's stated objective was to determine whether an attacker could realistically chain weaknesses to reach that database. The security operations team was told testing would occur during the month, but the engagement was not designed to measure long-term stealth or the defenders' overall detection maturity. Which conclusion is best supported about the testing performed?
Hint

Classify the test by its primary objective and scope, not by the first technique used.

Question 6

FinCo, a cloud-based company that processes payment card transactions, deployed a major application release to production last week that changed authentication logic and added new API endpoints that accept cardholder data for recurring billing. FinCo runs automated vulnerability scans weekly that cover hosts and network services but do not perform full application-layer testing. The external vendor that manages the payment gateway performs an annual external penetration test focused on infrastructure; that penetration test was completed two months before the release and explicitly excluded the new module. As the auditor evaluating controls over confidentiality and integrity of payment data after this deployment, which of the following is the most appropriate testing approach?
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?

Question 7

An auditor is evaluating the operating effectiveness of controls designed to prevent unauthorized remote access to confidential customer data at a service organization. Controls include centralized MFA for all remote privileged accounts, a company password policy, automated log monitoring with alerts for failed logins and privilege escalation, and monthly vulnerability scans. The last penetration test was performed more than 12 months ago; there have been no known breaches. Which single additional testing approach would provide the strongest direct evidence whether the controls are effectively preventing unauthorized remote access to confidential customer data?
Hint

Which approach actually tries to break the controls (active, demonstrative evidence) rather than only checking settings, records, or alerts?

Question 8

An entity that stores customer PII in a cloud-hosted application already performs weekly authenticated vulnerability scans. In 20X6, it implemented a new internet-facing identity federation module, changed role-mapping logic for privileged support users, and added an API used by third-party applications to retrieve masked customer records. Management must decide whether the next security test should be another broad vulnerability scan or a targeted penetration test. Assume no law, regulator, or contract expressly mandates a specific test type, both tests can be performed in a production-like environment, and the cloud provider's controls are covered by a current SOC 2 report. Which factor should govern the choice most directly?
Hint

Focus on the primary purpose of each testing method, not on what merely raises overall risk or provides background assurance.

Question 9

Ridge Co. used an automated tool to identify open ports and outdated software on its customer-facing portal. Management then authorized an external security specialist to try to use those weaknesses to gain unauthorized access to a test environment that mirrors production. The specialist's follow-up work is best classified as which type of testing?
Hint

Ask whether the procedure is only identifying weaknesses or actually trying to use 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 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

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.