|Finding ID||Version||Rule ID||IA Controls||Severity|
|Quest NC-Pass requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.|
|z/OS Quest NC-Pass for RACF STIG||2015-01-15|
|Check Text ( C-26057r1_chk )|
| Refer to the following report produced by the RACF Data Collection: |
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.
|Fix Text (F-6825r1_fix)|
| The IAO 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')