STIGQter: STIG Summary: z/OS TADz for ACF2 Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025:

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

DISA Rule

SV-224346r1141651_rule

Vulnerability Number

V-224346

Group Title

SRG-OS-000104

Rule Version

ZTADA030

Severity

CAT II

CCI(s)

• CCI-000764 - Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.

Weight

10

Fix Recommendation

The TADz systems 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

Check Contents

Refer to the following report produced by the ACF2 Data Collection:

- ACF2CMDS.RPT(LOGONIDS).

Verify that the logonid(s) for the TADz started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

For each STC logonid:

STC

For each Batch logonid:

JOB

Vulnerability Number

V-224346

Documentable

False

Rule Version

ZTADA030

Severity Override Guidance

Refer to the following report produced by the ACF2 Data Collection:

- ACF2CMDS.RPT(LOGONIDS).

Verify that the logonid(s) for the TADz started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

For each STC logonid:

STC

For each Batch logonid:

JOB

Check Content Reference

M

Target Key

4130