z/OS BMC MAINVIEW for z/OS for TSS Security Technical Implementation Guide

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.

Date: 2025-02-24Version: 7
Description
V-224607mediumBMC MAINVIEW for z/OS installation data sets are not properly protected.BMC MAINVIEW for z/OS installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
V-224608mediumBMC MAINVIEW for z/OS STC data sets are not properly protected.BMC MAINVIEW for z/OS STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
V-224609mediumBMC MAINVIEW resources must be properly defined and protected.BMC MAINVIEW 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 of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.
V-224610mediumBMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP.BMC Mainview for z/OS 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.
V-224611mediumBMC Mainview for z/OS Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.
V-224612mediumBMC Mainview for z/OS is not properly defined to the Facility Matrix Table for Top Secret.Improperly defined security controls for BMC Mainview for z/OS could result in the compromise of the network, operating system, and customer data.
V-224613mediumBMC Mainview for z/OS Resource Class must be 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-224614mediumBMC MAINVIEW for z/OS configuration/parameter values are not specified properly.BMC MAINVIEW for z/OS configuration/parameters controls 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.