Learning pathsPricingChecking sign-in…
← ML curriculum

AISD-008 · DESIGN PRACTICE

Practice: Production AI safety, security and governance

Draft the complete decision system before revealing the guidance. Use a 45-minute rehearsal budget and adapt it to the interviewer’s direction.

Preserve eligibility, available-at-decision inputs, mature labels, bounded work and compatible releases. Explain alternatives and test a normal, boundary and failure case.

Your practice draft

Design a production security and governance architecture for a multi-tenant RAG assistant with tools that can read private records and perform approved actions. Explain trust boundaries, direct/indirect prompt injection, data exfiltration, policy enforcement, privacy, auditability, governance, incident response and measurable security tests.

Saved locally on this device. The worked answer does not score your draft. Existing lesson notes and completion are separate.

Progressive hints

Hint 1

Start with assets, actors, trust boundaries and security invariants.

Hint 2

Separate model proposals from deterministic policy decisions.

Hint 3

Authorize before private document hydration and before every side effect.

Hint 4

Treat retrieved content and tool output as untrusted data.

Hint 5

Bind approvals to canonical payload hashes and use idempotency.

Hint 6

Trace policy decisions while minimizing raw sensitive payload capture.

Hint 7

Test adversarial scenarios and assert that forbidden data never crosses boundaries.

Self-review evidence

For each criterion, record Missing, Prompted, Independent or Adaptive reasoning. No automated scoring or offer prediction is provided.

  • Trust boundaries and attacker capabilities are explicit.
  • Model output never grants identity, permissions or tool authority.
  • RAG authorization occurs before sensitive content hydration.
  • Direct and indirect prompt injection are treated as untrusted input.
  • Outbound data and destinations are constrained independently of the model.
  • Tool execution validates schema, object scope, approval and idempotency.
  • Privacy controls cover prompts, embeddings, caches, logs and deletion.
  • Audit events record policy version, actor, resource, decision and outcome without raw secrets.
  • Policy outages fail closed for sensitive operations.
  • Adversarial tests assert no unauthorized data exposure or side effects.
Reveal worked design guidance

Authenticate the principal and derive tenant scope from trusted identity. Label user, retrieved and tool content as untrusted. Enforce deterministic policy before sensitive retrieval hydration and again before tool execution. Minimize and redact context before model egress. Validate model outputs and typed tool arguments. Use least-privilege capabilities, explicit approval bound to the canonical action hash, destination allowlists and idempotency. Record minimized append-only audit events correlated with distributed traces. Propagate retention and deletion to all derived stores. Test injection, cross-tenant access, revocation, exfiltration, approval replay and policy outages with synthetic fixtures.

Open the complete worked design in a new tab →

The new tab keeps this draft visible. Save it on this device before closing the page.