Start from the request, not from the tools
Open Burp Suite and launch its built-in browser, as the getting-started guide shows. Sign in with a test account in an app you own or in a training lab, capture one HTTP request, change a single number and send it again. If a record that is not yours comes back, you have just found a real access-control bug. You did not need Kali Linux or a hundred tools. You needed to understand the request.
Penetration testing is an authorized test of a real system. The tester tries to do what an attacker could do, then writes up what they found so it can be fixed. In web applications most of the story is one idea: the server believes what arrives in the request, and the attacker writes the request. In your experiment a moment ago, the server believed the number you changed.
The path here covers web applications and APIs, not networks or Active Directory. It uses free resources you can start with today, and each step has a sign that tells you when you are ready for the next, with no promised timeline because people move at different speeds. One rule before anything else: only experiment on an app you own or a lab built for training. Step 5 has the details.
Step 1: understand the web before you break it
Before any vulnerability, learn to read an HTTP request and its response the way you read a sentence. MDN defines HTTP as a protocol for fetching resources such as HTML documents, and describes it as a client-server protocol in which requests are sent by a client, most often a web browser.
In the example below, the first line holds the method, GET, and the path, /api/orders/1042. The Cookie is what tells the server who you are. The response starts with the status code 200, meaning the request succeeded, while 403 means the server refused and 404 means the resource was not found. Change 1042 to 1043 and look: if someone else’s order comes back, the server believed the number you sent and never asked whose order it was.
You then need a modest amount of four things, just enough not to freeze when you meet them: reading JavaScript, understanding JSON and how applications talk to APIs, the basics of SQL, and the Linux command line.
It also helps to build a small app yourself, with a login and two accounts. Someone who has built a permission system by hand knows where people get it wrong.
GET /api/orders/1042 HTTP/1.1
Host: shop.example
Cookie: session=<your session>
HTTP/1.1 200 OK
Content-Type: application/json
{"id":1042,"owner":"you","total":59.00}Step 2: learn Burp Suite as your first tool
Burp Suite from PortSwigger is a suite of tools for web application security testing, and PortSwigger’s Web Security Academy page notes that Community Edition lets you experiment for free. Focus on two tools at first: Proxy, which intercepts HTTP traffic between the browser and the application, and Repeater, which lets you reissue a single request manually after editing it. PortSwigger’s getting-started guide walks through both.
Do not start with automated scanning. Some steps in that guide, such as running your first scan, are marked as Professional-only. More importantly, an automated scan does not teach you why a vulnerability exists. Learn to see the request, change it and understand why the response changed.
Step 3: the PortSwigger labs are your main study
PortSwigger’s Web Security Academy is entirely free, and it includes interactive labs where you test what you have read. You do not need an account to access the content, only to track your progress. It is the free starting point I recommend first.
Start with the classic categories: SQL injection (tampering with database queries), XSS (running script in a victim’s browser), CSRF (making a user’s browser send a request they did not intend) and SSRF (making a server send a request on your behalf), then API testing. Each section explains the vulnerability before the labs, so you do not need to memorise them now. Give extra time to the Access control section, which defines access control as the application of constraints on who or what is authorized to perform actions or access resources. IDOR bugs grow from there: the application believes whatever identifier you send.
A useful rule: do not move to the next lab until you can explain the solution in your own words. If you solved a lab by copying the answer, you have not learned anything yet. Write three lines for every lab. What did the application believe? What did you control? How would it be fixed?
Step 4: the OWASP map, Top 10 for priorities and WSTG for method
The 2025 edition of the OWASP Top 10 puts Broken Access Control first and defines access control as what ensures users cannot act outside their intended permissions. That is why every beginner should master the two-account test: two ordinary accounts, and the first account’s data must never be visible to the second.
The OWASP Web Security Testing Guide, or WSTG, is the method reference. It splits testing into categories such as Authentication, Authorization, Session Management and Input Validation, and each test has an objective and steps. Do not read it cover to cover. Open it when you practise a specific topic.
When you have finished the ready-made labs, try OWASP Juice Shop, an intentionally insecure web application for training, awareness and CTFs, meaning contests where a vulnerability is hidden and you must find a flag that proves you reached it. Its repository and documentation explain how to run it. Hacker101 offers a free class for web security with CTF levels and video lessons, and it is aimed at people interested in bug bounties too.
Step 5: practise only within permission
Penetration testing is authorized work. Do not test a site you do not own or have no written permission to test, even if you are only trying to learn. Practise on labs built for it, on applications you run yourself, and on bug bounty programs within their published scope.
Respecting scope is part of the profession. In professional engagements the scope and rules of engagement are agreed before the first request is sent. Get used to reading the scope before you touch any target.
Step 6: bug bounty, after the foundation is solid
Many people jump to bug bounty on day one because it pays. It is better to arrive able to reproduce access-control bugs in labs without help, because a real target is harder than a lab: its scope is wider, and others have been there before you.
Read the program’s policy and its full scope before sending any request, and write your report so that someone who does not know you can follow it: what are the steps, what is the real impact, what is the proposed fix? A good report matters as much as the vulnerability. I have reported more than 150 security vulnerabilities through different channels, including seven in Facebook and Instagram that Meta acknowledged, and you can see my track record.
I will not promise you income from bug bounty. It varies a great deal, and I do not have a reliable figure to give you.
What about certifications?
While searching you will meet certification names such as eJPT, OSCP and CEH, and you will see many courses built around them. These certifications exist, and each has an issuing body and published requirements. I do not offer a certification track here, and this article does not prepare you for any of those exams. If an employer asks for a specific certification, read its requirements from the issuing body itself.
The stages in one table
The stages in one table, each with a sign that tells you when you are ready for the next.
| Stage | Free resource | Sign you are ready |
|---|---|---|
| Web basics | MDN: Overview of HTTP | You read a request and a response and explain every header in them |
| Burp Suite | Burp Suite Community Edition and PortSwigger’s getting-started guide | You intercept a request, edit it and resend it with Repeater |
| Labs | PortSwigger Web Security Academy | You explain each lab’s solution in your own words without looking at it |
| Method | OWASP Top 10 and OWASP WSTG | You choose tests from the WSTG for an application you run yourself |
| Practice targets | OWASP Juice Shop and Hacker101 | You find a vulnerability without a guided lab |
| Permission | The published scope and rules of a lab or program | You can say in one sentence what you may test and what you may not |
| Bug bounty and reports | A program’s published policy and scope | You write a report with steps, impact and fix that someone else can follow |
When does a mentor help?
If you have reached steps 3 and 4 and want someone to review your work and push you to professional-engagement level, that is where the web application penetration testing course comes in. It is one-to-one live online training, in Arabic or English, with the source code in hand. It covers scoping, reconnaissance and attack-surface mapping, then authentication, access control and multi-tenancy, then injection, browser-side flaws, business logic and APIs, and ends with report writing and retesting.
It is an intermediate course, not for someone starting from zero. It assumes you understand HTTP, have used Burp Suite or Caido and have worked through some PortSwigger labs. The course page itself says that anyone starting from scratch should begin with free resources such as the Web Security Academy, and that the initial assessment shows whether you are ready. That is why this article exists: so you finish the free part first.
The first assessment call (20 minutes) is free. The course is not certification preparation. Write to me through the course page about your level and what you want to be able to do, and I will reply within three days.
Sources
- MDN: Overview of HTTP
- PortSwigger: Getting started with Burp Suite (Community and Professional)
- PortSwigger Web Security Academy
- Web Security Academy: Access control vulnerabilities
- OWASP Top 10:2025, A01 Broken Access Control
- OWASP Web Security Testing Guide (WSTG)
- OWASP Juice Shop
- Hacker101: a free class for web security
Need this checked in your own product?
Web & API penetration testingWant to learn to find vulnerabilities like this yourself?
Web application penetration testing course, one to one