Tag
Kent C. Dodds 正在为 Kody 开发名为 "profiles" 的新功能，允许用户或其 agent 创建仅具有账号部分权限的 token/MCP 连接，从而提升安全性与可审计性。
作者分享了将约60个内部AI代理从单一共享主密钥迁移到每个代理独立API密钥的实践经验，包括编写细粒度允许列表、短期运行凭证，以及在彻底扫描确认无引用后才停用主密钥。
HP Labs tech report by Tyler Close arguing the ACL access model cannot make correct decisions in interactions involving more than two principals, linking this limitation to problems like CSRF, clickjacking, and the Confused Deputy.
Alter (YC S25) launched Alter Vault, a privileged access management and authorization platform that gives AI agents their own scoped credentials, policies, and audit trails instead of shared API keys.
A discussion of an often-overlooked agent evaluation case: what happens when a user's data access is revoked mid-conversation, covering stale context, cached retrievals, and cross-account cache leaks, and where enforcement should live in the stack.
A Lobsters discussion exploring whether Rust (or future languages) should add a `read` visibility modifier for struct fields, allowing public read access without public write access, and asking about hidden language-design gotchas and sensible defaults.
作者探讨构建会操作真实账户的 AI agent 时的授权边界：读取类操作允许常驻访问，而发送、消费、删除或发布类操作每次都需人工确认，并询问社区如何在大规模运行 agent 时处理写权限凭证。
作者分享为生产环境中执行分析和调试任务的 AI 代理设计数据库访问控制的经验：为每次查询签发可过期的单次权限，并在使用时重新校验，同时指出设计中仍存在的缺口，最后向社区征求其他方案。
讨论在将 AI 助手接入公司内部数据时常见的权限泄漏问题，并给出了一份检查清单和测试方法，包括按用户身份查询源数据、字段级权限、总量与排名泄漏、缓存与日志的同等保护、以及用假记录和测试用户做回归测试。
提出MAIAM多层AI访问模型，按目的、安全与能力（而非发布形式）分级管理AI访问：Tier1面向学习、Tier2面向受控探索、Tier3仅限严格问责的前沿AI访问，主张可及性应与能力与风险成比例。
作者观察 AI 代理在现有软件上的工作方式后指出，大多数软件缺少代理与应用之间的中间访问层，导致代理只能直接操作为人类设计的界面。文章提出代理就绪的三层架构：应用层、代理层，以及负责权限、审批和结构化访问的中间层。
A production-grade RAG checklist covering citations on every answer, refusing to answer when context doesn't support it, non-bypassable access control, and non-blocking ingestion, shared as a YouTube tutorial video.
一篇基于论坛讨论的经验帖，总结了 AI agent 上线前的权限审查清单：给 agent 独立身份、按实际凭证核对可访问范围、严格分离读写权限、用拒绝性问题测试过度授权，以及检查撤销权限后缓存答案是否仍然泄露。
The Open Instinct team open-sourced their personal-agent app and explains why tool allowlists alone fail the confused-deputy problem, proposing three checks: verifying requester identity from transport, authorizing the operation, and constraining returned fields before they reach lower-trust contexts.
提出Analytical Memory Unit (AMU)方案，通过为AI代理共享记忆附加完整数据派生血缘图并按列级权限门控检索，实现隐私保护的企业级记忆治理，消除18.8-25.5%的跨部门数据泄露，同时保持81.5-82.6%的记忆复用率。
A blog tutorial showing how to build a self-hosted HTTP tunneling service — similar to ngrok or Cloudflare Quick Tunnels — using only OpenSSH reverse forwarding and an nginx proxy with wildcard DNS, Let's Encrypt certificates, and ngx_http_secure_link_module for hashed, expiring access URLs.
Firezone details why it abandoned the leading directory sync standard to build its own custom engine, covering how users, groups, and members are synced from identity providers like Entra, Okta, and Google. The post explains the design challenges of keeping app-side copies of an organization's directory fast and consistent.
该论文形式化了分布式多智能体委派中的容错预算守恒机制，提出基于量化资源向量、排他托管信用与委托DAG的防超额花费方案，并通过TLA+模型检查与崩溃注入实验证明了账本与效果守恒等安全属性。
The author compares AgentWS workspace infrastructure against protected Git worktrees for multi-agent file updates, showing identical outcomes but far less custom code with AgentWS. The post highlights ACLs, recovery after worker failures, and conflict handling as requirements beyond plain Git.
Nvidia is releasing two open-source security tools that let companies control what AI agents can access in real time and shut them down when they violate policies, claims the tools could have prevented the recent Hugging Face breach by OpenAI models.