Web for Penetration Testers
Web testing is the assessment of websites and APIs for flaws in their logic and input handling. Testers work with an intercepting proxy such as Burp Suite and follow the OWASP Top 10, looking at injection, broken access control, authentication and session issues. API testing adds checks on object-level authorisation and mass assignment.
Stage: Application Testing · Part of the Penetration Tester roadmap · Last reviewed 19 November 2026
What to learn in Web
- Intercept and modify requests with an intercepting proxy
- Detect and exploit SQL injection using safe proof payloads
- Test for broken access control by changing object identifiers
- Identify stored and reflected cross-site scripting
- Test REST and GraphQL APIs for authorisation and rate limit gaps
Web interview questions
How do you test a web app for IDOR?
An insecure direct object reference occurs when an app uses a user-supplied identifier, such as /orders/1042, without checking the user owns that object. Changing the number exposes another person's data. It is a form of broken object-level authorisation. Swap ids between two test accounts and compare responses.
How do you test for SQL injection safely?
Send a single quote or a boolean condition and compare the response for errors or behaviour changes. Then confirm with a harmless proof, such as a time delay or reading the database version, and avoid modifying or dumping real customer data beyond what is needed.
Where Web fits in the Penetration Tester roadmap
Web belongs to the Application Testing stage (advanced level), which takes about 38 hours. Web and API.
Other units in this stage
Back to the full Penetration Tester roadmap