Path 6 of 6Practitioner6 lessons · 55 minReviewed 2026-11-10
Detecting and responding to AI abuse
LLMjacking, the cloud and agent telemetry that records AI use, detection engineering for AI abuse, agent incident response, AI-enabled attackers, and using AI in the SOC without trusting it blindly.
For: SOC analysts, detection engineers and incident responders
- 01 LLMjacking: stolen cloud credentials used against hosted models
Follow an LLMjacking operation from leaked key to resold access, and know which API calls give it away at each step.
9 min · 4 questions
- 02 The telemetry you actually have
Know which cloud, application and agent logs record AI use, which are off until you turn them on, and how to keep prompt logs from becoming a new data leak.
9 min · 4 questions
- 03 Detection engineering for AI abuse
Turn reported attacker behaviour into rules on logs you already collect, choose between alert, baseline and behavioural rules, and write false positives down instead of hiding them.
9 min · 4 questions
- 04 Responding to an agent incident
Run an incident where an agent or AI coding tool acted on injected instructions: contain the identity, preserve the agent's record, scope through audit logs and remove the trigger.
10 min · 4 questions
- 05 AI-enabled attackers: what has been reported and what changes
Separate documented attacker use of AI from speculation, and adjust detection and response for machine-paced intrusions and malware that calls model APIs.
9 min · 4 questions
- 06 Using AI in the SOC without inheriting its failure modes
Recognise how AI triage and investigation assistants fail (confabulation, automation bias, injection through alert data, excessive agency) and evaluate one on your own alerts before relying on it.
9 min · 4 questions
Lessons cite primary sources and were last checked on the date shown in each lesson. Corrections are welcome by email (footer). Other paths: Fundamentals · LLM applications · Agents & MCP · AI coding assistants · Red teaming