What is a pentest and what drives its cost
What a penetration test is, how it differs from an automated scan, why a written mandate is required, what you get at the end and which factors determine the price.
11/16/2026 · 7 min read
A penetration test (pentest) is a security assessment in which a professional tries, in an authorized and controlled way, to do what an attacker would do: find a weak point and see how far it goes. The result is not "the site is secure" or "it is not secure", but a list of concrete problems, in order of severity, with guidance on how to close them.
Pentest, automated scan, surface check
These are three different things, and they are often confused.
- Surface check: looks only at what the site shows to anyone (certificates, headers, public configuration). It does not go inside systems, so it misses what sits "behind".
- Vulnerability scan: an automated tool looks for known flaws. Many false alarms and no understanding of context.
- Pentest: a person tests the system, chains problems together and judges real impact. Takes time, skill and a mandate.
They complement each other: the surface check is the first step, the pentest tells you how dangerous a problem really is.
Why a written mandate is required
Testing a computer system without authorization is a crime, even with good intentions. That is why every serious pentest starts with a written mandate defining:
- what is tested (domains, applications, APIs);
- where and with what limits (what is excluded, which actions are forbidden);
- when (time window, any hours to avoid);
- who is the contact and how urgent issues are escalated.
If someone offers you a test without a mandate, or on systems that are not yours or the client's, it is not a pentest: it is a risk to you.
How it works
- Scope and rules: agree what to test and sign the mandate (and an NDA if needed).
- Information gathering: map what is exposed.
- Testing: look for and try weak points within the authorized scope, avoiding damage or service disruption.
- Report: problems are explained, prioritized and backed by reproducible evidence.
- Debrief: a call to explain the results and decide what to fix first.
- Retest of the fixed points, to verify the issues are really closed.
What you get at the end
A report readable by non-technical people, with: an executive summary, problems by severity, an explanation of impact, recommended fixes, and technical notes attached for those who must act. If the report is incomprehensible, it is of no use to you.
What drives the cost
There is no honest "price list", because the factors vary a lot from case to case. The main ones:
- Scope size: a brochure site is very different from an e-commerce with a customer area, APIs and integrations.
- Application complexity: user roles, payments, file uploads, unusual business logic.
- Level of knowledge granted: an outside-in test with no information, or one with test accounts and documentation.
- Duration and depth required.
- Retest and fix support, if included.
- Urgency.
The right way to proceed is to start from a scope review and get a custom quote, with what is included written down clearly.
How to choose who does it
A few useful questions:
- Do you always work with a written mandate and NDA?
- Is the report understandable and does it include remediation steps?
- Is the retest included or quoted separately?
- Who actually runs the tests? What experience do they have?
- How do you handle data and access you receive during the test?
Our approach
For SMBs it works like this: we start with a surface check of what is already public. If something concrete emerges and you want to go deeper, you sign a short mandate and we run a deeper test on the agreed scope, free in the initial phase. Only afterwards, if you want the problems fixed, do you get a custom quote.
For an example of how it plays out, see the DodoTag case. If you want to know whether it makes sense for your site, book a call.
→ Related case: Pentest and follow-up on the DodoTag platform