STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS TADz for RACF Security Technical Implementation Guide

V-224539

CAT II (Medium)

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

Rule ID

SV-224539r1145282_rule

STIG

z/OS TADz for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Tivoli Asset Discovery for z/OS (TADz) requires a started task(s) that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system Access Control Program (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 TADz started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Fix Text

The Systems Programmer and ISSO will ensure that the started task for TADz is properly defined.

Define the started task for TADz.

Example:

au tadzmon name('stc, tivoli AD') nopass -
dfltgrp(stc) owner(stc) -
data('stc for tivoli asset discovery')