OPTES Cloud · Security
12 layers of protection on every server
Every server comes up hardened from the first boot, with no setup on your side.
Needs an OPTES account: the same one you use in the app.
The layers
On by default on every plan, except the optional web application firewall.
| Layer | What it does |
|---|---|
| Network DDoS protection | Large attacks are filtered before they reach your server, on every plan. |
| Edge firewall | Your rules also apply outside the server, so they hold even if the host firewall is wiped. |
| Default-deny host firewall | nftables: inbound is blocked except the rules you add, edited from the panel with a preview. |
| Key-only SSH | Passwords and root login are off, modern ciphers, and SSH is limited to your address by default. |
| Intrusion prevention | CrowdSec with a community blocklist bans known attackers and brute-force attempts automatically. |
| Automatic security updates | Security updates install every day; you choose the reboot window if one is needed. |
| Port 25 blocked against spam | Direct outbound mail is blocked so the network's addresses stay clean. We open it on request after review. |
| Egress abuse detection | We watch for scanning and outbound attacks from outside the server. A hijacked server is isolated automatically, and you keep access. |
| Web application firewall (optional) | Managed Shield: a reverse proxy with OWASP rules in front of your site, with automatic TLS. |
| Snapshots and encrypted backups | Snapshots included before any big change with one-click restore, and an encrypted daily backup as an optional add-on. |
| Full isolation per customer | Every server is its own KVM virtual machine with its own kernel and disk, not a shared container. |
| 2FA and an activity log | Two-factor confirmation for every delete, rebuild or restore, and every action is logged in Activity. |
Responsibility and limits
Shared responsibility
Ours: the network, isolation, the hardened image, the default firewall, OS security updates, optional backups and abuse detection. Yours: your applications and their passwords, your keys, and any change you make as root.
What we never do
We never keep your private key, read your disks, enter your server without your consent, or delete anything because of an automatic alert.
Security score
Every server has a score out of 100 with clear fixes: limit SSH to your address, close open databases, turn on two-factor and keep a recent snapshot.
Abuse ladder
What happens when a server starts harming others.
| State | When | Effect |
|---|---|---|
| Watch | A possible mining signal | No action; a person reviews. |
| Throttle | Spam or connections over the limit | Outbound traffic throttled for a while. |
| Isolate | Ongoing scanning or outbound attack | Outbound traffic is cut; SSH from your addresses and the console keep working. We review it as fast as we can. |
| Suspend | Confirmed or repeated abuse | An evidence snapshot first, then the service is suspended. |
Needs an OPTES account: the same one you use in the app.