Web application penetration testing
We test your product the way a determined attacker would, logged in as each of your user roles. Every finding is confirmed by hand, and one retest is included.
Mapped to the OWASP Web Security Testing Guide · Report and retest included · Proposal within 1 business day
- Access control
- Authentication and sessions
- Business logic
- Injection and input handling
- Files, uploads and integrations
- Configuration
What this test answers
Most serious web flaws are not found by scanners: one customer reading another’s records, a role that can promote itself, a discount applied twice. Those come from testing the product the way your users and an attacker would use it.
SaaS teams in an enterprise deal
The buyer’s security review asks for a recent independent test of the product they will use.
Teams preparing for an audit
SOC 2 or ISO 27001 evidence that the application was tested and the high findings were fixed.
Products after a major release
New roles, SSO, billing or data exports change what can go wrong.
What we test
The areas below are covered in a typical engagement. The proposal names every host, role and limit in scope.
Access control
Can one customer, role or tenant see or change another one’s data?
Authentication and sessions
Login, SSO, password reset, MFA, tokens and logout.
Business logic
Prices, limits, approvals and workflows used in ways nobody planned.
Injection and input handling
SQL, command, template and cross-site scripting paths.
Files, uploads and integrations
File handling, webhooks and third-party connections.
Configuration
Security headers, TLS, error messages and exposed admin paths.
How the engagement runs
Our full methodScope
We agree assets, roles, environments, limits and the deadline, in writing.
Test
Manual testing guided by the relevant standard, with tools to speed up the search.
Validate
Every finding is confirmed by hand and chained where it leads further.
Report
Executive summary, evidence, severity and fix guidance in one report.
Retest
We verify your fixes and update the report you share with customers and auditors.
What we need from you
- Test accounts
- Two accounts per user role, in two separate tenants where you have them.
- An environment
- Staging with realistic data, or agreed production hours.
- A point of contact
- An engineer who can answer questions during the test.
What you receive
- Executive summary
- Risk in plain language for leadership and your customer’s security team.
- Findings with evidence
- Severity, CVSS score, affected asset, proof and steps to reproduce.
- Fix guidance
- What to change, written for the engineers who will change it.
- Retest report
- An updated report after we verify your fixes.
Questions about web application penetration testing
No. We test the running application with accounts for each role. Code access is optional and helps with complex logic.
We prefer a staging copy with realistic data. Production tests are possible with agreed hours and limits.
Most single applications take one to two weeks of testing. The proposal states the exact days before you commit.
The report follows the structure security reviewers expect. Tell us who will read it, and we will match their questionnaire.
Related reading
How to scope a web application penetration test
The decisions that set the quality of a test before it starts: roles, tenants, environments and limits.
Your enterprise customer asked for a pentest report
What security reviewers look for, what to send, and how to get a test scheduled before the deal stalls.
Get a proposal for web application penetration testing.
You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.