User Access Review for Cloud Servers: SSH Keys, Admins, and Permissions

Serdar Tekin
Serdar Tekin
Co-Founder & CTO
Updated Nov 19, 202616 min read
Written for: Developers, administrators, MSPs, and small teams reviewing privileged access across Linux, Windows, automation, private networks, and recovery systems.
SecurityAccess ReviewAccess ControlSSHRDPCloud OperationsLeast Privilege
Last reviewed:
Guide
User Access Review for Cloud Servers: SSH Keys, Admins, and Permissions
rafftechnologies.com/learn
On this page

Key Takeaways

Review identities, credentials, privileges, reachability, and recovery access together. Give every item a named owner and one outcome: keep, reduce, rotate, disable, or remove. Offboarding should be immediate.

Review SSH keys and team roles in your Raff account.

  1. 1Pick a Linux imageUbuntu, Debian and more, with your SSH key added.
  2. 2Choose a sizeFrom $4.99 a month. Resize when your app grows.
  3. 3Connect over SSHYour server is up in about 55 seconds.

Ubuntu, Debian and other Linux distributions with full root and SSH access, up and running in about 55 seconds.

An access review is a recurring check of who and what can reach your systems, what each identity can do, why that access still exists, and whether it should be kept, reduced, rotated, disabled, or removed. A useful cloud access review covers human accounts, SSH keys, Windows/RDP users, API keys, service accounts, private-network membership, recovery permissions, and other privileged paths—not only users in a cloud dashboard.

For Raff Technologies environments, the same principle applies across Linux VMs, Windows workloads, private networking, automation, and recovery: every privileged path should have a known owner, current purpose, appropriate scope, and clear next action.

The practical goal is simple:

No privileged access should survive only because nobody remembers why it exists.

Access review: quick framework

For every user, key, token, service account, and privileged network path, answer five questions:

  1. Who or what owns it?
  2. Which systems can it reach?
  3. Which actions can it perform?
  4. Is that access still required today?
  5. What should happen next?

Every item should end in one of five decisions:

DecisionMeaning
KeepAccess is justified and correctly scoped
ReduceAccess is broader than the current role requires
RotateThe credential is old, shared, exposed, or difficult to attribute
DisableAccess may be needed again but should not remain active now
RemoveThe business or technical reason no longer exists

“Reviewed” is not an outcome. If excessive or unexplained access is found, the review should produce a change, owner, or documented dependency.

What is a user access review?

A user access review verifies that current permissions still match current responsibilities.

In cloud infrastructure, that usually means reviewing more than human user accounts. Include:

  • cloud/project users;
  • Linux accounts and SSH keys;
  • Windows and RDP users;
  • sudo and local Administrator membership;
  • API keys and tokens;
  • CI/CD and service identities;
  • VPN, bastion, and private-network access;
  • public administrative exposure;
  • backup and recovery permissions;
  • break-glass access.

The complete path is:

Text
Identity ↓ Credential ↓ Network reachability ↓ Authentication ↓ Privilege ↓ Resource or business action

Removing a contractor from a cloud dashboard is incomplete if their SSH key still works. Disabling a Windows account is incomplete if the person still knows a shared Administrator password. Rotating one API key is incomplete if an old personal token still runs in CI/CD.

Access reviews should cover identity, credentials, privileges, and reachability together

Checking only one layer creates false confidence.

LayerExamplesReview question
Human identityCloud user, Linux user, Windows userDoes this person still need access?
CredentialSSH key, password, API key, certificateIs it attributable, protected, and current?
Machine identityCI/CD job, monitoring agent, backup processDoes the automation still exist and need this scope?
PrivilegeRoot, sudo, local Administrator, backup deletionIs the permission broader than required?
ReachabilityPublic SSH/RDP, VPN, VPC, bastionCan this identity reach more systems than it should?
Recovery accessSnapshot, backup, restore, break-glass accessCan one identity remove both production and recovery?

