Skip to content

Lesson 324·M26 AI Security

Human Approval as a Security Control

Open

Learning Objectives

By the end of this lesson you should be able to:

  • Explain the gate: the high-risk actions (L324)
  • Explain the mechanism: the pause and the callback (L208)
  • Explain the design: the least approvals and the clear context (L324)
  • Explain the placement: at the tool (L323)
  • Explain the AI shape: the human gate on the irreversible (L324)

One-Line Definition

The human approval is the highest-value control for the highest-risk actions (L324) — the gate (the high-risk actions: the refund L324, the transfer L324, the delete L324, the external send L324), the mechanism (the pause and the callback: the workflow L277 pauses, the human L208 reviews, the callback L277 resumes, L324), and the design (the least approvals: the low-risk automatic L324, the high-risk gated L324; the clear context: the who, the what, the cost L324) — the last line (L324).

The one-sentence interview answer: "The human approval is the highest-value control (L324). The gate (L324): the high-risk actions (L324) — the refund (L324), the transfer (L324), the delete (L324), the external send (L324) — the irreversible or the expensive (L324). The mechanism (L208): the pause (L208) — the workflow (L277) stops at the approval step (L208), publishes the task (L228) to the human (L324); the human reviews (L324) — the context (L324): who asked, what the action is, what it costs (L324); and the callback (L277) — the human approves or denies (L208), and the workflow (L277) resumes (L324). The design (L324): the least approvals (L324) — the low-risk actions (L324) automatic (L324), the high-risk (L324) gated (L324) — the approval fatigue (L324) avoided (L324); and the clear context (L324) — the approval decision (L324) informed (L324). The AI shape (L173): the agent (L200) with the tools (L315) — the refund, the transfer, the delete (L324) — gated by the human (L324): the L314 agency (L314) and the L323 tool (L323) — with the human as the last line (L324)."

Mental Model

Think of the human approval as the bank's two-key vault. The vault (the high-risk action, L324) needs the two keys (L324): the agent's (L200) and the manager's (the human, L324). The agent (L200) starts the withdrawal (the transfer, L324) — the vault (L324) locks (the pause, L208); the manager (L324) reads the slip (the context, L324) — the amount (the cost, L334), the account (the who, L319) — and turns the second key (the approval, L208) or refuses (L324). The vault opens only with both (L324). The bank designs the two-key rule (L324) for the big withdrawals only (L324) — the small ones (L324) are the teller's (L324). The bank works because the big vault needs the two keys, and the manager's decision is informed (L324).

   the two-key vault (the approval, L324)
   ┌────────────────────────────────────────────────────────┐
   │ the vault (the high-risk, L324) — the refund, the      │
   │ transfer, the delete (L324)                            │
   │ the agent's key (L200) · the manager's key (the        │
   │ human, L324)                                           │
   │ the slip (the context, L324) — the who, the what, the  │
   │ cost (L334)                                            │
   └────────────────────────────────────────────────────────┘

The mental model is the vault: the two keys, and the informed slip (L324).

Visual Flow — One Approval

   the agent's action (L200)
        │  the transfer (L324)
        ▼
   ┌────────────────────── THE GATE (L324) ─────────────────────────────┐
   │  the high-risk (L324)? → the pause (L208)                         │
   │  the low-risk (L324) → the automatic (L324)                       │
   └──────────────────────────┬───────────────────────────────────────┘
                              ▼
   ┌────────────────────── THE PAUSE (L208) ────────────────────────────┐
   │  the workflow (L277) stops (L208)                                 │
   │  the task (L228) published to the human (L324)                    │
   └──────────────────────────┬───────────────────────────────────────┘
                              ▼
   ┌────────────────────── THE REVIEW (L324) ───────────────────────────┐
   │  the context (L324): who, what, cost (L334)                       │
   │  the approve (L208) → the callback (L277) → the resume (L324)     │
   │  the deny (L324) → the workflow stops (L324)                      │
   └──────────────────────────────────────────────────────────────────┘

The flow is the approval: gate → pause → review (L324).

How It Works — The Control, Part by Part

  • The gate (L324). The high-risk actions (L324): the refund (L324), the transfer (L324), the delete (L324), the external send (L324) — the irreversible or the expensive (L324).
  • The mechanism (L208). The pause and the callback (L208): the workflow (L277) stops (L208), the task (L228) published (L324), the human reviews (L324), and the callback (L277) resumes (L324).
  • The design (L324). The least approvals (L324): the low-risk automatic (L324), the high-risk gated (L324) — the approval fatigue (L324) avoided; the clear context (L324): the who, the what, the cost (L334).
  • The placement (L323). At the tool (L323): the high-risk tool (L315) with the approval step (L324) — the boundary (L323) plus the human (L324).

Note

The approval is the last line, not the first (L324). The senior answer layers (L324): the least privilege (L314) and the scoped tools (L323) are the first lines (L324); the human approval (L324) is the last (L324) — for the actions the other controls (L325) can't contain (L324). The design (L324): the low-risk automatic (L324), the high-risk gated (L324) — the approval fatigue (L324) and the automation's speed (L324) balanced (L324).

