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

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

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

Overview

Version	Date	Finding Count (8)			Downloads
6	2022-10-10 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16 2015-01-16	CAT I (High): 0	CAT II (Med): 8	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.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC II - Mission Support Classified)

Finding ID	Severity	Title	Description
V-224609	Medium	BMC 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...
V-224608	Medium	BMC 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...
V-224612	Medium	BMC 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-224613	Medium	BMC 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-224607	Medium	BMC 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...
V-224611	Medium	BMC 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...
V-224614	Medium	BMC 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...
V-224610	Medium	BMC 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...