Skip to content
Friday, 20 November 2026
Tenesys AI News
Subscribe

All News

TENESYS AI NEWS tracks the most important AI news and explains what changed, why it matters and whether a technology is worth testing.

#Prompt Injection — 6 articles ✕

Models· Important· 🧪 Worth Testing

IBM releases LLMON-enabled Granite models to combat prompt injection

IBM has introduced LLMON (LLM Object Notation), an XML-like markup language that uses reserved special tokens to explicitly label components like instructions, data, and constraints. Two experimental models, Granite 4.1 3B and 8B LLMON-preview, are now available, demonstrating near-zero success rates for indirect prompt injection attacks.

Hugging Face
Cyber Security· Important· 🧪 Worth Testing

Mitigating memory poisoning in Amazon Bedrock AgentCore

Amazon has released a defense-in-depth architecture to prevent memory poisoning—a form of indirect prompt injection—in AI agents that use persistent memory. The solution uses a Lambda-based interceptor on the AgentCore Gateway to validate writes using semantic drift, regex patterns, namespace boundaries, and rate limiting.

AWS Security
Cyber Security· Important· 🧪 Worth Testing

Improved Security Monitoring for Tool-Using AI Agents

Recent research demonstrates that current security monitors often fail by confusing injection exposure with an agent's actual commitment to perform an unsafe action. The author proposes a double-stratified evaluation method that separates exposure from behavior, significantly improving the ability to predict unsafe tool calls up to two steps in advance.

arXiv cs.CL
Research· Important

New research: agents don't 'decide' to obey a prompt injection all at once — the choice unfolds as they reason

A new study questions the common belief that whether an AI agent falls for a prompt injection is settled the moment it reads the malicious text. The researchers built a branching-rollout technique on AgentDojo benchmarks: they replayed an agent's run up to the point it encounters an injected instruction, then let the rest of the episode play out many different ways to measure how much of the final outcome was already locked in versus still open. For a Qwen3 agent running without extended reasoning, 91% of the outcome was already determined at that moment; switching on reasoning ('thinking') cut that figure to 62%, showing the agent's compliance decision often keeps forming well after it first sees the attack. Enabling reasoning also cut Qwen3's susceptibility to successful attacks, but made two other tested models more vulnerable, and benchmark scores for reasoning agents flipped on a rerun as often as 35% of the time.

arXiv cs.CL
Cyber Security· Important· 🧪 Worth Testing

Microsoft treats AI agents as insider threats, launches new containment controls

Microsoft announced an expansion of its Project Perception security framework to address risks from autonomous AI agents, framing them as a new category of 'insider' that needs distinct identity, permission, and risk controls. The update introduces Dynamic Permissions (least-privilege, task-scoped, time-bound access), Dynamic Agent Risk (continuous risk scoring based on behavior drift and context), and Dynamic Conditional Access (graduated responses from narrowing access to full runtime isolation). Microsoft is also extending discovery and identity support (Microsoft Entra Agent ID) to 60 types of local agents, including Claude Code, OpenAI Codex, and GitHub Copilot, and introducing 'Guardian Agents' that monitor and respond to risky agent behavior at machine speed.

Microsoft Security