Hub rules-nginx

rules-nginx

v3 public Verified

Nginx

Nginx is a high-performance web server and reverse proxy. These rules govern Nginx configuration to prevent insecure SSL/TLS settings, misconfigured proxy headers, and unauthorized directory listing.

@sigmashakeinc 2 pulls 8 rules published Apr 8, 2026 synced Oct 11, 2026 sigmashakeinc/rules/rulesets/rules-nginx →
Severity
3 error 5 warn 0 info
demo.cast
Nginx is a high-performance web server and reverse proxy. These rules govern Nginx configuration to prevent insecure SSL/TLS settings, misconfigured proxy headers, and unauthorized directory listing.

Rules index

8 governance rules

Indexed from the repository's .rules files, grouped by technology. Expand any rule to read the raw source.

nginx

nginx-alias-path-traversal error block

Mismatched trailing slashes between 'location' and 'alias' can cause path traversal vulnerabilities (e.g. allowing access to '../config.php'). Both must either have a trailing slash or not.

Rule source requires an active Pro or Enterprise subscription.
nginx-missing-hsts warning log

RISK: HTTPS server blocks without a Strict-Transport-Security (HSTS) header allow downgrade attacks — a network attacker can strip TLS on the first request. FIX: add 'add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;' and consider submitting to the HSTS preload list.

Rule source requires an active Pro or Enterprise subscription.
nginx-root-inside-location warning log

It's best practice to define the 'root' directive at the 'server' block level rather than exclusively inside 'location' blocks, to prevent requests that don't match any block from falling back to a default, insecure system path.

Rule source requires an active Pro or Enterprise subscription.
nginx-server-tokens warning log

Nginx reveals its version number by default, which attackers use to find specific exploits. Add 'server_tokens off;' to your configuration.

Rule source requires an active Pro or Enterprise subscription.
nginx-ssl-verify-client-off warning log

RISK: ssl_verify_client off means the server does not verify client certificates on an endpoint that may require mutual TLS (mTLS). If this endpoint expects authenticated clients, set ssl_verify_client on (or optional_no_ca during migration) and supply ssl_client_certificate with the trusted CA bundle.

Rule source requires an active Pro or Enterprise subscription.
nginx-unsafe-variable-redirect error block

Using $uri or $document_uri in redirects can lead to HTTP Request Smuggling or CRLF injection. Use $request_uri instead, which contains the original, un-decoded request.

Rule source requires an active Pro or Enterprise subscription.
nginx-weak-ssl-ciphers warning log

RISK: the cipher suite includes broken algorithms (RC4, DES/3DES, MD5, NULL, EXPORT) that allow decryption of recorded traffic or trivial MITM (SWEET32 CVE-2016-2183, RC4 CVE-2013-2566). FIX: use a modern cipher string such as 'ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305;' and add ssl_prefer_server_ciphers on.

Rule source requires an active Pro or Enterprise subscription.
nginx-weak-ssl-protocols error block

RISK: SSLv2, SSLv3, TLS 1.0, and TLS 1.1 are cryptographically broken — SSLv3 is vulnerable to POODLE (CVE-2014-3566), TLS 1.0/1.1 to BEAST and numerous padding-oracle attacks. FIX: use only 'ssl_protocols TLSv1.2 TLSv1.3;' in your server block.

Rule source requires an active Pro or Enterprise subscription.

Version metadata

Published metadata

The hash-locked record of this published ruleset. When source contents change, the maintainer resyncs and the version bumps.

Version
v3
Published
Apr 8, 2026
Source commits
0
Synced
Oct 11, 2026
Hash
947f8043b2bcc209c6d9b365d3d789a11b9ab44fe1f7f4f709efd94499fdc839
Signature
Verified (publisher key)
Tested with
claude-code@current
Plan
Starter (free)
Visibility
Public

Source history

Recent commits

Latest commits touching rulesets/rules-nginx/.sigmashake/rules in sigmashakeinc/rules/rulesets/rules-nginx. The published version only bumps when a maintainer resyncs.

No commit history available.