STIG VIEWER

z/OS ROSCOE for ACF2 Security Technical Implementation Guide

Overview

Version Date Finding Count (6) Downloads
6 2024-09-24 CAT I (High): 0 CAT II (Medium): 6 CAT III (Low): 0 Excel JSON XML
Stig Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Classified Public Sensitive  
I - Mission Critical Classified I - Mission Critical Public I - Mission Critical Sensitive II - Mission Critical Classified II - Mission Critical Public II - Mission Critical Sensitive III - Mission Critical Classified III - Mission Critical Public III - Mission Critical Sensitive

Findings - All

Finding ID Severity Title Description
V-224341 Medium ROSCOE configuration/parameter values are not specified properly. Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data.
V-224340 Medium The ROSCOE's Resource Class is not defined or active in the ACP. Failure to use a robust ACP to control a product could potentially compromise the integrity and availability of the MVS operating system and user data.
V-224339 Medium ROSCOE Started Task name is not properly identified / defined to the system ACP. 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...
V-224338 Medium ROSCOE resources must be properly defined and protected. ROSCOE can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality and integrity of customer data. Many utilities assign resource controls that can be granted to...
V-224337 Medium ROSCOE STC data sets are not properly protected. ROSCOE STC data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
V-224336 Medium ROSCOE Install data sets are not properly protected. ROSCOE Install data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.