From z/OS TSS STIG
Part of TSS0770
Associated with IA controls: DCCS-1, DCCS-2
Batch jobs should have associated ACIDs defined to the system to designate the resources available to the job. Access levels for batch jobs should be limited to those levels required to perform its established function. Failure to control batch job access authorizations could compromise the operating system environment and customer data.
a) Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) Refer to the documentation of the processes used for submission of batch jobs via an automated process (i.e., scheduler or other sources) and each of the associated userids. b) Ensure that each identified batch ACID is sourced to a specific submission process used only for batch processing. Review the following items to ensure this is in effect: 1) The job scheduler is cross-authorized to the batch ACIDs. 2) The Facility of BATCH is specified for each batch ACID. 3) Batch ACIDs with facilities other then BATCH should be questioned to ensure they are truly used for batch processing only, especially if a non-expiring password is used. c) If all items are present, there is NO FINDING. d) If any items are missing, this is a FINDING.
Ensure associated ACIDs exist for all batch jobs and documentation justifying access to system resources is maintained and filed with the IAO. Evaluate the impact of correcting the deficiency. Develop a plan of action and implement the required changes.
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