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

V-224339

CAT II (Medium)

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

Rule ID

SV-224339r1144193_rule

STIG

z/OS ROSCOE for ACF2 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, datasets, 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 ACF2 Data Collection:

- ACF2CMDS.RPT(LOGONIDS).

If the logonids specified below have all the required fields completed and if the following attributes are defined, this is not a finding.

For Started Tasks logonid:

STC
JOBFROM
MUSASS
NO-SMC

For Batch logonid:

JOB
JOBFROM
MUSASS
NO-SMC

Fix Text

The ROSCOE systems programmer and the ISSO will verify 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.

Example:

SET LID
CHANGE ROSCOE STC JOBFROM MUSASS NO-SMC