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
Access→Firewall→TLS→Verify
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.