SV-227668r603266: All system start-up files must be owned by root. | Solaris 10 X86 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

All system start-up files must be owned by root.

Description

Discussion Text

System start-up files not owned by root could lead to system compromise by allowing malicious users or applications to modify them for unauthorized purposes. This could lead to system and network compromise.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000366V-4089SV-27207

References

DPMS Target Solaris 10 X86 DISA DPMS Target Solaris 10 X86 4061

Checks

DISA STIG (Manual Reference)

Check run control scripts' ownership.
# ls -lL /etc/rc* /etc/init.d
If any run control script is not owned by root, 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.fso.solaris11:def:114
# All system start-up files must be owned by root.
# 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) -- All system start-up files must be owned by root or bin: no extractor for field "user_id"

echo "MANUAL REVIEW REQUIRED -- see notes above; no part of this check could be automated"

Remediation

Change the ownership of the run control script(s) with incorrect ownership.
# chown root <run control script>