A strong access review evaluates all of these together. For the underlying role, permission, and identity model, see Cloud Access Management for Small Teams.

User access review best practices for small teams

Small teams do not need heavyweight governance software to run a useful review. They do need a repeatable process.

1. Maintain a current access inventory

Track privileged access in one place with at least:

FieldExample
IdentityJane Doe / deploy-api
TypeHuman / service account / SSH key
OwnerPlatform team
EnvironmentProduction
Resource scopeweb-01, db-prod
PrivilegeSSH user / sudo / API write
ReasonOn-call administration
Last reviewed2026-09-01
ExpiryNone / project end date
DecisionKeep / reduce / rotate / disable / remove

The inventory does not need to mirror every operating-system detail. It needs enough information to explain why access exists and who is accountable for it.

2. Prioritize high-impact permissions

Review identities first when they can:

  • create or delete infrastructure;
  • change firewall rules or private-network routes;
  • add administrators or SSH keys;
  • manage DNS;
  • view or change secrets;
  • export customer data;
  • restore or delete recovery points;
  • modify production databases;
  • change billing or account-level settings;
  • disable monitoring or logging.

These permissions have larger failure impact than ordinary read-only access.

3. Prefer named identities over shared credentials

Shared credentials make access reviews difficult because the team cannot reliably attribute use.

Avoid long-lived shared:

  • root passwords;
  • Administrator passwords;
  • SSH private keys;
  • API tokens;
  • VPN credentials;
  • generic production accounts.

Where a shared emergency credential is unavoidable, treat it as break-glass access and protect, audit, and rotate it accordingly.

4. Give temporary access an expiry condition

Temporary access should not silently become permanent.

For migration, support, contractor, or incident access, record:

  • owner;
  • exact scope;
  • reason;
  • start date;
  • expiry date or completion condition.

5. Verify changes after the review

A planned change and an applied change are not the same thing.

If the review says “remove SSH key,” verify that the key no longer authenticates. If a Windows account is disabled, verify sign-in is blocked. If an API token is rotated, confirm the replacement works and the old credential is rejected.

SSH key review should be treated like user-account review

SSH keys are easy to distribute and forget. Each trusted key should have a known owner, purpose, server scope, and removal condition.

Investigate or remove a key when:

  • its owner left the team;
  • nobody can identify who owns it;
  • several people share the same private key;
  • the private key may have been exposed;
  • it is trusted by more servers than required;
  • the automation or project that used it has been retired.

Linux access reviews should also cover:

  • active interactive users;
  • service users with shell access;
  • sudo groups;
  • direct root access;
  • deployment users;
  • old keys in authorized_keys;
  • credentials in home directories;
  • forgotten automation accounts.

A developer who needs logs does not automatically need unrestricted sudo.

Windows and RDP access reviews need separate attention

Windows administration has different access patterns from Linux SSH.

Review:

  • RDP users;
  • local Administrators membership;
  • shared Administrator credentials;
  • vendor and contractor accounts;
  • disabled but reusable accounts;
  • saved credentials on jump hosts or staff devices;
  • public RDP exposure;
  • Network Level Authentication where supported;
  • MFA at the access layer where the selected design supports it;
  • sign-in evidence where retained.

A user may need Remote Desktop access without needing local Administrator rights.

If the network path itself is too broad, use Private vs Public Admin Access and Bastion Host vs VPN vs Public SSH to redesign the access boundary rather than only reviewing users on the existing path.

API keys and service accounts need owners too

Machine identities often outlive human accounts because nobody notices them until an automation breaks.

Review credentials used by:

  • CI/CD pipelines;
  • infrastructure automation;
  • monitoring;
  • backup jobs;
  • applications;
  • integrations and webhooks;
  • migration scripts;
  • command-line tooling.

Each machine identity should answer:

FieldReview question
OwnerWhich person or team is accountable?
PurposeWhich live workload still needs it?
ScopeWhich resources and actions can it access?
StorageWhere is the credential protected?
RotationHow can it be replaced safely?
EvidenceIs recent use visible?
RetirementWhat event should cause removal?

