Saturday, 21 November 2026 Press Releases Newsletter RSS
Breaking
WhatsApp Business Account Hacked in Pakistan: Full Recovery Guide Special Technology Zones Authority (STZA) & IT Park Expansion in Pakistan: Islamabad, Karachi, and Lahore Ground Report Pakistan Software Export Board & Industry Consortium Launch 'TechBridge Pakistan 2026' to Connect 500 Startups With Global Markets Global Tech Safety Summit 2026: International Standards for Frontier AI and Data Security Announced WhatsApp Business Account Hacked in Pakistan: Full Recovery Guide Special Technology Zones Authority (STZA) & IT Park Expansion in Pakistan: Islamabad, Karachi, and Lahore Ground Report Pakistan Software Export Board & Industry Consortium Launch 'TechBridge Pakistan 2026' to Connect 500 Startups With Global Markets Global Tech Safety Summit 2026: International Standards for Frontier AI and Data Security Announced
WritePures

Work through this. If anything is unchecked, that is the next thing to do.

Access

  • SSH key authentication working.
  • PasswordAuthentication no, verified with sshd -T.
  • PermitRootLogin no.
  • A non-root sudo user for daily work.
  • Your private key has a passphrase.
  • No override in /etc/ssh/sshd_config.d/ undoing the above.

Network

  • UFW enabled, default deny incoming.
  • Only 80, 443 and SSH open.
  • Rules cover IPv6 if the server has an address.
  • Every Docker port published as 127.0.0.1:… unless it is genuinely public.
  • ss -tulpn shows nothing unexpected on 0.0.0.0.

Updates

  • unattended-upgrades installed and logging.
  • A habit for checking /var/run/reboot-required.
  • Container images updated on a schedule, not only when something breaks.

Data

  • Backups run automatically.
  • They are stored off the server.
  • They are encrypted, and the passphrase is stored elsewhere.
  • You have restored one and checked the contents.
  • Retention is set, so the repository does not grow forever.

Visibility

  • External uptime check on a meaningful endpoint.
  • Disk space alert.
  • Docker log rotation configured.
  • A weekly review you actually do.

Secrets

  • .env files are chmod 600.
  • No secrets in Compose files or in Git.
  • Default passwords changed on everything.

Worth hosting now that you can

  • Your own sites and APIs — the obvious one, and the economics are hard to beat.
  • A password manager such as Vaultwarden.
  • File sync with Nextcloud, if you have the disk.
  • Uptime monitoring for other things, with Uptime Kuma.
  • Analytics you own, with Plausible or Umami.
  • Local AI models, if the server has the memory — our local models tutorial and the private RAG tutorial both run well on a server with enough RAM, and the firewall chapter here is exactly what that setup needs.

The habit that matters most

None of this is difficult. The difficulty is that it is invisible: a well-maintained server and a neglected one look identical right up until the neglected one is someone else's.

Five minutes a week and a quarterly restore test is the whole discipline. Put both in a calendar now, while you still care.