how do you track what auth paths an AI agent uses when the app never went through the IdP?
we spun up an agent to handle some internal reporting, read access to a few databases, nothing privileged, at least that's what we assumed at the time. ran for maybe three months without anyone checking in on it.
during a routine audit someone pulled the agent's activity logs and noticed it was authenticating against one of our older internal databases using a credential that wasn't in our secrets manager. traced it back and found the agent had picked up a hardcoded credential sitting in a script from a migration we did two years ago. the original script was supposed to be decommissioned. it wasn't. the credential still worked. the agent found the most efficient path and used it.
the database it was accessing had customer records in it. read-only, so nothing was modified, but the access was never supposed to exist and we had no idea it was happening.
the IdP shows clean. okta has no idea this access path exists because it's not routing through the IdP at all. the application just has its own auth sitting there from years ago and the agent discovered it. there's no connector for it, no provisioning flow, it just exists.
how are people actually tracking what paths an agent takes once it's inside an environment? logging the task completion doesn't help if you don't know what it accessed to get there.