A credential without an owner is difficult to rotate safely. A service identity without a current service should be disabled or removed.

Do not keep long-lived secrets in source code, reusable VM images, tickets, shared chat, or broadly accessible documentation merely because updating the automation is inconvenient.

Offboarding is the most urgent access-review event

A scheduled review can wait for its planned date. Offboarding should not.

When an employee, vendor, or contractor leaves, remove relevant access across:

  • cloud/project membership;
  • Linux users and SSH keys;
  • Windows and RDP accounts;
  • sudo and administrator groups;
  • VPN or bastion membership;
  • API keys and personal tokens;
  • source-control and CI/CD systems;
  • password managers and secrets;
  • monitoring and incident tooling;
  • DNS and domain administration;
  • billing access;
  • customer environments;
  • backup and recovery administration.

Rotate shared credentials the departing person could still use.

Removing the named account is not enough if copied private keys, shared passwords, or personal tokens remain valid.

How often should access reviews happen?

There is no universal review cadence for every workload. Frequency should follow risk, team change, privilege level, and contractual requirements.

A practical starting model can be:

Access areaReview trigger or cadence
Employee offboardingImmediately
Contractor accessAt task completion and during long engagements
Production administratorsAfter material role/team changes and on a recurring schedule
SSH/RDP accessRecurring, with frequency based on exposure and change rate
API keys and service accountsRecurring and after ownership changes
Break-glass accessAfter every use and during periodic recovery checks
Billing and recovery-deletion privilegesRecurring because impact is high
Public admin exposureAfter architecture changes and on a recurring schedule

Increase frequency when contractors are common, customer data is sensitive, an MSP manages many environments, or privileges change frequently.

Privileged access review should focus on business actions

Role names can hide excessive privilege. Review what an identity can actually do.

Instead of asking only whether someone is an “admin,” ask whether the identity can:

  • create or delete infrastructure;
  • modify networking;
  • add other administrators;
  • export customer data;
  • change secrets;
  • delete recovery points;
  • modify production databases;
  • alter billing;
  • disable monitoring.

A support contractor may need logs without database export rights. A deployment identity may need to update one service without being able to delete backups.

Least privilege becomes easier to evaluate when access is described as actions rather than titles.

Review network reachability together with identities

A user may have limited operating-system permissions but still be able to connect to too many resources.

Review:

  • which servers expose SSH or RDP publicly;
  • which source ranges are allowed;
  • who can join a VPN or other private-access path;
  • which routes those users receive;
  • whether one private network creates unnecessary lateral reachability;
  • whether databases are reachable from unrelated systems;
  • whether IPv6 exposure matches IPv4 policy;
  • whether retired hosts still appear in firewall rules.

Private networking reduces exposure. It does not create implicit trust.

Use Cloud Firewall Best Practices and Private Networking: Public vs Private Traffic for the network-policy layer.

Break-glass access needs its own review

Break-glass access is intentionally powerful and rarely used, which makes it easy to forget.

Confirm:

  • the emergency identity or credential still works;
  • access is protected from casual use;
  • authorized users are still correct;
  • recovery instructions are current;
  • use is logged where possible;
  • credentials are rotated after use or exposure;
  • the emergency path has not become routine administration.

An emergency path that cannot be used during an incident is not useful. An emergency path used every day is no longer an emergency control.

Backup and recovery permissions deserve stricter review

Recovery systems are high-impact because an identity able to delete production and every backup can remove the team's recovery options.

Review who can:

  • create recovery points;
  • restore them;
  • change retention;
  • delete snapshots or backups;
  • access application-level exports;
  • alter backup credentials.

Where workload impact justifies it, separate ordinary server administration from backup-deletion rights.

Use Cloud Snapshots vs Backups and Restore Testing Checklist for Production VMs for the recovery side of the design.

Access review evidence: activity is not authorization

The access inventory shows who can act. Logs and activity records can help show who did act.

