Menu
Ensure the upstream traffic server certificate is trusted (Manual)
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-nginx-v300-4-1-10The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
Based on SOC occupation classification
| name | cis-nginx-v300-4-1-10 |
| description | Ensure the upstream traffic server certificate is trusted (Manual) |
| category | cis-nginx |
| version | 3.0 |
| author | cyberstrike-official |
| tags | ["cis","nginx","web-server","reverse-proxy","tls-ssl","encryption"] |
| cis_id | 4.1.10 |
| cis_benchmark | CIS NGINX Benchmark v3.0.0 |
| tech_stack | ["nginx","linux","web-server"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
When acting as a reverse proxy, NGINX must be configured to function as a secure TLS client. This requires validating the identity of the upstream server by verifying its certificate against a trusted Certificate Authority (CA). Furthermore, NGINX must ensure that the hostname of the upstream server matches the name (Subject Name / SAN) within the certificate itself.
Without proper validation, NGINX blindly trusts the identity of the upstream server, making it vulnerable to man-in-the-middle (MitM) attacks within the internal network. An attacker could impersonate a legitimate backend service and intercept sensitive traffic. By enforcing certificate validation (proxy_ssl_verify) and hostname verification (proxy_ssl_name), NGINX guarantees that it is communicating with the intended, authentic upstream server.
Enabling strict upstream verification introduces a dependency on certificate lifecycle management. If the upstream server's certificate expires or is misconfigured, or if the CA certificate file on the NGINX server is outdated, NGINX will refuse to connect to the upstream, resulting in a service outage. This behavior is intentional and secures the connection at the cost of requiring careful certificate management.
Run the following command to inspect the fully loaded NGINX configuration for the three required directives within the relevant proxy location block:
nginx -T 2>/dev/null | grep -E \
'^\s*(proxy_ssl_verify|proxy_ssl_trusted_certificate|proxy_ssl_name)'
Verify that the output contains the following directives:
proxy_ssl_verify on;proxy_ssl_trusted_certificate /path/to/ca.crt;proxy_ssl_name your-upstream-hostname.com;If any of these three directives are missing, this recommendation is not fully implemented. Additionally, manually verify that the certificate referenced by proxy_ssl_trusted_certificate is the correct, valid CA certificate for your upstream services.
To securely configure upstream validation, you must obtain the CA certificate that signed your upstream server's certificate.
upstream_ca.crt) in a secure directory on the NGINX server (e.g., )./etc/nginx/ssl/location block that proxies traffic, add the following three directives. The proxy_ssl_name must match the hostname used in the proxy_pass directive.location /api/ {
proxy_pass https://your-upstream-hostname.com;
# 1. Enable verification
proxy_ssl_verify on;
# 2. Specify the CA to trust for verification
proxy_ssl_trusted_certificate /etc/nginx/ssl/upstream_ca.crt;
# 3. Verify the certificate's name matches the server's hostname
proxy_ssl_name your-upstream-hostname.com;
}
By default, proxy_ssl_verify is set to off. This means NGINX does not validate the upstream server's certificate, creating a significant security risk equivalent to a browser ignoring all certificate warnings.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.10 Encrypt Sensitive Data in Transit | N | Y | Y |
| v7 | 14.4 Encrypt All Sensitive Information in Transit | N | Y | Y |
| Tactic | Technique |
|---|---|
| Credential Access | T1557 - Adversary-in-the-Middle |
| Lateral Movement | T1021 - Remote Services |