Web Application Penetration Testing
Authorized, practical testing of your web application against the OWASP Top 10, with evidence and fixes your developers can use.
Overview
Web applications are where business logic, user data and money meet. I test your application the way an attacker would, within an agreed scope and rules of engagement, then explain each finding in plain English and show your team how to fix it. I work as a developer and a tester, so I look at both the exploit and the code path behind it.
Who this is for
This is for teams that own or operate a web application and want an independent security review. It fits SaaS products, business portals, e-commerce sites and custom PHP applications. It is also useful before a launch, after a major release, or when a client or tender asks for evidence of security testing.
What is included
- Scoping and rules of engagement
- Application and content mapping with Burp Suite, Nmap, ffuf and Gobuster
- Testing for injection flaws such as SQL injection and command injection
- XSS, IDOR and broken access control
- Authentication and session flaws
- CSRF, SSRF, file upload and authentication bypass
Deliverables
- Written report with risk ratings, evidence and remediation steps
- Retest of fixed issues, depends on scope
Process
- 01 Scope and rules of engagement
- 02 Map the application
- 03 Test
- 04 Validate findings
- 05 Report with risk rating, evidence and a fix
- 06 Retest, depends on scope
Standards and references
Tools used
About this work.
Yes. I test only systems you own or systems for which you can show written permission from the owner. Testing starts after a signed scope and rules of engagement. I do not test live third-party systems.
Yes. Strict NDA compliance is a default part of how I work. Tell me your requirements in the request form or by email and we can put the agreement in place before discussing sensitive details.
The report contains findings with a risk rating, evidence, the potential impact and clear remediation steps a developer can act on. The scope and any retest are recorded too. A test shows the issues found within the agreed scope and time; it does not prove the application is free of vulnerabilities.
I agree the testing window and off-limits systems before work starts, avoid denial-of-service tests and prefer a staging environment where one is available. Any testing carries risk, which is why scope and rules of engagement come first. No specific outcome or uptime guarantee is promised.
It depends on scope. A focused review and a large multi-role platform are different projects. After I understand the scope, I provide a written plan with the testing or delivery window. I do not promise a fixed timeline before scoping.
I do the work myself. I am early in my penetration testing career, with practice-lab experience, personal development projects and a developer background. I have tested 20+ lab environments and validated SQL injection on 10+ lab endpoints. If something is outside my experience, I will say so rather than take on work I cannot do properly.
Have an application that needs a careful set of eyes?
Tell me what you are building, what worries you and what a good outcome looks like. I will reply with the questions needed to scope it properly.