LecturaInvestigaciónRadarMarco de inversión
Iniciar sesión / Registrarse
← Volver a la lectura
NoticiasTema · AI智能体安全Material3 min de lecturaEditorial de DisconfirmAI

Vercel: AI Agents Amplify Static Key Risks; Marketplace to Remove Vendors Without Secure Authentication Starting in 2027

Vercel argues that machine-to-machine authentication is at the same stage HTTPS was in 2010—standards exist but adoption is extremely low. AI agents exacerbate this by granting permissions far exceeding task requirements. Vercel surveyed over 1,000 SaaS vendors and found only 8.4% support secure authentication methods, proposing tool simplification and delisting deadlines to drive change.

Verificado 2026-10-23 07:12 GMT+8

Vercel posits in its official blog that machine-to-machine authentication currently resembles the state of HTTPS in 2010: standards such as OAuth and OIDC provide the foundational building blocks for secure authentication, yet long-lived static credentials (API keys, database passwords) remain the default practice for most SaaS vendors and infrastructure providers. Vercel believes that standards alone do not make secure methods the norm; the widespread adoption of HTTPS relied on tools that made encryption easy, coupled with sustained efforts to make it the expected standard.

The article identifies AI agents as a factor significantly worsening this issue. Developers now grant agents access to systems, tools, and data through credentials, often conferring permissions far beyond what is necessary for the agent's current task. Credentials may leak into code repositories or chat logs, be stolen when a service or dependency is compromised, or fall into attackers' hands if prompt injection causes an agent to actively expose them. Regardless of the vector, an attacker can use the credential until it expires or is revoked. Vercel specifically notes that recent industry incidents involving credential theft and supply chain attacks demonstrate that encryption at rest is insufficient when malicious code can read application credentials in production environments.

Vercel states it previously spent thousands of engineering hours on multiple, highly painful key rotations and wishes to avoid such experiences again. This constitutes the direct motivation for driving alternative solutions.

Iniciar sesión / Registrarse
LecturaInvestigaciónRadarMarco de inversión

Regarding evidence, Vercel self-reported a survey: among more than 1,000 SaaS vendors surveyed, only 8.4% supported secure authentication methods. Vercel attributes the low adoption rate to three barriers: tooling and configuration make secure authentication more complex than using static keys directly; fetching or exchanging tokens along the request path adds latency; and vendors lack incentives to offer and prioritize secure authentication.

Vercel’s proposed solution follows the path taken by HTTPS: first making the secure path easier to use than the insecure one, then applying pressure via deadlines. Specific tools include: OIDC UI (a shadcn/ui component registry that generates trust policy forms and token verification code for API providers), Vercel Connect (which allows applications and agents to request short-lived tokens using deployment identity at runtime, eliminating the need to store long-term keys in environment variables), and platform-level token caching and refresh mechanisms to reduce latency.

In terms of incentives, Vercel announced two deadlines: by November 30, 2026, Marketplace vendors that do not support OIDC authentication from Vercel to their services and continue to use long-term keys will display a "Not secure" notice on their listings; by January 2027, vendors still failing to provide secure authentication will be delisted. Vercel also stated that its own APIs and native integrations will adhere to the same standard.

Fuentes

  • vercel.comVercel↗
Tema

AI智能体安全

随着AI智能体从对话助手转向执行复杂任务(如支付、代码部署),其安全风险已从单纯的提示词注入扩展至身份认证、资金流转及系统权限滥用。2026年10月,多家机构披露了针对智能体的新型防御机制与漏洞:美国大型银行限制外部AI访问客户凭证;1Pa…

7 pasos9 piezasActualizado 2026-10-26 06:42

Cómo llegó hasta aquí

  1. 2026-07-21METR与Redwood Research开始对OpenAI内部智能体监控系统进行为期三周的红队测试,旨在评估其防绕过能力。tech.yahoo.com ↗
  2. 2026-10-22METR发布报告称,OpenAI的Codex代理监控系统存在三类可被利用的漏洞,包括绕过沙箱边界和序列化差异导致的监控失效。ithome.com.tw ↗
  3. 2026-10-221Password推出“1Password for Agents”,允许AI智能体在用户确认下登录账户,而无需接触实际密码或凭证。techcrunch.com ↗

Lo que aún está pendiente

  • OpenAI是否已完全修复METR指出的所有生产环境监控漏洞,且第三方能否独立验证?
  • Vercel设定的2027年除名截止日是否会迫使更多SaaS供应商快速采用标准机器对机器认证协议?
  • 银行限制AI智能体访问的政策是否会阻碍合法的企业级自动化财务流程发展?

También en este hilo

  • METR and Redwood Report: OpenAI Codex Agent Monitoring System Had Bypass Vulnerabilities, Now Fixed2026-10-23
  • Google Cloud Launches Agent Compute Engine: Isolated VMs and External Gateways Secure AI Agents2026-10-23
Leer el tema completo →
Continuar investigando →