UCF STIG Viewer Logo

Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP.


Overview

Finding ID Version Rule ID IA Controls Severity
V-17452 ZTADA030 SV-28612r2_rule ECCD-1 ECCD-2 Medium
Description
Tivoli Asset Discovery for z/OS (TADz) requires a started task(s) that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system Access Control Program (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.
STIG Date
z/OS TADz for ACF2 STIG 2016-01-04

Details

Check Text ( C-28852r2_chk )
Refer to the following report produced by the ACF2 Data Collection:

- ACF2CMDS.RPT(LOGONIDS)

Ensure the following field is completed for each STC logonid for the product:

STC

Ensure the following field is completed for each Batch logonid for the product:

JOB

If the logonids specified in (b) and/or (c) have all the required field is completed, this is not a FINDING.

If the logonids specified in (b) and/or (c) do not have the above field completed, this is a FINDING.
Fix Text (F-70737r1_fix)
The TADz 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.

Example:

SET LID
CHANGE TADZMON STC