Aaron Levie：智能体集群可助企业防御安全风险

这是多事的一周。面向互联网的软件、代码仓库中出现多个漏洞，一些智能体行为的例子令人担忧，还有一大批安全专家提出了只能部分解决你问题的方案。挑战就在这里。鉴于IT和安全基础设施的现状，没有哪一种解决方案能奏效。让我们逐一分析： 1/3 1. 随着模型能力越来越强，漏洞正在被发现，而且还会继续被发现；这种工作的碎片化性质使我们无法拥有一个全面的“查找并替换”选项。 2. 即使所有漏洞都能被瞬间发现并且补丁可用——我们仍将依赖企业快速部署所有这些变更的能力。目前尚不清楚，如果大规模部署，所有这些补丁会对我们的基础设施造成怎样的连带影响。 我们需要一种混合补丁策略。 3. 虚拟补丁（VP）需要与直接打补丁结合使用，但要实现全面的（VP）解决方案，你必须足够幸运，拥有“现代前沿防御者”（那些拥有金库级基础设施、能够快速创建补丁并迅速推送内容以保护客户的网络安全公司）——你需要他们来保护你的网络流量、你流向云上应用的流量、你的WAF、你的终端。 4. 仍会不断有需要直接部署的补丁，但虚拟补丁将承担大部分重负。 2/3 中期解决方案： 不幸的是，代币经济和当前的网络安全架构将不允许防御者集群与使用智能体发起的攻击相抗衡。（一些并不精通网络安全的X平台评论者应当注意。）是的，理论上我们应该渴望在遭受攻击时由这些智能体集群来防御我们，但不幸的是，攻击是一个狙击手时刻：漏洞链、隐蔽攻击，随后是迅速的数据外泄。这是一个速度问题，而不是蛮力问题。 要解决这个问题，企业需要把SOC架构做对，通过现代SOAR编排日志、数据源和网络安全产品，以实现快速响应。只有到那时，我们才能部署智能体来检测和修复。此外，企业需要现代化，而且我敢说，需要将其边界栈平台化，以确保一致性。 不幸的是，企业似乎仍未全面认识到紧迫性，决策陷入停滞，CIO/CISO们手头事务繁多。虽然有些人确实从未见过如此规模的问题，也很难说服组织相信需要为IT和安全基础设施的现代化打开闸门。因此，我们将继续看到环境被下线以打补丁——今天是为了PHP，明天就会是为了下一个。 3/3 AI部署是“狂野西部”——LLM能力的扩展速度快于我们构建产品来保护它们的速度。当然，智能体会在研究实验室里越过护栏，这对我们所有人都是一个教训：要安全地部署智能体。但从发现、到该能力在公开模型中可用、再到网络安全行业构建治理或解药所需的时间，之间存在滞后。而且，不，亲爱的前沿实验室朋友们，世界不能仅仅信任你们来构建解决方案。科技界的基础设施行业负责构建，网络安全行业负责保障，并向董事会和组织提供有关安全与安保的保证。 AI安全是新的攻击面。CEO们（包括本公司）希望采用AI，采用节奏出错可能是我们做出的最后一个决定，同时“错误地部署它”也可能带来同样的后果。 有数十亿美元正花在编码上，你的编码框架安全吗？从那里开始。如果智能体能够越过护栏，它们就能在代码中藏东西。 验证所需的业务成果，测试你的用例，并确保智能体部署受到良好的护栏保护。部署第二双眼睛来监视你的部署，以发现漂移、合规性和可验证性问题。

查看原文

It's been an eventful week. Multiple vulnerabilites in Internet facing software, coding repositories, examples of agent behavior that seem concerning and a flurry of security specialists with solutions that can partially solve your problem. There in lies the challenge. Given the state of IT and security infrastructure, no one solution works. Let's break it down: 1/3 1. Vulnerabilites are being found and will continue to be found as models get more capable, the fragmented nature of the effort denies us the opportunity for a comprehensive find and replace option. 2. Even if all vulnerabilities could be found instantly and patches available - we will be reliant on the ability of enterprises to deploy all these changes at speed. It is not clear what the collateral impact of all these patches will/could be to our infrastructure of deployed en masse. We will need a hybrid patch approach. 3. Virtual patching(VP) is needed in conjunction with direct patching but for a comprehensive (VP) solve you have to be lucky enough to have "modern frontier defenders" (Cyber companies that have vaulted infrastructure that can create patches at speed and push content rapidly to protect their customers) you need them for your network traffic, your traffic to applications on the cloud, your WAF, your end point. 4. There will continue to be patches that will need to be deployed directly but virtual patching will take the heavy load off. 2/3 Medium term solve: Unfortunately token economics and current cyber architectures will not allow for defender swarms to contend with an offensive attack launched using agents. (Some x pundits who aren't steeped in cyber should take heed). Yes, theoretically we should aspire to have these agentic swarms defend us when we are under attack, unfortunately an attack is a sniper moment, chained vulnerabilities, cloaked attack followed by swift exfiltration. It's a speed program not a brute force problem. To solve for this, enterprises need to get their SOC architecture right, logs, feeds, cyber products orchestrated via a modern SOAR for swift response. Only then can we deploy agents to detect and remediate. In addition, enterprises need to modernize and dare I say platformize their perimeter stack to ensure consistency. Unfortunately, enterprises still seem to not see the urgency across the board, decisions are stuck, CIO/CISO's have a lot on their plate. While some honestly have bit seen the scale of such a problem before and it's hard convincing the organization that one needs to open the floodgates on modernizing the IT and security infrastructure. So we will continue to see environments being brought down to patch today it's for PHP, tomorrow it will be for the next one. 3/3 AI deployments are the"wild wild west" - LLM capabilities are expanding faster than we can build products to secure them. Sure an agent will jump across guardrails in a research lab, which is a lesson for all of us to deploy agents securely. But there is a lag between the discovery, the availability of that in a public model and the time needed for the cyber industry to build governance or an antidote. And no, dear frontier lab friends, the world cannot just trust you to build the solve. The infrastructure industry in tech builds and the cyber industry secured and provides assurance to the boards and organizations around security and safety. AI security is the new attack surface. CEOs (present company included) want AI adoption, getting the pace of adoption wrong could be the last decision we make, at the same time "deploying it wrong" could have the same consequence. There are billions of dollars being spent on coding, is your coding harness secure? Start there. If agents can jump guardrails, they can hide stuff in code. Validate business outcomes needed, test your user case and ensure agentic deployments are well guard railed. Deploy a second set of eyes to watch your deployments for drift, compliance and verifiability.