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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-17452	ZROST030	SV-23711r1_rule	ECCD-1 ECCD-2	Medium

Description

Products that require a started task will require that the started task 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 ROSCOE for TSS STIG	2015-01-15

Details

Check Text ( C-28851r1_chk )
a) Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) b) Review each ROSCOE STC/Batch ACID(s) for the following: ___ Is defined with Facility of STC and/or BATCH. ___ Is defined with Master Facility of ROSCOE. ___ Is sourced to the INTRDR. c) If all of the above are true, there is NO FINDING. d) If any of the above is untrue, this is a FINDING.

Fix Text (F-27951r1_fix)

The ROSCOE system programmer and the IAO will ensure that a product's Started Task(s) is properly Identified / defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. A sample is provided here: TSS CREATE(ROSCOE) TYPE(USER) - NAME('*STC* for ROSCO') DEPT(xxxx) - FAC(STC) - MASTFAC(ROSCOE) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND