用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-nginx-v300-2-5-3命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-nginx-v300-2-5-3 |
| description | Ensure hidden file serving is disabled (Manual) |
| category | cis-nginx |
| version | 3.0 |
| author | cyberstrike-official |
| tags | ["cis","nginx","web-server","reverse-proxy","information-disclosure","basic-configuration"] |
| cis_id | 2.5.3 |
| cis_benchmark | CIS NGINX Benchmark v3.0.0 |
| tech_stack | ["nginx","linux","web-server"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Hidden files and directories (starting with a dot, e.g., .git, .env) often contain sensitive metadata, version control history, or environment configurations. Serving these files should be globally disabled.
Version control systems (Git, SVN) and editors create hidden files that may unintentionally be deployed to the web root. If accessible, files like .git/config or .env can leak database credentials, source code, and infrastructure details, leading to full system compromise. Blocking requests to any path starting with a dot (.) neutralizes this risk.
Blocking all dot-files will break Let's Encrypt / Certbot validation (.well-known/acme-challenge) unless explicitly allowed. Ensure the exception rule is placed before the deny rule or is more specific.
1. Check Configuration:
Search the loaded configuration for hidden file protection rules:
nginx -T 2>/dev/null | grep "location.*\\\."
Evaluation:
location ~ /\. { deny all; ... }.2. Functional Test (Recommended):
Try to access a dummy hidden file:
curl -k -I https://127.0.0.1/.git/HEAD
Evaluation:
403 Forbidden or 404 Not Found.200 OK (if file exists) or the content of the file.To restrict access to hidden files, add the configuration block below inside each server block.
Option A: Direct Configuration
Place this block directly into your server contexts:
# Allow Let's Encrypt validation (must be before the deny rule)
location ^~ /.well-known/acme-challenge/ {
allow all;
default_type "text/plain";
}
# Deny access to all other hidden files
location ~ /\. {
deny all;
return 404;
}
Option B: Using a Shared Snippet (Recommended)
Create a reusable snippet file (e.g., /etc/nginx/snippets/deny-hidden.conf) containing the rules above, and include it in your server blocks:
/etc/nginx/snippets/deny-hidden.conf with the content from Option A.root:root, Mode: 640) as described in Recommendation 2.3.2.server {
# Modern HTTP/3 (QUIC) and HTTP/2 Setup
listen 443 ssl; # TCP for HTTP/1.1 & HTTP/2
listen 443 quic reuseport; # UDP for HTTP/3
http2 on; # Explicitly enable HTTP/2 (since NGINX 1.25.1)
server_name example.com;
include /etc/nginx/snippets/deny-hidden.conf;
# ... rest of configuration
}
This protection is not set by default. NGINX will serve any hidden file if it exists in the web root.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 16.1 Establish and Maintain a Secure Application Development Process | N | Y | Y |
| v7 | 18.1 Establish Secure Coding Practices | N | Y | Y |
| Tactic | Technique |
|---|---|
| Reconnaissance | T1592 - Gather Victim Host Information |
| Collection | T1213 - Data from Information Repositories |