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 TSS Security Technical Implementation Guide

V-225610

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-225610r1146160_rule

STIG

z/OS TADz for TSS 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. 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.

Check Content

Refer to the following reports produced by the TSS Data Collection:

- TSSCMDS.RPT(@ACIDS).

Review TADz STC/Batch ACID(s). If the following attributes are defined, this is not a finding.

FACILITY(STC, BATCH)
PASSWORD(xxxxxxxx,0)
SOURCE(INTRDR)
NOSUSPEND

Fix Text

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

Define the started task for TADz.

Example:

TSS CRE(TADZMON) DEPT(Dept) NAME('TADz STC') -
FAC(STC) PASSWORD(password,0) -
SOURCE(INTRDR) NOSUSPEND