Ensure the SSSD service is enabled and active
sssd-service-enabled-active · UBUNTU ≥ 22, RHEL ≥ 8 · 1 impl
Description
The System Security Services Daemon (sssd) must be both enabled (starts on boot) and active (currently running) on any host that has SSSD configured. SSSD is the process that answers "may this user log in" wherever it is in use, whether the answer comes from a directory or from a certificate on a smart card. If it is stopped, the host silently falls back to its local files.
Rationale
Whatever SSSD was configured to enforce stops being enforced when the daemon is not running, and the host gives no sign of it. On a directory-joined host that means account policy, disabled accounts and password lifetime stop being consulted. On a host set up for certificate or smart-card login it means the broker for that login is dead. Either way the host still boots and still accepts whatever local accounts it carries, so the gap is invisible from the outside: a directory cannot tell that a member stopped asking, and a smart card cannot tell that nothing is reading it. Only a check on the host finds it.
Check → Remediate
enabled=$(systemctl is-enabled sssd 2>/dev/null)
active=$(systemctl is-active sssd 2>/dev/null)
if [ "$enabled" != "enabled" ]; then
echo "FAIL: SSSD is configured on this host but is not enabled (is-enabled=${enabled:-unknown})."
echo " After a reboot nothing would broker directory or certificate logins."
exit 1
fi
if [ "$active" != "active" ]; then
echo "FAIL: SSSD is configured on this host but is not running (is-active=${active:-unknown})."
echo " Whatever it was configured to enforce is not being enforced right now."
exit 1
fi
echo "OK: sssd is enabled and active, so its configuration is in force"
exit 0
- expected_exit:
- 0
- name:
- sssd
- start:
- true
Framework references
STIG
NIST 800-53
NIST 800-171
CMMC Level 2