Cybersecurity

What Is a Penetration Test? Types, Process & Cost Factors

Penetration testing explained in plain language — the main types, how a professional test runs from scoping to re-test, and what drives the price.

A penetration test (or pen-test) is an authorised, simulated attack on your systems. A skilled tester tries to break in the way a real attacker would, then shows you exactly what they found and how to fix it.

It is not the same as running a scanner. Scanners list possible weaknesses; a pen-tester proves which ones are real, how they can be combined, and what an attacker could actually reach.

The main types of penetration test

  • Web application testing — login, sessions, payments, file uploads, business logic and the OWASP Top 10 risks.
  • API testing — the hidden interfaces behind mobile apps and modern websites, often less protected than the website itself.
  • Mobile app testing — Android and iOS apps, how they store data and how they talk to your servers.
  • External network testing — everything your organisation exposes to the internet: firewalls, VPNs, mail servers, remote-access tools.
  • Internal network testing — what an attacker (or a malicious insider) could do once inside your office network.
  • Cloud configuration testing — permissions, storage and services in AWS, Azure or Google Cloud.

Black box, grey box or white box?

  • Black box: the tester starts with almost no information, like an outside attacker.
  • Grey box: the tester gets normal user accounts or some documentation. This is the most common and usually best value.
  • White box: full access to code and architecture for the deepest review.

How a professional test runs

  1. Scoping — agree exactly what is in scope, dates, testing windows and contacts.
  2. Written authorisation — testing without permission is illegal; a signed authorisation protects both sides.
  3. Reconnaissance — mapping the target and its attack surface.
  4. Testing and exploitation — manual testing supported by tools, carefully avoiding disruption.
  5. Reporting — an executive summary and technical findings, each with evidence, risk rating and fix guidance.
  6. Remediation and re-test — you fix, the tester confirms the fixes work.

What drives the cost

Rather than quote a number that may not fit your situation, here is what actually changes the price:

  • Size and complexity — number of pages, user roles, API endpoints or IP addresses.
  • Depth — a quick external check versus a deep grey-box test of payment flows.
  • Environment — testing production out of hours takes more care than a staging copy.
  • Re-testing and reporting needs — for example a report suitable for a bank, investor or enterprise client.

A good provider will give you a fixed quote after a short scoping call, and will tell you if a cheaper vulnerability assessment is enough for your needs right now.

How often should you test?

At least once a year, and after any major release, new payment integration or infrastructure change. Businesses handling card payments or sensitive personal data often test more frequently.

Thinking about a test? Read about our penetration testing service or book a free scoping call.

penetration testingsecurity testingvulnerability assessment