Suspicious GCP Service Account Key Creation for Persistence (via gcp.audit)

PremiumReviewedSigma · Medium · v1
Product
gcp
Service
gcp.audit
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects creation of a GCP service account key which yields long-lived credentials that survive session revocation. The cloud persistence IR guide highlights new service account keys as a favored durable-access technique. Key creation on a sensitive service account from an unexpected identity should be investigated.

Related detections9 linkedT1098.001 — drag to rearrange
Suspicious AWS Login Profile Creation for Persistence
Suspicious Credential Addition to Entra Application via Azure Audit Logs
Suspicious IAM Persistence and Privilege Escalation Actions
Suspicious MURKY PANDA Credential Addition to Entra ID Service Principal (via azure)
Suspicious IAM Access Key Creation for Persistence (via cloudtrail)
Suspicious AWS Administrator Policy Attachment via CloudTrail (via aws)
Suspicious AWS Inline Policy Granting Full S3 Access
Suspicious GCP Service Account Key Creation for Persistence (via gcp.audit)
Malicious Credential Added to an Azure AD Application (via auditlogs)
Suspicious GCP Service Account Key Creation for Persistence (via gcp.audit)
Pivot detection · T1098.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.