STIGQter: STIG Summary: zOS BMC CONTROL-M for TSS Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025:

BMC CONTROL-M Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.

DISA Rule

SV-224575r1145936_rule

Vulnerability Number

V-224575

Group Title

SRG-OS-000104

Rule Version

ZCTMT032

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 BMC CONTROL-M systems programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the system ACP.

A unique ACID must be assigned for the BMC CONTROL-M started task(s) through a corresponding STC table entry.

The following sample set of commands is shown here as a guideline:

TSS ADD(STC) PROCNAME(CONTOLM) ACID(CONTROLM)

Check Contents

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

- TSSCMDS.RPT(#STC).

Automated Analysis
Refer to the following report produced by the TSS Data Collection:

- PDI(ZCTM0032).

If the BMC CONTROL-M started task(s) is (are) defined in the TSS STC record, this is not a finding.

Vulnerability Number

V-224575

Documentable

False

Rule Version

ZCTMT032

Severity Override Guidance

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

- TSSCMDS.RPT(#STC).

Automated Analysis
Refer to the following report produced by the TSS Data Collection:

- PDI(ZCTM0032).

If the BMC CONTROL-M started task(s) is (are) defined in the TSS STC record, this is not a finding.

Check Content Reference

M

Target Key

4168