Source: c123 × c125 — the OWASP® Agentic Top 10, where Qpoint can watch and act · 2026-10-27 · spec cycles/c123.compliance-frameworks/owasp-agentic-tour-v2.md
Ordered by the customer's concern, not the paper's. Each stop names the risks and numbered mitigations it answers, then walks beats on the live lab pages: Watch what Qpoint sees, Tune it to your organization (staged in the draft, never published by the tour), Drill a simulated violation through your real alert path, and Prove it with the record. The tour floats over the composed mocks; they carry data-qp-id attributes and nothing else.
The route
Stop | Your concern | Answers | Walk it |
|---|---|---|---|
| 0 | Where do my agents get their parts, and where does Qpoint see? Opening | — | |
| 1 | Are the parts my agents load healthy? Supply chain · Strong fit | ASI04 #1 #2 #6 #7 · ASI06 #4 · ASI01 #6 | |
| 2 | What are my MCP servers doing, and on whose terms? MCP servers and their tools · Strong fit | ASI02 #1 #4 #7 #8 · ASI04 #2 · ASI07 #1 #4 | |
| 3 | What can my agents change, and who signs off? Consequential actions · Strong fit | ASI02 #2 #5 · ASI03 #4 · ASI05 #6 · ASI08 #5 · ASI09 #1 | |
| 4 | Do secrets or sensitive data reach a model? Data protection · Strong fit | ASI03 ex.2 · ASI06 #2 · ASI09 #3 · ASI02 #8 | |
| 5 | If something goes bad, can I stop it everywhere, and how far did it reach? Kill switch and blast radius · Strong fit | ASI04 #8 · ASI10 #4 #5 · ASI08 #4 #6 #9 | |
| 6 | What have I got, and what is still mine? Close | — | |
Held for later: a sixth stop, Where do my agents run code, and with what rights? (ASI05). It's a strong fit, but the lab has no endpoint-process view yet. Stops 3–5 carry a Prove beat (2026-10-29); stops 1 and 2 don't yet. All five tours: Tours.
The tour layer, and what the dashboard carries
On the dashboard: IDs, and one mount
A page marks the regions a tour may point at. Nothing else: no tour imports, props or state. A layer component takes the attribute on its root by fallthrough. Rows add a key.
<DataMachine data-qp-id="home.sensitive-data" … />
<section data-qp-id="mcp.policy.approval-verbs"> … </section>
<span data-qp-id="sources.row" :data-qp-key="s.name">{{ s.name }}</span>The layout mounts <TourHost /> once; it's inert until a tour starts. The IDs these tours use, by page: