← Back to z/OS ROSCOE for RACF Security Technical Implementation Guide

V-224531

CAT II (Medium)

ROSCOE Started Task name is not properly identified/defined to the system ACP.

Rule ID

SV-224531r1144972_rule

STIG

z/OS ROSCOE for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Products that require a started task will require that the started task be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Check Content

Refer to the following report produced by the RACF Data Collection:

- RACFCMDS.RPT(LISTUSER).

Verify that the userid(s) for the ROSCOE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Fix Text

The ROSCOE system programmer and the ISSO will ensure that a product's Started Task(s) is properly Identified/defined to the System ACP. 

If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

A sample is provided here:

au roscoe name('stc, roscoe') owner(stc) dfltgrp(stc) nopass