Server Hardening

PROJECT 002 / LINUX · SECURITY AUTOMATION

A stronger starting point.

A repeatable security baseline for production Linux, covering network access, SSH, TLS, and Nginx.

The context

Repeated server setup benefits from a documented baseline. The goal was to make the expected configuration clear and apply it consistently across environments.

My contribution

  • Configured UFW rules and cloud security groups to control network access.
  • Applied key-only SSH access and disabled root login.
  • Automated SSL certificate provisioning and renewal with Bash.
  • Hardened Nginx with security headers, HTTPS redirects, and suppressed server version tokens.

The workflow

AccessFirewallTLSVerify
nginx.conf · representative excerpt
# Illustrative directives within a configured server block
server_tokens off;

add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Certificate paths, listeners, upstreams, and redirect rules
# are configured for the specific application.

These directives illustrate part of the baseline; they are not a complete Nginx configuration or a complete security policy.

Alvin K Sabu ›Server HardeningMade to be explored.

alvin — bash — 80 × 24

Welcome to Alvin’s desktop.

Type help to explore. This is a browser simulation.

esc to close

Search this desktop

↑ ↓ to navigate ↵ to openesc to close

A little desktop tour

Click an app in the dock or a folder in the sidebar. The window controls work, too.

Search everything
Ctrl / ⌘ K
Open terminal
`
Overview / Projects / About / Toolbox / Contact
1 — 5
Close a dialog or menu
Esc

Pipeline Lab and Terminal are local demos. They never connect to production infrastructure.