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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-224286	ZCLSA030	SV-224286r519730_rule		Medium

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

Description

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

STIG	Date
z/OS CL/SuperSession for ACF2 Security Technical Implementation Guide	2021-06-25

Details

Check Text ( C-25959r519728_chk )
a) Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) b) If the logonid for the CL/SUPERSESSION started task includes MUSASS and NO-SMC, there is NO FINDING. c) If the logonid for the CL/SUPERSESSION started task does not include MUSASS and/or NO-SMC, this is a FINDING.

Fix Text (F-25947r519729_fix)
The Systems Programmer and IAO 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: INSERT KLS NAME(STC, CL/SuperSession) MUSASS NO-SMC STC