What a vulnerability scan is good at

A vulnerability scan checks systems for known indicators such as exposed services, outdated software versions or common configuration issues. It can be useful for recurring visibility across a known set of assets and for identifying items that need a closer look.

Scan results require review. A reported issue can be inaccurate, unreachable or irrelevant to the way a particular system is configured. A scan may also miss weaknesses in business logic, authorization rules or a sequence of actions that only becomes clear when someone follows the application flow.

What a penetration test adds

A penetration test uses manual investigation and appropriate tools to examine the agreed scope. The tester validates whether selected weaknesses can be reached and explains how they affect the target system within the authorization provided.

The depth depends on scope, access and time. A web application test might examine user roles, data access, account recovery and important business workflows. It should state which areas were reviewed and which were outside the engagement.

Match the work to the decision

Choose scanning when you need repeatable checks across a defined inventory. Choose a penetration test when you need deeper investigation of an application, API or network and evidence tied to a specific security question. Some organisations use both: scanning for regular coverage and testing for focused validation.

Neither service replaces secure development, patch management, access reviews, backups or incident response planning. They provide evidence that can inform those activities; the team still needs to decide how findings will be fixed and verified.

Questions to settle before booking

Ask what assets and user roles are included, whether testing is authenticated, how production impact is controlled, what the report contains and how critical findings will be communicated. Confirm the provider has permission for every system in scope and agree how retesting will work.