Penetration Testing Explained: Scope, Cost and What You Get
What a penetration test involves, what affects the price and how to get value from the report.

Key Takeaways
- A penetration test is an authorised attempt to find and exploit weaknesses.
- Scope drives cost: more systems and more depth mean more time.
- The report should prioritise findings and explain how to fix them.
- Retest after remediation to confirm fixes.
Penetration testing is one of the clearest ways to find out how an attacker could get into your business. It also confuses many buyers, who are unsure what is included, how much it should cost and how to judge the result.
This guide answers the questions we are asked most often. It reflects our penetration testing services and links to NCSC and CREST guidance. If you are preparing for a test, see our guide on how to prepare for a penetration test.
What is a penetration test?
A qualified tester, with your written permission, attempts to break into your systems using the methods a real attacker would. The aim is to find weaknesses before someone else does, and to show how serious they are.
It differs from an automated scan because a person reasons about what they find and combines weaknesses.
↑ Back to ContentsWhat types of test are there?

Common types include external network, internal network, web application, wireless, cloud configuration and social engineering tests. Each looks at a different way in.
Choose based on what you most need to protect and what an attacker is most likely to target.
↑ Back to ContentsHow does scoping work?
Scope defines what is tested, from where, when and with what limits. It lists systems, applications, addresses and anything excluded. Clear scope avoids surprises and ensures you test what matters.
A good provider will ask about your business, not just your IP addresses.
↑ Back to ContentsWhat affects the cost?
Price reflects the number of systems, their complexity, the depth of testing, the time required and the tester’s expertise. A small website costs less than a large application with many roles.
Be cautious about very cheap quotes that may be little more than a scan.
↑ Back to ContentsHow do you judge a provider?
Ask about the qualifications of the testers, whether the company is accredited by a body such as CREST, how they handle your data and what the report looks like. Ask for a sample report.
Check they will agree rules of engagement and keep your results confidential.
↑ Back to ContentsWhat should the report contain?
A management summary, a clear list of findings ranked by severity, evidence, steps to reproduce and practical remediation advice. It should explain what was and was not tested.
Reports full of unexplained tool output are less useful.
↑ Back to ContentsWhat happens during the test?
Testers gather information, look for vulnerabilities, attempt to exploit them and document results. They should follow agreed rules, avoid disruption and tell you immediately about critical issues.
Agree a contact for out-of-hours problems.
↑ Back to ContentsHow should you act on the results?
Fix the highest risks first, assign owners and set deadlines. Some fixes are quick, such as changing a setting, while others need projects.
Retest to confirm that issues are closed. Without that step, you are relying on assumption.
↑ Back to ContentsHow often should you test?
At least annually and after significant changes, such as a new application, a migration or an acquisition. Some customers and regulators expect regular testing.
A test is a snapshot, so combine it with routine updates and monitoring.
↑ Back to ContentsHow is a penetration test different from a vulnerability scan?
A scan is automated and finds known issues. A penetration test involves a person attempting to exploit weaknesses and chain them together. Scans suit regular checks. Penetration tests suit deeper assurance.
Many organisations use both.
↑ Back to ContentsWhy do customers ask for a penetration test?
Larger customers, insurers and frameworks such as Cyber Essentials Plus or ISO 27001 may ask for evidence of testing. A recent report can speed up due diligence.
It also helps you decide where to spend security budget.
↑ Back to ContentsWhat is the difference between black box, grey box and white box testing?
In a black box test, the tester has no inside information and behaves like an outsider. In a grey box test, they receive limited information, such as a user account. In a white box test, they have full access to architecture, documentation and sometimes source code.
Black box shows what an anonymous attacker can see, but it can miss deeper issues within the time available. Grey box is often the best balance for businesses because it reflects what a malicious customer or a compromised user could do. White box finds the most issues per day of effort, which suits critical applications.
↑ Back to ContentsWhat is the difference between internal and external testing?
External testing targets what is visible from the internet: websites, email servers, remote access and cloud services. It answers the question of whether an outsider can get in. Internal testing assumes an attacker already has a foothold, perhaps through phishing, and asks how far they can travel.
Most businesses should start with an external test and add an internal test once the basics are sound. Together they show whether the front door is locked and whether it matters if someone gets past it.
↑ Back to ContentsWhat affects the price of a test in practice?
The main drivers are the number of days of tester time, the seniority of the testers and the complexity of what is tested. A web application with several user roles and many functions needs more time than a small brochure website. A network with many addresses takes longer than one with a handful.
Reporting, retesting and out-of-hours work can add cost. Ask for a quote that separates testing from reporting and retesting, and for a statement of the number of days included, so you can compare providers fairly.
↑ Back to ContentsWhat should you do before you ask for quotes?
Write a one-page brief: what the business does, what you want to protect, which systems you want tested, any compliance driver such as a customer requirement, and your preferred timing. A clear brief produces quotes that can be compared.
Involve your IT support provider early, since they will know what needs permission and how systems are connected. It also helps to decide who will own remediation, because findings with no owner rarely get fixed.
↑ Back to ContentsHow do you read a penetration test report?
Start with the summary and the list of findings by severity. For each finding, look for a description in plain language, evidence, the likely impact on your business and a recommended fix. Be sceptical of findings with no evidence or with severity ratings that are not explained.
Look also for what was not tested. Every report has limits, and an honest report will state them clearly. The scope statement and the testing dates tell you how far to trust the conclusions.
↑ Back to ContentsHow often do findings reappear?
Common repeat findings include weak or reused passwords, missing multi-factor authentication, out-of-date software, exposed administrative interfaces and over-generous permissions. These recur because they are cheap to introduce and easy to forget.
Building routines around them, such as regular patching, access reviews and multi-factor authentication for every external service, reduces the number of issues the next test will find. Our guide to preparing for a penetration test covers the groundwork.
↑ Back to ContentsDoes a penetration test help with compliance and insurance?
Many customers, insurers and frameworks ask for evidence of testing. A recent report from a reputable provider can answer security questionnaires quickly, support a Cyber Essentials Plus or ISO 27001 programme and help during cyber insurance renewals.
It is not a certificate of safety. It shows the state of your systems on particular dates and what you did about the findings, which is what assessors and underwriters want to see.
↑ Back to ContentsWhat should you do if the test finds a critical issue?
Act immediately. Agree beforehand how critical issues will be reported, and who can authorise emergency changes. Typical examples are exposed administrator interfaces, default credentials or unprotected databases.
After the fix, ask the tester to confirm it. Then check whether the same weakness exists elsewhere, because a mistake made once is often repeated across systems.
↑ Back to ContentsHow do you choose between a one-off test and a regular programme?
A one-off test suits a specific event such as a new application or a customer requirement. A regular programme, with annual tests and checks after major changes, suits businesses that change systems often or hold sensitive data.
Ask providers about retesting, discounts for repeat work and continuity of testers. A team that learns your environment finds deeper issues each year. Our penetration testing team can discuss options.
↑ Back to ContentsWhat are the limits of a penetration test?
A test covers what is in scope, during the testing window, with the skills and time available. It cannot prove that no vulnerabilities exist, and new ones appear after the test ends. It also tests technical weaknesses more than human behaviour, unless social engineering is included.
Understanding these limits prevents false comfort. Combine testing with patching, monitoring, staff awareness and incident planning. Our phishing simulator covers the human side.
↑ Back to ContentsHow do testers find weaknesses in web applications?
Testers examine how the application handles input, sessions, permissions and errors. They try to bypass sign-in, access other users’ data, inject commands and manipulate business logic. Many serious issues come from design flaws, not from software bugs.
A grey box approach, with accounts for different user types, finds more in less time. Developers benefit from seeing issues reproduced step by step, which is why evidence in the report matters.
↑ Back to ContentsHow do you choose the right time of year to test?
Avoid peak trading periods, major releases and holidays when staff are away. Test after significant changes to systems rather than before, so that findings reflect the live environment. Leave time for fixes before audits or contract deadlines.
Many businesses test annually, aligned to budget cycles and insurance renewals. Our penetration testing team can help plan a schedule, and we support businesses in Manchester and Salford.
↑ Back to ContentsWhat do testers do with the data they find?
Reputable testers record only what is needed as evidence, store it securely, encrypt it and delete it at the end of the engagement. Ask for their data handling policy and confirm retention periods in the contract.
Ask who will have access to your report and how it is delivered. Our penetration testing team follows a clear confidentiality process.
↑ Back to ContentsHow do you tell if a penetration testing quote is realistic?
A realistic quote states days of effort, the seniority of testers, the scope, the deliverables and retest terms. Very low prices often indicate a scan with a report attached, and very high ones may include unneeded extras.
Ask for a sample report and references. Our penetration testing service provides a clear scope and fixed price.
↑ Back to ContentsHow do you brief the board on test results?
Summarise the number and severity of findings, the business risks, the plan and the timeline for fixes. Show before and after for retests. Avoid jargon, and explain what residual risk remains.
Our penetration testing team provides a management summary for this purpose.
↑ Back to ContentsHow can NetMonkeys help beyond the test itself?
After testing, we can help fix the issues found, update policies and run a phishing simulator campaign to test people as well as systems. Our penetration testing service includes a clear scope and a report written for both management and technical teams.
We support businesses across the UK, including IT support in Leeds, IT support in Birmingham and IT support in Nottingham.
↑ Back to ContentsFrequently Asked Questions (FAQs)
How much does a penetration test cost?
It depends on scope and depth. Request a quote based on a defined scope from a qualified provider.
How often should we run a penetration test?
At least annually and after major changes to systems or applications.
Is a vulnerability scan the same as a penetration test?
No. A scan is automated and finds known issues. A penetration test involves a skilled person attempting to exploit weaknesses.
Will a penetration test disrupt our systems?
Testers take care to avoid disruption, but there is some risk. Agree testing windows and backups first.
What is CREST?
CREST is an accreditation body for penetration testing providers. Accreditation indicates assessed standards and ethics.