SV-37973r1: If the system is using LDAP for authentication or account information, the LDAP TLS key file must have mode 0600 or less permissive. | Red Hat Enterprise Linux 5 Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

If the system is using LDAP for authentication or account information, the LDAP TLS key file must have mode 0600 or less permissive.

Description

Discussion Text

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. Note: Depending on the particular implementation, group and other read permission may be necessary for unprivileged users to successfully resolve account information using LDAP. This will still be a finding, as these permissions provide users with access to system authenticators.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000225

Additional Details

Responsibility

System Administrator

IA Controls

ECLP-1

References

DPMS Target Red Hat 5 DISA DPMS Target Red Hat 5 2154

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.fso.rhel11:def:436
# If the system is using LDAP for authentication or account information, the LDAP TLS key file must have mode 0600 or less permissive.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.
#
# MANUAL REVIEW REQUIRED -- the module(s) below could not be reconstructed
# into working code from curated SCC reference data, and are excluded from
# the automated result:
#   - file_object (file_test) -- TLS key file with 0600 perms: no extractor for field "gexec"

# The /etc/ldap.conf file exists but does not have at least one correctly formated tls_key entry
# textfilecontent54_object (textfilecontent54_test)
test_1() {
  ! ( grep -Pq '^\s*[tT][lL][sS]_[kK][eE][yY][ \t]+[^ \t\n]+/([^ \t\n/]+)$' '/etc/ldap.conf' &>/dev/null )
}
# The /etc/ldap.conf file does not exist
# file_object (file_test)
test_2() {
  ! ( test -e '/etc/ldap.conf' &>/dev/null )
}

if ! ( test_1 || test_2 ); then
  echo "PASS (automated portion only -- MANUAL REVIEW still required, see notes above)"
else
  echo "FAIL (or see MANUAL REVIEW note above)"
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
# oval:mil.disa.fso.rhel11:def:436

if [ ! -f "/etc/ldap.conf" ]; then
    echo "PASS"
    exit 0
fi

if grep -q "^\\s*[tT][lL][sS]_[kK][eE][yY][ \\t]+[^ \\t\\n]+/" /etc/ldap.conf; then
    keyfile=$(grep -oP "^\\s*[tT][lL][sS]_[kK][eE][yY][ \\t]+[^ \\t\\n]+/" /etc/ldap.conf | tr -d ' ')
    if [ ! -f "$keyfile" ]; then
        echo "PASS"
        exit 0
    fi
fi

perm=$(stat -c "%a" "$keyfile")
if [ "$perm" -ge 600 ]; then
    echo "FAIL"
    exit 1
fi

echo "PASS"
exit 0

Remediation

Change the mode of the file.
# chmod 0600 <keypath>