~/sang

playground

A relaxed, fictional sandbox. A tiny security bot explores a small lab with a door to each room: a toy software pipeline, a defense line and an incident room. No timer, no score, no tracking. It is not a model of any real company or system.

Game area

CURRENT ROOM

Lab Hub

Choose a room.

3 rooms available

Walk to a glowing door and press Space or Enter.

Move: WASD / arrows · Interact: Space / Enter

The local 3D room loads when this frame comes into view. The station guide is available below.

Touch: press and hold a direction. Keyboard: WASD / arrows to move, Space / Enter to interact.

Room guide, controls and OWASP references

rooms

  1. The Pipeline

    Inspect the sample checks and make a release decision at the gate.

    Available

  2. Defense Line

    Match each threat to a control at the response board, then carry the controls to their gates. One option is a decoy; wrong tries cost nothing. Each threat maps to an OWASP Web Top 10:2025 risk.

    Available

  3. Incident Room

    Gather and order the evidence into a cause chain before choosing a containment change. Clues map to the OWASP Top 10 for LLM Applications 2025.

    Available

defense line

First match each threat to a defense at the response board, then carry a fitting control from its rack to the threat gate. One option is a decoy: hiding record IDs does not replace a server-side access check. Plans can be revised before play; there is no timer or penalty for wrong tries.

0 of 3 threats neutralized · Carrying: nothing

defense options

  1. Access check

    Verify on the server that this user may use this specific record. Deny by default.

  2. Pin and review

    Pin exact dependency versions, review updates and audit them before they ship.

  3. Parameterized queries

    Keep user data separate from query structure and validate input.

  4. Hide record IDs

    Make the URL harder to guess. This can reduce casual guessing, but it does not enforce access.

  1. Unchecked lookup

    A request fetches a record by ID and the server never checks who owns it.

    A01:2025 Broken Access Control (OWASP Top 10 for web applications, 2025).

    Active

  2. Unpinned update

    A build pulls the newest version of a package automatically, with no review.

    A03:2025 Software Supply Chain Failures (OWASP Top 10 for web applications, 2025).

    Active

  3. Raw query

    User text is pasted straight into a database query.

    A05:2025 Injection (OWASP Top 10 for web applications, 2025).

    Active

incident room

The helpful assistant. A fictional support assistant summarized a shared document and then emailed private project notes to an outside address. Gather the evidence, trace the cause to the impact, then choose a containment change.

0 of 3 pieces of evidence found

  1. Retrieved document

    The shared document ends with hidden text telling the assistant to send the private notes to an outside address.

    LLM01:2025 Prompt Injection (OWASP Top 10 for LLM Applications, 2025)

    Not found

  2. Tool permissions

    The assistant was allowed to read private notes and send email to any address, though it only needed to summarize public documents.

    LLM06:2025 Excessive Agency (OWASP Top 10 for LLM Applications, 2025)

    Not found

  3. Sent message

    The outgoing email contained the private notes word for word, and no person reviewed it before it was sent.

    LLM02:2025 Sensitive Information Disclosure (OWASP Top 10 for LLM Applications, 2025)

    Not found

objective

In the Pipeline room, inspect Source, Scan and Dependencies, then hold the release, apply the fictional patch, rerun three checks, review the SBOM and release evidence, and open Release Gate.

0 of 4 checkpoints complete

controls

Focus game area, then W A S D / Arrow keys
Move the bot. The room and station platforms are solid.
Space / Enter
Go through a nearby door or inspect a station. At Release Gate, patch, rerun checks, review the SBOM and release evidence, then open the gate.

stations

  1. Source

    The toy service change is reviewed on a protected branch; required review is recorded.

    Not inspected

  2. Scan

    Static analysis and secret scanning report no critical findings for this sample change.

    Not inspected

  3. Dependencies

    Fictional TinyParse 1.4.0 is pinned, but a local advisory lists a known issue. Apply 1.4.1, rerun checks, review its SBOM relationship, then verify release evidence.

    Not inspected

  4. Release Gate

    The gate stays closed until the patch, rerun checks, SBOM review, and fictional source, builder and artifact evidence review pass.

    Not inspected

guest@sang:~$