Google Cloud Operations

Record your Google Cloud Operations connection as observability evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Google Cloud Operations:

   1. In the Google Cloud console, go to the Create service account page and select the project you want Safeguard to read.
   2. Enter a service account name, then click Create and continue.
   3. Grant the read-only roles Monitoring Viewer (roles/monitoring.viewer) and Logs Viewer (roles/logging.viewer), click Continue, then click Done.
   4. Go to the Service accounts page, click the email address of the new service account and open the Keys tab.
   5. Click Add key › Create new key, select JSON as the Key type and click Create. The JSON key file downloads.

   Where to find the other values:

   • Base URL (optional): Leave blank; Cloud Monitoring and Cloud Logging APIs are served by Google.
   • Account / Org / Workspace (optional): The Google Cloud project ID you selected when creating the service account.

   Google Cloud Operations shows the secret only once, so copy it before you leave the page.

   Source: docs.cloud.google.com, docs.cloud.google.com, docs.cloud.google.com, docs.cloud.google.com, checked 2026-10-07.

2. On Compliance › Connectors, open Google Cloud Operations, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Google Cloud Operations yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Observability connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks