Establish ownership and a baseline

Record the operating system, version, applications, network exposure and administrator. Confirm that the system still receives security updates. Plan an upgrade if the operating system has reached the end of support.

Capture the current configuration before changing it. Identify the services the application needs and remove or disable services that have no owner or purpose. Keep a rollback plan for changes that could affect availability.

Restrict administrative access

Limit Secure Shell access to approved users and networks where practical. Use individual accounts and keys, protect private keys, and remove access when a person or supplier no longer needs it. Use multi-factor authentication on the control plane and hosting accounts where available.

Avoid direct root login where the operating system supports safer administration. Use least privilege and log administrative actions. Review firewall rules and confirm that public services match the intended design.

Patch, monitor and recover

Apply security updates through a controlled process and restart services when required. Collect logs in a place that a compromised server cannot easily alter. Alert on events that need action, such as repeated login failures or unexpected service changes.

Keep protected backups and test a restore. A server security assessment can review the exposed services, permissions and configuration against the agreed scope.