QuestionQ68

VerifiedSecuring and governing agentic workflows

You are configuring a secure agent-to-tool API integration for a financial agent on Gemini Enterprise Agent Platform. The agent calls an internal payment processing microservice protected by OAuth 2.0.

To comply with strict enterprise security policy, you must ensure that:

  1. OAuth client credentials used for service-to-service tool authentication are encrypted at rest and never hardcoded in tool definitions or repository source code.
  2. Tool execution is strictly limited to the minimum required API permissions, so the agent cannot perform unauthorized administrative operations on the payment microservice.

What should you do?

Choose two
Explanation

Least-privilege OAuth scopes restrict the payment tool to the required operations, provided the authorization server issues those scopes and the microservice enforces them. Storing client credentials in managed secret storage avoids hardcoding them in tool definitions or source code. Agent Identity auth manager also provides a managed credential vault and supports 2-legged OAuth for an agent acting on its own behalf. (docs.cloud.google.com)

The intended configuration requires verification: Google's 2-legged OAuth documentation shows client credentials supplied to the auth provider but does not document a Secret Manager resource URI in that configuration. Agent Registry documents provider bindings separately. (docs.cloud.google.com)

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!