CL/SuperSession Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224654 | ZCLST032 | SV-224654r1145878_rule | CCI-000764 | medium |
| 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. | ||||
| STIG | Date | |||
| z/OS CL/SuperSession for TSS Security Technical Implementation Guide | 2025-09-28 | |||
Details
Check Text (C-224654r1145878_chk)
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(ZCLS0032).
If the CL/SuperSession started task(s) is (are) defined in the TSS STC record, this is not a finding.
Fix Text (F-26325r1145877_fix)
The CL/SuperSession 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 CL/SuperSession 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(KLS) ACID(KLS)