Useful evidence may include:

  • SSH login history;
  • sudo activity;
  • Windows security events;
  • cloud account changes;
  • API-key use;
  • firewall and private-network changes;
  • deployment records;
  • backup restore/deletion events;
  • incident records.

Do not keep an unexplained privilege indefinitely merely because recent activity is unclear. Investigate the owner and dependency, then make an explicit decision.

A practical access-review meeting for small teams

A lightweight review can follow this sequence:

  1. Inventory users, keys, tokens, service identities, and privileged paths.
  2. Assign a named owner to every item.
  3. Compare each item with the owner's current role or workload.
  4. Review public and private network reachability.
  5. Check recent use where reliable evidence exists.
  6. Choose keep, reduce, rotate, disable, or remove.
  7. Assign required changes to owners.
  8. Apply the changes.
  9. Verify the changes took effect.
  10. Confirm emergency access still works as designed.
  11. Record unresolved dependencies and the next review trigger.

The output should be a change list with owners and due dates, not only a completed checklist.

MSP access reviews need customer-level separation

MSPs and managed IT providers have a larger version of the same problem because administrators may reach several customer environments.

Review whether:

  • one credential is reused across customers;
  • one VPN or private network creates excessive lateral access;
  • customer production access can be attributed to a named person;
  • contractors retain access after an engagement ends;
  • one automation token can modify unrelated tenants;
  • backup or recovery permissions cross customer boundaries.

Prefer named users, customer-scoped permissions, separate credentials, restricted network paths, auditable access, and explicit offboarding.

Use Private Cloud Networking for MSPs and Secure Remote Access for MSPs for the surrounding architecture.

How this applies to Raff infrastructure

A Raff-focused access review can include:

  • Raff Cloud Servers for Linux users, SSH keys, root/sudo access, and VM administration;
  • Windows VM for RDP users and local Administrator access;
  • Raff VPC for current private-networking paths;
  • Data Protection for recovery access, restore authority, and deletion rights;
  • Raff IAM for platform members, project-scoped roles, API keys, MFA, and account-level action records.

Raff provides infrastructure controls and recovery capabilities. Your team still owns guest-OS accounts, SSH/RDP access, credential ownership, application authorization, contractor offboarding, and internal access-review policy.

Audit Linux, Windows, private-network, automation, and recovery access together so every privileged path has a current owner and purpose.

14-day money-back guarantee

Deploy Your Server

User access review checklist

Human access

  • Every privileged account belongs to a named person.
  • Departed users are removed immediately.
  • Contractor access has an expiry or review condition.
  • Linux sudo and Windows Administrator membership are justified.

Credentials

  • SSH keys have identifiable owners.
  • Shared keys and passwords are being eliminated or controlled.
  • API keys and service accounts have owners and purposes.
  • Exposed or unexplained credentials are rotated.

Reachability

  • Public SSH/RDP exposure is intentional.
  • VPN/private-network membership is current.
  • Private routes do not create unnecessary lateral access.
  • Firewall rules for retired systems are removed.

Recovery

  • Backup and snapshot deletion rights are reviewed.
  • Break-glass access has current owners.
  • Emergency access is tested and protected.

Review outcome

  • Every item ends in keep, reduce, rotate, disable, or remove.
  • Required changes have owners and due dates.
  • Applied changes are verified.
  • The next review trigger is recorded.

Frequently asked questions

What is an access review?

An access review checks who or what can reach systems, what each identity can do, why the access still exists, and whether it should be kept, reduced, rotated, disabled, or removed.

What is a user access review?

A user access review verifies that current permissions still match current responsibilities for human users and, in cloud environments, related credentials and privileged paths such as SSH keys, RDP access, and private-network membership.

What should a cloud access review include?

Review human users, Linux and Windows accounts, SSH keys, RDP access, API keys, service accounts, privileged actions, public and private reachability, break-glass access, and recovery permissions.

How often should user access reviews happen?

