Secure-RAG

What do the authoritative sources say, and can we trust the answer?

Chirag Dani · Secure-RAG v3.0.1
Model: huggingface · Semantic search: on · API key: required

Breach Lab

Attack a RAG application the way an insider or outsider would, remember every breach, and prove each fix. Test the built-in pipeline on any workspace, or any external RAG application over HTTP. Each failure becomes a finding; when a replay passes, Secure-RAG issues a hashed Proof-of-Fix Record, and the release gate fails if any high or critical test fails again.

Insider and cross-department leakage
Direct prompt injection
Indirect injection through a poisoned document
Indirect instruction to call a tool
Mosaic leakage (harmless questions combined)
Revoked permission still exposed
Bulk exfiltration request
Imported red-team prompt (from ARA)

Targets (0)

No targets yet. Create one below.

Test the built-in pipeline

Runs the Secure-RAG pipeline on a workspace with planted test records (canary values) and attack documents. Tick "planted weakness" in the configuration to see what a failure and fix look like.

Test an external RAG application

Describe the endpoint, how each test identity authenticates, where the answer is in the response, and which protected values each identity must not see. Internal and private addresses are refused unless the deployment allows them.

Only test systems you own or are authorised to test. Breach Lab sends attack prompts and records masked responses.

Answers come only from the governed library and are decision support, not legal advice. Verify regulatory content against the regulator's current publication.