New Cheat Sheet: RAG Security#2131
Open
razashariff wants to merge 2 commits intoOWASP:masterfrom
Open
Conversation
Contributor
Author
|
Hi @mackowski -- just checking if this is ready for review or if there's anything you'd like changed before looking at it. Happy to adjust. Thanks |
Collaborator
|
@razashariff it is ready for review but we need some time to review it ;) |
Contributor
Author
|
Thanks @mackowski. Just wanted to make sure nothing was blocking on my side. The Secure Coding with AI one (#2132) was also revised based on Jim's feedback. Cheers, Raza |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #2126.
Thanks @mackowski for approving and assigning this one — here it is.
RAG is now standard architecture for enterprise AI but introduces a unique attack surface distinct from both traditional web vulnerabilities and standalone LLM risks. This covers the topic practically with a first-approach focus that I hope will help our community immensely.
14 sections covering the complete pipeline from document ingestion through to output validation:
Each section has practical Do/Don't guidance. Happy to iterate on feedback.
I have also built DVRAG (Damn Vulnerable RAG Pipeline) as a companion training tool — a deliberately insecure RAG system with 25 vulnerabilities mapped to each section of this cheat sheet. Practitioners can use it to understand and test each attack vector hands-on. Happy to share details if useful for the community.
Thanks again — Raza Sharif :)