We let our cloud agents query prod (with OIDC, not secrets)

Posted by saligrama 1 hour ago

Counter11Comment3OpenOriginal

Comments

Comment by rvz 2 minutes ago

Very bad idea and is just asking for the agent to breached itself via a bad prompt.

Comment by anuptalwalkar 35 minutes ago

Ugh. OIDC’s whole trust model assumes the subject of the token is the responsible party. Sounds like you are opening a door for a future security problem.

OIDC is good when the end user needs short-term access validation and authorization. The claim and responsibilities of what they do are on that user. Now that you have agents involved, the user can just shrug it off, saying 'oh the AI went rogue'. You probably need a separate role for agent specific tasks that severely limits the access specific to your workload, but that is a work of its own.

Comment by motoroco 22 minutes ago

just relating my personal/professional setup, I run Pocket ID for myself and made an agent account for claude. I have it set up with limited access policies to pre-prod Cloudflare resources and Tailscale servers for occasional tasks. I really like the control I have over access, grant it just when it’s needed and only exactly as much as needed. I wish SSO didn’t require biz/enterprise plans on so many services so I could use my OIDC in more ways