Engineers Clinic
AdvancedSecurity trackFP-CS-09

Web application penetration test against OWASP Juice Shop

Run a structured penetration test of OWASP Juice Shop, find and prove real vulnerabilities, and write the report a consultancy would send to a paying client.

Cloud, DevOps & SecurityVAPT
5 Guided Steps37h Internship TierSubmit: A penetration test report (PDF or Markdown) with findings, evidence, severity and fixes + a methodology section + the environment setup notesVerified CertificateAI Rubric Graded
Program Overview

Industry project · for Orchard Labs, a security consultancy training a junior tester before putting them on real client work

Orchard Labs puts every new tester through the same exercise before client work: a full penetration test of OWASP Juice Shop, a deliberately vulnerable web application built for training. The point is not to score points in the game; it is to work like a professional tester and produce a report a client would pay for.

You will test Juice Shop running on your own machine, so there is no question of touching a system you do not own. You will work to a scope, map the application, and then test for the common classes of web vulnerability: broken access control, injection, authentication weaknesses, and sensitive data exposure, among others. For each real finding you prove it with clear steps someone else can repeat, rate its severity using a standard method, and write a fix the development team could act on.

The deliverable is the report, because in this job the report is the product. A finding with no reliable steps to reproduce is worthless, and a severity rating with no reasoning is just an opinion. Done looks like at least 8 genuine vulnerabilities across at least 4 classes, each with evidence, a severity rating with its justification, and a concrete remediation. You also write a short methodology section so a reader knows what you did and did not test. Orchard Labs signs off when the report is something they could hand to a client with only light editing, and when a second tester can reproduce every finding from your steps alone.

Web penetration testingVulnerability analysisOWASP Top TenSeverity ratingProof-of-concept writingSecurity reporting
What you submit

A penetration test report (PDF or Markdown) with findings, evidence, severity and fixes + a methodology section + the environment setup notes

Stack: OWASP Juice Shop, An intercepting proxy such as Burp or ZAP, A browser, A note-taking tool for evidence

How it is graded
  • Range of findings25

    At least eight genuine vulnerabilities across at least four OWASP classes are found and confirmed.

  • Reproducible evidence30

    Every finding has clear steps and evidence so a second tester can reproduce it without help.

  • Severity and fixes25

    Each finding has a justified severity rating and a concrete fix a development team could apply.

  • Report quality20

    The report reads as client-ready, with a methodology section and scope, and needs only light editing.

Pass 60% · Merit 75% · Distinction 90%

Learning Outcomes
Test a web app against the OWASP Top Ten
prove a vulnerability with repeatable steps
rate severity with a standard method
write a client-ready security report
Target Audience

Engineering Students

Diploma, B.Tech, B.E., BCA, MCA, or M.Tech students seeking practical experience.

Aspiring Developers

Developers who want to build proof-of-work capstone projects for tech resumes.

Job Seekers

Graduates looking for AI-evaluated code review & verified industry credentials.