Case 1BF529 · AI security · L2 Practitioner

The Assistant Knows Everyone's Salary

Practise as: Incident drillLevel: L2 Practitioner

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.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Cause: ingestion used an over-privileged account and retrieval ignored source permissions; the model just repeated the chunks.
  2. Impact: personal data exposed internally; treat it as a privacy incident and assess DPDP or GDPR notification duties.
  3. Contain: remove HR sources from the index or pause the assistant; preserve query and retrieval logs to see who else saw what.
  4. Fix: enforce the asking user's permissions at retrieval with ACL-aware filters, keep ACLs synced, and scope ingestion.
  5. 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?

More AI security cards

All AI security cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09