Prismata: Confining Cross-Site Prompt Injection in Web Agents
Abstract: Autonomous web agents promise to automate everyday browsing tasks, but inherit one of the web's oldest attack surfaces. Cross-Site Scripting proved that mixing trusted and untrusted content is dangerous, even on benign pages. Agents resurface this risk by interpreting natural language as instructions, allowing third-party and user-generated content to hijack the agent via prompt injection. The core challenge is that deriving a task-specific security policy requires reasoning over page structure that is entangled with the attacker's content. We present Prismata, a defense enforcing contextual least privilege for web agents, constraining both what the agent sees and what it can do. Prismata's dynamic trust derivation produces permission labels for page content, with structural confinement guarantees, inspired by classical integrity models, that bound any labeling errors so that labels can only decrease in privilege and mislabelings are bounded. Prismata's mechanical confinement enforces these labels by redacting content and restricting agent capabilities. Importantly, these mechanisms require no developer annotations, so Prismata supports the long tail of websites. Across recent published web agent attacks, including adaptive variants, Prismata substantially reduces attack success while preserving benign task utility.
Paper Prompts
Sign up for free to create and run prompts on this paper.
Top Community Prompts
Explain it Like I'm 14
Prismata: Confining Cross-Site Prompt Injection in Web Agents — A Simple Explanation
What’s this paper about?
This paper introduces Prismata, a safety system for “web agents” — computer programs that browse websites and do tasks for you (like “buy the best-reviewed bow tie”). Prismata protects these agents from being tricked by sneaky messages hidden in web pages, a problem the authors call Cross-Site Prompting (XSP). In short, Prismata helps your browsing robot see only what it needs and do only what it should, so it won’t reveal private information or click dangerous things.
What questions are the researchers trying to answer?
To keep web agents safe and useful, the paper focuses on questions like:
- How do we stop web agents from following harmful instructions hidden in user comments, ads, or other untrusted parts of a page?
- Can we give a web agent only the permissions it needs for the user’s task (and nothing more)?
- Is there a way to do this on almost any website without asking website developers to add special tags or instructions?
How does Prismata work (in everyday terms)?
Think of a web agent as a helpful robot in a big store (the website). Sometimes strangers leave sticky notes (hidden instructions) around the store, trying to trick the robot. Prismata does two big things to keep the robot safe:
- Action gate: Only let the robot do actions that fit the task
- Analogy: If you tell the robot “Buy a bow tie,” it should only go to shelves related to shopping and checkout — not wander into “reset your password” or “send a direct message.”
- How it’s done: For every clickable thing on the page (buttons, links, fields), Prismata traces its “critical path” — the route from the top of the page’s structure (the DOM) down to that element. It then decides, using the task and just that path’s context, whether the action is allowed. This keeps random, untrusted parts of the page from influencing the decision.
- Biba parsing: Spot and contain untrusted content before it can trick the agent
- Analogy: The website is like a building with trusted floors (site content) and less-trusted floors (user reviews, ads). You can go down the building, but once you step into an untrusted floor, you treat everything below it as untrusted — no one gains more trust as you go. Also, you try to detect the “untrusted zone” as early as possible using signs like “Reviews” headers or class names (developer labels).
- How it’s done: Prismata looks for structural cues (like headings “Reviews,” accessibility labels, or class names) to detect where user content or ads begin. Then it:
- Removes unneeded untrusted content completely, or
- Lets the agent read it but not interact with it (read-only), if the task needs it (e.g., reading reviews when shopping).
- Important rule (put simply): “Don’t read deeper untrusted stuff before deciding the trust of what you’re already looking at,” and “children can’t be more trusted than their parents.” This keeps trust from being “upgraded” by attacker content.
- Mechanical confinement: Enforce the rules every step of the way
- The system sits between the agent and the browser. It filters what the agent sees and blocks actions the agent shouldn’t take. If a button is out of scope or in an untrusted zone, Prismata removes its ID or disables it so the agent can’t click it.
- This doesn’t require changing the website itself, and it works repeatedly as the page changes.
Why this is needed: Old web defenses (against things like Cross-Site Scripting) don’t stop natural-language instructions or sneaky images placed in comments or ads. Prismata adapts classic “least privilege” ideas — only give the minimum necessary permissions — to the world of web agents that read and follow natural language.
What did the researchers find?
Here are the main results the paper reports:
- Big drop in successful attacks: In test environments with known attack patterns, Prismata cut attack success from 85.5% down to 0.7% on average.
- Better task completion under attack: Without Prismata, agents finished tasks only 4.5% of the time when under attack; with Prismata, that rose to 23.0%.
- Keeps most normal usefulness: On harmless (benign) tasks, agents’ success rates were similar (29.9% without Prismata vs. 26.6% with Prismata).
- Works broadly without extra help from websites: Prismata doesn’t need special labels from developers. By analyzing the page’s structure, it can usually detect and contain untrusted areas.
- Rare “hard” cases: The team checked 1,500+ popular sites and 90,000+ untrusted content samples. Only about 1.2% of untrusted content sat on the “critical path” to a clickable item. After combining their techniques, about 0.1% of paths remained tricky; using standard web best practices brought this down to ~0.017%.
Why this matters:
- It shows that a system-level, least-privilege approach can protect web agents against many kinds of hidden prompts — even adaptive ones — without heavily sacrificing normal performance.
Why is this important?
- Protects your privacy and accounts: Stops agents from being tricked into leaking credit cards, sending DMs, changing account settings, or doing other unsafe actions.
- Scales to the real web: It doesn’t rely on each website adding special security tags, so it can help on the “long tail” of sites.
- Moves beyond model-only defenses: Instead of hoping the AI model resists every trick, Prismata builds practical guardrails into how the agent sees and acts on the page.
Final takeaway: What could this change?
If web agents are going to handle everyday tasks for people — shopping, booking, researching — they must be safe around user posts, ads, and other untrusted content. Prismata shows a promising way to do that: give agents only what they need to see and only what they need to do, based on the user’s task and the page’s structure. This could help make future AI-powered browsing much safer, without needing every website to redesign itself.
Knowledge Gaps
Below is a concise, actionable list of the paper’s unresolved knowledge gaps, limitations, and open questions that future work could address:
- Residual Case 3 risk: How to detect and mitigate cases where attacker content lies on the critical path with no preceding structural cues; can we algorithmically synthesize missing cues or redesign gating to be injection-free in these paths?
- Structural cue reliability: To what extent can headings, ARIA attributes, and class names be spoofed or absent, especially in third-party/hosted content; how can cue provenance be authenticated (e.g., origin-aware cues, signed templates, CSP-based provenance)?
- Assumption of benign-site best practices: What happens when sites lack strong CSPs, sandboxed iframes, or sanitization; can Prismata degrade gracefully or compensate when these protections are missing or misconfigured?
- Formal guarantees: Beyond the informal argument, can Prismata’s security be formalized (e.g., non-interference or integrity guarantees) with machine-checked proofs and quantified worst-case bounds on mislabeling and privilege escalation?
- Applicability to multimodal agents: How to extend DOM-based least privilege to screenshot-only or multimodal agents (VLAs), preserving fine-grained labels and occlusions in pixel space without reintroducing prompt-injection channels?
- Browser and platform diversity: Do DOM/AxTree differences across browsers (Chromium vs. WebKit/Gecko), mobile web, and accessibility engines affect labeling accuracy and enforcement correctness?
- Modern web features: How to handle Shadow DOM, Web Components, virtualized lists, dynamic IDs, canvas/SVG-heavy UIs, and event delegation, where actionable semantics may not be evident in traditional DOM ancestry?
- Critical-path manipulation: Can attackers force goal actions into untrusted subtrees (e.g., hosted templates with purchase widgets) or exploit ancestor event handlers to subvert capability assignment; what countermeasures are effective?
- Tasks requiring interaction in untrusted regions: When a task legitimately requires writes in user/hosted-party content (e.g., responding to a marketplace seller), how to define and enforce safe micro-actions without enabling exfiltration?
- Policy derivation ambiguities: How to define “task-required” privileges when user instructions are vague, composite, or open-ended; what principled algorithms determine minimal sufficient privileges, with clear conflict resolution and override protocols?
- Closed action-space assumption: Many real agents can run arbitrary JavaScript, call OS tools, or load plugins; how can Prismata’s confinement extend to these richer action spaces and prevent bypass via non-DOM channels?
- Non-element-target leakage: Can navigation, URL parameters, search queries, and allowed text inputs be abused for data exfiltration within permitted capabilities; systematic analysis of such channels is missing.
- Performance and cost: What is the latency, throughput, and monetary cost of per-element LLM gating at web scale (long pages, SPAs, infinite scroll); which caching/incremental strategies provably bound overhead while preserving security?
- Privacy implications: How to prevent leaking sensitive DOM content to remote LLMs during labeling; can on-device models, redaction, or secure enclaves be used without harming accuracy?
- Robustness to adaptive attacks: How vulnerable are the labeling/policy models to multi-round adversaries and red-team jailbreaks; can abstention, ensembles, or adversarial training improve worst-case robustness?
- Internationalization and accessibility: How well do labeling and cues generalize to non-English/RTL languages, locale-specific UI conventions, and diverse accessibility patterns; what data or prompts are needed to maintain accuracy?
- Visual deception and layout tricks: Can CSS overlays, z-index traps, or clickjacking-like patterns cause mismatches between visual affordances and DOM paths; how to reconcile visual and DOM-based semantics in the gate?
- Authentication flows and cross-origin iframes: How to safely support OAuth popups, 2FA, CAPTCHAs, and embedded payment frames that are necessary for tasks yet cross origin boundaries that Prismata may prune or restrict?
- Session/memory contamination: How to ensure injected content never reaches the agent’s long-term memory across steps/tabs; are there scenarios where legacy memory contains unfiltered content that influences future decisions?
- Interaction with model-level defenses: What are principled methods to compose Prismata with model-level guardrails; when and how do combined defenses yield additive or multiplicative security benefits?
- Developer guidance and tooling: Which concrete HTML patterns and cues reduce residual risk to 0.017%; can linters, build-time checkers, or template libraries automatically insert or verify structural cues?
- Failure recovery and UX: How should users override over-restrictive blocks; what explanations, logging, and human-in-the-loop workflows minimize utility loss without creating bypass channels?
- Comparative and ablation studies: How much does each component (action gate vs. Biba parsing vs. enforcement) contribute; how does Prismata compare to other system-level approaches (e.g., CaMeL) on data-dependent tasks?
- Clipboard, file, and download channels: Are uploads, downloads, clipboard access, drag-and-drop, or print dialogs within the action space; what enforcement is needed to prevent covert channels through these vectors?
- Provenance of cues inside untrusted content: If class/ARIA attributes within untrusted regions are attacker-controlled, how does Prismata avoid trusting them; can provenance tagging or DOM taint tracking differentiate developer-authored vs. attacker-supplied cues?
- Shadow-boundary traversal: How to compute critical paths across shadow roots and slots where conventional ancestry is encapsulated; can standardized APIs expose safe structural metadata for labeling?
- Real-world external validity: Beyond WebArena/WASP, how does Prismata perform on live, diverse sites (news, banking, government, social media), under real network conditions, cookie banners, paywalls, and A/B tests?
- Reproducibility and datasets: Releasing code, site samples, DOM annotations, and measurement protocols would enable independent verification and longitudinal tracking of residual risk and utility trade-offs.
Practical Applications
Practical Applications of Prismata’s Findings, Methods, and Innovations
Prismata proposes a contextual least-privilege defense for autonomous web agents that confines both what an agent can see and what it can do, via dynamic trust derivation (action gating + Biba-style parsing) and mechanical confinement enforced at the DOM/accessibility-tree boundary. The following applications map these contributions to actionable use cases across industry, academia, policy, and daily life.
Immediate Applications
- Secure agent middleware for enterprise web automation (software; finance; healthcare; HR)
- Application: Deploy Prismata-like middleware between existing web agents and browsers to prevent credential exfiltration, unintended account changes, and out-of-scope actions in workflows such as expense processing, invoice approvals, benefits enrollment, and HR portal updates.
- Tools/products/workflows: “Agent Firewall” SDK for Playwright/Selenium; BrowserGym adapter; task-scoped capability gating that builds an element-ID-to-capability map and audits rejected actions.
- Assumptions/dependencies: Closed action space (no arbitrary JS execution); access to rendered DOM/AxTree; sites follow basic XSS/CSP/safeframe practices; tasks are expressed clearly enough for policy derivation; text-centric modality.
- Consumer browser extension for safe shopping bots (e-commerce; finance; daily life)
- Application: A “Prismata Shield” extension that allows personal shopping assistants to compare products and complete purchases without interacting with risky elements (e.g., direct messages, password resets) and with reviews restricted to read-only.
- Tools/products/workflows: Extension intercepts page capture, applies action gating + Biba parsing, redacts untrusted content, and disables dangerous buttons; lightweight per-site audit panel.
- Assumptions/dependencies: Availability of accessibility attributes and structural cues for reliable parsing; sandboxed ads; user consent for limited utility trade-offs.
- Data Loss Prevention (DLP) layer for web agents (software; security; compliance)
- Application: Prevent agents from leaking sensitive information (credentials, PII) into untrusted page regions or third-party widgets; enforce “no-write-up” and “read-only” on untrusted subtrees.
- Tools/products/workflows: Policy engine that prunes external/user/hosted-party content for tasks that don’t require it; centralized logs for compliance audits (PCI, HIPAA, SOC2).
- Assumptions/dependencies: Deterministic enforcement before agent actions; organizational policy mapping (which origins are allowed per task); site provenance is inferable.
- Safe deep-research mode for knowledge workers and academics (academia; software; education)
- Application: Use Prismata in “deep research” workflows to restrict interactions to reading and navigating while blocking data entry and posting on untrusted embeds, forums, and social channels.
- Tools/products/workflows: Research assistant configured with read-only capabilities on user-generated content; integration with WebArena/BrowserGym for reproducible experiments.
- Assumptions/dependencies: Labeler models are reasonably accurate; acceptable reduction in interactivity on dynamic sites; task policy separates reading vs. writing clearly.
- Security benchmarking and CI for agent platforms (academia; software/security)
- Application: Adopt XSP as a standardized class of web-agent attacks and integrate Prismata into test harnesses to measure attack success under adaptive injections.
- Tools/products/workflows: CI pipeline with WASP + WebArena scenarios; regression tests that assert attack success stays below threshold and benign utility remains acceptable.
- Assumptions/dependencies: Access to representative attack templates; repeatable headless runs; stable DOM snapshots for caching.
- Web development guidance to reduce residual risk (software/web dev; policy)
- Application: Developer linting and guidelines that add early structural cues (headings, aria-labels, descriptive class names) to precede user-generated content, reducing Case 3 (no-cue) paths.
- Tools/products/workflows: ESLint-style DOM provenance linter; design system components with explicit origin tags; accessibility checkers extended with “trust boundary” hints.
- Assumptions/dependencies: Teams adopt accessibility and semantic HTML best practices; minimal layout refactoring needed.
- Customer support automation with constrained privileges (software; telecom; SaaS)
- Application: Allow agents to navigate help centers, initiate cancellations, request refunds, or schedule callbacks, while disabling editing of sensitive account settings unless explicitly in-scope.
- Tools/products/workflows: CRM-side agent gateway applying Prismata policies; per-task allowlists (developer origin only) for state-changing actions.
- Assumptions/dependencies: Clear task intents; support portals that separate user content from actionable controls.
- Read-only scraping and monitoring bots (software; data; compliance)
- Application: Configure bots to collect data from marketplaces, portals, and forums without leaving posts, ratings, or messages that could be adversarially induced.
- Tools/products/workflows: Read-only mode enforced via capability downgrades; provenance-aware scraping that excludes external/ad widgets.
- Assumptions/dependencies: Tolerance for reduced coverage on sites with poor structural cues; reliance on textual DOM rather than image-based extraction.
- Campus and enterprise portal assistants (education; HR; daily life)
- Application: Assist with course registration, benefits selections, or appointment scheduling while blocking cross-site prompts embedded in announcements or community posts.
- Tools/products/workflows: Institution-distributed agent wrapper; task templates with policy model specifying required origins (usually developer-only).
- Assumptions/dependencies: Portals have distinct sections for UGC vs. administrative actions; accessibility-tree stability.
- Government service navigation (public sector; daily life)
- Application: Aid citizens in booking appointments, filing forms, or checking status while confining interactions to the official components of the site.
- Tools/products/workflows: Agent middleware at the agency browser stack; audit trails for rejected actions.
- Assumptions/dependencies: Government portals maintain robust separation of content origins; secure embedding of third-party widgets.
Long-Term Applications
- Browser-native agent security sandbox (software; standards)
- Application: Integrate Prismata-like least-privilege controls into Chromium/Firefox to provide OS-level guardrails for any agent using the browser’s action interface.
- Tools/products/workflows: Browser APIs for action gating; native DOM provenance channels; policy hooks in DevTools.
- Assumptions/dependencies: Vendor adoption; standardized capability model; performance overhead kept low at scale.
- Web standards for provenance and trust cues (policy; standards; software)
- Application: W3C/WHATWG specifications introducing optional provenance attributes and trust-boundary markers to assist automated labeling and Biba-style confinement.
- Tools/products/workflows: New HTML attributes (e.g., origin-provenance, trust-boundary); accessibility guidelines updated to include security cues; validators in CI.
- Assumptions/dependencies: Cross-ecosystem agreement; backward compatibility; developer tooling support.
- Cross-modal extension to vision-language agents (software; robotics; accessibility)
- Application: Generalize DOM-based permissions to screenshot/vision contexts by aligning bounding boxes with interactable elements, enabling defense against image-based prompt injections.
- Tools/products/workflows: Screenshot-to-DOM alignment pipeline; VLM-aware capability gating; read-only overlays in UI automation.
- Assumptions/dependencies: Robust DOM-to-pixel mapping; VLM reliability; mitigation of adversarial images.
- “Agent OS” with unified capability management across tools (software; enterprise)
- Application: A runtime that enforces least privilege for web actions, file I/O, messaging, and API calls, with composable policies per task and tenant.
- Tools/products/workflows: Capability registry; cross-tool policy composer; auditable enforcement layer; per-action receipts.
- Assumptions/dependencies: Tool vendors expose closed, hookable action interfaces; identity and policy federation.
- Security certification and insurance for agent platforms (policy; finance; industry)
- Application: Create certification schemes that quantify XSP resilience and benign utility loss, enabling risk-based premiums and procurement requirements.
- Tools/products/workflows: Standardized benchmarks (WASP/WebArena); audit artifacts; disclosed residual-risk metrics (e.g., Case 3 rate).
- Assumptions/dependencies: Neutral test bodies; accepted metrics; mapping to regulatory frameworks (e.g., GDPR, HIPAA).
- Ad tech and embed compliance programs (advertising; software; standards)
- Application: Safeframe and CSP conformance badges for ad networks and third-party widgets that minimize agent exposure and aid provenance labeling.
- Tools/products/workflows: Automated scanners; compliance registries; page builders that warn on non-sandboxed embeds.
- Assumptions/dependencies: Industry alignment; economic incentives for compliance; browser-enforced sandbox defaults.
- Secure financial and healthcare autopilots (finance; healthcare; daily life)
- Application: Task-scoped agents for bill pay, claims filing, appointment management, and benefits changes that confine actions to trusted site controls while reading required user content safely.
- Tools/products/workflows: PII-aware policies; escalation workflows requiring explicit user approval for high-risk actions (e.g., password changes).
- Assumptions/dependencies: Strict separation of content origins on portals; strong auditability; alignment with HIPAA/PCI requirements.
- Autonomous procurement across marketplaces (enterprise; supply chain)
- Application: Agents that compare vendors, place orders, and manage returns while avoiding interactions with seller-hosted content beyond read-only reviews/specs.
- Tools/products/workflows: Marketplace adapters; procurement policy templates; exception handling for ambiguous provenance.
- Assumptions/dependencies: Reliable structural cues across marketplaces; tolerable utility trade-offs; approvals for state-changing actions.
- Enterprise agent governance integrated with identity/MDM (software; IT)
- Application: Centralized orchestration of task policies, least-privilege profiles, and per-team allowlists, enforced across agent fleets.
- Tools/products/workflows: Policy-as-code repo; integration with SSO/MDM; telemetry for rejected/allowed actions.
- Assumptions/dependencies: Organization-wide policy discipline; unified observability; cross-platform agent hooks.
- Developer libraries and SDKs for provenance-aware UIs (software; web dev)
- Application: UI components that embed origin metadata, trust-boundary markers, and accessible semantics to make pages “agent-friendly” by design.
- Tools/products/workflows: “DOM Biba Parser” library; React/Vue component kits; build-time validators.
- Assumptions/dependencies: Adoption in design systems; training for teams; balancing developer productivity with security cues.
- Academic research lines and benchmarks (academia)
- Application: Formal models, empirical studies on the Web Entanglement Problem, cross-modal defenses, and adaptive attack generation frameworks.
- Tools/products/workflows: Public datasets of DOM structures and attack placements; reproducible evaluation pipelines; proof tooling for confinement properties.
- Assumptions/dependencies: Community-maintained benchmarks; funding for longitudinal studies; openness of agent vendors to collaborative testing.
Notes on feasibility and constraints:
- Prismata’s guarantees rely on textual DOM/AxTree visibility, a closed agent action space, and sites that already mitigate classical XSS. Within-scope persuasion attacks (e.g., biased reviews when reading reviews is required) remain a model-level challenge.
- Mechanical confinement may reduce utility on highly dynamic or poorly structured sites; developer adoption of structural cues (accessibility, semantic HTML) improves reliability and reduces residual risk.
Glossary
- Accessibility attributes (ARIA): HTML attributes that improve accessibility and expose semantic information (e.g., labels) to assistive technologies and tooling. "accessibility attributes (aria-label="Customer Reviews")"
- Accessibility tree (AxTree): A browser-exposed tree reflecting the accessible representation of the page used by assistive technologies and agents. "the accessibility tree (AxTree) to reduce the verbosity of the restricted observation."
- Action gate: A per-element decision mechanism that determines whether an action is within task scope before allowing interaction. "the action gate's decision is injection-free"
- Biba integrity model: A classic integrity model enforcing no-read-down and no-write-up to prevent information contamination from lower-integrity sources. "Inspired by the 1977 Biba integrity model"
- Biba parsing: A parsing strategy that applies Biba’s no-read-down/no-write-up constraints to label content origins along DOM paths. "Biba parsing's decision is injection-free."
- BrowserGym: A framework that runs web agents in a controlled browser environment and exposes structured page observations. "Prismata builds on BrowserGym"
- Chrome DevTools: Browser instrumentation that provides metadata and interfaces for inspecting and interacting with page elements. "and Chrome DevTools metadata"
- Closed action space: A constrained set of allowable actions that an agent can perform, preventing arbitrary code execution. "The agent's action space is closed"
- Content security policies (CSP): Browser-enforced policies that restrict what resources can be loaded or executed to mitigate web attacks. "content security policies"
- Cross-Site Prompting (XSP): An agent-side analogue of XSS where prompt injections on benign sites manipulate a victim’s web agent. "We call the agent-side analogue Cross-Site Prompting (XSP)"
- Cross-Site Scripting (XSS): A web attack where malicious scripts injected into benign sites execute in the victim’s browser. "Cross-Site Scripting (XSS) allows malicious scripts injected into a benign website to execute in a victim's browser."
- Critical path (DOM): The sequence of ancestor nodes from the DOM root to a target element, providing structural context for decisions. "a critical path from the root of the Document Object Model (DOM) to that element."
- Document Object Model (DOM): The hierarchical representation of a web page’s structure that scripts and tools can traverse and manipulate. "Document Object Model (DOM)"
- Dynamic trust derivation: A process that infers content provenance and permissions on-the-fly based on structural cues and task context. "Prismata's dynamic trust derivation produces permission labels for page content"
- Headless Chromium: A browser mode without a visible UI, used for automated or programmatic browsing by agents. "headless Chromium browser"
- Least privilege: A security principle granting only the minimal capabilities necessary to accomplish a task. "contextual least privilege"
- Mechanical confinement: Deterministic enforcement that redacts content and restricts capabilities before the agent observes or acts. "Prismata's mechanical confinement enforces these labels"
- No-read-down, no-write-up policy: An integrity rule preventing reading from lower-trust sources and writing to higher-trust contexts. "we apply a no-read-down, no-write-up policy"
- Playwright: A browser automation library used to drive and interact with web pages in testing and agent environments. "BrowserGym uses Playwright to drive the live Chromium page"
- Prompt injection: Malicious instructions embedded in content that aim to manipulate an LLM or agent’s behavior. "via prompt injection."
- Sandboxed iframes: Isolated embedded browsing contexts with restricted capabilities to contain untrusted code. "Any attacker-supplied JavaScript is confined to sandboxed iframes"
- Structural cues: Developer-provided indicators (e.g., headings, ARIA labels, class names) that signal content boundaries or provenance. "structural cues that signal the boundary of untrusted content"
- Trust label: A provenance annotation assigned to content or elements indicating their origin and allowed capabilities. "The trust label assigned to element is injection-free"
- Web entanglement problem: The challenge that security meaning depends on site structure intertwined with untrusted content, complicating policy derivation. "We refer to this as the web entanglement problem"
- WebArena: A benchmark environment for evaluating web agents and their robustness to attacks. "in the WebArena environment"
- WASP (benchmark): A benchmark/stress test suite for evaluating web-agent security and behavior under adversarial conditions. "WASP plain-goal success"




