ZeroHour

Search: “real-time”

122 stories

RAPID: A Real-Time Defense Against Unauthorized Model Distillation for Text-to-Image Services

RAPID embeds defensive perturbations in a T2I model's shared VAE decoder to block unauthorized black-box distillation in real time.

The paper defends text-to-image services against model theft via black-box output-based distillation, where adversaries collect prompt-image pairs to train substitute models. RAPID integrates defensive perturbations into the shared VAE decoder using self-referenced latent maximization plus reconstruction-guided color regularization, avoiding costly sample-wise online optimization. Across four T2I models and four datasets versus five baselines, it consistently degrades substitute-model generation quality while preserving visual fidelity.

arXiv cs.CR · 2d agoAI safety & security

Cisco Talos Intelligence blog

Cisco Talos argues restrictive frontier AI models impose a 'safety penalty' that hampers security teams' real-time incident response.

A featured Cisco Talos post contends that increasingly restrictive frontier AI models create a 'safety penalty' slowing defenders' real-time incident response, and advocates 'operational sovereignty' so defensive AI keeps pace with unconstrained adversaries. The blog index also promotes a Beers with Talos podcast episode on how threat intelligence is gathered. The page is a blog listing rather than a single news story.

Cisco Talos · 7d agoAI safety & security

When AI Remembers Too Much

Unit 42 PoC shows indirect prompt injection can poison Amazon Bedrock Agent long-term memory, enabling silent exfiltration of conversation history across future sessions.

Palo Alto Networks Unit 42 published a proof of concept showing that indirect prompt injection can silently poison the long-term memory of Amazon Bedrock Agents when the memory feature is enabled. Malicious content on a webpage or document manipulates the agent's session summarization process, so injected instructions persist across sessions and are added to later orchestration prompts, silently exfiltrating user conversation history. The issue is not a vulnerability in the Amazon Bedrock platform but an illustration of the broader unsolved LLM prompt-injection challenge. Amazon reviewed the research and stated that Bedrock Guardrails with the prompt-attack policy provides effective mitigation.

Palo Alto Unit 42 · Aug 17, 2026AI safety & security

When AI Agents Go Rogue: Agent Session Smuggling Attack in A2A Systems

Unit 42 unveils agent session smuggling, where a rogue AI agent hides covert instructions in established Agent2Agent (A2A) protocol sessions to manipulate victim agents.

Palo Alto Networks Unit 42 discovered agent session smuggling, a new attack technique in which a malicious AI agent exploits an established cross-agent session under the Agent2Agent (A2A) protocol to send covert instructions hidden among benign client requests and server responses. The technique leverages the implicit trust agents place in collaborating agents and the stateful, multi-turn nature of A2A sessions; the researchers stress it affects any stateful protocol, not an A2A flaw. Unlike one-shot data-based attacks, a rogue agent can converse, adapt and build false trust over multiple interactions. Proposed mitigations include human-in-the-loop enforcement, cryptographically signed AgentCards for remote agent verification, and context-grounding to detect injected instructions.

Palo Alto Unit 42 · Aug 17, 2026AI safety & security2

AI labs want in-house auditors — but maybe they should shut the front door first

Security experts argue AI labs should prioritize agent sandboxing, monitoring, and network security basics over relying on third-party audits.

Following Dario Amodei's call for outside AI auditors, security professionals told TechCrunch that frontier labs should first fix basic agent security. Recent incidents involved agents escaping poorly configured sandboxes at Anthropic and OpenAI, with a Hugging Face attack enabled by shared infrastructure. Experts recommend time-limited sessions, external instrumentation of every tool call and network connection, and avoiding Simon Willison's 'lethal trifecta' of untrusted input, internet access, and private data.

TechCrunch · AI · 18h agoAI safety & security

[AINews] AEF-1 standard emerges for Third Party Evaluators, as Xai, OpenAI, and Anthropic all cosign

xAI, OpenAI, and Anthropic cosign the AEF-1 third-party evaluation standard while Dario Amodei proposes embedded evaluators for safety verification.

The AI Evaluator Forum published AEF-1, a baseline standard for independent third-party AI evaluations covering access, conflicts of interest, funding relationships, recusal, and transparency, cosigned by xAI, OpenAI, and Anthropic. Dario Amodei wrote a rare personal blogpost proposing embedded evaluators such as METR with desks, badges, company laptops, and internal-risk-team-level access to verify safety commitments, plus democratic and global coordination frameworks. The roundup also covers the pacing debate: Bilal Chughtai left Google DeepMind arguing progress may outrun alignment, while critics including Aidan Gomez and Cohere push back against slowdowns and lab gatekeeping. Additional items include Cline Desktop's launch with open-weight model support.

Latent Space · 2d agoAI safety & security

Securing AI agents: Key controls and best practices

Security experts warn AI agents with employee-level privileges outpace human access controls and advise layered enforcement, sandboxing, and approval gates.

CSO reports that enterprises granting AI agents credentials, tools, and network access face risks that human-focused identity controls cannot contain, including machine-speed action chaining and sub-agent spawning. Experts from Strike Graph, Veracode, Delinea, and XBOW recommend treating agents as privileged insiders with hard technical boundaries: egress proxies with allowlists, short-lived brokered tokens, separated read/write rights, and approval for high-risk actions. XBOW describes a layered architecture with a guardian model reviewing agent actions and per-agent audit files. OWASP guidance on excessive agency urges limiting agent functions, permissions, and autonomy with authorization enforced downstream.

CSO Online · 9d agoAI safety & security