- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes DualView, a system to tackle indirect prompt injection (IPI) attacks. In particular, rather than traditional IPI the paper focuses on stored IPI. In this scenario attacker controlled content can persist in an agent's environment and thus can later be reintroduced into its contex hijacking the model. DualView addresses this challenge by maintaining separate agent- and human-facing views of the environment, replacing untrusted content with symbols in the agent view while preserving the original content for users and external applications in human view.
Critical strengths
-
The paper identifies a concrete and relevant weakness in Dual LLM setups - in this scenario although Dual LLM configurations can isolate untrusted content while within the agent context. However, if an agent then writes the content into its environment the provenance can be lost and an attack performed.
-
I like that the defence proposed is not model based (e.g. another detector model) nor does it rely on the LLM recognising and blocking malicious instructions. Hence, the defence can be more principled within its bounds. The overall idea of separating agent- and human-facing views that preserve provenance without exposing symbols to end users is a nice approach.
-
The empirical results, particularly the utility-robustness results, show a good trade off in favour of the defence (although the pratical overheads are high). Further, provided the data trust boundaries are correct then the method also gives a marked performance increase over prior works.
Critical weaknesses
-
There is a reliance on manually specified trust boundaries (discussed in the Data trust policy section). With DualView's guarantee only holds if the data trust policy (which needs to be manually defined) correctly identifies all attacker-controlled data. In practical deployment scenario this can make DaulView's performance significantly more configuration dependant than the presented 0% ASR result. In complex real environments things like data provenance can be ambiguous as content moves between things like downloads, shared directories, and third parties.
-
There is a substantial practical overhead - costs can be close to double the baseline setup, and a substantial increase over the baseline Dual LLM setup. Aside from the direct dollar and latency costs when directly using DualView, the system itself is complex: DualView uses two synchronized filesystem views, an SQLite sybol table, desymbolization/resymbolization logic, runtime hooks, U-LLM processing dependancies, Git worktrees, etc. If the claim is for a deployable system the rigour needed for things like a systematic failure-injection analysis is high, and arguably likely out of scope for ICLR.
-
At a higher level, the paper follows in large as a security/systems paper around building a secure agent runtime v.s a ML paper proposing or studying a machine-learning method. Perhaps most compactly, I would describe the contribution as information-flow isolation implemented around a agent's surrounding system. ICLR is a broad conference, but may not be the ideal venue fit. I do think there is ML-agentic contributions, for example to which extent an LLM can operate effectively if useful environmental information is replaced by opaque handles. Hence, the utility experiments are therefore relevant to broader ML contributions, but they are not the paper's focus.
Questions for authors
No specific questions: see weaknesses for general points.