{
  "schema": "owasp-browser-security-missions/v1",
  "version": 1,
  "missions": [
    {
      "id": "support-widget",
      "title": "Third-Party Support Widget",
      "summary": "Review a browser support feature that combines cross-window messaging, DOM rendering and a loaded client dependency.",
      "story": "A support widget receives browser messages and displays replies inside an authenticated application page. Compare the deployed behavior with a repaired implementation.",
      "category": "Browser trust boundaries",
      "engines": ["SCA", "SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/support-widget/",
      "dependency": {
        "name": "jQuery",
        "license": "MIT",
        "reviewVersion": "3.4.1",
        "repairedVersion": "3.7.1"
      },
      "targets": {
        "review": {
          "id": "support-widget-vulnerable",
          "title": "Support widget review route",
          "route": "./targets/support-widget/vulnerable/",
          "displayRoute": "/targets/support-widget/vulnerable/",
          "source": "./targets/support-widget/vulnerable/widget.js",
          "visibleBehavior": "The prepared strong element is interpreted and rendered as markup."
        },
        "repaired": {
          "id": "support-widget-fixed",
          "title": "Support widget repaired route",
          "route": "./targets/support-widget/fixed/",
          "displayRoute": "/targets/support-widget/fixed/",
          "source": "./targets/support-widget/fixed/widget.js",
          "visibleBehavior": "The same markup-shaped value is displayed literally as text."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Discover the trust boundary",
          "summary": "Inspect the deployed widget and identify the browser behavior that deserves investigation.",
          "instructions": [
            "Open the review target and inspect its loaded dependency and widget source.",
            "Compare the browser-message input with the operation that updates the conversation preview.",
            "Choose the observation that best describes the security boundary."
          ],
          "concepts": ["loaded dependency", "browser message", "HTML rendering"],
          "hint": "Follow data from the message event into the conversation preview and note the loaded library version.",
          "demoCue": "Show that code, runtime behavior and the loaded dependency are three views of one browser feature.",
          "completion": {
            "type": "choice",
            "prompt": "Which observation should be investigated?",
            "options": [
              { "value": "message-html", "label": "Browser-message content is interpreted as HTML by an older dependency." },
              { "value": "button-style", "label": "The support button uses a strong visual style." },
              { "value": "local-route", "label": "The page and widget share the same route origin." }
            ],
            "answer": "message-html"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the browser behavior",
          "summary": "Trigger one harmless prepared browser message and collect deterministic visible evidence.",
          "instructions": [
            "Open the review target in a separate tab.",
            "Press Send support reply and observe whether the prepared strong element becomes DOM markup.",
            "Enter the evidence token shown by the target."
          ],
          "concepts": ["runtime source", "DOM sink", "visible evidence"],
          "hint": "The token appears only after the target finds the prepared marker inside the rendered support thread.",
          "demoCue": "Run the same button action while IAST is active, then correlate the visible marker with runtime evidence.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "WIDGET-MESSAGE-RENDERED"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate the repair",
          "summary": "Repeat the feature on the repaired route and verify that functionality remains without HTML interpretation.",
          "instructions": [
            "Open the repaired target and repeat Send support reply.",
            "Confirm that the markup-shaped content is displayed literally.",
            "Inspect the strict origin, payload-type and text-rendering controls, then enter the remediation token."
          ],
          "concepts": ["exact origin", "payload type", "text rendering", "dependency upgrade"],
          "hint": "The repaired route keeps the same user action but validates the message and writes text rather than HTML.",
          "demoCue": "Compare the dependency versions and the two source files, then show that the safe route preserves the feature.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "WIDGET-SAFE-RENDER"
          }
        }
      ]
    },
    {
      "id": "deployment-response-boundary",
      "title": "Deployment Response Boundary",
      "summary": "Compare two visually identical deployments whose security difference exists only in browser-observed response metadata.",
      "story": "An account console looks identical in review and repaired deployments. One response discloses its server technology while the repaired response preserves the same page and security baseline without the disclosure.",
      "category": "HTTP response evidence",
      "engines": ["DAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/deployment-response-boundary/",
      "evidenceSummary": "Paired HTTP response control",
      "targets": {
        "review": {
          "id": "deployment-response-disclosure",
          "title": "Deployment response with metadata disclosure",
          "route": "./passive/cases/headers/powered-by.html",
          "displayRoute": "/passive/cases/headers/powered-by.html",
          "source": "./passive/header_disclosure_canary.html",
          "runtime": {
            "kind": "route-aware-server",
            "protocol": "https",
            "port": 3443
          },
          "visibleBehavior": "The page matches the repaired control, but inspecting its response reveals a technology disclosure header."
        },
        "repaired": {
          "id": "deployment-response-control",
          "title": "Deployment response without metadata disclosure",
          "route": "./passive/cases/headers/secure-control.html",
          "displayRoute": "/passive/cases/headers/secure-control.html",
          "source": "./passive/header_disclosure_canary.html",
          "runtime": {
            "kind": "route-aware-server",
            "protocol": "https",
            "port": 3443
          },
          "visibleBehavior": "The same page and security baseline are returned without the technology disclosure header."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Look beyond the rendered page",
          "summary": "Identify why identical page content does not imply identical security posture.",
          "instructions": [
            "Start the route-aware server and open both deployment targets.",
            "Confirm that their rendered content is identical.",
            "Choose the browser evidence that must be compared."
          ],
          "concepts": ["response headers", "passive analysis", "paired control"],
          "hint": "The meaningful difference travels with the HTTP response rather than appearing in the DOM.",
          "demoCue": "Show both identical pages first, then move to the browser-observed response metadata to explain why source-only inspection is incomplete.",
          "completion": {
            "type": "choice",
            "prompt": "Which evidence distinguishes the deployments?",
            "options": [
              { "value": "response-metadata", "label": "Their HTTP response metadata." },
              { "value": "page-heading", "label": "Their visible page headings." },
              { "value": "button-style", "label": "Their button presentation." }
            ],
            "answer": "response-metadata"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the disclosure",
          "summary": "Inspect the review response and collect deterministic evidence from the browser.",
          "instructions": [
            "Open the review target through the route-aware server.",
            "Press Inspect response metadata.",
            "Enter the evidence token displayed by the target."
          ],
          "concepts": ["technology disclosure", "HTTP response", "browser traffic"],
          "hint": "The review response contains one additional technology-identifying header.",
          "demoCue": "Run passive DAST while loading the route, then correlate the finding with the target's harmless response-inspection proof.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "RESPONSE-METADATA-DISCLOSED"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate the repaired response",
          "summary": "Verify that the disclosure is gone without changing page behavior or the secure header baseline.",
          "instructions": [
            "Open the repaired target through the route-aware server.",
            "Press Inspect response metadata and confirm the disclosure header is absent.",
            "Enter the repaired evidence token."
          ],
          "concepts": ["negative oracle", "same body", "header minimisation"],
          "hint": "The paired response keeps the same body and security headers while removing only the technology disclosure.",
          "demoCue": "Use the repaired route as a negative oracle: identical functionality, same secure baseline and no disclosure finding.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "RESPONSE-METADATA-CLEAN"
          }
        }
      ]
    },
    {
      "id": "session-bound-order-search",
      "title": "Session-Bound Order Search",
      "summary": "Capture and test a same-origin POST request that only exists after the browser establishes scoped session state.",
      "story": "An account console searches the current user's orders through a form-encoded POST request. The browser establishes the session and request context; the review API exposes a database error under malformed input while the repaired API preserves the workflow safely.",
      "category": "Authenticated browser traffic",
      "engines": ["DAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/session-bound-order-search/",
      "evidenceSummary": "Session-bound POST request",
      "productPreview": {
        "label": "PTK Pro",
        "availability": "coming-soon",
        "status": "in-progress",
        "engines": ["DAST"],
        "summary": "Additional active browser-request coverage is being developed for a future release."
      },
      "targets": {
        "review": {
          "id": "session-order-search-review",
          "title": "Order search review workflow",
          "route": "./targets/session-bound-order-search/vulnerable/",
          "displayRoute": "/targets/session-bound-order-search/vulnerable/",
          "source": "./targets/session-bound-order-search/order-search.js",
          "runtime": {
            "kind": "route-aware-server",
            "protocol": "https",
            "port": 3443
          },
          "request": {
            "method": "POST",
            "route": "/targets/session-bound-order-search/vulnerable/api/search",
            "contentType": "application/x-www-form-urlencoded",
            "parameterNames": ["query"],
            "setup": "Open the review page to establish its scoped session and submit the search form."
          },
          "visibleBehavior": "A normal order search succeeds; the harmless prepared diagnostic exposes a database-query error."
        },
        "repaired": {
          "id": "session-order-search-control",
          "title": "Order search repaired workflow",
          "route": "./targets/session-bound-order-search/fixed/",
          "displayRoute": "/targets/session-bound-order-search/fixed/",
          "source": "./targets/session-bound-order-search/order-search.js",
          "runtime": {
            "kind": "route-aware-server",
            "protocol": "https",
            "port": 3443
          },
          "request": {
            "method": "POST",
            "route": "/targets/session-bound-order-search/fixed/api/search",
            "contentType": "application/x-www-form-urlencoded",
            "parameterNames": ["query"],
            "setup": "Open the repaired page to establish its scoped session and submit the same search form."
          },
          "visibleBehavior": "The same normal and diagnostic searches complete without exposing a database-query error."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Capture the real browser request",
          "summary": "Identify the request context that a URL-only scanner would not possess.",
          "instructions": [
            "Open the review workflow through the route-aware server.",
            "Submit the normal order search and inspect the browser request.",
            "Choose the evidence needed to replay the same operation."
          ],
          "concepts": ["session cookie", "POST body", "same-origin request context"],
          "hint": "The API is not a useful standalone URL: the page establishes a scoped session and creates the form-encoded request.",
          "demoCue": "Start DAST before submitting the normal form and show how browser traffic provides the method, body, session and request context together.",
          "completion": {
            "type": "choice",
            "prompt": "What makes this request replayable?",
            "options": [
              { "value": "browser-request-context", "label": "Its captured method, body and scoped browser session." },
              { "value": "api-path-only", "label": "The API pathname by itself." },
              { "value": "page-title", "label": "The visible account-console title." }
            ],
            "answer": "browser-request-context"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the server-side weakness",
          "summary": "Use the prepared diagnostic to expose a deterministic database error inside the scoped session.",
          "instructions": [
            "Open the review workflow and first submit the normal search.",
            "Press Run prepared diagnostic.",
            "Enter the evidence token displayed by the target."
          ],
          "concepts": ["active request mutation", "server response", "database error"],
          "hint": "The prepared input changes only the query value while preserving the captured request context.",
          "demoCue": "Correlate the active DAST finding with the review API's deterministic error response without exposing or changing private scanner payloads.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "ORDER-SEARCH-DATABASE-ERROR"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate the repaired query path",
          "summary": "Repeat the identical browser workflow and confirm that malformed data is handled without a database error.",
          "instructions": [
            "Open the repaired workflow and submit the normal search.",
            "Run the same prepared diagnostic.",
            "Enter the repaired evidence token."
          ],
          "concepts": ["paired API control", "same request shape", "safe query handling"],
          "hint": "The repaired route keeps the same page, session, method, headers and body shape; only server-side query handling changes.",
          "demoCue": "Use the repaired route as a negative oracle and verify that active DAST does not inherit the review finding.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "ORDER-SEARCH-SAFE"
          }
        }
      ]
    },
    {
      "id": "on-demand-analytics",
      "title": "On-Demand Analytics",
      "summary": "Observe a client dependency that does not exist in initial page traffic and appears only after a browser action opens an application feature.",
      "story": "An account page keeps its analytics workspace dormant until the user opens it. That action loads a same-origin client dependency; compare the deployed version with the reviewed replacement while preserving the same feature.",
      "category": "Action-loaded dependencies",
      "engines": ["SCA"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/on-demand-analytics/",
      "dependency": {
        "name": "jQuery",
        "license": "MIT",
        "reviewVersion": "3.4.1",
        "repairedVersion": "3.7.1"
      },
      "evidenceSummary": "Dependency request after browser action",
      "targets": {
        "review": {
          "id": "on-demand-analytics-review",
          "title": "Analytics workspace review route",
          "route": "./targets/on-demand-analytics/vulnerable/",
          "displayRoute": "/targets/on-demand-analytics/vulnerable/",
          "source": "./targets/on-demand-analytics/analytics-loader.js",
          "visibleBehavior": "The initial page is dependency-free; opening the workspace requests and runs the pinned review dependency."
        },
        "repaired": {
          "id": "on-demand-analytics-control",
          "title": "Analytics workspace repaired route",
          "route": "./targets/on-demand-analytics/fixed/",
          "displayRoute": "/targets/on-demand-analytics/fixed/",
          "source": "./targets/on-demand-analytics/analytics-loader.js",
          "visibleBehavior": "The same action and analytics result are preserved while the browser loads the reviewed dependency version."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Observe the initial dependency boundary",
          "summary": "Establish why a page-load-only inventory misses part of this application's browser attack surface.",
          "instructions": [
            "Open the review target without pressing its workspace button.",
            "Inspect the initial browser traffic and confirm that the analytics dependency has not been requested.",
            "Choose the action needed to observe the complete client dependency set."
          ],
          "concepts": ["dynamic dependency", "browser action", "initial traffic"],
          "hint": "The analytics feature is dormant until the application user opens its workspace.",
          "demoCue": "Start with the quiet initial page and show why package files present in browser traffic can depend on a real user journey.",
          "completion": {
            "type": "choice",
            "prompt": "What reveals the additional dependency?",
            "options": [
              { "value": "open-workspace", "label": "Open the analytics workspace and observe the new script request." },
              { "value": "reload-only", "label": "Reload the untouched page repeatedly." },
              { "value": "read-title", "label": "Read the visible page title." }
            ],
            "answer": "open-workspace"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the action-loaded component",
          "summary": "Load the review workspace and collect deterministic evidence that its dependency executed.",
          "instructions": [
            "Start composition analysis before triggering the feature.",
            "Press Open analytics workspace and observe the new same-origin dependency request.",
            "Enter the evidence token displayed after the analytics summary renders."
          ],
          "concepts": ["loaded component", "runtime traffic", "component version"],
          "hint": "The evidence token appears only after the requested dependency executes and updates the workspace.",
          "demoCue": "Correlate the new script request and loaded component finding with the visible analytics result, without relying on a static package manifest.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "ANALYTICS-DEPENDENCY-LOADED"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate the reviewed replacement",
          "summary": "Repeat the same browser journey and verify that the feature works with the reviewed dependency.",
          "instructions": [
            "Open the repaired target with a new composition-analysis session.",
            "Press Open analytics workspace and confirm that the same summary is rendered.",
            "Enter the repaired evidence token and compare the loaded component versions."
          ],
          "concepts": ["dependency upgrade", "paired control", "feature preservation"],
          "hint": "The repaired target changes the dependency version, not the user action or analytics output.",
          "demoCue": "Use the repaired route as a negative advisory oracle while showing that the browser feature remains intact.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "ANALYTICS-DEPENDENCY-REVIEWED"
          }
        }
      ]
    },
    {
      "id": "saved-workspace",
      "title": "Saved Workspace",
      "summary": "Follow user-controlled browser state from a settings page into a separate same-origin dashboard document.",
      "story": "A team member saves a dashboard announcement in workspace settings. A child dashboard route restores that origin-scoped state; compare markup interpretation with a repaired text-rendering path while preserving the two-document workflow.",
      "category": "Persistent browser state",
      "engines": ["SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/saved-workspace/",
      "evidenceSummary": "Local storage across navigation",
      "productPreview": {
        "label": "PTK Pro",
        "availability": "coming-soon",
        "status": "validated",
        "engines": ["SAST"],
        "summary": "Additional advanced analysis for persistent browser state has completed initial validation for a future release."
      },
      "targets": {
        "review": {
          "id": "saved-workspace-review",
          "title": "Saved workspace review journey",
          "route": "./targets/saved-workspace/vulnerable/",
          "displayRoute": "/targets/saved-workspace/vulnerable/",
          "source": "./targets/saved-workspace/vulnerable/dashboard.js",
          "journey": {
            "summary": "Save the prepared announcement and follow the same-origin dashboard navigation.",
            "entrySelector": "#save-announcement",
            "childRoute": "/targets/saved-workspace/vulnerable/dashboard.html",
            "childReadySelector": "#announcement-status"
          },
          "visibleBehavior": "The settings page persists a harmless markup-shaped value; the child dashboard restores it as DOM markup."
        },
        "repaired": {
          "id": "saved-workspace-control",
          "title": "Saved workspace repaired journey",
          "route": "./targets/saved-workspace/fixed/",
          "displayRoute": "/targets/saved-workspace/fixed/",
          "source": "./targets/saved-workspace/fixed/dashboard.js",
          "journey": {
            "summary": "Save the same prepared announcement and follow the same-origin dashboard navigation.",
            "entrySelector": "#save-announcement",
            "childRoute": "/targets/saved-workspace/fixed/dashboard.html",
            "childReadySelector": "#announcement-status"
          },
          "visibleBehavior": "The same state and navigation are preserved while the child dashboard restores the value as literal text."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Discover the cross-document source",
          "summary": "Identify the browser state that survives navigation and becomes input to a new document.",
          "instructions": [
            "Open the review setup route and inspect the save action.",
            "Follow the prepared announcement from the settings form into origin-scoped storage and the child dashboard.",
            "Choose the evidence boundary that connects the two documents."
          ],
          "concepts": ["local storage", "same-origin navigation", "new document"],
          "hint": "The dashboard does not receive the announcement in its URL or response body; it reads state left by the previous document.",
          "demoCue": "Show the clean dashboard URL first, then trace the saved value across navigation to explain why browser state matters.",
          "completion": {
            "type": "choice",
            "prompt": "What connects the settings page to the dashboard sink?",
            "options": [
              { "value": "origin-storage", "label": "Origin-scoped browser storage restored by the child document." },
              { "value": "dashboard-url", "label": "A value embedded in the dashboard URL." },
              { "value": "server-header", "label": "A response header sent by the dashboard server." }
            ],
            "answer": "origin-storage"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the persisted rendering path",
          "summary": "Save the prepared value, follow the child navigation and observe how the new document renders it.",
          "instructions": [
            "Start runtime analysis on the review setup route.",
            "Press Save and open dashboard, allowing the browser to navigate to the child route.",
            "Enter the evidence token displayed after the dashboard restores the saved value."
          ],
          "concepts": ["persistent source", "HTML sink", "child navigation"],
          "hint": "The token appears when the restored strong element exists in the child dashboard DOM.",
          "demoCue": "Correlate the visible element with static source evidence and the runtime storage-to-DOM flow across navigation.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "SAVED-WORKSPACE-MARKUP-RENDERED"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate safe restoration",
          "summary": "Repeat the same two-document journey and verify that the saved value remains literal text.",
          "instructions": [
            "Open the repaired setup route and keep the prepared announcement unchanged.",
            "Save it and follow the same child-dashboard navigation.",
            "Confirm that the markup-shaped value is displayed literally, then enter the repaired token."
          ],
          "concepts": ["text rendering", "paired journey", "negative oracle"],
          "hint": "The storage mechanism and navigation are unchanged; only the dashboard's DOM write is repaired.",
          "demoCue": "Compare the two small dashboard sources and show that the application workflow remains intact without markup interpretation.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "SAVED-WORKSPACE-TEXT-SAFE"
          }
        }
      ]
    },
    {
      "id": "live-profile-preview",
      "title": "Live Profile Preview",
      "summary": "Follow a same-origin JSON response field into a DOM rendering path that exists only after a browser action.",
      "story": "An account page keeps profile data out of initial traffic until a user opens its live preview. Compare the deployed response-to-DOM path with a repaired text-rendering path while preserving the endpoint, response and browser action.",
      "category": "Action-loaded response data",
      "engines": ["SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/live-profile-preview/",
      "evidenceSummary": "JSON response after browser action",
      "targets": {
        "review": {
          "id": "live-profile-preview-review",
          "title": "Live profile review target",
          "route": "./targets/live-profile-preview/vulnerable/",
          "displayRoute": "/targets/live-profile-preview/vulnerable/",
          "source": "./targets/live-profile-preview/vulnerable/profile-preview.js",
          "action": {
            "summary": "Press Open live profile preview and wait for the response status.",
            "triggerSelector": "#load-profile",
            "readySelector": "#profile-status"
          },
          "visibleBehavior": "The initial page has no profile traffic; the action loads a JSON field and interprets its harmless markup in the preview."
        },
        "repaired": {
          "id": "live-profile-preview-control",
          "title": "Live profile repaired control",
          "route": "./targets/live-profile-preview/fixed/",
          "displayRoute": "/targets/live-profile-preview/fixed/",
          "source": "./targets/live-profile-preview/fixed/profile-preview.js",
          "action": {
            "summary": "Press the same preview button and wait for the response status.",
            "triggerSelector": "#load-profile",
            "readySelector": "#profile-status"
          },
          "visibleBehavior": "The same action and JSON response are preserved while its markup-shaped field is displayed as literal text."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Discover the response boundary",
          "summary": "Identify why initial page traffic and a standalone source file do not prove the complete browser flow.",
          "instructions": [
            "Open the review target without pressing its preview button.",
            "Confirm that the profile JSON has not been requested, then inspect the button's response-to-rendering path.",
            "Choose the browser evidence needed to connect the API field to the visible preview."
          ],
          "concepts": ["browser action", "JSON response", "DOM rendering"],
          "hint": "The response exists only after the feature is opened, and the important value is one field inside its parsed JSON body.",
          "demoCue": "Begin with an empty network view, then open the feature to correlate new browser traffic, source and runtime evidence.",
          "completion": {
            "type": "choice",
            "prompt": "What proves the complete data path?",
            "options": [
              { "value": "action-response-render", "label": "The browser action, parsed response field and resulting DOM write." },
              { "value": "page-title", "label": "The account page title by itself." },
              { "value": "endpoint-name", "label": "The JSON pathname without executing the feature." }
            ],
            "answer": "action-response-render"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove response-field reachability",
          "summary": "Open the review preview and collect deterministic evidence that the response field became DOM markup.",
          "instructions": [
            "Start static and runtime analysis on the review target.",
            "Press Open live profile preview and observe the same-origin JSON request.",
            "Enter the evidence token shown after the prepared marker becomes a DOM element."
          ],
          "concepts": ["response field", "runtime reachability", "HTML sink"],
          "hint": "The token appears only when the marker from the parsed JSON field exists as an element in the preview.",
          "demoCue": "Correlate the visible marker with the exact response field and sink instead of treating every response or DOM write as equivalent.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "PROFILE-RESPONSE-MARKUP-RENDERED"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate text-only rendering",
          "summary": "Repeat the same action and response while confirming that the response field remains literal text.",
          "instructions": [
            "Open the repaired target and press the same profile-preview button.",
            "Confirm that it requests the same JSON document and displays the same response bytes as text.",
            "Enter the repaired evidence token."
          ],
          "concepts": ["paired response", "text rendering", "negative oracle"],
          "hint": "The endpoint, JSON field and browser action are unchanged; only the final DOM write differs.",
          "demoCue": "Compare the two small scripts and prove that the user flow survives without interpreting the response field as markup.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "PROFILE-RESPONSE-TEXT-SAFE"
          }
        }
      ]
    },
    {
      "id": "transient-route-notice",
      "title": "Transient Route Notice",
      "summary": "Observe a short-lived SPA deep-link value that reaches the DOM after an in-document hash-route change.",
      "story": "An incident workspace accepts a notice through its client-side route and removes it almost immediately. Compare a transient markup-rendering path with an allow-listed text-only repair while preserving the same action, route parameter and expiry boundary.",
      "category": "Transient SPA route state",
      "engines": ["DAST", "SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/transient-route-notice/",
      "evidenceSummary": "Short-lived hash-query rendering",
      "targets": {
        "review": {
          "id": "transient-route-notice-review",
          "title": "Transient route notice review target",
          "route": "./targets/transient-route-notice/vulnerable/",
          "displayRoute": "/targets/transient-route-notice/vulnerable/",
          "source": "./targets/transient-route-notice/vulnerable/route-notice.js",
          "action": {
            "summary": "Press Open prepared route notice and scan the resulting hash-query route.",
            "triggerSelector": "#open-route-notice",
            "readySelector": "#route-status"
          },
          "visibleBehavior": "The action changes only the fragment route; its harmless notice becomes markup for 30 ms before expiring."
        },
        "repaired": {
          "id": "transient-route-notice-control",
          "title": "Transient route notice repaired control",
          "route": "./targets/transient-route-notice/fixed/",
          "displayRoute": "/targets/transient-route-notice/fixed/",
          "source": "./targets/transient-route-notice/fixed/route-notice.js",
          "action": {
            "summary": "Press the same button and scan the resulting hash-query route.",
            "triggerSelector": "#open-route-notice",
            "readySelector": "#route-status"
          },
          "visibleBehavior": "The same known route value maps to constant text for 30 ms; unknown values are rejected without reflection."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Discover the in-document route boundary",
          "summary": "Identify why an initial response or persistent DOM snapshot can miss the important browser behavior.",
          "instructions": [
            "Open the review target and confirm that its initial URL has no route notice.",
            "Press Open prepared route notice and observe the hash-query change without a document reload.",
            "Choose the evidence needed to understand the short-lived rendering path."
          ],
          "concepts": ["SPA route", "hash query", "transient DOM"],
          "hint": "The response document does not change; the browser route and DOM change briefly inside the existing page.",
          "demoCue": "Keep the network and DOM views visible to show that a real browser sees an application transition that a response-only scanner can miss.",
          "completion": {
            "type": "choice",
            "prompt": "What reveals the complete behavior?",
            "options": [
              { "value": "route-mutation-observation", "label": "The hash-route mutation and DOM changes observed during the live page transition." },
              { "value": "initial-response-only", "label": "Only the initial HTML response body." },
              { "value": "expired-snapshot", "label": "A DOM snapshot taken after the notice has expired." }
            ],
            "answer": "route-mutation-observation"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the transient route flow",
          "summary": "Trigger the deep link and collect evidence while the route-controlled markup exists only briefly.",
          "instructions": [
            "Start browser traffic, static and runtime analysis on the review target.",
            "Press Open prepared route notice and scan the resulting hash-query parameter.",
            "Enter the persistent evidence token after the visible notice has expired."
          ],
          "concepts": ["active route mutation", "runtime source", "HTML sink"],
          "hint": "The notice itself lasts 30 ms, but the proof token records that the prepared marker became an element.",
          "demoCue": "Correlate the SPA attack, static source-to-sink path and runtime hash-query flow around one browser action.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "ROUTE-NOTICE-TRANSIENT-MARKUP"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate allow-listed text rendering",
          "summary": "Repeat the same route action and expiry while verifying that arbitrary values are not reflected.",
          "instructions": [
            "Open the repaired target and press the same route-notice button.",
            "Confirm that the known value displays as text and an unexpected route value is rejected.",
            "Enter the repaired evidence token."
          ],
          "concepts": ["allow-list", "text rendering", "negative oracle"],
          "hint": "The action, parameter and 30 ms expiry are unchanged; the application maps one accepted value to constant text.",
          "demoCue": "Show that the repair preserves the normal SPA workflow while providing a clean active and runtime control.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "ROUTE-NOTICE-TEXT-SAFE"
          }
        }
      ]
    },
    {
      "id": "imported-request-preferences",
      "title": "Imported Request Preferences",
      "summary": "Trace a user-imported client configuration into an inherited browser request option, then compare an own-property allow-list repair.",
      "story": "An account preview imports a small JSON preferences document before loading a same-origin resource. Compare an unsafe object merge that creates an inherited request option with a null-prototype allow-list that preserves the same user action and request.",
      "category": "Client configuration integrity",
      "engines": ["SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/imported-request-preferences/",
      "evidenceSummary": "Imported data changes inherited request options",
      "productPreview": {
        "label": "PTK Pro",
        "availability": "coming-soon",
        "status": "validated",
        "engines": ["SAST"],
        "summary": "Additional advanced analysis for imported client configuration has completed initial validation for a future release."
      },
      "targets": {
        "review": {
          "id": "imported-request-preferences-review",
          "title": "Imported preferences review target",
          "route": "./targets/imported-request-preferences/vulnerable/",
          "displayRoute": "/targets/imported-request-preferences/vulnerable/",
          "source": "./targets/imported-request-preferences/vulnerable/request-preferences.js",
          "action": {
            "summary": "Press Import and load preview, then inspect the request-options evidence.",
            "triggerSelector": "#import-preferences",
            "readySelector": "#preferences-status"
          },
          "visibleBehavior": "The imported document leaves the request object with no own credentials key, but its inherited value changes the same-origin preview request."
        },
        "repaired": {
          "id": "imported-request-preferences-control",
          "title": "Imported preferences repaired control",
          "route": "./targets/imported-request-preferences/fixed/",
          "displayRoute": "/targets/imported-request-preferences/fixed/",
          "source": "./targets/imported-request-preferences/fixed/request-preferences.js",
          "action": {
            "summary": "Press the same import button and inspect the repaired request-options evidence.",
            "triggerSelector": "#import-preferences",
            "readySelector": "#preferences-status"
          },
          "visibleBehavior": "The same input and preview request use a null-prototype object containing only an accepted own credentials option."
        }
      },
      "objectives": [
        {
          "id": "discover",
          "number": 1,
          "title": "Discover the configuration boundary",
          "summary": "Identify how a harmless-looking imported object can change request behavior without adding an own option key.",
          "instructions": [
            "Open the review target and inspect the prepared JSON before importing it.",
            "Follow the parsed object through the merge and into the preview request options.",
            "Choose the browser evidence that reveals the complete behavior."
          ],
          "concepts": ["JSON input", "object merge", "inherited property"],
          "hint": "Compare the object's own keys with the value the browser reads through its prototype chain.",
          "demoCue": "Show the clean list of own request keys first, then the inherited option used by the live request.",
          "completion": {
            "type": "choice",
            "prompt": "What reveals the configuration integrity problem?",
            "options": [
              { "value": "own-vs-inherited-request-option", "label": "The difference between own option keys and the inherited value read by the request." },
              { "value": "preview-copy", "label": "The text returned by the preview endpoint by itself." },
              { "value": "button-label", "label": "The wording of the import button." }
            ],
            "answer": "own-vs-inherited-request-option"
          }
        },
        {
          "id": "prove",
          "number": 2,
          "title": "Prove the inherited request option",
          "summary": "Import the prepared document and correlate its merge with the resulting same-origin request.",
          "instructions": [
            "Start static and runtime analysis on the review target.",
            "Press Import and load preview and observe the one local JSON request.",
            "Enter the evidence token shown when the request option exists only through inheritance."
          ],
          "concepts": ["runtime merge", "request options", "browser impact"],
          "hint": "The request object reports no own credentials key even though reading the property returns include.",
          "demoCue": "Correlate the static merge path, runtime prototype write and the browser request that consumes the inherited field.",
          "completion": {
            "type": "proof",
            "prompt": "Evidence token",
            "value": "PREFERENCE-INHERITED-REQUEST-OPTION"
          }
        },
        {
          "id": "fix",
          "number": 3,
          "title": "Validate reviewed own properties",
          "summary": "Repeat the import while proving that inherited, dangerous and unknown keys cannot become request options.",
          "instructions": [
            "Open the repaired target and import the same prepared document.",
            "Confirm that the request options have no prototype and contain only an own reviewed credentials key.",
            "Try the prepared unknown-key variation, then enter the repaired token."
          ],
          "concepts": ["null prototype", "own-property check", "allow-list"],
          "hint": "The repaired builder copies only accepted own values and supplies a constant safe default.",
          "demoCue": "Show that the preview still loads while arbitrary and inherited input no longer controls request options.",
          "completion": {
            "type": "proof",
            "prompt": "Remediation token",
            "value": "PREFERENCE-ALLOWLISTED-REQUEST-OPTION"
          }
        }
      ]
    },
    {
      "id": "history-order-router",
      "title": "History Order Router",
      "summary": "Follow an in-document History API transition into a browser-created authenticated JSON request.",
      "story": "An account shell opens an order without reloading the document. The route updates the live view and sends one session-bound JSON request; compare route-state interpretation and an active API error with a behavior-preserving repaired path.",
      "category": "SPA navigation and authenticated traffic",
      "engines": ["DAST", "SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/history-order-router/",
      "evidenceSummary": "History API route plus session-bound JSON POST",
      "targets": {
        "review": {
          "id": "history-order-router-review",
          "title": "History order router review target",
          "route": "./targets/history-order-router/vulnerable/",
          "displayRoute": "/targets/history-order-router/vulnerable/",
          "source": "./targets/history-order-router/vulnerable/history-order-router.js",
          "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 },
          "action": { "summary": "Press Open prepared order and observe the route, DOM and JSON request.", "triggerSelector": "#open-order-route", "readySelector": "#order-route-status" },
          "request": {
            "method": "POST",
            "route": "/targets/history-order-router/vulnerable/api/order",
            "contentType": "application/json",
            "parameterNames": ["orderId"],
            "setup": "Open the review page to establish its scoped session, then press Open prepared order."
          },
          "visibleBehavior": "The document stays loaded while route-controlled markup is interpreted and a browser-session JSON request is emitted."
        },
        "repaired": {
          "id": "history-order-router-control",
          "title": "History order router repaired control",
          "route": "./targets/history-order-router/fixed/",
          "displayRoute": "/targets/history-order-router/fixed/",
          "source": "./targets/history-order-router/fixed/history-order-router.js",
          "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 },
          "action": { "summary": "Press the same order action and observe the reviewed route and JSON request.", "triggerSelector": "#open-order-route", "readySelector": "#order-route-status" },
          "request": {
            "method": "POST",
            "route": "/targets/history-order-router/fixed/api/order",
            "contentType": "application/json",
            "parameterNames": ["orderId"],
            "setup": "Open the repaired page to establish its scoped session, then press Open prepared order."
          },
          "visibleBehavior": "The same route and request use an allow-listed identifier, constant text, and a clean API response."
        }
      },
      "objectives": [
        {
          "id": "discover", "number": 1, "title": "Discover the route-to-request boundary",
          "summary": "Identify the evidence created only after the SPA action.",
          "instructions": ["Open the review target and note its initial URL and quiet request state.", "Press Open prepared order and observe that the document does not reload.", "Compare the changed route, live DOM and captured JSON request."],
          "concepts": ["History API", "live route state", "authenticated request"],
          "hint": "The important view and request do not exist in the initial HTML response.",
          "demoCue": "Keep the URL, DOM and network views visible around one click.",
          "completion": { "type": "choice", "prompt": "What completes the browser evidence?", "options": [{"value":"route-dom-request","label":"The route transition, live DOM update and resulting JSON request."},{"value":"initial-html","label":"Only the initial HTML response."},{"value":"page-title","label":"Only the document title."}], "answer": "route-dom-request" }
        },
        {
          "id": "prove", "number": 2, "title": "Prove the browser-created flow",
          "summary": "Correlate route state, DOM behavior and the scoped active request.",
          "instructions": ["Start browser traffic, static and runtime analysis on the review target.", "Press Open prepared order and capture the JSON POST.", "Enter the evidence token shown by the in-document route."],
          "concepts": ["route source", "HTML sink", "JSON parameter"],
          "hint": "Use the local route-aware runtime when you want to attack the captured API parameter.",
          "demoCue": "Show how one browser action gives SAST, IAST and DAST complementary evidence.",
          "completion": { "type": "proof", "prompt": "Evidence token", "value": "HISTORY-ORDER-ROUTE-MARKUP" }
        },
        {
          "id": "fix", "number": 3, "title": "Validate the paired repair",
          "summary": "Preserve the route and request while removing interpretation and the API error oracle.",
          "instructions": ["Open the repaired target and repeat the same action.", "Confirm the History API and JSON request still execute.", "Enter the repaired route token and compare malformed API responses locally."],
          "concepts": ["allow-list", "text rendering", "clean active control"],
          "hint": "The repaired path changes validation and rendering, not the browser journey.",
          "demoCue": "Use the repaired route as a negative oracle for both browser and API evidence.",
          "completion": { "type": "proof", "prompt": "Remediation token", "value": "HISTORY-ORDER-ROUTE-TEXT-SAFE" }
        }
      ]
    },
    {
      "id": "lazy-route-module",
      "title": "Lazy Analytics Route",
      "summary": "Reveal an SPA route module and dependency that do not exist in browser traffic before the user action.",
      "story": "An application shell loads its analytics feature only after a History API transition. Compare an older dependency and route-controlled HTML sink with a reviewed dependency and allow-listed text output while keeping the same lazy journey.",
      "category": "Lazy SPA modules and dependencies",
      "engines": ["SCA", "SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/lazy-route-module/",
      "dependency": { "name": "jQuery", "license": "MIT", "reviewVersion": "3.4.1", "repairedVersion": "3.7.1" },
      "evidenceSummary": "Dynamic route import and action-loaded dependency",
      "targets": {
        "review": {
          "id": "lazy-route-module-review",
          "title": "Lazy analytics route review target",
          "route": "./targets/lazy-route-module/vulnerable/",
          "displayRoute": "/targets/lazy-route-module/vulnerable/",
          "source": "./targets/lazy-route-module/vulnerable/analytics-route.js",
          "action": { "summary": "Observe initial traffic, then press Open analytics route.", "triggerSelector": "#open-analytics-route", "readySelector": "#analytics-route-status" },
          "visibleBehavior": "The route action imports a new module, loads jQuery 3.4.1, and interprets the prepared route summary as markup."
        },
        "repaired": {
          "id": "lazy-route-module-control",
          "title": "Lazy analytics route repaired control",
          "route": "./targets/lazy-route-module/fixed/",
          "displayRoute": "/targets/lazy-route-module/fixed/",
          "source": "./targets/lazy-route-module/fixed/analytics-route.js",
          "action": { "summary": "Observe initial traffic, then press the same analytics action.", "triggerSelector": "#open-analytics-route", "readySelector": "#analytics-route-status" },
          "visibleBehavior": "The same lazy route loads jQuery 3.7.1 and renders an allow-listed summary as text."
        }
      },
      "objectives": [
        {
          "id": "discover", "number": 1, "title": "Establish the quiet initial state",
          "summary": "Prove that neither the feature chunk nor dependency appears at page load.",
          "instructions": ["Open the review target without using its route action.", "Inspect initial browser traffic for the analytics module and jQuery.", "Choose the transition needed to expose the real client surface."],
          "concepts": ["code splitting", "dynamic import", "dependency timing"],
          "hint": "The application shell alone is not the complete client application.",
          "demoCue": "Start with a clean network view, then reveal both files with one route transition.",
          "completion": { "type": "choice", "prompt": "What reveals the hidden client surface?", "options": [{"value":"route-action","label":"Open the lazy route and observe its new module and dependency requests."},{"value":"reload-shell","label":"Reload only the untouched shell."},{"value":"read-heading","label":"Read the page heading."}], "answer": "route-action" }
        },
        {
          "id": "prove", "number": 2, "title": "Prove the late-loaded behavior",
          "summary": "Correlate the imported source, dependency version and live route sink.",
          "instructions": ["Start SCA, SAST and IAST on the review target.", "Press Open analytics route and observe both new requests.", "Enter the evidence token after the route content appears."],
          "concepts": ["runtime component", "late source collection", "HTML sink"],
          "hint": "The route module and dependency are requested in sequence after the click.",
          "demoCue": "Show why browser actions matter to both composition and code analysis.",
          "completion": { "type": "proof", "prompt": "Evidence token", "value": "LAZY-ROUTE-MODULE-AND-DEPENDENCY-LOADED" }
        },
        {
          "id": "fix", "number": 3, "title": "Validate lazy-loading safely",
          "summary": "Keep code splitting while upgrading the dependency and rendering reviewed text.",
          "instructions": ["Open the repaired target and confirm its initial traffic remains quiet.", "Repeat the route action and compare the requested files and output.", "Enter the repaired evidence token."],
          "concepts": ["dependency upgrade", "allow-listed state", "text rendering"],
          "hint": "The repair does not make the route eager or remove the feature.",
          "demoCue": "Compare request timing and visible output before discussing the two small code changes.",
          "completion": { "type": "proof", "prompt": "Remediation token", "value": "LAZY-ROUTE-MODULE-TEXT-SAFE" }
        }
      ]
    },
    {
      "id": "same-origin-child-tab",
      "title": "Related Child Tab",
      "summary": "Continue analysis in a causally related same-origin tab while preserving an explicit different-origin scope boundary.",
      "story": "A support launcher opens a same-origin child workspace. The child loads its own dependency and context response before receiving a structured browser message; compare permissive HTML handling and response disclosure with exact validation, text rendering, a reviewed component, and a clean response.",
      "category": "Related browser contexts and scope",
      "engines": ["DAST", "SCA", "SAST", "IAST"],
      "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/same-origin-child-tab/",
      "dependency": { "name": "jQuery", "license": "MIT", "reviewVersion": "3.4.1", "repairedVersion": "3.7.1" },
      "evidenceSummary": "Same-origin child message, dependency and response",
      "targets": {
        "review": {
          "id": "same-origin-child-tab-review",
          "title": "Related child-tab review journey",
          "route": "./targets/same-origin-child-tab/vulnerable/",
          "displayRoute": "/targets/same-origin-child-tab/vulnerable/",
          "source": "./targets/same-origin-child-tab/vulnerable/child-runtime.js",
          "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 },
          "journey": { "summary": "Open the prepared child and inspect evidence in the new same-origin tab.", "entrySelector": "#open-related-child", "childRoute": "/targets/same-origin-child-tab/vulnerable/child.html", "childReadySelector": "#child-runtime-status" },
          "visibleBehavior": "The related child loads jQuery 3.4.1, accepts the workspace message as HTML, and receives a response metadata disclosure locally."
        },
        "repaired": {
          "id": "same-origin-child-tab-control",
          "title": "Related child-tab repaired journey",
          "route": "./targets/same-origin-child-tab/fixed/",
          "displayRoute": "/targets/same-origin-child-tab/fixed/",
          "source": "./targets/same-origin-child-tab/fixed/child-runtime.js",
          "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 },
          "journey": { "summary": "Open the paired child and inspect evidence in the new same-origin tab.", "entrySelector": "#open-related-child", "childRoute": "/targets/same-origin-child-tab/fixed/child.html", "childReadySelector": "#child-runtime-status" },
          "visibleBehavior": "The related child validates its opener, loads jQuery 3.7.1, renders text, and receives a clean local response."
        }
      },
      "objectives": [
        {
          "id": "discover", "number": 1, "title": "Discover the related browser context",
          "summary": "Identify why the launcher tab is not the whole authorised application journey.",
          "instructions": ["Start on the review launcher and note its origin.", "Open the prepared related child and compare its origin and opener relationship.", "Observe which code, dependency and request exist only in the child."],
          "concepts": ["opener relationship", "same-origin child", "bounded scope"],
          "hint": "Causality and exact origin both matter; a random same-origin tab is not automatically related.",
          "demoCue": "Keep launcher and child visible, then contrast the optional alternate-host control locally.",
          "completion": { "type": "choice", "prompt": "Which tab belongs to the journey?", "options": [{"value":"causal-same-origin-child","label":"The same-origin child opened by the tracked launcher."},{"value":"every-same-origin-tab","label":"Every unrelated tab that happens to share a hostname."},{"value":"alternate-host-control","label":"The alternate-host control with no application state."}], "answer": "causal-same-origin-child" }
        },
        {
          "id": "prove", "number": 2, "title": "Prove child-owned evidence",
          "summary": "Collect runtime, component, source and response evidence from the child itself.",
          "instructions": ["Start all browser engines on the review launcher.", "Open the related child and wait for its dependency, request and message.", "Enter the evidence token displayed inside the child."],
          "concepts": ["child runtime", "postMessage", "child dependency", "response metadata"],
          "hint": "The proof token appears only in the child document after its own lifecycle runs.",
          "demoCue": "Show that the browser journey—not one tab ID—is the useful security boundary.",
          "completion": { "type": "proof", "prompt": "Evidence token", "value": "RELATED-CHILD-MESSAGE-MARKUP" }
        },
        {
          "id": "fix", "number": 3, "title": "Validate trust and scope controls",
          "summary": "Preserve the related child while validating its exact message and dependency boundaries.",
          "instructions": ["Open the repaired launcher and its related child.", "Confirm the message is displayed literally and the reviewed dependency loads.", "Use the local alternate-host control only to verify that it receives no state, then enter the repaired token."],
          "concepts": ["exact origin", "exact opener", "text rendering", "scope exclusion"],
          "hint": "The repaired application still follows its child; it does not broaden ownership to the alternate-host control.",
          "demoCue": "Use the repaired child and external control as two different negative oracles.",
          "completion": { "type": "proof", "prompt": "Remediation token", "value": "RELATED-CHILD-MESSAGE-TEXT-SAFE" }
        }
      ]
    },
    {
      "id": "graphql-order", "title": "GraphQL Cross-owner Order Query", "summary": "Compare an Alice-to-Bob GraphQL order query with an owner-checking control.",
      "story": "A bounded local GraphQL operation reads an order using a browser-created JSON POST. Alice must not receive Bob's order just by changing the ID variable.",
      "category": "Access control", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/graphql-order/", "evidenceSummary": "Same-session GraphQL data versus FORBIDDEN control; manual PTK proof",
      "targets": {
        "review": { "id": "graphql-order-review", "title": "Cross-owner GraphQL query", "route": "./targets/graphql/order/vulnerable/", "displayRoute": "/targets/graphql/order/vulnerable/", "source": "./assets/js/graphql-lab.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice receives Bob's order via the documented Order query." },
        "repaired": { "id": "graphql-order-control", "title": "Owner-checked GraphQL query", "route": "./targets/graphql/order/fixed/", "displayRoute": "/targets/graphql/order/fixed/", "source": "./passive/workshop-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice receives FORBIDDEN for Bob's order but may query her own." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Capture the operation", "summary": "Observe the browser-created Order query under Alice's session.", "instructions": ["Start Alice's local session.", "Capture the documented GraphQL POST in PTK Proxy."], "concepts": ["GraphQL operation", "session"], "hint": "The order identifier is in variables.id.", "demoCue": "Show the query, variable and session without exposing the cookie value.", "completion": { "type": "choice", "prompt": "Which field selects the object?", "options": [{"value":"variable","label":"variables.id"},{"value":"field","label":"The selected response field"}], "answer": "variable" } },
        { "id": "prove", "number": 2, "title": "Read across owners", "summary": "Query Bob's order while signed in as Alice.", "instructions": ["Select Bob's order and press Query order.", "Record data.order.owner and compare with Alice's identity."], "concepts": ["BOLA", "cross-owner query"], "hint": "The review endpoint does not check record ownership.", "demoCue": "Show Alice's session and Bob's order in the response.", "completion": { "type": "choice", "prompt": "What proves the vulnerable result?", "options": [{"value":"bob-data","label":"Alice receives Bob's order data."},{"value":"own-data","label":"Alice receives only her own order."}], "answer": "bob-data" } },
        { "id": "fix", "number": 3, "title": "Verify ownership control", "summary": "Repeat the same query on the repaired endpoint.", "instructions": ["Query Bob's order as Alice on the repaired route.", "Confirm FORBIDDEN and that Alice's own order still succeeds."], "concepts": ["authorization", "negative control"], "hint": "The fixed endpoint checks the current session owner.", "demoCue": "Compare data.order and errors, then query Alice's own order.", "completion": { "type": "choice", "prompt": "What is the repaired result?", "options": [{"value":"forbidden","label":"Bob's order is null with FORBIDDEN; Alice's order succeeds."},{"value":"all-blocked","label":"Every order query is blocked."}], "answer": "forbidden" } }
      ]
    },
    {
      "id": "idor-read", "title": "Authenticated IDOR: Read", "summary": "Compare another user's order read with an ownership-enforcing control.",
      "story": "Alice and Bob have independent synthetic sessions and orders. Alice must not read Bob's object simply by changing an identifier.",
      "category": "Access control", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/idor-read/", "evidenceSummary": "Cross-owner read and repaired 403",
      "targets": {
        "review": { "id": "idor-read-review", "title": "Cross-owner read", "route": "./targets/access-control/idor-read/vulnerable/", "displayRoute": "/targets/access-control/idor-read/vulnerable/", "source": "./assets/js/access-control-lab.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice can read Bob's order by selecting its identifier." },
        "repaired": { "id": "idor-read-control", "title": "Owner-checked read", "route": "./targets/access-control/idor-read/fixed/", "displayRoute": "/targets/access-control/idor-read/fixed/", "source": "./passive/workshop-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice receives 403 for Bob's order while Bob still reads it." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Establish two owners", "summary": "Start separate Alice and Bob browser sessions.", "instructions": ["Open the review page in two isolated browser contexts.", "Start Alice and Bob separately and inspect their own orders."], "concepts": ["session", "ownership"], "hint": "Use separate browser contexts, not two tabs sharing cookies.", "demoCue": "Show both own-object reads.", "completion": { "type": "choice", "prompt": "What identifies the owner?", "options": [{"value":"session","label":"The current authenticated session."},{"value":"id","label":"The requested object ID alone."}], "answer": "session" } },
        { "id": "prove", "number": 2, "title": "Read across owners", "summary": "Request Bob's object as Alice.", "instructions": ["Select Bob's order while signed in as Alice.", "Record the 200 response and object owner."], "concepts": ["IDOR", "cross-owner read"], "hint": "Keep Alice's cookie while changing only the object ID.", "demoCue": "Compare actor and owner fields.", "completion": { "type": "choice", "prompt": "What proves the vulnerable result?", "options": [{"value":"cross-owner-200","label":"Alice receives Bob's object with HTTP 200."},{"value":"own-200","label":"Alice receives her own object with HTTP 200."}], "answer": "cross-owner-200" } },
        { "id": "fix", "number": 3, "title": "Verify ownership check", "summary": "Repeat the same action on the fixed endpoint.", "instructions": ["Open the repaired route as Alice and request Bob's order.", "Confirm 403; verify Bob still reads his own order."], "concepts": ["authorization", "negative control"], "hint": "The feature should remain available to the owner.", "demoCue": "Show 403 cross-owner and 200 owner.", "completion": { "type": "choice", "prompt": "What is the repaired result?", "options": [{"value":"403-owner-200","label":"Cross-owner 403, own-object 200."},{"value":"all-403","label":"All object reads fail."}], "answer": "403-owner-200" } }
      ]
    },
    {
      "id": "idor-write", "title": "Authenticated IDOR: Update", "summary": "Prove a cross-owner object mutation and its repaired control.",
      "story": "Alice changes Bob's order note through a browser-created JSON POST. Bob then observes the mutation in his own session.",
      "category": "Access control", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/idor-write/", "evidenceSummary": "Cross-owner write and repaired 403",
      "targets": {
        "review": { "id": "idor-write-review", "title": "Cross-owner update", "route": "./targets/access-control/idor-write/vulnerable/", "displayRoute": "/targets/access-control/idor-write/vulnerable/", "source": "./assets/js/access-control-lab.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice can change Bob's order note." },
        "repaired": { "id": "idor-write-control", "title": "Owner-checked update", "route": "./targets/access-control/idor-write/fixed/", "displayRoute": "/targets/access-control/idor-write/fixed/", "source": "./passive/workshop-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Alice receives 403 and Bob's note remains unchanged." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Find the update request", "summary": "Observe the browser-created JSON POST.", "instructions": ["Start Alice's session.", "Update Alice's own order and inspect the POST body."], "concepts": ["JSON POST", "session"], "hint": "The object ID is in the path.", "demoCue": "Capture the request.", "completion": { "type": "choice", "prompt": "Which field selects the object?", "options": [{"value":"path","label":"The object ID in the request path."},{"value":"note","label":"The new note text."}], "answer": "path" } },
        { "id": "prove", "number": 2, "title": "Mutate across owners", "summary": "Change Bob's note as Alice.", "instructions": ["Select Bob's order as Alice and post a distinct note.", "In Bob's separate context, read his order to verify the change."], "concepts": ["BOLA", "state mutation"], "hint": "Use two isolated browser sessions.", "demoCue": "Show Alice actor and Bob owner.", "completion": { "type": "choice", "prompt": "What proves the defect?", "options": [{"value":"bob-changed","label":"Bob's note changed after Alice's POST."},{"value":"alice-changed","label":"Alice changed only her own note."}], "answer": "bob-changed" } },
        { "id": "fix", "number": 3, "title": "Validate the control", "summary": "Check that ownership blocks the write.", "instructions": ["Repeat Alice-to-Bob update on the fixed route.", "Confirm 403 and unchanged note; Bob can still update his own object."], "concepts": ["authorization", "negative control"], "hint": "The control checks the current session owner.", "demoCue": "Compare responses and persistent note.", "completion": { "type": "choice", "prompt": "Expected control?", "options": [{"value":"owner-check","label":"Cross-owner 403, owner update 200."},{"value":"no-write","label":"All writes fail."}], "answer": "owner-check" } }
      ]
    },
    {
      "id": "stored-xss", "title": "Stored XSS Across Two Sessions", "summary": "Alice saves a message that Bob later renders; compare HTML and text sinks.",
      "story": "The message is held by the local runtime. The security difference is in the receiving page's rendering path.",
      "category": "Stored browser content", "engines": ["SAST", "IAST", "DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/stored-xss/", "evidenceSummary": "Alice write, Bob render, text-safe control",
      "targets": {
        "review": { "id": "stored-xss-review", "title": "Stored message rendered as HTML", "route": "./targets/stored-xss/vulnerable/", "displayRoute": "/targets/stored-xss/vulnerable/", "source": "./targets/stored-xss/vulnerable/render.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Bob's page interprets Alice's stored markup." },
        "repaired": { "id": "stored-xss-control", "title": "Stored message rendered as text", "route": "./targets/stored-xss/fixed/", "displayRoute": "/targets/stored-xss/fixed/", "source": "./targets/stored-xss/fixed/render.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "Bob sees the same message literally, without markup execution." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Trace the two-session journey", "summary": "Identify the author and the viewer.", "instructions": ["Open two isolated browser contexts.", "Start Alice as author and Bob as viewer."], "concepts": ["storage", "session"], "hint": "Two tabs in one cookie jar are not two sessions.", "demoCue": "Show Alice and Bob contexts.", "completion": { "type": "choice", "prompt": "Who saves and who views?", "options": [{"value":"alice-bob","label":"Alice saves; Bob views."},{"value":"alice-alice","label":"Alice only views her own message."}], "answer": "alice-bob" } },
        { "id": "prove", "number": 2, "title": "Observe the browser sink", "summary": "Load harmless markup in Bob's context.", "instructions": ["Save the prepared local-only image proof as Alice.", "Load the message as Bob and inspect the DOM attribute."], "concepts": ["stored XSS", "HTML sink"], "hint": "The proof sets a DOM attribute; it makes no outbound request.", "demoCue": "Correlate write, read and DOM sink.", "completion": { "type": "choice", "prompt": "What is unsafe?", "options": [{"value":"html","label":"Stored content is interpreted as HTML."},{"value":"text","label":"Stored content remains literal text."}], "answer": "html" } },
        { "id": "fix", "number": 3, "title": "Validate safe rendering", "summary": "Keep the message feature without interpreting markup.", "instructions": ["Open the repaired viewer as Bob.", "Confirm the same message is displayed literally and no proof attribute appears."], "concepts": ["text rendering", "control"], "hint": "The message should remain visible.", "demoCue": "Compare DOM content and attribute.", "completion": { "type": "choice", "prompt": "What is the repaired result?", "options": [{"value":"literal","label":"Literal text, no execution."},{"value":"discarded","label":"The message disappears entirely."}], "answer": "literal" } }
      ]
    },
    {
      "id": "jwt-nested-weak-secret", "title": "JWT Weak Secret in Nested JSON", "summary": "Forge a synthetic admin JWT carried in auth.access_token and compare a strong-key control.",
      "story": "A low-privilege HS256 token travels in a JSON POST. The review verifier trusts a weak signing key; the repaired verifier uses an independent strong key.",
      "category": "JWT authorization", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/jwt-nested-weak-secret/", "evidenceSummary": "Nested JSON JWT privilege escalation",
      "targets": {
        "review": { "id": "jwt-nested-review", "title": "Weak-key nested JWT", "route": "./targets/jwt-lab/nested-json-weak-secret/", "displayRoute": "/targets/jwt-lab/nested-json-weak-secret/", "source": "./assets/js/jwt-nested-lab.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "A correctly forged admin token succeeds on the weak-key endpoint." },
        "repaired": { "id": "jwt-nested-control", "title": "Strong-key nested JWT", "route": "./targets/jwt-lab/nested-json-weak-secret/", "displayRoute": "/targets/jwt-lab/nested-json-weak-secret/", "source": "./passive/workshop-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same forged token fails on the strong-key endpoint." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Locate the token", "summary": "Capture the nested JSON POST.", "instructions": ["Issue a normal user token.", "Send it and find auth.access_token in the JSON body."], "concepts": ["JWT", "nested JSON"], "hint": "The token is not in a cookie or Authorization header.", "demoCue": "Inspect the request body.", "completion": { "type": "choice", "prompt": "Where is the JWT?", "options": [{"value":"nested","label":"auth.access_token in the JSON POST."},{"value":"cookie","label":"A browser cookie."}], "answer": "nested" } },
        { "id": "prove", "number": 2, "title": "Test the weak verifier", "summary": "Sign an admin claim with the lab's weak key.", "instructions": ["Use the PTK JWT tool to inspect and alter the role claim.", "Sign and send the token on the review endpoint."], "concepts": ["HS256", "weak signing key"], "hint": "The key is deliberately present in the PTK weak-secret wordlist.", "demoCue": "Show user 403 and forged admin 200.", "completion": { "type": "choice", "prompt": "What proves the exploit?", "options": [{"value":"admin-200","label":"Forged admin token receives HTTP 200."},{"value":"user-403","label":"Normal user token receives HTTP 403."}], "answer": "admin-200" } },
        { "id": "fix", "number": 3, "title": "Validate the key control", "summary": "Resend the identical forgery to the strict endpoint.", "instructions": ["Switch to the repaired endpoint without changing the forged token.", "Confirm the signature is rejected."], "concepts": ["signature verification", "control"], "hint": "The repaired route has an independent strong signing key.", "demoCue": "Compare 200 against 401.", "completion": { "type": "choice", "prompt": "Expected repaired result?", "options": [{"value":"reject-401","label":"The forged token is rejected with HTTP 401."},{"value":"grant-200","label":"The forged token is accepted."}], "answer": "reject-401" } }
      ]
    },
    {
      "id": "jwt-none", "title": "JWT Algorithm None", "summary": "Compare unsigned bearer-token acceptance with a rejecting verifier.",
      "story": "A synthetic Authorization request is accepted when the review verifier trusts an unsigned alg:none token.",
      "category": "JWT authorization", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/jwt-none/", "evidenceSummary": "Unsigned token 200 versus 401 control; PTK finding pending",
      "targets": {
        "review": { "id": "jwt-none-review", "title": "Unsigned token accepted", "route": "./labs/jwt-none/?variant=vulnerable", "displayRoute": "/labs/jwt-none/?variant=vulnerable", "source": "./assets/js/real-labs.js", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The unsigned synthetic bearer token receives HTTP 200." },
        "repaired": { "id": "jwt-none-control", "title": "Unsigned token rejected", "route": "./labs/jwt-none/?variant=fixed", "displayRoute": "/labs/jwt-none/?variant=fixed", "source": "./passive/server.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same unsigned bearer token receives HTTP 401." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Capture the carrier", "summary": "Observe a normal Authorization bearer request.", "instructions": ["Start the local runtime and PTK DAST.", "Run the review target and inspect its Authorization request."], "concepts": ["JWT", "Authorization"], "hint": "The token is in the request header.", "demoCue": "Show the normal 200 before the unsigned mutation.", "completion": { "type": "choice", "prompt": "Where is the token?", "options": [{"value":"header","label":"Authorization header"},{"value":"cookie","label":"Cookie only"}], "answer": "header" } },
        { "id": "prove", "number": 2, "title": "Test unsigned acceptance", "summary": "Send the alg:none mutation.", "instructions": ["Run the review target's paired requests.", "Compare the unsigned response with the normal response."], "concepts": ["algorithm none", "signature"], "hint": "The unsigned token has an empty signature segment.", "demoCue": "Show unsigned HTTP 200 on review.", "completion": { "type": "choice", "prompt": "What does review accept?", "options": [{"value":"unsigned-200","label":"Unsigned token: HTTP 200"},{"value":"unsigned-401","label":"Unsigned token: HTTP 401"}], "answer": "unsigned-200" } },
        { "id": "fix", "number": 3, "title": "Check the verifier", "summary": "Repeat the same mutation on the repaired route.", "instructions": ["Run the repaired target.", "Confirm normal 200 and unsigned 401."], "concepts": ["negative control"], "hint": "The normal synthetic token should still work.", "demoCue": "Compare 200 and 401 without claiming a native PTK finding.", "completion": { "type": "choice", "prompt": "Repaired result?", "options": [{"value":"reject","label":"Normal 200; unsigned 401"},{"value":"all-pass","label":"Both tokens 200"}], "answer": "reject" } }
      ]
    },
    {
      "id": "jwt-alg-confusion", "title": "JWT Algorithm Confusion", "summary": "A published RSA public key becomes an HMAC signing key only at the review verifier.",
      "story": "The browser signs a synthetic admin claim with public key bytes; a strict verifier pins RS256.",
      "category": "JWT authorization", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/jwt-alg-confusion/", "evidenceSummary": "Forged admin 200 versus 401 control; manual PTK proof candidate",
      "targets": {
        "review": { "id": "jwt-confusion-review", "title": "Public-key HMAC accepted", "route": "./labs/jwt-alg-confusion/?variant=vulnerable", "displayRoute": "/labs/jwt-alg-confusion/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The HS256 admin forgery receives HTTP 200." },
        "repaired": { "id": "jwt-confusion-control", "title": "RS256 pinned", "route": "./labs/jwt-alg-confusion/?variant=fixed", "displayRoute": "/labs/jwt-alg-confusion/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same HS256 forgery receives HTTP 401." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Inspect the key boundary", "summary": "Distinguish public verification data from a secret.", "instructions": ["Open the review target.", "Observe that the lab publishes only an RSA public key."], "concepts": ["RS256", "HS256", "public key"], "hint": "The private key never leaves the server.", "demoCue": "Show the published key without displaying the token.", "completion": { "type": "choice", "prompt": "What may the browser know?", "options": [{"value":"public","label":"The RSA public key"},{"value":"private","label":"The RSA private key"}], "answer": "public" } },
        { "id": "prove", "number": 2, "title": "Forge with public bytes", "summary": "Send an HS256 admin token signed using the public key as the HMAC secret.", "instructions": ["Run review requests.", "Compare the normal user response with forged admin response."], "concepts": ["algorithm confusion"], "hint": "The review verifier chooses its algorithm from the token header.", "demoCue": "Show user 403 and forged admin 200.", "completion": { "type": "choice", "prompt": "Review forgery result?", "options": [{"value":"grant","label":"Admin granted: HTTP 200"},{"value":"reject","label":"Signature rejected: HTTP 401"}], "answer": "grant" } },
        { "id": "fix", "number": 3, "title": "Pin the algorithm", "summary": "Repeat the forgery against the RS256-only control.", "instructions": ["Run repaired requests.", "Confirm normal user 403 and forged admin 401."], "concepts": ["algorithm pinning"], "hint": "The same public key no longer acts as an HMAC secret.", "demoCue": "Compare 200 review with 401 repaired.", "completion": { "type": "choice", "prompt": "Repaired forgery result?", "options": [{"value":"reject","label":"HTTP 401"},{"value":"grant","label":"HTTP 200"}], "answer": "reject" } }
      ]
    },
    {
      "id": "jwt-null-signature", "title": "JWT Null Signature", "summary": "An HS256 token with an empty signature is trusted by one synthetic verifier.",
      "story": "Keep HS256 in the JWT header, change the synthetic user claim to admin, and compare the same unsigned token on two verifiers.",
      "category": "JWT authorization", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/jwt-null-signature/", "evidenceSummary": "HS256 empty-signature admin 200 versus 401 control; manual Full proof pending",
      "targets": {
        "review": { "id": "jwt-null-signature-review", "title": "Empty HS256 signature accepted", "route": "./labs/jwt-null-signature/?variant=vulnerable", "displayRoute": "/labs/jwt-null-signature/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The empty-signature synthetic admin token receives HTTP 200." },
        "repaired": { "id": "jwt-null-signature-control", "title": "HS256 signature required", "route": "./labs/jwt-null-signature/?variant=fixed", "displayRoute": "/labs/jwt-null-signature/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same empty-signature admin token receives HTTP 401." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Inspect the signed user token", "summary": "Observe the HS256 header and normal signature.", "instructions": ["Run the local server and open the review lab.", "Issue a synthetic user token and inspect its header and signature in Full PTK JWT Inspector."], "concepts": ["HS256", "JWT signature"], "hint": "This case does not use alg:none.", "demoCue": "Show a signed user token receiving HTTP 403 on the admin route.", "completion": { "type": "choice", "prompt": "Which algorithm remains in the header?", "options": [{"value":"hs256","label":"HS256"},{"value":"none","label":"none"}], "answer": "hs256" } },
        { "id": "prove", "number": 2, "title": "Test the empty signature", "summary": "Compare an admin claim with no signature on the review route.", "instructions": ["Run paired requests once or submit the displayed forged token through PTK Request Builder.", "Check the empty third JWT segment and HTTP 200 response."], "concepts": ["null signature", "admin claim"], "hint": "The final dot is present but no signature bytes follow it.", "demoCue": "Show the exact request and synthetic admin response, not only the page result.", "completion": { "type": "choice", "prompt": "Review result?", "options": [{"value":"grant","label":"Forged admin: HTTP 200"},{"value":"reject","label":"Forged admin: HTTP 401"}], "answer": "grant" } },
        { "id": "fix", "number": 3, "title": "Check the repaired verifier", "summary": "Send the identical token to the fixed route.", "instructions": ["Keep the forged token unchanged.", "Confirm the repaired route rejects it with HTTP 401 while a signed user token still gets HTTP 403."], "concepts": ["signature verification", "negative control"], "hint": "The fixed route requires a valid HMAC.", "demoCue": "Compare vulnerable 200 with repaired 401.", "completion": { "type": "choice", "prompt": "Fixed result?", "options": [{"value":"reject","label":"Forged admin: HTTP 401"},{"value":"grant","label":"Forged admin: HTTP 200"}], "answer": "reject" } }
      ]
    },
    {
      "id": "jwt-jwk-injection", "title": "JWT Embedded JWK Injection", "summary": "A synthetic verifier trusts a public key supplied by the JWT header.",
      "story": "An attacker-owned, temporary RSA key signs the admin token and embeds its public JWK; only the review verifier trusts it.",
      "category": "JWT authorization", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/jwt-jwk-injection/", "evidenceSummary": "Embedded-JWK admin 200 versus pinned-key 401 control; manual Full proof pending",
      "targets": {
        "review": { "id": "jwt-jwk-review", "title": "Embedded public JWK trusted", "route": "./labs/jwt-jwk-injection/?variant=vulnerable", "displayRoute": "/labs/jwt-jwk-injection/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The attacker-key synthetic admin token receives HTTP 200." },
        "repaired": { "id": "jwt-jwk-control", "title": "Server key pinned", "route": "./labs/jwt-jwk-injection/?variant=fixed", "displayRoute": "/labs/jwt-jwk-injection/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same attacker-key token receives HTTP 401." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Inspect the issued token", "summary": "Observe the server-signed RS256 user token.", "instructions": ["Open the review lab on the local server.", "Inspect the issued token in Full PTK JWT Inspector; it has no embedded JWK."], "concepts": ["RS256", "trusted key"], "hint": "The user's token is not an admin token.", "demoCue": "Show the normal user's HTTP 403 admin response.", "completion": { "type": "choice", "prompt": "What key verifies a normal token?", "options": [{"value":"server","label":"The server's pinned public key"},{"value":"header","label":"An arbitrary header key"}], "answer": "server" } },
        { "id": "prove", "number": 2, "title": "Test the embedded key", "summary": "Use a temporary public JWK in the JWT header.", "instructions": ["Run paired requests once; the browser creates a temporary RSA key and signs a synthetic admin claim.", "Inspect the forged JWT header and HTTP 200 review response in PTK Proxy or Request Builder."], "concepts": ["embedded JWK", "trust boundary"], "hint": "Only the public key is embedded; no remote key lookup occurs.", "demoCue": "Show the header key and the exact accepted admin request.", "completion": { "type": "choice", "prompt": "Review result?", "options": [{"value":"grant","label":"Forged admin: HTTP 200"},{"value":"reject","label":"Forged admin: HTTP 401"}], "answer": "grant" } },
        { "id": "fix", "number": 3, "title": "Pin the verification key", "summary": "Repeat the same token against the repaired route.", "instructions": ["Resend the identical forged token.", "Confirm the fixed route ignores the embedded JWK and returns HTTP 401."], "concepts": ["key pinning", "negative control"], "hint": "Do not re-sign the token between routes.", "demoCue": "Compare vulnerable 200 with repaired 401.", "completion": { "type": "choice", "prompt": "Fixed result?", "options": [{"value":"reject","label":"Forged admin: HTTP 401"},{"value":"grant","label":"Forged admin: HTTP 200"}], "answer": "reject" } }
      ]
    },
    {
      "id": "sql-single-quote", "title": "SQL Single-Quote Injection", "summary": "A real string-literal query returns extra synthetic rows when input is concatenated.",
      "story": "The category search uses an in-memory SQLite table; a bound repaired query treats the same input as data.",
      "category": "SQL injection", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/sql-single-quote/", "evidenceSummary": "Two versus four versus zero rows; PTK finding pending",
      "targets": {
        "review": { "id": "sql-single-review", "title": "Concatenated category", "route": "./labs/sql-single-quote/?variant=vulnerable", "displayRoute": "/labs/sql-single-quote/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The injected category returns four products instead of two." },
        "repaired": { "id": "sql-single-control", "title": "Bound category", "route": "./labs/sql-single-quote/?variant=fixed", "displayRoute": "/labs/sql-single-quote/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same injected category returns zero products." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Capture the category", "summary": "Find the browser-created POST field.", "instructions": ["Run a normal category search.", "Inspect the category field."], "concepts": ["POST", "string literal"], "hint": "The baseline fruit query returns two products.", "demoCue": "Show baseline rows.", "completion": { "type": "choice", "prompt": "Baseline rows?", "options": [{"value":"two","label":"Two"},{"value":"four","label":"Four"}], "answer": "two" } },
        { "id": "prove", "number": 2, "title": "Change the predicate", "summary": "Send the bounded single-quote mutation.", "instructions": ["Run review requests.", "Count the returned products."], "concepts": ["SQL predicate"], "hint": "The query really executes in SQLite.", "demoCue": "Show four returned rows, not a canned error.", "completion": { "type": "choice", "prompt": "Review mutation rows?", "options": [{"value":"four","label":"Four"},{"value":"zero","label":"Zero"}], "answer": "four" } },
        { "id": "fix", "number": 3, "title": "Bind the value", "summary": "Repeat the same mutation on the control.", "instructions": ["Run repaired requests.", "Confirm zero mutated rows and two normal rows."], "concepts": ["parameter binding"], "hint": "The injected text is one data value.", "demoCue": "Compare normal and mutated controls.", "completion": { "type": "choice", "prompt": "Repaired mutation rows?", "options": [{"value":"zero","label":"Zero"},{"value":"four","label":"Four"}], "answer": "zero" } }
      ]
    },
    {
      "id": "sql-double-quote", "title": "SQL Double-Quote Identifier Injection", "summary": "An injected sort identifier changes actual query ordering.",
      "story": "A quoted identifier enters the ORDER BY clause; the repaired route accepts only exact known columns.",
      "category": "SQL injection", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/sql-double-quote/", "evidenceSummary": "SKU order versus injected descending-name order",
      "targets": {
        "review": { "id": "sql-double-review", "title": "Concatenated sort identifier", "route": "./labs/sql-double-quote/?variant=vulnerable", "displayRoute": "/labs/sql-double-quote/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The injected sort starts with Date rather than Apple." },
        "repaired": { "id": "sql-double-control", "title": "Allowlisted sort identifier", "route": "./labs/sql-double-quote/?variant=fixed", "displayRoute": "/labs/sql-double-quote/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The injected identifier is rejected with HTTP 400." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Observe normal ordering", "summary": "Run the SKU baseline.", "instructions": ["Run a normal sort request.", "Record the first product."], "concepts": ["ORDER BY", "identifier"], "hint": "SKU ascending starts with Apple.", "demoCue": "Show the baseline order.", "completion": { "type": "choice", "prompt": "First baseline product?", "options": [{"value":"apple","label":"Apple"},{"value":"date","label":"Date"}], "answer": "apple" } },
        { "id": "prove", "number": 2, "title": "Change the sort clause", "summary": "Send the double-quote mutation.", "instructions": ["Run review requests.", "Observe the changed first product."], "concepts": ["quoted identifier"], "hint": "The mutation changes ORDER BY without changing table rows.", "demoCue": "Show Date first.", "completion": { "type": "choice", "prompt": "First review product?", "options": [{"value":"date","label":"Date"},{"value":"apple","label":"Apple"}], "answer": "date" } },
        { "id": "fix", "number": 3, "title": "Allowlist the sort", "summary": "Reject a non-column value.", "instructions": ["Run repaired requests.", "Confirm normal sort works and mutation returns HTTP 400."], "concepts": ["identifier allowlist"], "hint": "Binding identifiers is not equivalent to binding values.", "demoCue": "Show exact rejection.", "completion": { "type": "choice", "prompt": "Repaired mutation?", "options": [{"value":"reject","label":"HTTP 400"},{"value":"reorder","label":"Date first"}], "answer": "reject" } }
      ]
    },
    {
      "id": "sql-auth-bypass", "title": "SQL Synthetic Login Bypass", "summary": "An injected username bypasses a real SQLite password predicate.",
      "story": "No real account or session exists: this lab returns only a synthetic identity to prove the broken predicate.",
      "category": "SQL injection", "engines": ["DAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/sql-auth-bypass/", "evidenceSummary": "Wrong password 401, injected review admin 200, fixed 401",
      "targets": {
        "review": { "id": "sql-auth-review", "title": "Concatenated login predicate", "route": "./labs/sql-auth-bypass/?variant=vulnerable", "displayRoute": "/labs/sql-auth-bypass/?variant=vulnerable", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The injected username grants the synthetic admin identity." },
        "repaired": { "id": "sql-auth-control", "title": "Bound login predicate", "route": "./labs/sql-auth-bypass/?variant=fixed", "displayRoute": "/labs/sql-auth-bypass/?variant=fixed", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same injected username receives HTTP 401." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Check wrong credentials", "summary": "Establish the ordinary 401.", "instructions": ["Send the normal admin name with a wrong password.", "Observe the rejected response."], "concepts": ["login predicate"], "hint": "No browser session is created.", "demoCue": "Show the baseline 401.", "completion": { "type": "choice", "prompt": "Normal wrong password?", "options": [{"value":"reject","label":"HTTP 401"},{"value":"grant","label":"HTTP 200"}], "answer": "reject" } },
        { "id": "prove", "number": 2, "title": "Bypass the predicate", "summary": "Send the injected username with the same wrong password.", "instructions": ["Run review requests.", "Observe the returned synthetic identity."], "concepts": ["SQL injection", "authentication"], "hint": "The response is an identity, not a real account session.", "demoCue": "Show admin identity with HTTP 200.", "completion": { "type": "choice", "prompt": "Review mutation?", "options": [{"value":"admin","label":"Synthetic admin, HTTP 200"},{"value":"reject","label":"HTTP 401"}], "answer": "admin" } },
        { "id": "fix", "number": 3, "title": "Bind the identity", "summary": "Treat the same username as data.", "instructions": ["Run repaired requests.", "Confirm HTTP 401 and no identity."], "concepts": ["parameter binding"], "hint": "The control does not parse SQL from the username.", "demoCue": "Compare 200 and 401.", "completion": { "type": "choice", "prompt": "Repaired mutation?", "options": [{"value":"reject","label":"HTTP 401"},{"value":"admin","label":"Synthetic admin"}], "answer": "reject" } }
      ]
    },
    {
      "id": "xss-reflected", "title": "Reflected XSS", "summary": "A bounded query value executes a harmless marker only on the review response.",
      "story": "The server returns the same message with unsafe HTML interpolation or repaired encoding.",
      "category": "Cross-site scripting", "engines": ["DAST", "IAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/xss-reflected/", "evidenceSummary": "Browser execution versus encoded text; PTK finding pending",
      "targets": {
        "review": { "id": "xss-reflected-review", "title": "Unsafe reflected response", "route": "./targets/xss/reflected/vulnerable/", "displayRoute": "/targets/xss/reflected/vulnerable/", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The prepared query executes a harmless local marker." },
        "repaired": { "id": "xss-reflected-control", "title": "Encoded reflected response", "route": "./targets/xss/reflected/fixed/", "displayRoute": "/targets/xss/reflected/fixed/", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same query is visible as text and does not execute." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Trace the query", "summary": "Identify the reflected input.", "instructions": ["Open the review target.", "Locate the prepared query action."], "concepts": ["query parameter", "response HTML"], "hint": "The input is named message.", "demoCue": "Show the empty baseline.", "completion": { "type": "choice", "prompt": "Source?", "options": [{"value":"query","label":"Query parameter"},{"value":"cookie","label":"Cookie"}], "answer": "query" } },
        { "id": "prove", "number": 2, "title": "Execute the marker", "summary": "Run the prepared harmless proof.", "instructions": ["Click Run harmless proof on review.", "Observe the execution marker."], "concepts": ["reflected XSS"], "hint": "The marker changes inside the current document.", "demoCue": "Show executed on review.", "completion": { "type": "choice", "prompt": "Review marker?", "options": [{"value":"executed","label":"Executed"},{"value":"literal","label":"Not executed"}], "answer": "executed" } },
        { "id": "fix", "number": 3, "title": "Encode the response", "summary": "Repeat the same input on the control.", "instructions": ["Click the repaired target's proof link.", "Confirm literal text and no execution."], "concepts": ["HTML encoding"], "hint": "The message remains visible.", "demoCue": "Show the negative control.", "completion": { "type": "choice", "prompt": "Repaired marker?", "options": [{"value":"literal","label":"Not executed"},{"value":"executed","label":"Executed"}], "answer": "literal" } }
      ]
    },
    {
      "id": "xss-dom", "title": "DOM XSS", "summary": "A fragment message reaches innerHTML only on the review route.",
      "story": "The same hash value is interpreted as HTML by one client script and rendered as text by its control.",
      "category": "Cross-site scripting", "engines": ["SAST", "IAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/xss-dom/", "evidenceSummary": "Hash source to DOM sink; browser proof, PTK finding pending",
      "targets": {
        "review": { "id": "xss-dom-review", "title": "Fragment to innerHTML", "route": "./targets/xss/dom/vulnerable/", "displayRoute": "/targets/xss/dom/vulnerable/", "source": "./targets/xss/dom/vulnerable/app.js", "visibleBehavior": "The prepared hash executes a harmless local marker." },
        "repaired": { "id": "xss-dom-control", "title": "Fragment to textContent", "route": "./targets/xss/dom/fixed/", "displayRoute": "/targets/xss/dom/fixed/", "source": "./targets/xss/dom/fixed/app.js", "visibleBehavior": "The same hash displays literally and does not execute." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Trace the hash", "summary": "Identify the client-side source.", "instructions": ["Open the review target.", "Inspect the fragment-driven message preview."], "concepts": ["location.hash", "DOM sink"], "hint": "The hash is not sent in the HTTP request.", "demoCue": "Show the URL fragment and script source.", "completion": { "type": "choice", "prompt": "Source?", "options": [{"value":"hash","label":"URL fragment"},{"value":"header","label":"HTTP header"}], "answer": "hash" } },
        { "id": "prove", "number": 2, "title": "Reach the HTML sink", "summary": "Run the prepared harmless proof.", "instructions": ["Start PTK IAST on review.", "Click Run harmless proof and inspect the marker."], "concepts": ["innerHTML", "runtime execution"], "hint": "The review script uses innerHTML.", "demoCue": "Show executed marker.", "completion": { "type": "choice", "prompt": "Review marker?", "options": [{"value":"executed","label":"Executed"},{"value":"literal","label":"Not executed"}], "answer": "executed" } },
        { "id": "fix", "number": 3, "title": "Use a text sink", "summary": "Repeat the same hash on the control.", "instructions": ["Open repaired target and click Run harmless proof.", "Confirm literal markup text and no marker."], "concepts": ["textContent", "negative control"], "hint": "The value remains visible.", "demoCue": "Compare sink and result.", "completion": { "type": "choice", "prompt": "Repaired marker?", "options": [{"value":"literal","label":"Not executed"},{"value":"executed","label":"Executed"}], "answer": "literal" } }
      ]
    },
    {
      "id": "xss-attribute", "title": "Reflected attribute XSS", "summary": "A query breaks out of a quoted server-rendered attribute only on the review route.",
      "story": "The same label is interpolated raw or encoded for an HTML attribute.",
      "category": "Cross-site scripting", "engines": ["DAST", "IAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/xss-attribute/", "evidenceSummary": "Attribute breakout versus encoded value; native PTK finding pending",
      "targets": {
        "review": { "id": "xss-attribute-review", "title": "Unsafe result label", "route": "./targets/xss/reflected-attribute/vulnerable/", "displayRoute": "/targets/xss/reflected-attribute/vulnerable/", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The prepared label executes a harmless local marker." },
        "repaired": { "id": "xss-attribute-control", "title": "Encoded result label", "route": "./targets/xss/reflected-attribute/fixed/", "displayRoute": "/targets/xss/reflected-attribute/fixed/", "source": "./passive/real-labs.mjs", "runtime": { "kind": "route-aware-server", "protocol": "http", "port": 3080 }, "visibleBehavior": "The same label remains inside the attribute and does not execute." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Trace the label", "summary": "Find the query source and quoted attribute.", "instructions": ["Open the review target.", "Inspect its label query and data-label attribute."], "concepts": ["query parameter", "HTML attribute"], "hint": "The input is named label.", "demoCue": "Show the empty baseline.", "completion": { "type": "choice", "prompt": "Source?", "options": [{"value":"query","label":"Query"},{"value":"cookie","label":"Cookie"}], "answer": "query" } },
        { "id": "prove", "number": 2, "title": "Break out of the attribute", "summary": "Run the prepared browser proof.", "instructions": ["Click Run harmless proof on review.", "Observe the execution marker."], "concepts": ["attribute breakout"], "hint": "The prepared input closes the quote.", "demoCue": "Show the resulting DOM.", "completion": { "type": "choice", "prompt": "Review marker?", "options": [{"value":"executed","label":"Executed"},{"value":"literal","label":"Not executed"}], "answer": "executed" } },
        { "id": "fix", "number": 3, "title": "Encode for the attribute", "summary": "Repeat the same input on the control.", "instructions": ["Click Run harmless proof on repaired.", "Confirm the marker remains unchanged."], "concepts": ["context-aware encoding"], "hint": "The quote must stay inside data-label.", "demoCue": "Compare attribute values.", "completion": { "type": "choice", "prompt": "Repaired marker?", "options": [{"value":"literal","label":"Not executed"},{"value":"executed","label":"Executed"}], "answer": "literal" } }
      ]
    },
    {
      "id": "xss-query-code", "title": "Query to JavaScript XSS", "summary": "A URL query reaches a client-side JavaScript execution sink only on review.",
      "story": "The vulnerable script constructs a function with query data; the repaired script renders that data as text.",
      "category": "Cross-site scripting", "engines": ["SAST", "IAST"], "modes": ["campaign", "explorer", "demo", "scanner"],
      "route": "./campaigns/xss-query-code/", "evidenceSummary": "Query-to-code execution versus text rendering; native PTK finding pending",
      "targets": {
        "review": { "id": "xss-query-code-review", "title": "Query in executable code", "route": "./targets/xss/query-code/vulnerable/", "displayRoute": "/targets/xss/query-code/vulnerable/", "source": "./targets/xss/query-code/vulnerable/app.js", "visibleBehavior": "The prepared query executes a harmless local marker." },
        "repaired": { "id": "xss-query-code-control", "title": "Query rendered as data", "route": "./targets/xss/query-code/fixed/", "displayRoute": "/targets/xss/query-code/fixed/", "source": "./targets/xss/query-code/fixed/app.js", "visibleBehavior": "The same query displays literally and does not execute." }
      },
      "objectives": [
        { "id": "discover", "number": 1, "title": "Trace the query", "summary": "Identify the URL source and client code.", "instructions": ["Open the review target.", "Inspect the message query and app.js."], "concepts": ["location.search", "JavaScript execution sink"], "hint": "This is not the URL hash.", "demoCue": "Show the source path.", "completion": { "type": "choice", "prompt": "Source?", "options": [{"value":"query","label":"Query"},{"value":"hash","label":"Hash"}], "answer": "query" } },
        { "id": "prove", "number": 2, "title": "Execute the marker", "summary": "Run the harmless prepared input.", "instructions": ["Click Run harmless proof on review.", "Observe the execution marker."], "concepts": ["JavaScript string context"], "hint": "The input closes a string.", "demoCue": "Show executed marker.", "completion": { "type": "choice", "prompt": "Review marker?", "options": [{"value":"executed","label":"Executed"},{"value":"literal","label":"Not executed"}], "answer": "executed" } },
        { "id": "fix", "number": 3, "title": "Keep query as data", "summary": "Compare the repaired route.", "instructions": ["Click Run harmless proof on repaired.", "Confirm visible literal input and no execution."], "concepts": ["textContent", "no code construction"], "hint": "The control never uses Function.", "demoCue": "Compare scripts and results.", "completion": { "type": "choice", "prompt": "Repaired marker?", "options": [{"value":"literal","label":"Not executed"},{"value":"executed","label":"Executed"}], "answer": "literal" } }
      ]
    }
  ]
}
