Ensure access on sudoers configuration files is configured

How it is checked

Audit method: Shell command

alt0() { command -v find >/dev/null 2>&1 || { echo "step1: find not installed"; return 1; }; o=$(bash -c 'find /etc/sudoers /etc/sudoers.d/ -type f \( -perm /0337 -o ! -user root -o ! -group root \)' 2>/dev/null); [ -z "$o" ] || { echo "step1: $o" | head -c 300; return 1; }; }; if alt0; then echo compliant; fi

Expected output

compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Set the owner, group, and permissions on the sudoers files so that only root can read or modify them: # chown root:root /etc/sudoers # chmod u-wx,g-wx,o-rwx /etc/sudoers # find /etc/sudoers.d/ -type f -exec chown root:root {} + # find /etc/sudoers.d/ -type f -exec chmod u-wx,g-wx,o-rwx {} + Modify sudoers content only with visudo.

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

tmaegis scan --target linux