创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

AWS详解Bedrock知识库工具细粒度权限控制

AI 总结

AWS Machine Learning Blog发布了面向多租户AI智能体的Amazon Bedrock Managed Knowledge Base工具安全指南。该架构结合Amazon Bedrock AgentCore Gateway和Model Context Protocol工具,由可信代码注入已验证的用户属性,并覆盖模型生成的搜索上下文。AgentCore策略和基于资源的策略则提供额外防护。

深度见解

AWS Machine Learning Blog指出,该设计不让LLM决定授权身份,可降低提示注入或模型错误导致内部及客户数据越权访问的风险。

More enterprises are building AI agents into their daily work, and a common pattern is an agent that searches internal documents to compose its answers. A single organization might soon run hundreds of agents, each connected to many data sources and tools. This raises a question. When an agent searches on behalf of a user, can you make sure that it uses only the information that user is allowed to see?

Consider AnyCompany, a fictional company that builds an internal assistant shared by all employees. An employee in department A asks, “Compare my department’s business plan with the notice to all departments, and list the initiatives that are behind schedule.” The agent writes its own search queries and keeps searching internal documents until it has enough information. Employees in department B ask the same assistant the same question. If the application doesn’t scope searches to each user, the department B business plan can end up in an answer to an employee in department A. If you replace the departments with customer companies, the same problem occurs in a multi-tenant software as a service (SaaS) architecture where multiple customers share one assistant and knowledge base.

#Amazon Bedrock Managed Knowledge Base#Amazon Bedrock AgentCore Gateway#Amazon Bedrock AgentCore#Model Context Protocol#Amazon Cognito

原文约 20 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。