Customize this training

Get a certificate — $34.29$12

Web Application Penetration Testing with Burp Suite

Web Application Penetration Testing with Burp Suite

Run a lawful web application test: set scope, use Burp Suite, find injection, XSS, access control, SSRF, login and API flaws on lab targets, and write a report that rates risk.

What you will learn

  • Define a lawful scope and rules of engagement, and set up a safe practice lab.
  • Read HTTP requests and responses and explain how cookies, sessions and tokens carry trust.
  • Use Burp Suite proxy, scope, Repeater and Intruder, and map an application’s attack surface.
  • Detect SQL injection and cross-site scripting with minimal proof and explain the fixes.
  • Test for broken access control, SSRF and authentication weaknesses safely.
  • Map and test an API using the OWASP API Security Top 10, including mass assignment.
  • Write a reproducible finding and rate its risk with CVSS v4.0 and business context.

Modules

  1. Legal scope and rules of engagement
  2. HTTP and sessions: what you are really testing
  3. The Burp Suite workflow and reconnaissance
  4. Injection and cross-site scripting
  5. Access control, SSRF and authentication flaws
  6. API testing
  7. Reporting and risk rating

Course facts

Estimated study time
about 60 minutes
Final assessment
42 questions · Pass mark 80%
Available in
English, Français, العربية
Price
Free. Optional verifiable certificate: $19
Last updated
Published by
AMAADOR ACADEMY

Who this course is for

Junior security analysts, developers moving into application security, SOC and IT staff, and career changers preparing for pentester or AppSec roles.

Prerequisites

Basic networking and web knowledge (what HTTP, a cookie and a database query are). A computer where you can install Burp Suite Community and run a lab such as OWASP Juice Shop.

Course content

1. Legal scope and rules of engagement

A web application penetration test is a controlled, authorised attack carried out to find weaknesses before a criminal does. The same actions without permission are a crime. Accessing a computer system without authority is an offence in the UK (Computer Misuse Act 1990), in France (Code pénal, articles 323-1 and following), in Morocco (Law 07-03 on offences relating to automated data processing systems), in the US (Computer Fraud and Abuse Act) and in the Gulf states under their cybercrime laws. "I was only checking" is not a defence.

Your protection is a signed document, written before the first request is sent. It comes from someone who has the power to authorise testing of that system, not only from a friendly contact.

  1. Written authorisation — names the client, the tester or firm, and the dates.
  2. Scope — exact hostnames, URLs, IP ranges, and what is explicitly out of scope.
  3. Rules of engagement (RoE) — allowed techniques, forbidden ones, testing hours, request rate.
  4. Contacts — a 24/7 person to call if something breaks or you find a live breach.
  5. Data handling — what you may store, how it is encrypted, when it is deleted.

2. HTTP and sessions: what you are really testing

Every web test is a conversation of requests and responses. A browser hides it; Burp shows it. You must read it fluently.

A request has a method (GET, POST, PUT, PATCH, DELETE), a path with parameters, headers and sometimes a body (form data, JSON, XML). A response has a status code, headers and a body. Parameters can sit in the URL query, the body, a cookie, a header or inside the path itself, and each one is an input you can change.

StatusMeaningWhat a tester reads
200OKRequest accepted; compare the body length with others
302RedirectWhere does it send you after login or on error?
401 / 403Not authenticated / not allowedDoes the server enforce it, or only the screen?
404Not foundDoes a missing page differ from a forbidden one?
500Server errorYour input broke something; look for stack traces

Useful headers to know: Host, Cookie, Authorization, Content-Type (it tells the server how to parse the body), Origin, Referer and User-Agent. Response headers such as Set-Cookie, Content-Security-Policy, Strict-Transport-Security and Server reveal defences and technology.

3. The Burp Suite workflow and reconnaissance

Burp Suite by PortSwigger is the standard toolkit for web testing. It sits between your browser and the application as an intercepting proxy. The Community edition is free; Professional adds the vulnerability scanner, project saving, the full-speed Intruder and more. Check the current feature list on PortSwigger's site before you buy.

  1. Proxy — Burp listens on 127.0.0.1:8080 by default. Use its built-in browser, or point yours at that address and install Burp's CA certificate so HTTPS can be read.
  2. Target scope — add only the in-scope hosts. Then tell the Proxy to ignore everything else, so you never send a stray request to a third party.
  3. HTTP history — browse the whole application normally while Burp records every request. Turn interception off; look at the history instead.
  4. Repeater — send an interesting request here (Ctrl+R). Change one thing, press Send, read the response. This is where most testing happens.
  5. Notes and Organizer — save the requests that matter, with a comment.
