Architecting Security for Agentic Capabilities in Chrome
Posted by Nathan Parker, Chrome security team Chrome has been advancing the web’s security for well over 15 years, and we’re committed to meeting new challenges and opportunities with AI.
Posted by Nathan Parker, Chrome security team Chrome has been advancing the web’s security for well over 15 years, and we’re committed to meeting new challenges and opportunities with AI. Billions of people trust Chrome to keep them safe by default, and this is a responsibility we take seriously. Following the recent launch of Gemini in Chrome and the preview of agentic capabilities , we want to share our approach and some new innovations to improve the safety of agentic browsing. The primary new threat facing all agentic browsers is indirect prompt injection .
Our layered defense also includes user confirmations for critical steps, real-time detection of threats , and red-teaming and response . Checking agent outputs with User Alignment Critic The main planning model for Gemini uses page co
We built on Gemini's existing protections and agent security principles and have implemented several new layers for Chrome. We’re also extending Chrome’s origin-isolation capabilities to constrain what origins the agent can interact with, to just those that are relevant to the task.
Who is affected
Our layered defense also includes user confirmations for critical steps, real-time detection of threats , and red-teaming and response .
Checking agent outputs with User Alignment Critic The main planning model for Gemini uses page co
How organizations are responding
We built on Gemini's existing protections and agent security principles and have implemented several new layers for Chrome.
We’re also extending Chrome’s origin-isolation capabilities to constrain what origins the agent can interact with, to just those that are relevant to the task.
What remains unknown
The available reporting does not establish whether the issue is being actively exploited in the wild.
The available reporting does not establish who is behind the activity, if an attacker is involved.