Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should security teams investigate service account key…
Governance, Ownership & Risk

How should security teams investigate service account key usage in Google Cloud?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Governance, Ownership & Risk

Start by correlating Cloud Monitoring authentication events with audit logs. Use the key ID or service account ID to identify when the key was used, then review creation logs, caller IP, user agent, and impersonation chains. This helps distinguish human activity from workload activity and supports faster review of exposed or overused keys.

Correlating the Right Signals for Service Account Key Use

The investigation starts by tying the key ID back to the service account, then aligning authentication events with the surrounding audit trail. That gives you a usable timeline for when the key authenticated, which principal appears to have exercised it, and whether the activity looks like expected workload behaviour or a more suspicious interactive pattern.

In Google Cloud, that means treating Cloud Monitoring authentication events and audit logs as complementary evidence. The authentication record shows usage, while the audit log can show key creation, changes to the service account, delegation activity, and other context that helps you decide whether the key was simply present or actually driving access.

When the usage pattern is unclear, review the same identity across its related control plane events. If the key was used soon after creation, repeatedly from unusual infrastructure, or in parallel with impersonation activity, the account may be serving as a broad access path rather than a narrow workload credential.

What to Extract From Each Key Event

Once you have the first and last observed use of the key, build out the surrounding evidence set. The most useful fields are caller IP, user agent, target resource, and any impersonation chain that appears in the audit trail. Together they help separate legitimate automation from copied credentials, scripted abuse, or human misuse of a credential that should have remained non-interactive.

Service account key investigation is rarely about a single event. It is about identifying the access pattern behind that event: whether the key was used by the expected workload, whether the same source repeatedly appears, and whether the activity matches the service account’s normal purpose. If the source changes abruptly, that is often more informative than a single anomalous request.

For teams running broader Google Cloud programs, the same review should be connected to the control environment around the key. NHIMG’s Google Cloud Security Guide is useful when you need to place key usage into the wider logging, IAM, and org-policy picture rather than treating the alert in isolation.

How to Decide Whether the Key Is Exposed or Just Busy

Not every observed use of a service account key is a compromise, but volume and context matter. A key that is being used by one known workload from a stable source is different from a key that appears across multiple environments, from changing IPs, or alongside unexpected API calls. That is why the investigator should compare the observed usage to the service account’s intended role and the systems that are supposed to depend on it.

It also helps to distinguish the key from the surrounding identity design. If the workload could have used short-lived credentials or impersonation instead of a long-lived key, the investigation should ask why the static key exists at all. That question often surfaces hidden operational dependencies, stale integrations, or overbroad access that makes the key more attractive to an attacker and harder to monitor cleanly.

If the account is part of a broader workload-identity pattern, NHIMG’s Cloud Workload Identity Guide provides useful background on how keyless patterns change what investigators should expect to see. For teams focused specifically on Google Cloud identity design, the Google Cloud IAM and Service Accounts Guide helps connect key use to impersonation, least privilege, and credential lifecycle choices.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AU-6 — Audit Review, Analysis, and ReportingKey usage investigation depends on reviewing and correlating audit evidence.
IA-5 — Authenticator ManagementService account keys are authenticators whose lifecycle and use must be controlled.
IA-9 — Service Identification and AuthenticationThe subject concerns a service account authenticating with a non-human credential.
Recommendation — Correlate key-use events with audit records to reconstruct source, timing, and actor context. Review key lifecycle, usage, and rotation triggers when usage appears abnormal. Verify that service-to-service authentication relies on the intended service identity and credential path.
CIS Controls v8CIS-5 — Account ManagementService account key usage is an account governance and monitoring problem.
Recommendation — Inventory service accounts and review their usage, ownership, and credential status regularly.

Practitioner Guidance

What to verify: Confirm that the key usage lines up with a known workload, expected source network, and expected user agent before treating it as benign. If the key is used outside the normal deployment path, assume the blast radius may be wider than the original alert suggests.

What to measure: Track first seen, last seen, source diversity, and whether the key appears in audit events that also show impersonation or privilege changes. A sudden change in any of those signals is often a better trigger for escalation than simple request count.

Practitioner takeaway: The goal is not just to see that a service account key was used, but to prove who or what used it, from where, and with what authority. If you cannot build that chain confidently, treat the key as a potentially exposed access path and investigate the surrounding identity controls, not just the event itself.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org