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 BMC CONTROL-D for TSS Security Technical Implementation Guide

V-224585

CAT II (Medium)

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

Rule ID

SV-224585r1145912_rule

STIG

z/OS BMC CONTROL-D for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

Check Content

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(ZCTD0032).

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

Fix Text

The BMC CONTROL-D 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-D 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(CONTOLD) ACID(CONTROLD)