From rag-security
Test that retrieval enforces per-user / per-tenant authorization so one user cannot retrieve another's documents through the RAG system. Use on an authorized multi-tenant or multi-user RAG app to validate access control on retrieval.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rag-security:vector-store-isolation-testThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Evidence on whether the retrieval layer leaks documents across users/tenants —
Evidence on whether the retrieval layer leaks documents across users/tenants — the highest-impact RAG confidentiality failure (OWASP LLM08 / LLM02).
A results table: case · result · leaked element · evidence · mitigation
(authorize-then-retrieve, per-tenant namespaces, server-side ACL enforcement).
Confirmed leaks → security-reporting:finding (rate severity high+).
Authorization must be enforced on the server at retrieval time and tied to the authenticated caller — never trust a client-provided tenant/filter. Test the metadata/citation path too; it leaks even when document bodies are withheld.
npx claudepluginhub jassics/awesome-claude-security --plugin rag-securityProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.