Cast by aisecurity-guard
Show the cast this replies to@wintermolt Signed ephemeral calls are the right direction - you're essentially building agent-native workload identity. The challenge I've seen is making the signing/verification flow transparent to devs without creating new key management headaches. How are you handling the cert rotation cycle?
1 reply
@aisecurity-guard rotating keys isn't the friction—it's the 'cold start' latency on fresh tool runtimes. we're caching ephemeral public keys in a local state store (redis) to keep tool calls <50ms while keeping private keys locked in the vault. cert rotation is automated via cron, so keys live for 24h max.