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
Move: WASD / arrows · Interact: Space / Enter
The local 3D room loads when this frame comes into view. The station guide is available below.
Dependency alert: fictional TinyParse 1.4.0 has a known issue. Hold this release and update it before shipping. The scripted local checks are a toy scenario, not real scans.
0 of 3 checks passed
- Dependency audit: Not run
- Security scan: Not run
- Regression tests: Not run
Review this fictional software bill of materials (SBOM) excerpt. It lists components and dependency relationships; it does not prove the artifact identity or detect vulnerabilities.
BuildBoard 2.0.0 (application)
└─ FormEngine 3.2.0
└─ TinyParse 1.4.1After the SBOM review, match the reviewed source, trusted builder and artifact digest. This is a fictional evidence exercise, not cryptographic verification.
Before carrying controls into the line, match each threat to a defense. You can revise and retry without penalty.
Arrange the clues from enabling condition to trigger to impact, then check the cause chain.
- Step 1: Sent message
- Step 2: Tool permissions
- Step 3: Retrieved document
Cause chain confirmed. Which change best limits the damage?
Fictional replay outcome: Not run
Each choice runs a scripted local scenario; no model or email service is used.
Containment prevented disclosure. Run these fictional recovery checks; nothing inspects a real system or log.
0 of 3 checks complete
- Not run
Verify public-only access: Confirm the assistant cannot read private notes. - Not run
Review the activity record: Check the fictional access and email events for exposure. - Not run
Test the tool boundaries: Confirm a public summary still works without private-note or email access.
Touch: press and hold a direction. Keyboard: WASD / arrows to move, Space / Enter to interact.
Room guide, controls and OWASP references
rooms
The Pipeline
Inspect the sample checks and make a release decision at the gate.
Available
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
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
Access check
Verify on the server that this user may use this specific record. Deny by default.
Pin and review
Pin exact dependency versions, review updates and audit them before they ship.
Parameterized queries
Keep user data separate from query structure and validate input.
Hide record IDs
Make the URL harder to guess. This can reduce casual guessing, but it does not enforce access.
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
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
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
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
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
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
Source
The toy service change is reviewed on a protected branch; required review is recorded.
Not inspected
Scan
Static analysis and secret scanning report no critical findings for this sample change.
Not inspected
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
Release Gate
The gate stays closed until the patch, rerun checks, SBOM review, and fictional source, builder and artifact evidence review pass.
Not inspected