Google Cloud Service Account accessing anomalous number of Google Cloud APIs

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect when a Google Cloud service account is compromised.

Strategy

Inspect the Google Cloud admin activity logs (@data.logName:*%2Factivity) and filter for only Google Cloud service accounts (@usr.id:*.iam.gserviceaccount.com). Count the unique number of Google Cloud API calls (@evt.name) which are being made for each service account (@usr.id). The anomaly detection baselines each service account and then generates a security signal when a service account deviates from their baseline.

To read more about Google Cloud audit logs, read the blog post.

Triage and response

Investigate the logs and determine whether or not the Google Cloud service account is compromised.

Changelog

  • 17 October 2022 - Updated tags.
PREVIEWING: antoine.dussault/service-representation-ga-docs-us1