There is no universal cadence. Offboarding should happen immediately, while recurring reviews should be scheduled according to privilege level, team change, exposure, customer risk, and contractual requirements.

What are user access review best practices?

Maintain an inventory, use named owners, prioritize high-impact privileges, give temporary access an expiry condition, review identity and reachability together, and verify that removals or reductions actually took effect.

Should SSH keys be reviewed like user accounts?

Yes. Each key should have an owner, purpose, server scope, and removal condition. Unexplained or shared keys should be investigated and removed or rotated when no longer justified.

Do API keys and service accounts belong in access reviews?

Yes. Machine identities need owners, limited permissions, protected storage, a rotation method, usage evidence where available, and a defined retirement condition.

What is a privileged access review?

A privileged access review focuses on identities that can perform high-impact actions such as changing infrastructure, adding administrators, exporting data, modifying secrets, or deleting recovery points.

Does private networking eliminate the need for access reviews?

No. Private networking reduces reachability, but user identities, routes, firewall rules, operating-system permissions, application authorization, and stale credentials still require review.

What is the most urgent access-review event?

Offboarding. Access can exist across dashboards, servers, SSH keys, RDP accounts, tokens, repositories, VPNs, secrets, DNS, billing, and recovery systems, so it should be removed as soon as the role ends.

Conclusion

An access review keeps cloud privileges aligned with the people, services, and systems that exist today rather than the organization that existed when access was first granted.

Review human and machine identities, credentials, privileges, network reachability, and recovery access together. Give every privileged item a named owner and current purpose, treat offboarding as immediate, and end every review with a concrete decision: keep, reduce, rotate, disable, or remove.

If the review shows that the access path itself needs redesign, continue with Private vs Public Admin Access or Bastion Host vs VPN vs Public SSH.

Sources

Was this article helpful?
Serdar Tekin
Serdar Tekin
Co-Founder & CTO

Co-Founder & CTO at Raff, focused on cloud infrastructure, systems architecture, security, reliability, and production operations.

Review SSH keys and team roles in your Raff account.

Ubuntu, Debian and other Linux distributions with full root and SSH access, up and running in about 55 seconds.

14-day money-back guarantee

Frequently asked questions

What is an access review?
An access review checks who or what can reach systems, what each identity can do, why the access still exists, and whether it should be kept, reduced, rotated, disabled, or removed.
What is a user access review?
A user access review verifies that current permissions still match current responsibilities for human users and related cloud credentials and privileged paths.
What should a cloud access review include?
Review human users, Linux and Windows accounts, SSH keys, RDP access, API keys, service accounts, privileged actions, public and private reachability, break-glass access, and recovery permissions.
How often should user access reviews happen?
There is no universal cadence. Offboarding should happen immediately, while recurring reviews should be scheduled according to privilege level, team change, exposure, customer risk, and contractual requirements.
What are user access review best practices?
Maintain an inventory, use named owners, prioritize high-impact privileges, give temporary access an expiry condition, review identity and reachability together, and verify that required removals or reductions actually took effect.
Should SSH keys be reviewed like user accounts?
Yes. Each key should have an owner, purpose, server scope, and removal condition. Unexplained or shared keys should be investigated and removed or rotated when they are no longer justified.
Do API keys and service accounts belong in access reviews?
Yes. Machine identities need owners, limited permissions, protected secret storage, a rotation method, usage evidence where available, and a defined retirement condition.
What is a privileged access review?
A privileged access review focuses on identities that can perform high-impact actions such as changing infrastructure, adding administrators, exporting data, modifying secrets, or deleting recovery points.
Does private networking eliminate the need for access reviews?
No. Private networking reduces reachability, but user identities, routes, firewall rules, operating-system permissions, application authorization, and stale credentials still require review.
What is the most urgent access-review event?
Offboarding. Access can exist across dashboards, servers, SSH keys, RDP accounts, tokens, repositories, VPNs, secrets, DNS, billing, and recovery systems, so it should be removed as soon as the role ends.