Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Vulnerability Assessment vs Penetration Testing

Reviewed 13 November 2026Concept 1 min read

Quick answer

A vulnerability assessment uses automated scanning plus expert review to find and rank as many known weaknesses as possible across your systems. A penetration test goes further: a skilled tester actively exploits weaknesses and chains them together to show what an attacker could actually achieve. Assessments give breadth; penetration tests give proof and depth.

On this page
01

How It Works

A vulnerability assessment runs authenticated and unauthenticated scans across a defined range of systems, removes false positives, and ranks findings by severity and exploitability. It answers "what known weaknesses do we have?" and is efficient to repeat frequently. A penetration test starts from an attacker's position, such as the internet, a standard user account or a web application, and uses manual techniques to exploit vulnerabilities, misconfigurations and logic flaws, then chains them. It answers "what could an attacker do, and how far could they get?"

02

Why It Matters

Choosing the wrong one wastes budget. Scanning alone misses business-logic flaws, chained attacks and access control issues, and produces long lists without context. Penetration testing alone is too expensive to run across every system every month. Mature programs combine regular vulnerability assessments for coverage with targeted penetration tests for depth on the systems that matter most.

03

How to Test for It

  1. Use a vulnerability assessment to establish a baseline across all systems and track remediation over time.
  2. Use a penetration test on internet-facing systems, critical applications and before major releases.
  3. Use an assumed-breach internal test to see how far a compromised account could go.
  4. Check whether your compliance framework requires one, the other or both.
  5. After either, retest the fixes so the result reflects your current state.
04

How to Reduce the Risk

Run vulnerability assessments at least quarterly and after major changes, penetration test your most important systems at least annually and after significant changes, remediate by real-world risk (exploited in the wild first) rather than raw severity score, and verify fixes with a retest.

05

Regulatory and Framework Context

In Australia, the Essential Eight's patching controls rely on regular vulnerability scanning, while penetration testing is commonly expected under frameworks such as ISO 27001, PCI DSS and APRA's CPS 234 for critical assets.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

Is a vulnerability scan the same as a vulnerability assessment?

A scan is the automated part. An assessment adds expert validation, false-positive removal and prioritisation, which turns raw output into a usable list.

Which do I need for compliance?

Many frameworks require both. PCI DSS, for example, requires quarterly scans and an annual penetration test.

How often should we do each?

Vulnerability assessments quarterly or continuously; penetration tests at least annually and after significant changes.

Change log

  1. 13 November 2026First published.
1300 654 898