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

Security Lab

Each test runs through the real pipeline against an isolated copy of the library that adds synthetic protected records (with canary strings) and a poisoned document. A test passes only when the control actually held; the evidence for every result is shown. Nothing outside this application is attacked.

Deterministic, no model calls, a few seconds.

Live model challenge

Sends one attack to the configured model with synthetic canaries in its instructions and reports whether the model itself leaked them, before Secure-RAG's output checks.

Controls under test

ControlWhat it doesTests
Server-side identity and authorisationRole, department and clearance come from the server, not the request; documents are filtered before search.ACL-01, ACL-02
Question injection checkDirective patterns aimed at the assistant block the request before retrieval.INJ-01, EXF-01, POL-01, SYS-01, BEN-01
Passage quarantineRetrieved passages carrying instructions never reach the model.INJ-02
Answer checksCitations must be retrieved sources; canaries, secrets and personal data are redacted.CIT-01, OUT-01
Input redactionEmails, keys, TFN and ABN (checksum), BSB, Medicare, cards (Luhn), phone numbers.PII-01
Hash-chained auditEvery request, block, quarantine and test is recorded; tampering is detectable.Audit trail

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