GO TO A SECTION

↑ ↓ to navigate · Enter to openExplore all sections →
FDEInterviews logo
← AI Security, Privacy & Governance / 34
hardOpenAIGleanMicrosoft

Write the incident runbook for a data-leak-via-model event: the assistant showed one customer's data to another.

Cross-tenant or cross-user data exposure through a model is the breach that starts regulatory clocks. The runbook has to answer 'whose data, to whom, how many' from logs that most teams never designed for, and contain a leak that may live in a cache or a fine-tuned model, not a deploy.

Updated Aug 2026 · Grounded in real Forward Deployed Engineer interview loops and written to a senior-engineer editorial bar.

Cross-tenant or cross-user data exposure through a model is the breach that starts regulatory clocks. The runbook has to answer 'whose data, to whom, how many' from logs that most teams never designed for, and contain a leak that may live in a cache or a fine-tuned model, not a deploy.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 548 remaining answers · ₹2,000 / $25

Every answer, concept and course, every paper breakdown, all published video lessons, hands-on FDE Lab missions, Premium PDF guides and companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.

6 months · One payment · No auto-renewal

Study alongside free video lessons.

Keep practising

Next in this trackA customer's CISO wants to see your AI risk management mapped to the NIST AI RMF. How do you operationalize it?PremiumNext in this trackThreat-model a multi-agent system where agents call each other. Where are the trust boundaries and how does one compromise spread?PremiumNext in this trackDesign a fully on-premise diarization and summarization pipeline for sensitive meeting recordings that provably does not retain transcriptsPremium
FEDITOR'S NOTE

This is narrower than the general AI-incident question on purpose: the harm class is confirmed data exposure, so notification clocks dominate the timeline and the forensic question is 'reconstruct disclosure scope from the audit trail.' The instant-fail is treating it as a quality bug and tuning prompts while the GDPR 72-hour clock runs. The senior move is naming the leak source taxonomy (retrieval ACL gap, shared cache, fine-tuned weights, log exposure) because the containment and the can-we-even-fix-it answer differ completely across them, and being honest that a leak baked into weights is not deletable.

DISCUSSION · 0

No comments yet — be the first to share your approach.