What problem does it solve?
AI systems built on LLMs expose sensitive data through prompt leakage, training data memorization, unsecured vector databases, and poisoned RAG knowledge bases, and security teams lack a structured methodology to assess these risks.
Core Features & Use Cases
- Layered Attack Surface Coverage: Organizes testing across application layer (system prompt leakage, API information disclosure, PII theft), model layer (training data extraction, membership inference, model inversion), and deployment layer (RAG poisoning, vector database access control, cache and log leakage).
- Concrete Attack Techniques: Provides step-by-step procedures including prefix completion and divergence attacks for training data extraction, shadow model and loss-based membership inference, malicious document construction and embedding manipulation for RAG poisoning, and vector database traversal.
- Detection Checklist: Ships a ready-to-use checklist covering prompt leakage, endpoint exposure, multi-tenant context isolation, RAG poisoning resistance, and vector database authentication.
- Use Case: During a red team assessment of a customer-facing LLM chatbot, use this methodology to probe whether the model regurgitates training data, whether the RAG knowledge base can be poisoned via public sources, and whether the Milvus vector store is exposed without authentication.
Quick Start
Ask the AI to assess an LLM application for data security risks covering prompt leakage, training data extraction, membership inference, RAG poisoning, and vector database exposure using this methodology.