11-19 更新 实时
首页/ 技术栈/ 正文

看清智能体、设定规则:个人智能体的可见性与管控

技术栈 来源:Cloudflare Blog 2026-11-04 22:00 0 阅读 机器翻译
看清智能体、设定规则:个人智能体的可见性与管控

个人智能体是人与互联网之间的中介,将个人的指令转化为在网站上的请求和操作。客户可能会让个人智能体在你的网站上比较产品、查找支持文章或完成购买。对网站所有者来说,这三种交互都会表现为自动化流量——如果无法清楚了解哪些智能体在访问以及它们在做什么,就很难判断这些流量是在帮助你的业务,还是在带来风险。完全屏蔽智能体看似是最安全的选择,但可能意味着流失客户。更好地了解智能体活动,让你能决定哪些访问权限对你的网站是合理的。

今天,我们推出新的分析功能,帮助你了解个人智能体如何代表人类访问你的网站,同时提供更细粒度的访问策略,将这些决策付诸实践。两者结合,让你能按自己的规则欢迎智能体,并以支持你业务的方式实现。

知道请求背后是哪个智能体,能把无法解释的自动化流量变成你可以放心采取行动的流量。Cloudflare 维护着全球最大的已验证机器人目录,现在我们正将这些情报引入你的流量详情。在 Security Analytics 中,Bot Analysis 图表现在将 Personal Assistants 显示为一个新类别,与 Verified Bot、Likely Human、Likely Automated 和 Automated 并列。安全团队可以选择它,仅查看一段时间内的个人智能体流量。

在 Top statistics 中,一个新的 Personal Assistants 组件会列出哪些智能体正在访问你的网站,以及每个智能体发送了多少请求。筛选某一个智能体后,其他所有组件都会随之更新,只显示它的流量详情:它请求的路径、收到的状态码,以及它来自的网络。一眼就能看出某个智能体是否在登录、在读取你的产品页面、在进入结算流程,还是在它无法使用的页面上撞上错误。

对于使用 Account Abuse Protection(目前处于早期访问阶段)保护用户账号的站点,站点所有者和反欺诈团队能够看到每个智能体代表哪一个用户。总体概览页面会显示哪些个人智能体在你的用户中处于活跃状态,以及有多少账号在使用它们,从而让你判断智能体流量是否是业务中不可忽视的一部分。现在每一次登录和注册事件都会显示该请求是否由个人智能体发起,以及是哪一个智能体。反欺诈团队可以按 AI 助手事件或 AI 助手数量来筛选账号。

此外,每个用户的账号概览会显示为该账号行动的智能体。反欺诈分析师在调查一次异常登录时,可以判断它来自客户已经依赖数周的智能体,还是来自今天首次出现、需要进一步查看的智能体。如果看起来是攻击者在某个账号上使用某个智能体,反欺诈分析师可以直接对该账号采取缓解措施,即针对其 Hashed User ID 设置 WAF 规则,而不必为所有依赖该智能体的其他用户屏蔽这个智能体。

综合来看,这些视图为你决定欢迎、限制还是屏蔽哪些个人智能体提供了更清晰的依据。

我们在今年夏天推出了 AI 机器人策略,让网站所有者可以针对用于 Search、Training 和 Agent 行为的 AI 机器人分别做出访问控制选择。现在,我们正在扩展已有的 Agents 策略,为受支持的个人智能体加入细粒度控制选项。为体现这一更广泛的范围,我们将该设置更名为 AI Crawler and Agent access policies。

在 Security Settings 中,你可以设置一个总体的 Agents 策略,然后为每个受支持的个人智能体选择不同的策略:Allow(不拦截)、Block on pages with ads(在含广告的页面上拦截)或 Block。例如,你可以将总体 Agents 策略设为 Block on pages with ads,然后为你希望放行的某个受支持的个人智能体选择 Allow(不拦截)。你现有的 Search 和 Training 策略保持不变。

在向 Cloudflare 添加新区域时,你也可以做出这些选择。在引导流程中,我们会询问你是否通过广告对页面进行变现,然后根据你的回答定制推荐的策略。你随时可以在 Security Settings 中重新调整访问控制。

正确的策略取决于你的网站。有的发布商可能在其整个网站允许某个受支持的个人智能体访问,以便读者找到其文章;而另一家发布商可能会在广告支撑内容的页面上拦截同一个智能体。两家发布商都在选择适合自身业务的访问控制方式。

我们今天推出的分析工具和相关政策,让网站所有者能够查看个人智能体的活动情况,并控制其访问权限。我们的下一个目标,是在个人智能体充当中间人时,帮助网站所有者保留其与用户之间关系的上下文。网站或许能识别出正在发出请求的智能体,却缺少原本可以掌握的用户信息:该用户是否为现有客户、其授权智能体做哪些事、是否订阅了服务,以及应当适用哪些保护措施。

要实现这一目标,需要以隐私友好的方式做到三件事:(1) 让用户上下文随智能体一同传递;(2) 帮助网站评估信誉;(3) 在出现问题时报清楚界定责任。随着我们与智能体运营方以及生态系统中其他各方展开合作,我们会分享更多进展,从而让网站所有者能够自行选择是否授予智能体更大的访问权限,同时继续与用户建立关系。

