Service Account Cleanup: Reduce Automation Access Safely

Service account cleanup is about proving which automation still needs an identity. A service account may belong to a deployment job, a data export, a workload identity binding, a vendor integration, or a migration that ended months ago.

The useful output is a service-account cleanup record with workload callers, credential inventory, permission diff, cutover date, and rollback owner. Keep the review concrete: Move known callers to a replacement identity before deleting keys or the account, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when breaking deploys and scheduled 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, data exports, and incident automation before deciding that “quiet” means “unused.”
Prefer reversible changes first when breaking deploys and scheduled jobs is still plausible.
Leave behind a service-account cleanup record with workload callers, credential inventory, permission diff, cutover 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.

Map Automation Callers

Start with one service account family across workload bindings, CI secrets, scheduled jobs, data exports, IAM grants, and owner records. 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.

Service Account Evidence

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 service account cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Workload callers	Deploy jobs, pods, serverless functions, data pipelines, CI workflows, and vendor integrations	No active workload should authenticate as the account
Credential shape	Keys, token exchange, workload identity bindings, secret copies, and rotation age	Long-lived credentials remain where managed identity would now work
Permission fit	Roles, scopes, accessible projects, storage, databases, and production systems	The account can reach more than its current job requires
Cutover path	Replacement identity, staged disable plan, audit-log watch, and rollback owner	Callers can move before final revocation

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

Search for workload callers and copied credentials before disabling a service account.

rg "SERVICE_ACCOUNT|serviceAccountName|workload_identity|client_email" infra deploy .github
rg "data export|scheduled job|vendor|deployer" docs runbooks scripts
rg "key_file|credentials_json|service_account" src scripts config

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.

Move Callers Before Revoking

Use the least permanent move that proves the decision. In 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.

Move known callers to a replacement identity before deleting keys or the account.
Remove broad roles first when the account still has uncertain but legitimate use.
Delete copied credentials from CI, manifests, docs, and local examples 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.

Automation That Needs Patience

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Deployment pipelines, scheduled exports, incident automation, and vendor jobs.
Workloads using copied keys instead of an auditable identity binding.
Cross-project or cross-account roles whose owner is not visible from the service account name.

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 Identity Cutover

Run 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 a service-account cleanup record with workload callers, credential inventory, permission diff, cutover 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.

Prefer Managed Identity Paths

Prevention should change the creation path, not just the cleanup path. For 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 each non-human identity to declare owner, workload, credential type, expiry, and rotation path.
Prefer platform-native workload identity over long-lived copied keys.
Review service accounts after migrations, vendor offboarding, and pipeline rewrites.

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 cloud and SaaS platforms
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Workload callers, Credential shape, and owner confirmation
First reversible move	Move known callers to a replacement identity before deleting keys or the account
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, data exports, and incident automation
Prevention rule	Require each non-human identity to declare owner, workload, credential type, expiry, and rotation path

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 service account cleanup?

Use a window long enough to include deploys, scheduled jobs, data exports, and incident automation 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, move known callers to a replacement identity before deleting keys or the account. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to deployment pipelines, scheduled exports, incident automation, and vendor jobs. 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.