Case 1BF529 · AI security · L2 Practitioner
The Assistant Knows Everyone's Salary
Live alertAn intern asks the new internal AI assistant about pay bands and gets a table of named employees' salaries. The RAG index was built by a service account that can read the whole HR SharePoint site.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Cause: ingestion used an over-privileged account and retrieval ignored source permissions; the model just repeated the chunks.
- Impact: personal data exposed internally; treat it as a privacy incident and assess DPDP or GDPR notification duties.
- Contain: remove HR sources from the index or pause the assistant; preserve query and retrieval logs to see who else saw what.
- Fix: enforce the asking user's permissions at retrieval with ACL-aware filters, keep ACLs synced, and scope ingestion.
- Often oversharing at source: AI search surfaces files that "everyone" links already exposed but nobody had found.
If the interviewer pushes back
- The vendor says its assistant "respects permissions". What tests would you run before you believe it?
- How do ACL changes in the source, like a fired employee or a moved file, reach the vector index, and how fast?