Loading...
RAG System Poisoning
RAGPInjection of malicious documents or data into Retrieval-Augmented Generation (RAG) knowledge bases to poison retrieved context and manipulate agent responses.
Example Scenario
Inserting documents with embedded malicious instructions into a RAG knowledge base, designed to rank highly for common queries and inject harmful directives when retrieved by the agent.
Testing Objectives
- Test document validation
- Assess retrieval integrity
- Evaluate source verification
- Validate embedding security
Defensive Strategies
- Document validation and sanitization
- Source authentication
- Retrieval result verification
- Embedding integrity checks
- Access controls on knowledge bases
Key Features
- Knowledge base document poisoning
- Retrieval result manipulation
- Vector embedding corruption
- Search result injection
Use Cases
- RAG security testing
- Knowledge base integrity assessment
- Retrieval validation
- Document verification testing
Tools & Frameworks
Security Risks
Ethical Guidelines
- •Only test RAG systems with authorization
- •Never poison production knowledge bases
- •Report RAG vulnerabilities promptly
- •Focus on improving retrieval security
- •Consider downstream impact of poisoned knowledge
Remember: This information is for educational and defensive security purposes only. Always ensure you have proper authorization before testing any techniques.
From the engineer behind this catalog
Get your agent system red-teamed
The attacks documented here work on production agent systems every day. Have yours tested before someone else does: prompt injection, jailbreaks, tool misuse and data exfiltration, with every finding written up next to its fix.
€750 instead of €1,500, one week, written report and walkthrough call, until 30 September