概述
The closing reminder may reinforce the intended task, but it remains text-based guidance inside the same model context and cannot guarantee that an injection will be ignored.
深入探討
The sandwich defense places untrusted content between an initial trusted task instruction and a closing repetition or restatement of that instruction. For example, a prompt may ask for a summary, insert an external page, and then remind the model to summarize the page rather than follow directions inside it. This is a prompt-template change: it does not modify the model, create a separate data channel, or restrict tool access. It is easy to test, but it should be treated as a heuristic rather than a security boundary. The intuition is that the final reminder may help the model focus on the intended task after reading the untrusted passage. That does not mean models always follow the last instruction, nor that the closing reminder structurally outranks hostile text. A malicious passage may imitate trusted instructions, contain multiple directives, or exploit behavior not covered by the template. The defense can also fail if the untrusted block enters context through another route that the prompt author did not account for. Evidence is model- and attack-dependent. A 2026 preprint tested prompt sandwiching and other prompt-level defenses against domain-camouflaged injection across three model families and three synthetic deployment domains. It found substantial variation by model, and none of the tested prompt-level defenses eliminated the threat across weaker models. The study is limited to its setup; it is evidence against assuming a universal effect, not a complete ranking for every real system. Use sandwiching only as one layer alongside explicit data handling, permission checks on tools, attack testing, and user confirmation for consequential actions. Measure both resistance and task quality before release.
現實世界的實施
A translation prompt gives the task, inserts a user-provided paragraph, then repeats that the paragraph should be translated rather than obeyed.
A document question-answering workflow states the question, includes a retrieved passage, and restates the requested answer format before generation.
A summarizer tells the model to summarize a forum post, places the post in a marked region, then closes by reiterating that post text is source material.
A security test compares a sandwich prompt with a baseline using the same benign and malicious documents across several model versions.
The Future of The Sandwich Defense for Prompts
Prompt-level defenses will remain attractive because they are quick to prototype, but their value will depend on model behavior and the attacks a system encounters. As evaluations improve, teams may get better evidence about when repetition helps. The lasting lesson is to test this pattern within a layered design and retain deterministic limits on what an agent can do. New models may respond differently to the same closing reminder, so validate updates before relying on them. Keep safeguards outside the prompt for consequential actions.
付諸實踐
為什麼這很重要
- 成本與預算. 多年來,架構決策決定著效能和營運成本。
- 更明確的決策. 技術教育幫助團隊選擇正確的堆疊,而不僅僅是最新的堆疊。
- 品質管控. 更好的工程選擇可以減少生產中的可靠性事故。
留意
- 優化一項基準測試可以隱藏更廣泛的系統弱點。
- 基礎設施和維護成本常常被低估。
- 隨著系統變得更加複雜,安全性和可觀察性差距可能會擴大。
後續步驟
- 在實施之前定義延遲、品質和成本目標。
- 在實際負載和資料條件下進行基準測試。
- 儀器監控錯誤、漂移和使用者影響。
- 在擴展之前準備回滾和事件回應路徑。
不斷探索
常見問題
What is The Sandwich Defense for Prompts?
The sandwich defense repeats or restates the trusted task instruction after untrusted content has been inserted into a prompt. The closing reminder may reinforce the intended task, but it remains text-based guidance inside the same model context and cannot guarantee that an injection will be ignored.
三明治防禦將重複的任務指令放在哪裡?
該指南將模式定義為在不可信通道之前和之後的可信任務指令。
結束提醒對這種模式有何幫助?
該指南將提醒描述為可以強化任務的啟發式方法,而不是保證。
夾心對應用程式有何影響?
指南稱,夾心是一種提示範本更改,而不是模型或權限更改。
為什麼三明治防禦不是安全邊界?
該指南解釋說,文字重複不會創建單獨的通道或結構存取控制。
引用的領域迷彩預印本評估了什麼?
該指南描述了預印本的有限設定:三個模型系列、網域和綜合文件。