← All playbooks
AI
AI-era threats playbook
Spot attacks that use AI, or that target a company's AI tools, and judge them by the evidence like any other alert.
Use this when: A chatbot or AI assistant doing something it should not, a voice or video request for money, a flawless phishing email, an unapproved AI tool, or a stolen AI key.
Steps
0 of 6 tickedSigns it is real
- An AI tool took an action nobody asked for
- Instructions hidden in a document or message
- An urgent payment request by voice or video with no second check
- Key use from a new place or at a new scale
Signs it is harmless
- An approved AI tool inside the company's own tenant
- Matching change or contract record
- Normal volume and users for that tool
Escalate when
- Data or money has left
- An AI tool is acting with real permissions on attacker text
- Credentials or keys are exposed
- Many users received the same attack
Common mistakes
- Trusting a request because it sounds and looks right
- Assuming a polished email is safe
- Checking only the AI's output and not the input it read
- Treating every AI-tool alert as an attack
Tools you will use
AI tool admin and audit logsCloud billing and API usageMail gatewaySecond-channel call-back
Practice with this playbook
- SL-1031Anomalous API usage by chatbot servicemedium
- SL-1032User-reported: suspicious phone request for paymenthigh
- SL-1036DLP: sensitive attachments sent to external domaincritical
- SL-1038Web proxy: uploads to uncategorised domain from browser extensionmedium
- SL-1046User-reported: unexpected payment request by phonemedium
- SL-1050Cloud AI: daily spend above budget thresholdlow
- SL-1051DLP: AI assistant sent document to external domainmedium
Found something confusing or unrealistic?