---
title: >-
  Attempt to add SSH key to Google Compute Engine project metadata by a
  previously unseen user
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Attempt to add SSH key to Google
  Compute Engine project metadata by a previously unseen user
---

# Attempt to add SSH key to Google Compute Engine project metadata by a previously unseen user
Classification:attackTactic:[TA0003-persistence](https://attack.mitre.org/tactics/TA0003)Technique:[T1098-account-manipulation](https://attack.mitre.org/techniques/T1098) 
## Goal{% #goal %}

Detect when a previously unseen user attempts to add or modify an SSH key to GCE project metadata.

## Strategy{% #strategy %}

This rule monitors Google Cloud Audit Logs to determine when a previously unseen user attempts to add or modify an SSH key in the GCE project metadata. An attacker who has already gained initial access may try to preserve access or laterally move to other GCE instances by adding their SSH key to the project metadata.

**Note:** This rule uses the `New Value` detection method, to determine when a previously unseen user performs this action.

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

1. Reach out to the user or owner of the service account to determine if this action is legitimate.
1. If the action is legitimate, consider including the IP address or ASN in a suppression list. For more information, 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).
1. Otherwise, use the Cloud SIEM - IP Investigation dashboard to see if the IP address: `{{@network.client.ip}}` 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 investigate.