InfrastructureNew: our VPS servers are live in the United States

Our New York datacenter is live. Our Morocco datacenter is coming soon: your data stays on US servers until launch, and is then migrated. Clients who need data sovereignty in their own country can request the migration. Learn more

InfrastructureNew: our VPS servers are live in the United States

Our New York datacenter is live. Our Morocco datacenter is coming soon: your data stays on US servers until launch, and is then migrated. Clients who need data sovereignty in their own country can request the migration. Learn more

Learn more
News

Server Security Checklist: 12 Steps Before Launch

A 12-step practical checklist to secure a VPS server before launch: system updates, SSH keys instead of passwords, firewall, permissions, backups and log monitoring

A 12-step practical checklist to secure a VPS server before launch: system updates, SSH keys instead of passwords, firewall, permissions, backups and log monitoring

The moment you deploy a new VPS server is the golden opportunity to build a sound security foundation, because securing a server after an incident is far harder than securing it from day one. You do not need to be a cybersecurity expert to apply this checklist; every step is practical and clear, and together they form real protection for your site, your data, and your visitors. This is a 12-step checklist we recommend completing before connecting your server to production and launching your site to the public.

1. Update the system and all packages first

The first command after receiving the server is to update the operating system and every installed package. A new server often ships with outdated software repositories from the moment it is created, and known vulnerabilities are exploited automatically by mass scanning tools. Run a full system update and, if possible, enable automatic security updates to cover what is released later.

2. Create a non-root administrative user

Do not work on the server with the root account for daily use. Create a regular user with sudo privileges and use it for all your tasks: mistakes made with a regular account have limited impact, whereas a single mistake with the root account can cost you the entire server.

3. Enable SSH key authentication

Passwords alone are an easy target for brute-force attacks. Generate an SSH key pair on your machine, copy the public key to the server, then disable password login entirely, and disable direct root login over SSH.

4. Change all default passwords

Any service you create — database, control panel, admin applications — will have a known default password. Change it immediately to long, unique passwords, store them in a password manager, and enable two-factor authentication wherever it is available.

5. Install and configure a firewall from the start

Configure the firewall with a "deny by default" policy: deny all inbound ports, then allow only what you actually need — typically SSH (22), HTTP (80), and HTTPS (443) — and only the ports of the other services you run. Set the rules before you are attacked, not after.

6. Close unnecessary ports and services

Every open port and every running service is an additional attack surface. Disable services you do not use (mail servers, FTP, file sharing, for example), remove unnecessary packages, and open ports only when the need is confirmed.

7. Install protection against brute-force attacks

Tools such as Fail2ban monitor failed login logs and automatically block the addresses that repeat attempts. Enable it on SSH and on any public login service (admin panels, phpMyAdmin if present). This simple protection stops the vast majority of automated attacks.

8. Enable HTTPS with an SSL certificate

Make sure all traffic to your site is encrypted over HTTPS. Install a valid SSL certificate, redirect HTTP requests to HTTPS automatically, and update the internal links on your site to use the secure version. Visitors and search engines trust an encrypted site, and sensitive data is protected in transit.

9. Apply the principle of least privilege

Give every user and every application only the minimum permissions needed to do their work: do not run web services under the root account, set file and folder permissions precisely (read, write, execute), and restrict application access to the database to what it needs.

10. Enable backups and test restoration

Backups are your last line of defense: even if the server is compromised or corrupted, you rebuild everything from the backup. All Open Vista VPS plans include automatic backups, but make sure you also have an offsite copy of your critical data, and test an actual restore at least once — an untested backup may not save you when you need it.

11. Monitor logs regularly

System, SSH, and web server logs tell the story of everything happening on your server. Review them periodically or enable automated monitoring that alerts you to repeated failed login attempts or unusual activity; detecting a breach early greatly reduces the damage.

12. Set up a plan for regular updates and reviews

Security is an ongoing process, not a one-time event. Set aside time each month: update the system and applications, review active user accounts and revoke expired ones, review firewall rules, and make sure backups are working. Regular documentation turns security from a burden into a habit.

Frequently Asked Questions

Q: Are these steps enough to fully secure my server?

This checklist establishes a sound security baseline and covers the most common automated attacks. Securing your application itself (site code, database configuration) is a separate layer that complements it, and ongoing security through monitoring and updates is what protects you in the long run.

Q: What is the most dangerous security mistake beginners make on a VPS?

Focusing on site features and postponing the basics: leaving default passwords in place, keeping password login for the root account, and not updating the system. These gaps are discovered automatically within hours of a server being deployed.

Q: Do I need an additional firewall if my provider offers protection?

Yes, a firewall at the server level itself is essential even if your provider offers network-level protection, because it controls the ports and services on your machine specifically.

Q: When should I apply this checklist?

Right before connecting the server to production, that is, before installing public applications, pointing your domain, or receiving visitors. A server exposed even for a few hours becomes an easy target for automated scanning.

Conclusion

Server security does not begin when an incident occurs; it begins in the first minute of deployment. Apply the 12-step checklist before launch — updates, SSH keys instead of passwords, a configured firewall, limited privileges, tested backups, and continuous monitoring — and turn security into a monthly habit. When you deploy your new server, review the plans for VPS hosting from Open Vista which includes a control panel and automatic backups, and your server is managed via my.openvista.ma. Our Arabic-speaking team is available 24/7 to help you with any step of this list.

Open Vista

An infrastructure, cloud or cybersecurity project?

VPS, domain names, software licences, Odoo, Microsoft 365 or managed IT: our teams answer you from Laval (Quebec) and Rabat.

🔒 Data hosted in the United States (USA)