SSH Authorized Key Cleanup for Contractor Access

SSH authorized key cleanup starts with machine access that outlived a project, contractor, bastion, or emergency repair path. The key may not show recent logins, but removing it blindly can lock out automation or the only documented recovery route.

For stale contractor SSH keys, the review has to connect risk acceptance, reachability, compensating controls, and the current owner. The useful output is an SSH key cleanup record with fingerprints, host scope, login evidence, automation check, and staged removal date: Move valid users to centralized SSH certificates or bastion roles before deleting keys, keep proof of the security decision, and avoid letting revoking valid emergency access or leaving old external access on hosts become the hidden default.

Key takeaways

• Review stale contractor SSH keys through Key identity, Login behavior, Automation path, not age alone.
• Use one maintenance cycle plus the longest backup, deploy, and emergency-access interval before deciding that quiet means unused.
• Start with the reversible move: move valid users to centralized ssh certificates or bastion roles before deleting keys.
• Slow down when revoking valid emergency access or leaving old external access on hosts is still plausible.
• Prevent repeat cleanup by making teams create ssh access with owner, source system, expiry, and emergency replacement.

Map Machine Access

Start with one host group across authorized_keys files, bastions, configuration management, user accounts, login logs, and automation jobs. 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.

SSH Key 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 SSH authorized key cleanup for contractor access, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Key identity	Comment, fingerprint, owner, source repository, config management rule, and user account	No current owner can justify the key
Login behavior	SSH auth logs, bastion records, sudo activity, and failed attempts	The key has no legitimate use across the review window
Automation path	Deploy jobs, backup scripts, monitoring checks, and repair runbooks	No non-human workflow depends on the key
Replacement access	SSO, certificates, bastion role, break-glass process, and rollback plan	Valid access survives after key removal

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 Key Review

Review fingerprints and config-management references before deleting key lines from hosts.

ssh-keygen -lf ~/.ssh/authorized_keys
rg "ssh-rsa|ssh-ed25519|authorized_keys|TrustedUserCAKeys" infra ansible puppet chef scripts
rg "bastion|deploy_key|break-glass|ssh" docs runbooks .github

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.

Stage Key Removal

Use the least permanent move that proves the decision. In SSH authorized key cleanup for contractor access, 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 valid users to centralized SSH certificates or bastion roles before deleting keys.
• Remove copied keys from configuration management after hosts converge.
• Stage key removal on one host group and watch failed-login logs.

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 Paths That Hide

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

• Break-glass access, backup jobs, legacy deploy scripts, and vendor support keys.
• Keys pushed by configuration management after manual removal.
• Shared Unix accounts where key comments do not prove identity.

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 SSH Access Review

Run SSH authorized key cleanup for contractor access as a decision review, not an open-ended hygiene project.

1. Pick the narrow scope and export the candidate list.
2. Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
3. Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
4. Apply the least permanent useful change first.
5. Watch the signals that would reveal a bad decision.
6. Complete the final removal only after the review window closes.
7. Save an SSH key cleanup record with fingerprints, host scope, login evidence, automation check, and staged removal date.

For broader cleanup planning, use the cleanup library to pair this guide with related notes.

Prefer Short-Lived Access

Prevention should change the creation path, not just the cleanup path. For SSH authorized key cleanup for contractor access, 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.

• Create SSH access with owner, source system, expiry, and emergency replacement.
• Prefer short-lived certificates over permanent authorized_keys entries.
• Review host keys when projects, contractors, bastions, or deploy systems retire.

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 contractor SSH keys in servers, bastions, configuration management, and temporary access workflows
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Key identity, Login behavior, and owner confirmation
First reversible move	Move valid users to centralized SSH certificates or bastion roles before deleting keys
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 one maintenance cycle plus the longest backup, deploy, and emergency-access interval
Prevention rule	Create SSH access with owner, source system, expiry, and emergency replacement

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 SSH authorized key cleanup for contractor access?

Use one maintenance cycle plus the longest backup, deploy, and emergency-access interval 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 valid users to centralized ssh certificates or bastion roles before deleting keys. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to break-glass access, backup jobs, legacy deploy scripts, and vendor support keys. 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.