Security Responsibilities on Unmanaged VPS
Short answerOn an unmanaged VPSGrid VPS, you secure the guest OS and everything inside it (patches, firewall, SSH/RDP, apps, data, backups). VPSGrid secures and operates the platform (hypervisor, primary networking, power controls, billing).
Overview
VPSGrid sells unmanaged KVM VPS hosting — you get root/Administrator access and full control inside the VM. That control includes security responsibility. Model overview: What Is Unmanaged VPS Hosting?.
What VPSGrid is responsible for
- Hypervisor / virtualization platform (Proxmox/KVM layer)
- Primary network connectivity to your VPS
- Power controls (boot, reboot, shutdown) and client-area console access
- Billing, account access, and platform-level abuse handling
- Provisioning workflow and primary IP assignment
VPSGrid does not log into your guest OS to patch applications, harden SSH/RDP, or debug your codebase on standard unmanaged plans.
What you are responsible for securing
| Area | Your responsibility |
|---|---|
| Operating system | Install security updates, reboot when required, remove unused packages |
| Access control | Strong passwords, SSH keys, limit RDP exposure, disable unused accounts |
| Firewall | Linux: ufw/iptables/nftables · Windows: Defender Firewall inbound rules |
| Applications | Web stack, databases, runtime versions, dependency CVEs |
| Data | Backups, restore testing, encryption at rest/in transit where needed |
| Monitoring | Logs, intrusion signs, disk growth, failed login attempts |
| Email sending | Follow port 25 policy; use authenticated relays — VPSGrid Port 25 Outbound SMTP Policy |
Day-one security baseline
- Change initial passwords immediately after first login
- Apply OS updates
- Enable a firewall allowing only required ports
- Prefer SSH keys on Linux; harden RDP on Windows
- Identify what you will back up and where copies live off-box
Checklists: First-Day Checklist for a New VPS · VPS Security Checklist · Windows RDP: How to Secure RDP on Windows VPS.
Linux-specific responsibilities
- Keep OpenSSH patched; consider key-only auth and non-default ports carefully
- Configure ufw/iptables before exposing services publicly
- Review running services — disable what you do not need
- Watch for crypto miners or unknown processes after compromise
Windows-specific responsibilities
- Windows licensing is typically BYOL — Windows VPS Licensing Requirements
- Manage Windows Update and firewall rules — Enable or Disable Windows Firewall Rules
- Restrict RDP; use strong Administrator credentials
When a security incident happens
- Isolate if possible (stop affected services, block ports temporarily)
- Preserve logs before rebooting
- Rotate credentials and review authorized keys/users
- Restore from a known-good backup after root cause is understood
- Report abuse/compromise to VPSGrid if outbound attack traffic originates from your VPS
Legal and acceptable-use terms: vpsgrid.net/legal.
Support vs security work
VPSGrid support can help with platform/billing issues (provisioning stuck, invoice disputes, suspected hypervisor problems) and point you to KB guides. Support generally cannot perform guest OS hardening, malware removal, or application debugging for you on unmanaged plans.
Before opening a ticket, gather service ID, primary IP, and what you already tried — see related troubleshooting articles for connectivity and performance.
Frequently Asked Questions
Does VPSGrid manage firewall rules inside my VPS?
No. You configure the guest OS firewall. VPSGrid does not remotely manage ufw or Windows Firewall rules on unmanaged plans.
Will VPSGrid install security patches for me?
No. You run apt/dnf/Windows Update inside the VM — How to Update Ubuntu on a VPS.
Is VPSGrid responsible if my WordPress site is hacked?
Application compromise inside the guest OS is your responsibility to investigate and remediate on unmanaged hosting, though you should report outbound abuse promptly.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net for platform/billing issues or if you suspect infrastructure-level problems — include service ID, primary IP, and security-relevant logs (sanitized).
Was this answer helpful?