ToolUse it to
ProxyCapture and edit traffic
RepeaterResend and modify one request by hand
DecoderConvert Base64, URL, HTML and hex
ComparerSpot differences between two responses
Collaborator (Pro)Detect out-of-band interactions such as blind SSRF

4. Injection and cross-site scripting

Injection happens when user input is mixed into a command or query and the interpreter treats it as code. In SQL injection (SQLi) the input changes the database query. It sits inside A05 Injection in the OWASP Top 10:2025.

Case: MOVEit Transfer, 2023. Attackers exploited CVE-2023-34362, a SQL injection in Progress Software's file-transfer product, to reach data held by many organisations. The US CISA published advisory AA23-158A about it. Lesson: one injectable parameter in a widely used web application can expose data of hundreds of customers.
  1. Find inputs — every parameter in URL, body, cookie and header that may reach a database (search, filters, sort, IDs, login).
  2. Probe — send a single quote and watch for an error, a changed page or a different response length. Send a quote pair and compare: the error should disappear.
  3. Confirm with logic — add a true condition and a false condition and see two different results. Where nothing is shown, a delay payload (time-based) can confirm it.
  4. Stop early — to prove impact, retrieve the database version or one harmless value. Do not dump customer tables.

5. Access control, SSRF and authentication flaws

Broken access control is ranked first (A01) in the OWASP Top 10:2025. The user is logged in correctly, but the server does not check what that user is allowed to do. It is the most common serious finding in real tests, and scanners find it poorly because they do not know who should see what. You do.

FlawTest
IDOR (insecure direct object reference), also called BOLA in APIsChange /orders/1001 to /orders/1002 with user A's session
Vertical escalationCall an admin URL or action with a normal user token
Horizontal escalationRead or edit another user's profile
Method or parameter tamperingSwitch GET to POST/DELETE, add role=admin to a request
Forced browsingOpen /admin, /backup, /api/v1/users directly
  1. Get two accounts of the same role, plus one admin if available.
  2. Record a request as user A that touches A's object (order, invoice, message).
  3. Replay it in Repeater with user B's session cookie or token, without changing the object ID.
  4. Read the result: if B gets A's data, that is a confirmed finding. 403 or 404 means it is enforced here.
  5. Repeat for every function: view, edit, delete, export.

6. API testing

Modern web apps are a thin screen on top of an API: JSON over HTTP (REST), or a single GraphQL endpoint. The screen shows a few calls; the API often offers many more. Testing the API directly finds what the interface hides.

  1. Capture — browse the app with Burp running and filter the HTTP history for /api/, /v1/ or JSON responses.
  2. Find documentation — try common paths such as /swagger, /openapi.json, /api-docs. A published OpenAPI file lists every endpoint, method and parameter. Burp extensions such as OpenAPI Parser or a Postman import can load it.
  3. Read the JavaScript — front-end bundles contain endpoint paths the menus never use.
  4. List versions and verbs — compare /v2/users with an old /v1/users; test each method (GET, POST, PUT, PATCH, DELETE) on every path.
  5. Check authentication — API key, bearer token or cookie? Is it required on every call?
StyleHow you test it
RESTOne URL per resource; change IDs, methods and JSON fields in Repeater
GraphQLOne endpoint, queries in the body; check whether introspection is on and whether each field enforces access
SOAP / XMLLook at the WSDL; test XML parsing for XXE where allowed

7. Reporting and risk rating

The report is the product. A client cannot fix what they cannot understand or reproduce. Two readers matter: an executive who needs the business risk in one page, and a developer who needs exact steps and a fix.

A good report has five parts:

  1. Executive summary — what was tested, the overall risk, the top three issues in plain language.
  2. Scope and method — hosts, dates, accounts used, tools, limits (for example, "no denial of service").
  3. Findings — one entry each, sorted by severity.
  4. Remediation plan — what to fix first and how.
  5. Appendix — raw evidence, tool output, retest results.

Each finding uses the same template:

FieldWhat to write
TitleSpecific: "IDOR on /invoice allows reading other customers' invoices"
Severity and scoreRating with the method named (CVSS vector or OWASP)
Affected assetExact URL, parameter and method
Description and impactWhat is wrong and what an attacker gains, in business terms
Steps to reproduceNumbered, with the request and response (Burp "Copy as curl" or a screenshot)
RemediationThe fix, for example "check object ownership on the server", plus references (OWASP, CWE)

The full lesson continues in the interactive course on this page.

Sources and references

Educational course. Not affiliated with, endorsed by or sponsored by PortSwigger or the OWASP Foundation; Burp Suite and OWASP are trademarks of their owners. Test only systems you own or are authorised in writing to test, such as PortSwigger Web Security Academy labs or a local OWASP Juice Shop. Unauthorised testing is a criminal offence in most countries. This course is not legal advice.

All courses · Cybersecurity and IT — Free courses, certificate from $7