System start-up files must only execute programs owned by a privileged UID or an application.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-216307SOL-11.1-020380SV-216307r959010_ruleCCI-000366medium
Description
System start-up files executing programs owned by other than root (or another privileged user) or an application indicates the system may have been compromised.
STIGDate
Solaris 11 SPARC Security Technical Implementation Guide2025-05-05

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
CM-6
1.00
  • DISA · 3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
  • DISA · 3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
  • DISA · 3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
  • DISA · 3 · disa_xccdf · related

Details

Check Text (C-216307r959010_chk)

Determine the programs executed by system start-up files. Determine the ownership of the executed programs. # cat /etc/rc* /etc/init.d/* | more Check the ownership of every program executed by the system start-up files. # ls -l <executed program> If any executed program is not owned by root, sys, bin, or in rare cases, an application account, this is a finding.

Fix Text (F-17541r371010_fix)

Change the ownership of the file executed from system startup scripts to root, bin, or sys. # chown root <executed file>