Every scenario here is synthetic and local: no real target, no real credential, no live network call. Click a row for the full flow, what it touches, and what is redacted or missing shown as pseudocode.
explain help
This page is a searchable index of every rehearsal in the penTell red-team lab: what each one attacks, what defense catches it, and exactly what code and files it touches.
search and filter
Type in the search box to match a scenario's name, source file, or what it proves. Use the category and OWASP chips to narrow the list; click an active chip again to remove it. "clear filters" resets everything.
what each field means
eli5: a plain-English, no-jargon explanation of the scenario.
flow: the real call and decision path, arrow by arrow.
files touched: the actual source files and functions this scenario runs against.
guard reason codes: the exact deny or allow codes this scenario exercises.
missing / redacted, as pseudocode: where the real payload, detector, or fixture is withheld or not connected to a live check, this line names what is missing, in pseudocode, instead of pretending it is fully live.
warning: shown only when a scenario is adjacent to something that could become genuinely dangerous if pointed at a real target. Most scenarios have none, because they are inert by construction.
Standing note: nothing on this page executes anything. Every payload is a synthetic fixture, every target is fake, and every "warning" describes what would make the underlying idea dangerous outside this lab, not an action this page performs.