TMA-NGINX-2.2.2
Ensure the NGINX service account is locked
SedangLevel 1Otomatisnginx
Deskripsi
The NGINX service account must not have a usable password and should be explicitly locked in the system's shadow file to prevent direct login or password-based privilege escalation. Reads the account from the user directive and expects passwd -S to report L or LK (run as root). Evaluated on the merged configuration printed by `nginx -T` (all included files; needs permission to read them). CIS marks this recommendation Manual; the automated check implements its audit procedure.
Cara pemeriksaan
Metode audit: Perintah shell
shell
out=$(nginx -T 2>/dev/null) || exit 1; u=$(printf '%s\n' "$out" | awk '$1=="user"{x=$2; sub(/;$/,"",x); print x; exit}'); [ -n "$u" ] || { echo noncompliant; exit 0; }; s=$(passwd -S "$u" 2>/dev/null) || exit 1; printf '%s\n' "$s" | awk '{print ($2=="L"||$2=="LK")?"compliant":"noncompliant"}'- Output yang diharapkan
compliant
Cara perbaikan
Metode perbaikan: Panduan atau patch infrastruktur
Lock the account: passwd -l <nginx user>.
Properti
- Sistem operasi
- Apa saja
- Tag
- nginxaccounts
- Referensi
- CIS NGINX Benchmark v3.0.0 - 2.2.2 Ensure the NGINX service account is locked
Periksa host ini
Jalankan ini pada mesin yang diizinkan untuk Anda audit. Pemindaian bersifat hanya baca.
shell
tmaegis scan --target nginx