Individual skill

investigating-gcp-incidents

Investigate a security incident in Google Cloud — establishing what audit logging exists before trusting a gap, reconstructing activity from Cloud Audit Logs, triaging service-account and OAuth abuse, following Security Command Center findings, and scoping IAM and resource changes. Use when responding to a suspected GCP compromise, investigating a leaked service-account key, working a Security Command Center or Event Threat Detection alert, or reconstructing what a principal did across a GCP organization.

secskills-defense/skills/investigating-gcp-incidents/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 188
Repository last updated: Sep 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

security Repository topic
skills Repository topic
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 8,732 bytes
SKILL.mdcore · 8,732 bytes
SKILL.mdcore · 8,732 bytes
SKILL.mdcore · 8,732 bytes
SKILL.mdcore · 8,732 bytes

Read excerpt


# Investigating GCP Incidents

The completeness of a GCP investigation is decided before the incident, by
which audit logs were enabled. The single most damaging mistake is reading an
empty query result as "nothing happened" when the real answer is "that log
category was never turned on." Establish visibility first; conclude second.

GCP's audit model is not AWS's and not Azure's. Two categories are always on
and two are mostly off, and knowing which is which is the difference between a
scoped investigation and a false all-clear.

## When to Use

- Responding to a suspected compromise in a GCP project or organization