reduce-prompt-leak changedtest-and-evaluate/strengthen-guardrails/reduce-prompt-leak

Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here 21 Oct 2026 19:37 UTC

Lines+5added

Lines−5removed

From line 4 where the diff opens

First seen 14 Aug 2026 this site's first read of the page

Recorded edits2to this page, all time

The whole hunk

from line 4, old and new numbered

lines

from line 4

44description: Reduce the risk of prompt leaks by separating context from user queries, filtering Claude's outputs, and auditing prompts, without degrading task performance.

55---

7Prompt leaks can expose sensitive information that you expect to be "hidden" in your prompt. While no method is foolproof, the strategies below can significantly reduce the risk.

7Prompt leaks can expose sensitive information that you expect to be "hidden" in your prompt. Although no method is foolproof, the following strategies can significantly reduce the risk.

99## Before you try to reduce prompt leak

1010

11Consider using leak-resistant prompt engineering strategies only when **absolutely necessary**. Attempts to leak-proof your prompt can add complexity that may degrade performance in other parts of the task due to increasing the complexity of the LLM’s overall task.

11Consider using leak-resistant prompt engineering strategies only when **absolutely necessary**. Attempts to leak-proof your prompt can make the LLM’s overall task more complex, which might degrade performance in other parts of the task.

1212

1313If you decide to implement leak-resistant techniques, be sure to test your prompts thoroughly to ensure that the added complexity does not negatively impact the model’s performance or the quality of its outputs.

1414

1515<Tip>

16 Try monitoring techniques first, like output screening and post-processing, to try to catch instances of prompt leak.

16 Try monitoring techniques first, such as output screening and post-processing, to try to catch instances of prompt leak.

1717</Tip>

1818

1919***

from line 53

5353 <Note>

5454 You can also use a prompted LLM to filter outputs for more nuanced leaks.

5555 </Note>

56* **Avoid unnecessary proprietary details:** If Claude doesn't need it to perform the task, don't include it. Extra content distracts Claude from focusing on "no leak" instructions.

57* **Regular audits:** Periodically review your prompts and Claude's outputs for potential leaks.

56* **Avoid unnecessary proprietary details:** If Claude doesn't need it to perform the task, don't include it. Extra content reduces Claude's adherence to "no leak" instructions.

57* **Audit regularly:** Periodically review your prompts and Claude's outputs for potential leaks.

5858

5959Remember, the goal is not just to prevent leaks but to maintain Claude's performance. Overly complex leak-prevention can degrade results. Balance is key.

6060