From z/OS ROSCOE for ACF2 STIG
Part of ZB000030
Associated with IA controls: ECCD-2, ECCD-1
Associated with: CCI-000764
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.
a) Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(LOGONIDS) b) Ensure the following fields are completed for each STC logonid for the product: STC JOBFROM MUSASS NO-SMC c) Ensure the following fields are completed for each Batch logonid for the product: JOB JOBFROM MUSASS NO-SMC d) If the logonids specified in (b) and/or (c) have all the required fields are completed, this is not a FINDING. e) If the logonids specified in (b) and/or (c) do not have all the above fields completed, this is a FINDING.
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. Example: SET LID CHANGE ROSCOE JOBFROM MUSASS NO-SMC
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer