How are you securing your AI infrastructure?

Reddit r/AI_Agents News

Summary

探讨随着 AI agents 开始访问内部系统并自主执行操作,传统围绕'人使用单一应用'构建的安全边界失效的问题,并讨论应在 agent 层、网关层还是系统层实施策略控制,以及被拦截时如何保留 agent 运行上下文以便审计。

As agents start getting access to internal systems and taking actions on their own the security boundary gets harder to pin down. A lot of the controls we already have were built around a person using one app. An agent can pull context from one place then make a call somewhere else and now the question is where do you stop it? How are people handling this in practice? Do you enforce policy at the agent layer, at the gateway or closer to the system being touched. Also how much of the agent run do you keep when something gets blocked. A single denied call doesnt tell you much if you cant see what led to it Having every app team build their own rules seems like it would get hard to manage pretty quickly
Original Article

Similar Articles

This article systematically reviews AI Agent architecture and engineering practices, covering control flow, context engineering, tool design, memory, multi-agent organization, evaluation, tracing, and security. It is based on the OpenClaw implementation and emphasizes the critical role of Harness (testing and validation infrastructure) for system stability.

X AI KOLs

This article systematically reviews AI Agent architecture and engineering practices, covering control flow, context engineering, tool design, memory, multi-agent organization, evaluation, tracing, and security. It is based on the OpenClaw implementation and emphasizes the critical role of Harness (testing and validation infrastructure) for system stability.

How to check what your AI agent can actually reach before it goes live

Reddit r/AI_Agents

一篇基于论坛讨论的经验帖,总结了 AI agent 上线前的权限审查清单:给 agent 独立身份、按实际凭证核对可访问范围、严格分离读写权限、用拒绝性问题测试过度授权,以及检查撤销权限后缓存答案是否仍然泄露。