A community print-coop knowledge base still contains workshop rosters with emails. A public kiosk can retrieve them. Which problem is that, and what is the fix?
Select an answer to reveal the explanation.
Short Explanation
Think of workshop rosters with emails sitting in the knowledge base, retrievable from a public kiosk. That is insecure RAG. Scrub or restrict the store, not just the prompt template.
Full Explanation
Secure RAG requires governing PII inside the retrieved corpus, not only in the visible prompt. Workshop emails in the store are a leak path. A template tweak, treating the leak as a feature, and a dashboard do not scrub the store.