SV-216429r959010: Reserved UIDs 0-99 must only be used by system accounts. | Solaris 11 SPARC STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Reserved UIDs 0-99 must only be used by system accounts.

Description

Discussion Text

If a user is assigned a UID that is in the reserved range, even if it is not presently in use, security exposures can arise if a subsequently installed application uses the same UID.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000366SV-60949V-48077

References

DPMS Target Solaris 11 SPARC DISA DPMS Target Solaris 11 SPARC 4022

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.

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 Definition: oval:mil.disa.stig.solaris11:def:57


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

for user in $(cut -d: -f1 /etc/passwd); do
    uid=$(cut -d: -f3 /etc/passwd | grep "^[0-9]\{1,2\}:" | grep -w "$user" | cut -d: -f1)
    if [ "$uid" -le "99" ] && [ ! -e "/var/reserved/$user" ]; then
        echo "FAIL"; exit 1
    fi
done

echo "PASS"; exit 0

Remediation

The root role is required.

Correct or justify any items discovered in the Check step. Determine if there are any accounts using these reserved UIDs, and work with their owners to determine the best course of action in accordance with site policy. This may require deleting users or changing UIDs for users.