Solaris 11 SPARC Security Technical Implementation Guide

The Solaris 11 SPARC Security Technical Implementation Guide (V3 R7) has 215 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

215STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V3 · R7

CurrentPublished Wed Sep 30 2026

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

Solaris 11 SPARC Security Technical Implementation Guide

Assessment Title

Rule Text

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

Description

Discussion Text

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.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-216307

Rule

SV-216307r959010_rule

Severity

medium

Rule Version

SOL-11.1-020380

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

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.

Implementation Procedure

Fix Text

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

# chown root <executed file>

STIG check 47 of 215 in the Solaris 11 SPARC STIG checklist

← Previous · V-216306All system start-up files must be group-owned by root, sys, or bin.Next · V-216308 →Any X Windows host must write .Xauthority files.