Nginx TLS Hardening: Manual Config vs Delegated Edge Policy Explained
Nginx TLS hardening often gets addressed reactively — triggered by pentest findings or compliance audits flagging outdated protocols and missing security headers. Engineers face a core architectural choice: manage TLS and header policy directly in nginx server blocks, or delegate it to a CDN, WAF, or shared infrastructure-as-code generator. The manual approach offers per-host control and full audit trails in git, but risks silent drift across multiple server blocks, especially due to nginx's non-merging add_header behavior in nested location blocks. Delegated or automated hardening ensures consistent policy across services and simplifies updates, but sacrifices per-service granularity. Regardless of approach, cipher suite lists should always come from actively maintained sources like the Mozilla SSL Configuration Generator, since static copied lists can become stale and provide a false sense of security.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in