A customer questionnaire asks for "evidence of regular penetration testing"; the IT provider offers a monthly vulnerability scan report and says it amounts to the same thing. It does not, and the difference matters to the customer, to the insurer and to an information security audit. Both are useful and most organisations need both, but they answer different questions and are bought, priced and scheduled differently.
What a vulnerability scan does
A vulnerability scan is an automated comparison of your systems against a database of known weaknesses: missing patches, outdated software versions, default configurations, open services, known-vulnerable components. It runs in hours, can be repeated weekly or monthly, covers every address in scope, and produces a list ranked by a severity score. Its strengths are breadth, repeatability and cost. Its limits are that it only finds what is already catalogued, that it cannot tell whether a weakness is actually exploitable in your environment, that it produces false positives that someone must triage, and that it knows nothing about the logic of your applications, your users or the way your systems are connected.
What a penetration test does
A penetration test is a time-boxed, authorised attempt by a skilled tester to achieve an objective an attacker would want: read customer data, take over an account, move from the public website into the internal network, escalate from a user to an administrator. The tester uses scanners, but also reads the application, chains low-severity findings into a high-impact path, tests business logic that no scanner understands, and stops at agreed boundaries. It takes days, is scoped to specific systems, and produces a report of what was achieved, how, with evidence, and what to fix first. Its strength is that it proves impact: a finding in a penetration test report is something a person actually did, not something a database says might be possible. Its limits are cost, scope and the fact that it is a point in time.
What each proves to the people asking
A customer or a framework asking for "penetration testing" wants to know that someone competent has tried to break in and reported what they found; a scan report does not answer that, and a procurement team that knows the difference will say so. An insurer usually wants both: scanning as evidence of ongoing hygiene and a test as evidence that the perimeter and the key applications have been examined. A certification audit against ISO/IEC 27001 looks for the organisation to have decided, on the basis of its risk assessment, what technical testing it needs and to have done it; for most organisations that decision is a regular scan plus an annual test of internet-facing systems and any application that handles sensitive data, with a re-test after significant change. In the UK, Cyber Essentials Plus includes a specific external vulnerability assessment as part of the scheme; it is not a penetration test and is not accepted as one.
How often, and of what
The pattern that satisfies most buyers and audits is monthly or continuous scanning of everything, annual penetration testing of internet-facing infrastructure and the applications that matter, a test of any new system or major change before it goes live, and re-testing of critical findings after they are fixed. Scope the test to the systems that hold the data your customers care about, agree the objectives in writing, and choose a tester whose report separates evidence from opinion and rates findings by exploitability as well as by severity.
What to do next
If you have scan reports and no test, an external infrastructure and web application test is the usual first engagement and the one most questionnaires are asking about. TRAIBCERT's penetration testing page describes the nine test types, how scoping works and what the report contains.
Engagement with TRAIBCERT: Penetration testing
Application, network, mobile, cloud, IoT, physical, social engineering, red teaming. Tell us your sites, headcount and the date you need it by; a sector specialist replies within one working day with a fixed quotation for the whole cycle.
