BMC Mainview for z/OS Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224611 | SRG-OS-000104 | ZMVZT032 | SV-224611r1146082_rule | 2025-09-28 | 7 |
| Description |
|---|
| 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 |
|---|
| 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(ZMVZ0032). If the BMC Mainview for z/OS started task(s) is (are) defined in the TSS STC record, this is not a finding. |
| ✔️ Fix |
|---|
| The BMC Mainview for z/OS 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 Mainview for z/OS 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(MV$CAS) ACID(MV$CAS) TSS ADD(STC) PROCNAME(MV$MVS) ACID(MV$MVS) |