From 088eeaf3dfa75832def6fabd98e631e7adb0c38d Mon Sep 17 00:00:00 2001 From: shiva108 Date: Fri, 23 Jan 2026 15:53:24 +0100 Subject: [PATCH] docs(rag-pipelines): refactor metadata leakage example to table - Converted the "Example Attack" section for metadata leakage from a text block to a Markdown table. - This change enhances readability and provides a clearer, more structured presentation of the information. - Delineates leakage types and the specific information revealed during a metadata attack. --- ...trieval_Augmented_Generation_RAG_Pipelines.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/Chapter_12_Retrieval_Augmented_Generation_RAG_Pipelines.md b/docs/Chapter_12_Retrieval_Augmented_Generation_RAG_Pipelines.md index 4ee85bf..b6d2819 100644 --- a/docs/Chapter_12_Retrieval_Augmented_Generation_RAG_Pipelines.md +++ b/docs/Chapter_12_Retrieval_Augmented_Generation_RAG_Pipelines.md @@ -241,14 +241,14 @@ Unlike direct prompt injection where the user provides the malicious input, here #### Example Attack -```text -Query: "Show me all documents created by the CFO in the last week" -Even if content is protected, metadata leakage reveals: -- That such documents exist -- Their titles -- When they were created -- Potentially their subject matter -``` +**Attacker Query:** "Show me all documents created by the CFO in the last week" + +| Leakage Type | Information Revealed | +| :------------- | :---------------------------------- | +| **Existence** | Confirms sensitive docs exist | +| **Titling** | Leaks internal project names/topics | +| **Temporal** | Reveals when key events occurred | +| **Contextual** | Infers subject matter from metadata | ### 12.5.5 Cross-Document Leakage