CL/SuperSession Started Task name is not properly identified/defined to the system ACP.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224465	SRG-OS-000104	ZCLSR030	SV-224465r1144731_rule	2025-09-27	7

Description
CL/SuperSession requires a started task that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

ℹ️ Check
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the CL/SUPERSESSION started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED

✔️ Fix
The Systems Programmer and ISSO will ensure that the started task for CL/SuperSession is properly defined. Review all session manager security parameters and control options for compliance. Develop a plan of action and implement the changes as specified. Define the started task userid KLS for CL/SuperSession. Example: AU KLS NAME('STC, SUPERSESSION') NOPASS - OWNER(STC) DFLTGRP(STC) - DATA('START CL SUPERSESSION')

✔️ Fix

The Systems Programmer and ISSO will ensure that the started task for CL/SuperSession is properly defined. Review all session manager security parameters and control options for compliance. Develop a plan of action and implement the changes as specified. Define the started task userid KLS for CL/SuperSession. Example: AU KLS NAME('STC, SUPERSESSION') NOPASS - OWNER(STC) DFLTGRP(STC) - DATA('START CL SUPERSESSION')