Initial Access: Dormant Service Account Key Created

This document describes a threat finding type in Security Command Center. Threat findings are generated by threat detectors when they detect a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index.

Overview

A dormant user-managed service account key was created. In this context, a service account is considered dormant if it has been inactive for more than 180 days.

How to respond

To respond to this finding, do the following:

Step 1: Review finding details

  1. Open the Initial Access: Dormant Service Account Key Created finding, as directed in Reviewing findings.

  2. In the finding details, on the Summary tab, note the values of following fields.

    Under What was detected:

    • Principal email: the user who created the service account key

    Under Affected resource:

    • Resource display name: the newly created dormant service account key
    • Project full name: the project where that dormant service account resides

Step 2: Research attack and response methods

  1. Use service account tools, like Activity Analyzer, to investigate the activity of the dormant service account.
  2. Contact the owner of the Principal email field. Confirm whether the legitimate owner conducted the action.

Step 3: Implement your response

The following response plan might be appropriate for this finding, but might also impact operations. Carefully evaluate the information you gather in your investigation to determine the best way to resolve findings.

  • Contact the owner of the project where the action was taken.
  • Remove the access of the owner of the Principal email if it is compromised.
  • Invalidate the newly created service account key in the Service Accounts Page.
  • Consider deleting the potentially compromised service account and rotate and delete all service account access keys for the potentially compromised project. After deletion, applications that use the service account for authentication lose access. Before proceeding, your security team should identify all impacted applications and work with application owners to ensure business continuity.
  • Work with your security team to identify unfamiliar resources, including Compute Engine instances, snapshots, service accounts, and IAM users. Delete resources not created with authorized accounts.
  • Respond to any notifications from Cloud Customer Care.
  • To limit who can create service accounts, use the Organization Policy Service.
  • To identify and fix overly permissive roles, use IAM recommender.

What's next