RAG cache or fresh retrieval ignores revoked access
A new retrieval or cache response exposes protected content after its applicable permission revocation has taken effect.
Candidate CWE: CWE-863
Test hypothesis#
Retrieve a shared synthetic document as A; revoke its share, wait the documented sync interval, then compare fresh and existing conversations plus cold/warm caches. Verify direct access denial in the same state.
Evidence required#
Share/revocation timestamps, sync policy, cache warm sequence, effective identity and newly delivered protected content.
Rule out false positives#
Content already delivered before revocation, intended transcript retention and behavior inside a documented sync window need separate interpretation.
Playbook and command references#
- RAG isolation: ingestion, retrieval, citations and revocation — Trace document authorization through vector search, generated answers, citation downloads, caches and sharing changes.
- Object, function, and property authorization — Turn identities, tenants, objects, roles, and lifecycle transitions into a reproducible permission matrix.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.