Real Project Usage

  • A finance agent (L314). The transfer (L324) — the approval (L324) mandatory (L324).
  • A customer support agent (L350). The refund (L324) — the human gate (L324), the replies automatic (L324).
  • An admin agent (L324). The delete (L324) — the approval (L324) before the deletion (L324).
  • A multi-tenant SaaS (L357). The per-tenant approvers (L320) — the tenant's human (L320) gates the tenant's actions (L324).
  • Anything high-risk (L324). The human gate (L324) — the last line (L324).

The through-line: the gate is the irreversible's — the two keys, the informed slip (L324).

Interview Explanation

Say it in four moves:

  1. The gate. "The high-risk — the refund, the transfer, the delete (L324)."
  2. The mechanism. "The pause and the callback (L208)."
  3. The design. "The least approvals, the clear context (L324)."
  4. The placement. "At the tool (L323) — the last line (L324)."

Senior-Level Insights

  • The high-risk is the gate's scope (L324). The irreversible and the expensive (L324) — the refund (L324), the transfer (L324), the delete (L324).
  • The pause is the workflow's (L208). The L277 step (L277) — the wait-for-callback (L208) — the L208 mechanism (L208), security-shaped (L324).
  • The context is the decision's (L324). The who (L319), the what (L315), the cost (L334) — the informed approval (L324).
  • The least approvals are the design's (L324). The low-risk automatic (L324) — the fatigue (L324) and the latency (L324) balanced (L324).
  • The audit is the approval's record (L322). The approved and the denied (L324) — the L322 record (L322) of the human's decision (L324).

Common Mistakes

  • The everything-gated (L324). The low-risk (L324) paused (L324) — the approval fatigue (L324) and the latency (L324); the least approvals (L324) are the design (L324).
  • The nothing-gated (L314). The transfer (L324) automatic (L314) — the L324 gate (L324) missing (L324).
  • The context-less approval (L324). The approve button (L324) without the who and the cost (L334) — the rubber stamp (L324).
  • The approver is the agent (L200). The agent (L200) approving its own action (L200) — the two-key rule (L324) needs the human (L324).
  • The un-audited approval (L322). The decisions (L324) unrecorded (L322) — the record (L322) of the human's gate (L324).

Best Practices

  • Gate the irreversible (L324) — the refund, the transfer, the delete (L324).
  • Pause with the workflow (L208) — the L277 wait-for-callback (L208).
  • Show the context (L324) — the who, the what, the cost (L334).
  • Keep the approvals few (L324) — the low-risk automatic (L324).
  • Audit the decisions (L322) — the approved and the denied (L322).

Interview Questions

Q: Walk me through the human approval as a control.

A: The highest-value control (L324). The gate — the high-risk actions: the refund, the transfer, the delete (L324). The mechanism — the pause and the callback (L208). The design — the least approvals and the clear context (L324). And the placement — at the tool (L323), the last line (L324).

Q: What needs the approval?

A: The high-risk (L324): the irreversible (L324) — the delete (L324), the external send (L324); and the expensive (L324) — the refund (L324), the transfer (L324). The low-risk (L324) — the reads and the replies (L324) — stays automatic (L324).

Q: How does the mechanism work?

A: The L208 mechanism (L208): the workflow (L277) stops at the approval step (L208), publishes the task (L228) to the human (L324); the human reviews the context (L324) — who asked, what the action is, what it costs (L334); and the callback (L277) resumes the workflow (L324) on the approval (L208) or stops it on the denial (L324).

Q: How do you avoid the approval fatigue?

A: The least approvals (L324): the low-risk actions (L324) automatic (L324), the high-risk (L324) gated (L324). The gate's scope (L324) is the design's (L324): the more gated (L324), the more fatigue (L324) and the slower the agent (L324) — the balance (L324) is the senior's (L324).

Follow-Up Questions

  • What needs the approval (L324)?
  • How does the mechanism work (L208)?
  • How do you avoid the fatigue (L324)?
  • What's the context (L324)?
  • What's the audit (L322)?

Comparison Table — The Automatic vs the Gated

The automatic (L324)The gated (L324)
The actions (L324)the reads, the replies (L324)the refund, the transfer, the delete (L324)
The latency (L324)the instant (L324)the human's (L324)
The risk (L324)the low (L324)the high (L324)
The fatigue (L324)none (L324)the bounded (L324)

The senior read: the automatic for the low, the gated for the irreversible (L324).

Code Example — The Gate, Applied

// The human approval (L324) — the gate on the irreversible (L324).
// 1 · THE GATE (L324) — the high-risk list (L324).
const HIGH_RISK = new Set(['refund', 'transfer', 'delete', 'external_send']);

