SV-217112r1050789: The SUSE operating system must reauthenticate users when changing authenticators, roles, or escalating privileges. | SUSE Linux Enterprise Server 12 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

The SUSE operating system must reauthenticate users when changing authenticators, roles, or escalating privileges.

Description

Discussion Text

Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When SUSE operating system provide the capability to change user authenticators, change security roles, or escalate a functional capability, it is critical the user reauthenticate. Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-002038Not mappedCCI-004895SV-91763V-77067

References

DPMS Target SUSE Linux Enterprise Server 12 DISA DPMS Target SUSE Linux Enterprise Server 12 4033

Checks

DISA STIG (Manual Reference)

Verify that the SUSE operating system requires reauthentication when changing authenticators, roles, or escalating privileges.

Check that "/etc/sudoers" has no occurrences of "NOPASSWD" or "!authenticate" with the following command:

> sudo egrep -i '(nopasswd|!authenticate)' /etc/sudoers

If any uncommented lines containing "!authenticate", or "NOPASSWD" are returned and active accounts on the system have valid passwords, this is a finding.

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.sles12:def:105
# The SUSE operating system must reauthenticate users when changing authenticators, roles, or escalating privileges.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Neither '!authenticate' nor 'NOPASSWD' exist in /etc/sudoers
# textfilecontent54_object (textfilecontent54_test)
test_1() {
  ! ( grep -Pq '^(?!#).*\s+(\!\s*authenticate|NOPASSWD).*$' '/etc/sudoers' &>/dev/null )
}
# Neither '!authenticate' nor 'NOPASSWD' exist in /etc/sudoers.d
# textfilecontent54_object (textfilecontent54_test)
test_2() {
  ! ( grep -rqP --include='*' '^(?!#).*\s+(\!\s*authenticate|NOPASSWD).*$' '/etc/sudoers.d' &>/dev/null )
}

if ( test_1 && test_2 ); then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# DISA STIG / SCAP compliance check for SUSE OS reauthentication rule (oval:mil.disa.stig.sles12:def:105)
if [ ! -f "/etc/sudoers" ]; then echo "PASS"; exit 0; fi
if grep -qE "^\\s*(\\!\\s*authenticate|NOPASSWD)" /etc/sudoers; then echo "FAIL"; exit 1; fi
if [ ! -d "/etc/sudoers.d" ]; then echo "PASS"; exit 0; fi
for file in /etc/sudoers.d/*; do
    if [ -f "$file" ] && grep -qE "^\\s*(\\!\\s*authenticate|NOPASSWD)" "$file"; then echo "FAIL"; exit 1; fi
done
echo "PASS"; exit 0

Remediation

Configure the SUSE operating system to remove any occurrence of "NOPASSWD" or "!authenticate" found in the "/etc/sudoers" file. If the system does not use passwords for authentication, the "NOPASSWD" tag may exist in the file.