agent-substrate / agent-substrate/substrate

ateapi needs better audit log

未关闭
#1,582 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
area/api-machinery area/observability area/security kind/feature
主要语言
Go
星标
1.8k
派生
316
平均合并
2 天 43 分钟
30 天内合并 PR
287

描述

Some gaps of the current ateapi audit logs:

1. Denied requests are never logged. The auth interceptor runs before the logging interceptor, so any request that fails auth just disappears. I sent calls with no token, a garbage token, and a Google ID token. All three got Unauthenticated back. Not a single line showed up in either api server pod, not even at debug level.

1. Stream RPCs are never logged. There is no logging interceptor on the stream chain. Reflection calls with a valid token leave no trace.

1. The principal is not the person. kubectl-ate mints a token for the shared ate-client service account, so every operator shows up as system:serviceaccount:ate-system:ate-client. The GKE audit log does not help either since TokenRequest is a data access event and is off by default.

1. No decision field, no resource field. We only have err. Which atespace or actor was touched is buried inside the serialized request and the shape is different for every RPC.

1. We log secrets. Redaction only clears fields named env. The response of MintJWT is a live actor bearer token and it is written to the log in full. Container command and args are logged too.

1. Too noisy to be an audit log. The router and egress health checks call ListActors every two seconds. That is about 7k log lines an hour on an idle cluster, each with the full response body.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。