Security
GCP Service Account Cleanup: Remove Stale Automation Access
GCP service account cleanup is an access review with an operational rollback plan. The stale identity is the visible object, but the real work is finding callers, replacing permissions, and avoiding a silent automation outage.
The useful output is an access-removal record with caller evidence, permission diff, staged disable date, and rollback owner. Keep the review concrete: Disable keys or remove high-risk permissions before deleting the whole identity, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when breaking deployment or data export jobs.
Key takeaways
- Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
- Use a window long enough to include deploys, scheduled jobs, and data exports before deciding that “quiet” means “unused.”
- Prefer reversible changes first when breaking deployment or data export jobs is still plausible.
- Leave behind an access-removal record with caller evidence, permission diff, staged disable date, and rollback owner so the next review starts with context.
- Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.
Find the Real Callers
Start with one slice of Google Cloud projects where the cleanup candidates are visible to both the owner and the person paying the operational cost. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.
| Field | Why it matters |
|---|---|
| Owner | Cleanup needs a person or team that can accept the decision |
| Current purpose | A short reason to keep the item, written in present tense |
| Last meaningful use | last use, permission scope, owner, rotation age, and reachable systems |
| Dependency evidence | audit logs, deployment references, identity provider records, and service owners |
| Risk if wrong | The outage, data loss, access failure, or rollback gap the review must avoid |
| Next action | Keep, reduce, archive, disable, remove, or investigate |
Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.
Access Evidence to Collect
The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For GCP service account cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Last use | Authentication logs, key use, token activity, and API calls | No legitimate use appears in the review window |
| Caller map | Deploy jobs, workloads, CI systems, scheduled exports, and service bindings | No active caller depends on the identity |
| Permission shape | Policies, roles, scopes, group membership, and reachable data | Access is broader than any current need |
| Rotation path | Replacement identity, key rotation, workload identity binding, and rollback plan | The team can remove or reduce access safely |
Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.
If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.
Example Evidence Check
Key age is a starting point. Confirm workload callers before disabling or deleting a key.
gcloud iam service-accounts keys list \
--iam-account="$SERVICE_ACCOUNT_EMAIL" \
--format='table(name,validAfterTime,validBeforeTime,keyType)'Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.
Reduce Access in Stages
Use the least permanent move that proves the decision. In GCP service account cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.
- Disable keys or remove high-risk permissions before deleting the whole identity.
- Move active callers to a named replacement with least privilege.
- Delete old secrets, bindings, and documentation references after the cutover.
Track the cleanup candidate with a simple priority score:
| Score | Good sign | Bad sign |
|---|---|---|
| Impact | Meaningful spend, risk, toil, noise, or confusion disappears | The item is cheap and low-risk but politically distracting |
| Confidence | Owner, purpose, and dependency path are understood | The team is guessing from age or name |
| Reversibility | Restore, recreate, re-enable, or rollback path exists | Deletion would be the first real test |
| Prevention | A rule can stop recurrence | The same pattern will return next month |
Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.
Access You Should Not Rush
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- CI/CD deployers, data exports, incident automation, and vendor integrations.
- Keys copied into places that audit logs do not make obvious.
- Nested groups or inherited roles that hide the real access path.
For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.
Run the Removal Review
Run GCP service account cleanup as a decision review, not an open-ended hygiene project.
- Pick the narrow scope and export the candidate list.
- Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
- Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
- Apply the least permanent useful change first.
- Watch the signals that would reveal a bad decision.
- Complete the final removal only after the review window closes.
- Save an access-removal record with caller evidence, permission diff, staged disable date, and rollback owner.
For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.
Make Stale Access Harder
Prevention should change the creation path, not just the cleanup path. For GCP service account cleanup, the useful prevention fields are owner, expiry date, least-privilege scope, rotation schedule, and removal notes. Make those fields part of normal creation and review.
- Require owner, purpose, expiry, and rotation schedule for non-human identities.
- Prefer short-lived credentials and workload identity where the platform supports it.
- Report unused identities and keys as security debt, not just cleanup backlog.
The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.
Example Decision Record
Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.
| Field | Example entry for this cleanup |
|---|---|
| Candidate | Stale service accounts in Google Cloud projects |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Last use, Caller map, and owner confirmation |
| First reversible move | Disable keys or remove high-risk permissions before deleting the whole identity |
| Watch signal | The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong |
| Final action | Keep, reduce, archive, disable, or remove after a window long enough to include deploys, scheduled jobs, and data exports |
| Prevention rule | Require owner, purpose, expiry, and rotation schedule for non-human identities |
This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.
FAQ
How often should teams do GCP service account cleanup?
Use a window long enough to include deploys, scheduled jobs, and data exports for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.
What is the safest first action?
The safest first action is usually ownership repair plus evidence collection. After that, disable keys or remove high-risk permissions before deleting the whole identity. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to ci/cd deployers, data exports, incident automation, and vendor integrations. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.
How do you make the decision useful later?
Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.