# Source: https://docs.datadoghq.com/security/default_rules/def-000-phy.md

---
title: Google Compute Engine instances created in multiple zones by user
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Google Compute Engine instances created
  in multiple zones by user
---

# Google Compute Engine instances created in multiple zones by user
Classification:attackTactic:[TA0040-impact](https://attack.mitre.org/tactics/TA0040)Technique:[T1496-resource-hijacking](https://attack.mitre.org/techniques/T1496) 
## Goal{% #goal %}

Detect when multiple Google Compute Engine instances are created in multiple distinct zones by an individual user or service account. This could be an indication of cryptomining activity.

## Strategy{% #strategy %}

Monitor Google Cloud Audit logs and detect when a single user or service account evokes the `v1.compute.instances.insert` or `beta.compute.instances.insert` API call in multiple distinct zones.

## Triage and response{% #triage-and-response %}

1. Determine if the user `{{@usr.id}}` and IP address `{{@network.client.ip}}` should be performing the observed event: `{{@evt.name}}`.
1. If the action is legitimate, consider including the user in a suppression list. See [Best practices for creating detection rules with Datadog Cloud SIEM](https://www.datadoghq.com/blog/writing-datadog-security-detection-rules/#fine-tune-security-signals-to-reduce-noise) for more information.
1. Otherwise, use the Cloud SIEM - User Investigation dashboard to see if the user `{{@usr.id}}` has taken other actions.
1. If the results of the triage indicate that an attacker has taken the action, begin your company's incident response process and an investigation.