Home / Cybersecurity / Track 1B: Application Security
Next batch January 2027. 15 seats.
Track 1B: Application Security
Security testing and code review for web applications and APIs. You attack practice apps by hand with Burp Suite and OWASP ZAP, trace each flaw back to the line of code that caused it, and write findings a developer can fix.
- Level
- 2, after the Foundation or equivalent
- Hours
- 20 hours, 7 modules
- Format
- Live online
- Schedule
- 5-day intensive or 5 weekends
- Fee
- On enquiry, team rates available
What you’ll learn
- Plan and scope an application security test, and set up Burp Suite and OWASP ZAP to intercept traffic.
- Find and exploit the OWASP Top 10, including injection, broken authentication and cross-site scripting, by hand and with automated scans.
- Test REST and GraphQL APIs against the OWASP API Security Top 10, including broken object level authorisation.
- Find access control and business logic flaws that scanners miss, such as tampered prices and race conditions.
- Review source code for vulnerabilities by hand, and separate real SAST findings from false positives.
- Test an LLM-powered feature for prompt injection.
- Write each finding with severity, evidence, root cause and a fix, then retest it.
Seven modules, from first request to final report.
Each module ends in a hands-on project. In the capstone, you test a practice application and deliver a full report.
| Module | Focus | Hands-on project | Hours |
|---|---|---|---|
| 0. Method and tools | Scoping a test, intercepting proxies | Set up Burp Suite and ZAP against a practice app | 2 |
| 1. Web vulnerabilities | OWASP Top 10, manual and automated | Exploit injection, XSS and broken authentication | 5 |
| 2. API security | OWASP API Security Top 10 | Find BOLA and mass assignment in crAPI | 4 |
| 3. Access control and logic | Flaws that scanners miss | Price tampering and a race condition | 3 |
| 4. Secure code review | Manual review and SAST triage | Trace a live finding to its line of code | 4 |
| 5. AI features | LLM application risks | Prompt-injection test with Garak | 1 |
| 6. Reporting | Severity, evidence and retesting | Write and retest a finding | 1 |
Lab targets include OWASP Juice Shop, WebGoat, DVWA and crAPI. Want to build security into your team’s pipeline instead? See Track 1A: Secure SDLC.
One finding, start to finish
From the Module 1, 4 and 6 labs. Real commands and real output from a deliberately vulnerable practice app.
-
Attack it
Log in as the admin with the wrong password. The
--turns the rest of the query, including the password check, into a comment.$ curl -X POST http://10.10.20.15:3000/login \ --data-urlencode "email=admin@practice.lab' --" \ --data-urlencode "password=anything" {"status":"ok","user":"admin@practice.lab","role":"admin"} -
Trace it in the code
Review the login handler. Line 18 builds the SQL query by pasting the email and password straight into the string, so input becomes part of the query.
15 def do_POST(self): 16 n = int(self.headers.get("Content-Length", 0)); f = parse_qs(self.rfile.read(n).decode()) 17 email, pw = f.get("email",[""])[0], f.get("password",[""])[0] 18 q = f"SELECT email, role FROM users WHERE email = '{email}' AND password = '{pw}'" # vulnerable on purpose 19 try: row = db.execute(q).fetchone() 20 except Exception as e: row = None 21 self.send_response(200 if row else 401); self.send_header("Content-Type","application/json"); self.end_headers()
-
Recommend the fix
Pass the values to the database separately, so input can never change the query. Write it up with severity, evidence and this change.
--- app.py +++ app.py @@ -17,4 +17,4 @@ email, pw = f.get("email",[""])[0], f.get("password",[""])[0] - q = f"SELECT email, role FROM users WHERE email = '{email}' AND password = '{pw}'" # vulnerable on purpose - try: row = db.execute(q).fetchone() + q = "SELECT email, role FROM users WHERE email = ? AND password = ?" + try: row = db.execute(q, (email, pw)).fetchone() except Exception as e: row = None
-
Retest
Run the same attack against the fixed build. It is refused, and a normal login still works, so the fix closes the hole without breaking the feature.
$ curl -X POST http://10.10.20.15:3001/login \ --data-urlencode "email=admin@practice.lab' --" \ --data-urlencode "password=anything" {"status":"denied"} # injection blocked $ curl -X POST http://10.10.20.15:3001/login \ --data-urlencode "email=priya@practice.lab" \ --data-urlencode "password=priya123" {"status":"ok","user":"priya@practice.lab","role":"learner"} # real login still works
Private batches for QA teams
We run Track 1B privately for QA and development teams, using your own staging applications as practice targets where you allow it. Online or at your office.
How is this different from Track 1A?
Track 1B is about finding flaws in software that already exists, by testing the running app and reviewing its code. Track 1A is about building security into how software is made, so fewer flaws reach testing. Testers and aspiring AppSec engineers usually start with 1B; developers with 1A.
Does this cover mobile apps?
Not in this track. It focuses on web applications and APIs, which is where most mobile apps’ server-side flaws live. Ask us if your team needs mobile testing.
Will I get a certificate?
Yes, a Sophorion certificate of completion with an ID your employer can check on our verification page, plus your capstone report.
Reserve a seat in the January batch.
Tell us your background and we’ll confirm the schedule that suits you.
