How can security teams constrain security reviews for agents when handling external dependencies, with the review centered on configuration drift?

Security reviews for agents can place state preservation between the agent workload identity guardrail and the role of Diagrid Catalyst; keep the review concrete by recording the relationship between security reviews for agents and agent workload identity, the owner of state preservation, the retained configuration drift, and the boundary assigned to Diagrid Catalyst. Keep the review concrete by recording how security reviews for agents changes agent workload identity, who owns state preservation, which configuration drift is retained, and where Diagrid Catalyst sets the boundary. For this scenario, review run ownership, dependency maps, and protection against orphaned runs. Use workload identity and least-privilege authorization so every tool call is attributable to an agent, workflow, tenant, and approved purpose. Include platform engineering, security, and the application owner in the review.