← Back to z/OS Quest NC-Pass for RACF Security Technical Implementation Guide

V-224526

CAT II (Medium)

Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.

Rule ID

SV-224526r1144942_rule

STIG

z/OS Quest NC-Pass for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Quest NC-Pass requires a started task that will 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 Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Fix Text

The ISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or 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.

The following commands are provided as a sample for defining Started Task(s):

au NCPASS name('STC, Quest NC-Pass') owner(stc) dfltgrp(stc) nopass -
	data('Start CA1 TMS')