Notifications
Clear all
Topic starter
24/06/2026 11:58 pm
TL;DR: AI systems widen the attack surface through prompt injection, jailbreaking, deepfakes, data poisoning, and AI-generated phishing that can bypass conventional controls, according to WitnessAI. The governance problem is not just adversarial content, but the fact that AI systems can be manipulated into taking actions, handling data, or impersonating identities outside intended guardrails.
NHIMG editorial — based on content published by WitnessAI: AI cybersecurity threats, AI agent abuse, and enterprise mitigation strategies
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should security teams govern AI systems that can take actions from untrusted input?
A: Security teams should separate untrusted input from action execution, especially where an AI system can call tools, retrieve data, or influence approvals.
Q: Why do deepfakes create a bigger problem than traditional phishing for IAM teams?
A: Deepfakes weaken the signals people use to approve access changes, reset credentials, or authorise transactions.
Q: What do organisations get wrong about AI-generated phishing and impersonation?
A: They often treat it as a messaging problem instead of an identity problem.
Practitioner guidance
- Classify AI-exposed workflows by trust boundary Map where AI systems consume untrusted input, make decisions, or trigger downstream actions.
- Restrict model-to-tool permissions tightly Limit which tools, datasets, and actions an AI system can reach, and require separate approval for high-risk operations.
- Harden human verification for approval paths Move beyond voice or message realism when approving resets, payments, or access changes.
What's in the full article
WitnessAI's full article covers the operational detail this post intentionally leaves for the source:
- Specific examples of prompt injection and jailbreak patterns that defenders can test against their own AI stack
- Detailed countermeasures for AI-specific phishing, deepfakes, and model abuse across enterprise workflows
- Guidance on how to update incident response playbooks for AI-enabled attack paths
- A vendor view of runtime security and observability for models, applications, and agents
👉 Read WitnessAI's analysis of AI cybersecurity threats and AI agent abuse →
AI cybersecurity threats: what IAM and security teams need to know?
Explore further
25/06/2026 8:47 am
AI cybersecurity threats are really identity trust failures at machine speed. The article groups together phishing, deepfakes, prompt injection, poisoning, and malware, but the shared pattern is that attackers are exploiting the points where organisations decide what to trust. That decision now spans humans, service identities, and AI systems that can act on what they ingest. The practitioner implication is that identity programmes need to treat AI as part of the trust boundary, not just a new attack channel.
A few things that frame the scale:
- Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks, according to The 2024 ESG Report: Managing Non-Human Identities.
- The average organisation believes more than 1 in 5 of their non-human identities are insufficiently secured, which shows how broad the control gap already is.
A question worth separating out:
Q: How can teams tell whether an AI model has been poisoned or influenced?
A: Look for sudden shifts in model outputs, unexplained changes in classification behaviour, or new failure patterns after data or connector updates. Poisoning is often visible first as behavioural drift, not as a clean technical alert. Teams need source provenance, change tracking, and review of retrieval inputs to detect it early.
👉 Read our full editorial: AI cybersecurity threats are widening enterprise identity risk