那个让个人智能体去比较产品、寻求支持或完成购买的人,仍然是一位试图与你的企业建立联系的客户。请查看个人智能体是如何访问你的网站的,然后前往“安全设置 → AI 爬虫与智能体访问政策”,设定适合你网站的条款。

译文由英文原文机器翻译,术语按行业惯例统一,可在文末展开原文核对。

查看英文原文(See the agents, set the terms: New visibility and control for personal agents)

Personal agents are the intermediary between humans and the Internet, turning a person’s instructions into requests and actions on websites. A customer might ask a personal agent to compare products across your site, find support articles, or complete a purchase. To a site owner, all three interactions show up as automated traffic — and without a clear view of which agents are visiting and what they are doing, it can be difficult to know whether that traffic is helping your business or creating risk. Blocking agents altogether can feel like the safest choice, but it can mean losing customers. Better visibility into agent activity allows you to decide what access makes sense for your site.

Today, we’re launching new analytics to help you understand how personal agents access your site on behalf of humans, along with more granular access policies to put those decisions into practice. Together, they let you welcome agents on your own terms, and in ways that support your business.

See how agents access your site

Knowing which agent is behind a request turns unexplained automated traffic into traffic you can act on with confidence. Cloudflare maintains the largest verified bot directory in the world, and we are now bringing that intelligence into your traffic details. In Security Analytics, the Bot Analysis chart now shows Personal Assistants as a new category, next to Verified Bot, Likely Human, Likely Automated, and Automated. Security teams can select it to see only personal agent traffic over time.

In Top statistics, a new Personal Assistants widget lists which agents are visiting your site and how many requests each one sends. Filter on one agent and every other widget updates to show only its traffic details: the paths it requests, the status codes it receives, and the networks it comes from. At a glance, you can see whether an agent is logging in, reading your product pages, reaching your checkout, or hitting errors on pages it cannot use.

For sites that protect user accounts with Account Abuse Protection (currently in early access), site owners and fraud teams are able to see which user each agent represents. The population overview page shows which personal agents are active across your users and how many accounts use them, so you can determine whether agent traffic is a meaningful part of your business. Every login and sign-up event now shows whether a personal agent made the request, and which one. Fraud teams can filter accounts by AI assistant events or number of AI assistants.

Additionally, each user's account overview shows the agents acting for that account. A fraud analyst investigating an unusual login can tell whether it came from an agent the customer has relied on for weeks, or from an agent that appeared for the first time today and needs a closer look. If it looks like an attacker is using an agent on an account, fraud analysts can mitigate that account directly, with a WAF rule on its Hashed User ID, without blocking the agent for everyone else who relies on it.

Together, these views give you a clearer basis for deciding which personal agents to welcome, limit, or block.

Set access policies that reflect your preferences

We introduced AI bot policies this summer so site owners could make separate access control choices for AI bots used for Search, Training, and Agent behaviors. Now we’re expanding the existing Agents policy to include granular control options for supported personal agents. To reflect this broader scope, we’re renaming the setting AI Crawler and Agent access policies.

In Security Settings, you can set an overall Agents policy, then choose a different policy for each supported personal agent: Allow (do not block), Block on pages with ads, or Block. For example, you can set the overall Agents policy to Block on pages with ads, then choose Allow (do not block) for a supported personal agent you want to welcome. Your existing Search and Training policies stay as they are.

You can also make these choices when you add a new zone to Cloudflare. During onboarding, we ask whether you monetize pages with ads and then tailor the recommended policies to your answer. You can always revisit your access controls later in Security Settings.

The right policy depends on your site. One publisher may allow a supported personal agent throughout its site so readers can find its articles, while another may block that same agent on pages where ads support the content. Both publishers are choosing the access control that works for their business.

Agent identity is only part of the story

The analytics and policies we’re launching today give site owners visibility into personal agent activity and control over their access. Our next goal is to help site owners preserve the context of their relationships with users when personal agents act as intermediaries. A site may recognize the agent making a request but lack information it would otherwise have about the user: whether they are an existing customer, what they authorized the agent to do, whether they have a subscription, or which protections should apply.

Reaching that goal will require privacy-aware ways to (1) carry user context through an agent, (2) help sites assess reputation, and (3) establish clear accountability when something goes wrong. We’ll be sharing more as we work with agent operators and others across the ecosystem, so site owners can choose whether to grant agents greater access while continuing to build relationships with their users.

Make the choice for your site

That person asking a personal agent to compare products, find support, or complete a purchase is still a customer trying to reach your business. Review how personal agents are accessing your site, then visit Security Settings → AI Crawler and Agent access policies to set the terms that work for your site.

正文保留英文原文,标题与摘要由机器翻译。

本文由采集器自动同步

原文发布于 Cloudflare Blog(See the agents, set the terms: New visibility and control for personal agents),标题、摘要与正文由机器翻译,术语按行业惯例统一,未经人工逐句校订。

阅读原文 ↗