// 2 · THE PAUSE (L208) — the workflow stops (L277).
async function executeWithApproval(action, ctx) {
  if (!HIGH_RISK.has(action.name)) {
    return execute(action, ctx);               // the automatic (L324)
  }

  // THE PAUSE (L208): the task published to the human (L324).
  const task = await approvals.publish({
    action: action.name,
    context: {
      who: ctx.userId,                        // the who (L319)
      what: action,                           // the what (L315)
      cost: await estimateCost(action),       // the cost (L334)
      tenant: ctx.tenantId,                   // the tenant (L320)
    },
  });

  // THE CALLBACK (L277): the human decides (L208).
  const decision = await approvals.wait(task.id);   // the wait-for-callback (L208)
  if (!decision.approved) return { denied: true };  // the denial (L324)

  const result = await execute(action, ctx);   // the resume (L324)
  await audit.log({ task: task.id, decision, result });   // L322
  return result;
}
What the reader must SEE — the gate, applied:

  HIGH_RISK set            → the gate's scope (L324)
  the automatic path       → the least approvals (L324)
  approvals.publish + wait → the pause and the callback (L208)
  context: who, what, cost → the informed decision (L319, L334)
  audit.log the decision   → the record (L322)

  The two keys: the agent's and the human's (L324).

Tip

The pair that defines the control: the high-risk set (the gate's scope, L324) and the wait-for-callback (the human's decision, L208). Gate the irreversible, show the context, keep the approvals few, audit the decisions — the highest-value control (L324).

Performance Notes

  • The gate is the latency's branch (L324). The high-risk check (L324) — the automatic (L324) instant, the gated (L324) the human's (L324).
  • The pause is the workflow's hold (L208). The wait-for-callback (L277) — the hours (L324) for the human (L324).
  • The approvals are the fatigue's cost (L324). The gated volume (L324) — the fatigue (L324) and the rubber stamps (L324).
  • The audit is the record's cost (L322). The decisions (L322) — the governance's (L322) record (L322).

Debugging Scenarios

SymptomFirst check (L324)The lever
The transfer went outThe gate (L324)The high-risk set (L324)
The approval never resumesThe callback (L208)The wait-for-callback (L277)
The approver rubber-stampsThe context (L324)The who, the what, the cost (L334)
The agent is slowThe gates (L324)The least approvals (L324)
The decision is disputedThe audit (L322)The record (L322)

Quick Revision Notes

  • The human approval = the highest-value control (L324): the gate, the mechanism, the design.
  • The gate: the high-risk — the refund, the transfer, the delete (L324).
  • The mechanism: the pause and the callback (L208).
  • The design: the least approvals, the clear context (L324).
  • The placement: at the tool (L323) — the last line (L324).

Cheat Sheet

HUMAN APPROVAL AS A SECURITY CONTROL = the gate on the irreversible

THE GATE (L324)
  the high-risk actions (L324): the refund (L324), the transfer
  (L324), the delete (L324), the external send (L324)
  the irreversible and the expensive (L324)

THE MECHANISM (L208)
  the pause (L208) — the workflow (L277) stops (L208)
  the task (L228) published to the human (L324)
  the review (L324) — the context: who (L319), what (L315), cost (L334)
  the callback (L277) — the resume (L324) or the denial (L324)

THE DESIGN (L324)
  the least approvals (L324) — the low-risk automatic (L324)
  the clear context (L324) — the informed decision (L324)
  the fatigue (L324) avoided (L324)

THE PLACEMENT (L323)
  at the tool (L323) — the boundary plus the human (L324)
  the last line (L324) — after the least privilege (L314)

INTERVIEW, 4 MOVES
  1 gate      "the refund, the transfer, the delete (L324)"
  2 mechanism "the pause and the callback (L208)"
  3 design    "the least approvals, the clear context (L324)"
  4 placement "at the tool — the last line (L323, L324)"

Key Takeaways

Recap

  • The human approval is the highest-value control for the highest-risk actions (L324): the gate (L324), the mechanism (L208), the design (L324), and the placement (L323)
  • The gate (L324): the high-risk actions (L324) — the refund (L324), the transfer (L324), the delete (L324), the external send (L324) — the irreversible and the expensive (L324)
  • The mechanism (L208): the pause (L208) — the workflow (L277) stops (L208), the task (L228) published (L324); the review (L324) — the context: the who (L319), the what (L315), the cost (L334); and the callback (L277) — the resume (L324) or the denial (L324)
  • The design (L324): the least approvals (L324) — the low-risk automatic (L324), the high-risk gated (L324) — and the clear context (L324) for the informed decision (L324)
  • The placement (L323): at the tool (L323) — the last line (L324), after the least privilege (L314) and the scoped tools (L323)
  • The AI shape (L324): the agent (L200) with the tools (L315) — the refund, the transfer, the delete (L324) — gated by the human (L324) — the L314 agency (L314) and the L323 tool (L323), with the human as the last line (L324)

Check your understanding

Answer each one out loud. Then rate yourself honestly.

0/8
1

What needs the approval (L324)?

2

How does the mechanism work (L208)?

3

How do you avoid the fatigue (L324)?

4

What's the context (L324)?

5

What's the last line (L324)?

6

What's the wait-for-callback (L277)?

7

What's the audit (L322)?

8

What is the highest-value control (L324)?

A Closing Note — The Vault, Two-Keyed

You now hold the control: the gate, the mechanism, and the design — with the two keys and the informed slip. The irreversible needs the manager's key — and the decision is recorded (L324).

Next: the layers stacked — AI Security Architecture (defense in depth) (L325).