HP-UX 11.23 Security Technical Implementation Guide

The HP-UX 11.23 Security Technical Implementation Guide (V1 R8) has 534 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

534STIG 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

V1 · R8

CurrentPublished Fri Jan 22 2016

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

HP-UX 11.23 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 that execute programs owned by other than root (or another privileged user) or an application indicate that the system may have been compromised.

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

Objective

V-4091

Rule

SV-38422r1_rule

Severity

medium

Rule Version

GEN001700

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Determine the ownership of programs executed by system start-up files. 
# more `ls -alL /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " "`

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, sys, or the application account, where required.
# chown root <executed file>

STIG check 342 of 534 in the HP-UX 11.23 STIG checklist

← Previous · V-4090All system startup files must be group-owned by root, sys, bin or other.Next · V-4246 →System BIOS or system controllers supporting password protection must have administrator accounts/passwords configured, and no others.