← Learning paths

14 lessons · take it step by step

AI Security

Protect application trust boundaries, authorized data and tool effects with tested policies and explicit limits.

Start here

Follow the order if you are new, or jump straight to a topic you need.

Start the first lesson →
  1. AI Threat Modeling & Trust Boundaries

    25–40 min

    A RAG answer can expose documents; an agent can change resources.

  2. Direct & Indirect Prompt Injection

    25–40 min

    Direct input, a retrieved document, a tool result or repository text may contain instructions that conflict with the task.

  3. Sensitive Data & Exfiltration

    25–40 min

    Identify secrets, personal records and restricted documents before a model call.

  4. Secure Output Handling

    25–40 min

    A model can return valid JSON containing an unauthorized resource, a dangerous URL or invented SQL.

  5. Secure RAG: Access & Ingestion

    25–40 min

    A document belongs to a tenant and requires a trusted approval decision before retrieval.

  6. Agent Tool Authorization & Approval

    25–40 min

    Treat model tool arguments as untrusted input.

  7. Resource, Cost & Availability Abuse

    25–40 min

    Limit input size, model steps, tool attempts and fan-out before launching work.

  8. AI Security Evaluation & Release Gates

    25–40 min

    A final response saying “I did not access it” is not evidence of authorization enforcement.

  9. Model, Tool & Dependency Supply Chain

    25–40 min

    Model files, datasets, tool packages and CI actions are distinct supply-chain inputs.

  10. Memory & Context Poisoning

    25–40 min

    An untrusted instruction stored as memory can influence later runs after the original document is gone.

  11. MCP & Connector Security

    25–40 min

    An MCP client name, server description or declared capability is not authenticated permission.

  12. Sandbox, Egress & Execution Isolation

    25–40 min

    Avoid exposing shell, arbitrary file access and generic network execution when the task does not need them.

  13. Monitoring & AI Incident Response

    25–40 min

    Capture sanitized event codes, scoped request identifiers, policy versions and effect outcomes.

  14. Agent-Assisted SDLC Security

    25–40 min

    An issue, dependency README, error log or skill may contain attacker-authored instructions.