LIVE FEED
FIRST LOOK Microsoft Copilot Gains Local File Access via Hybrid Intelligence // FIRST LOOK AWS Adds Native Access Controls for RAG via Amazon Quick and Bedrock // HIGH DPRK npm Supply Chain Worm Uses Web3 C2 to Steal Cloud Keys // FIRST LOOK Rein Security Launches $25M Runtime Guard for AI Agents // HIGH APT Uses AI-Generated Lures in Google AitM Phishing on Taiwan // CRITICAL Tensorlake npm Package Hijacked by Shai-Hulud Worm // FIRST LOOK Meta Launches Open Standard to Authenticate AI Agents on the Web // FIRST LOOK Anthropic Launches 3-Tier Cyber Verification Program for AI Access // FIRST LOOK CrowdStrike Maps LLM Safety Classifier Evasion for Defenders // HIGH OpenAI Adds Training Monitors After Medicare Data Breach //
RESOURCE-LIMITS

Resource-Limits

2 reports
All LLM Security Agentic AI Industry News Research First Look: Security Supply Chain Prompt Injection Regulatory Adversarial ML Jailbreaks Model Theft Data Poisoning Deep Signal Intelligence Report Monthly Review AI Governance AI Security AI Security Tools Identity & Access Management Security Operations
AWS and Google Cloud Launch Hard Spend Caps for AI Agent Workloads

AWS and Google Cloud Launch Hard Spend Caps for AI Agent Workloads

FIRST LOOK ATLAS OWASP LOW Limited impact · Standard review ▲ 5.5 Simon Willison

AWS and Google Cloud have both introduced hard monthly spending caps for cloud services, enabling developers and organisations to set firm financial ceilings that pause or terminate services rather than allowing runaway billing. For defenders overseeing agentic AI deployments, this closes a meaningful blast-radius gap: coding agents and personal agents that autonomously invoke paid APIs or spin up compute can now be constrained to a pre-approved financial envelope, limiting the operational damage of a misbehaving or compromised agent. The residual gap is significant — coverage remains fragmented across providers, enforcement depends on correct configuration by each team, and hard caps do not yet extend to non-financial resource consumption such as data egress or API call volume.

smolvm Brings Hardware-Isolated Sandboxing for AI Code Execution

smolvm Brings Hardware-Isolated Sandboxing for AI Code Execution

FIRST LOOK ATLAS OWASP LOW Limited impact · Standard review ▲ 6.2 Simon Willison

smolmachines/smolvm 1.8.3 provides hardware-isolated VM sandboxing for untrusted Python and JavaScript, with enforced CPU/RAM limits, no-network execution, filesystem quotas, and cold starts under 1.5 seconds. For defenders building AI platforms that execute user-supplied or LLM-generated code, this closes the critical gap between shared-kernel container isolation and true VM-level isolation for data transformation workloads. Residual maturity questions remain around orchestration integration, audit logging depth, and the KVM dependency that excludes nested-virtualisation environments like many CI and cloud agent runtimes.

◉ AI THREAT BRIEFING

Stay ahead of the threat.

Twice-weekly digest of critical AI security developments — every story mapped to MITRE ATLAS and OWASP LLM Top 10. Free.

No spam. Unsubscribe anytime.