Skip to content

Networking / security

Linux hardening

Baseline security for servers exposed to the internet.

Layer

Networking / security

Used in

All services

Same layer

4 technologies

How we use Linux hardening

Hardening covers SSH, firewall policy, patching rhythm, and least-privilege service accounts.

Where we reach for it

  • New internet-facing VPS

    Before any app is deployed, we lock down SSH to keys only, disable root login, and set a default-deny firewall that opens just the ports the stack needs.

  • Taking over an old server

    We audit open ports, user accounts, sudoers and unpatched packages, then close the gaps in small steps so running services are not interrupted.

  • Least-privilege services

    Each application runs under its own unprivileged account, with systemd sandboxing options and read-only mounts where the service allows it.

  • Regular patch rhythm

    Security updates are applied on a fixed schedule, with unattended upgrades for the base system and a planned window for kernel reboots.

When we pick something else

If you do not need to own a server, a managed platform such as Vercel, Netlify or a managed container service moves most of this work to the provider. Hardening a single box also does not replace a proper network design once you run several machines.

What we watch for

  • Lockout risk

    A wrong firewall or sshd change can cut off access. We keep a second session open, test changes before reloading, and keep console access with the hosting provider.

  • Patch ownership

    Hardening decays when nobody applies updates. We document who patches, how often, and how reboots are scheduled, so the answer survives handover.

  • Logs and alerts

    Failed logins and unexpected changes only help if someone sees them. We ship auth logs off the host and set a small number of alerts that people will act on.

Common questions

What does Linux server hardening include?

Typically key-only SSH, a default-deny firewall, automatic security updates, unprivileged service accounts, and removal of unused packages and services. Fail2ban or similar rate limiting and log forwarding are common additions.

Is hardening a one-off task?

No. The initial setup takes a short time, but patching, key rotation and access reviews continue. Without an owner, a hardened server slowly turns into an ordinary one.

Does hardening make us compliant with nDSG or GDPR?

It supports the technical measures those laws expect, such as access control and security of processing. Compliance itself also depends on data handling, contracts and documentation, which sit outside the server.

Next step

What is costing you time, money or customers today?

You get an honest assessment of whether and how we can help, followed by a written plan with a cost estimate and timeline.

Tell us what you're building

We reply within 1–3 working days, by email, call or video. Your choice.