← Back to services // Offensive

Web Application Pentest

OWASP, business logic, auth bypass - from login to back-end

€175 /hour CCV certified

We test your web applications and APIs for all known and unknown vulnerabilities. From OWASP Top 10 to complex business logic flaws. Our approach combines automated scanning with in-depth manual testing by experienced pentesters.

What is a web application pentest?

A web application pentest is a security assessment where we attack your web application like a real hacker would. SQL injection, cross-site scripting, broken authorisation, business-logic flaws - we test it all. To demonstrate what can actually go wrong: can an attacker steal data, take over accounts or manipulate payments?

The difference with an automated scan? Tools like Burp Suite, Nuclei and ZAP find known patterns. But the vulnerabilities we most frequently report - IDORs in API endpoints, race conditions in payment flows, JWT abuse, OAuth errors - are often not found by scanners. You only find those through manual work by someone who understands how web applications are built.

OWASP Top 10 and beyond

The OWASP Top 10 is our starting point, not our finish line. We test for injection, broken access control, security misconfiguration, SSRF and all other categories.

Why should you get a web application pentest?

Your web application is directly exposed to the internet. It is the first thing an attacker sees:

  • Prevent data breaches: broken authorisation leads to access to customer data, financial records or medical files.
  • Protect reputation: a hacked web application directly damages client trust.
  • Compliance: ISO 27001, NIS2, PCI-DSS and GDPR require demonstrably secure applications.
  • Early discovery is cheaper: fixing a vulnerability in production costs 10-100x more than during development.

We recommend embedding pentesting into your development cycle. Testing after every major release saves time and money in the long run.

Our approach

Our web application pentests combine methodical manual work with targeted automation:

  1. Scoping - you speak directly with the pentester who will perform the test. Together we determine which components, roles and functionalities are in scope.
  2. Mapping & discovery - mapping all endpoints, parameters, API calls and authentication flows. Burp Suite Professional, but also extensive manual exploration.
  3. Authentication & authorisation - login mechanisms (brute force, credential stuffing, MFA bypass), session management and RBAC. Can a regular user perform admin actions? Can customer A view customer B's data?
  4. Input handling - SQL, NoSQL, LDAP, OS command injection, XSS (reflected, stored, DOM-based), SSRF, XXE, template injection.
  5. Business logic - manual testing of workflows: can a user skip steps, manipulate prices, repeat actions that should be one-time?
  6. Reporting - management summary, technical write-ups with reproduction steps, CVSS scores and priority recommendations. We call you about critical findings - they do not sit in a report for three weeks first.
  7. Retest - after your fixes we can verify whether vulnerabilities have been resolved.

What does a web application pentest cost?

Our hourly rate is €175 per hour. The total investment depends on the size of your application. After a free scoping call you receive a fixed quote.

Methodology

1

Scoping

Inventory of application size, authentication and critical functionality.

2

Recon & Mapping

Mapping all endpoints, parameters and API calls.

3

Vulnerability Assessment

Systematic testing for OWASP Top 10 and application-specific vulnerabilities.

4

Exploitation

Demonstrating impact through controlled exploitation.

5

Reporting & Retest

Prioritised report with proof-of-concept and retest after fixes.

Frequently asked questions

Do you need access to the source code?

Not for a blackbox test. For a whitebox test yes, but we always discuss this in advance.

Can the pentest be performed on my staging environment?

Yes, we actually recommend it. Staging prevents risk to production data. The staging environment does need to be representative in terms of configuration. We help you assess whether that is the case.

Ready to test your security?

Get in touch with our team for a no-obligation conversation about your security challenges.