Getting started

Vulnerability assessment vs penetration test: which do you need?

The two terms are often used as if they mean the same thing. They do not, and buying the wrong one can leave you with either a long list you cannot act on or a deep test that missed half your systems.

By the Twarx Vulnerability Assessment team5 min read

If you have started looking into security testing for your business, you have probably seen the terms vulnerability assessment and penetration test used side by side, sometimes interchangeably. Suppliers do not always use them consistently, which makes it harder to know what you are buying.

This guide explains what each one is, what question it answers, and how to decide which is right for your organisation at this point. It is written for business owners, CTOs and anyone who has to commission testing and then act on the results.

The short answer

A vulnerability assessment asks: what weaknesses exist across these systems, and how serious is each one? It aims for breadth. The goal is to find and rate as many real issues as possible within an agreed scope, so you can fix them in a sensible order.

A penetration test asks: could someone actually achieve a specific goal, such as reaching customer data or gaining administrator rights, by exploiting weaknesses in these systems? It aims for depth. The tester takes findings further, in a controlled way, to show what an attacker could really do with them.

Both are carried out only with the written authorisation of the system owner, and both should end with a report that tells you what to fix. The difference is in the question each is designed to answer.

What a vulnerability assessment involves

A good vulnerability assessment combines automated scanning with manual testing. Scanners are fast and consistent at spotting known patterns, such as outdated software or missing security settings. Manual testing is needed for the things scanners cannot understand, such as whether one customer can see another customer's records, or whether a checkout process can be misused.

Every potential issue should be verified by a person before it appears in the report. A list of raw scanner output is not an assessment. It is often long, full of false positives and hard for a development team to act on.

The output is a prioritised list of findings, each with a severity rating, evidence that it exists and guidance on how to fix it. Because the work aims for coverage, it is well suited to answering the question "where are we exposed?" across an application, an API, a network range or a set of cloud accounts.

What a penetration test involves

A penetration test usually starts with similar discovery and testing, but goes further with selected findings. The tester demonstrates, safely and within agreed limits, how a weakness could be used, and whether several smaller weaknesses could be combined into something more serious.

Because this takes more time per finding, a penetration test often covers fewer areas in more depth. It is frequently built around specific objectives agreed in advance, for example "can an ordinary user reach the admin functions?" or "can an outsider reach the customer database?"

The value is in the evidence. A demonstrated path from an exposed login page to sensitive data is far more persuasive to a board, an investor or a customer than a list of individual issues rated medium. It shows not just that a weakness exists, but what it would mean in practice.

How to decide which you need

For most organisations commissioning testing for the first time, a vulnerability assessment is the right starting point. It gives you a broad picture of your exposure and a list of practical fixes. There is little value in a deep exploitation exercise against systems that still have many basic, easily fixed issues.

A penetration test becomes more useful once the basics are in hand, or when you have a specific question that needs a demonstrated answer.

  • Choose a vulnerability assessment if you have never had your systems tested, if you want coverage across several systems, or if you need a practical list of fixes for your developers.
  • Choose a penetration test if you have already fixed the obvious issues, if you need to know whether a specific scenario is possible, or if a customer or contract asks for one explicitly.
  • Consider a combination if you want broad coverage with deeper testing of one or two high-risk areas, such as payments or administrator access.

Questions to ask before you buy

Because the terms are used loosely, the label on a proposal matters less than what it actually includes. Before you agree to any testing, ask the supplier to be specific.

  • Which systems, environments and user roles will be tested, and which will not?
  • How much of the work is manual testing, and is every finding verified by a person?
  • Will you attempt to exploit findings, and if so, within what limits and with what safeguards on live systems?
  • What will the report contain, and who is it written for?
  • Is a retest of fixed issues included?
  • What authorisation do you need from us, and who needs to sign it?

What either one cannot tell you

Neither type of testing proves that a system is secure. Each is a snapshot of the systems in scope, at the time of testing, using the approach agreed. New code, new infrastructure and newly published vulnerabilities all change the picture afterwards.

Testing also cannot replace basic security practices: keeping software up to date, limiting who has administrator access, using multi-factor authentication and reviewing code before it is released. Testing tells you how well those practices are working. It is most valuable when it is repeated, so you can see whether exposure is going down over time.

Finally, a report can support compliance work, for example by providing evidence that testing took place and issues were fixed, but it does not make you compliant with any standard on its own. That depends on the full set of requirements of the standard in question.

The short version

A vulnerability assessment tells you where you are exposed and what to fix first. A penetration test shows what someone could actually do with those weaknesses. Most businesses should start with an assessment, fix what it finds, and consider deeper testing once the basics are in place. Whatever you choose, judge a proposal by its scope, its manual testing and its report, not by its label.

Know where you stand

Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.