Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

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

V7R2 · · · Released 01 Oct 2025 · 6 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Sort by
b
BMC MAINVIEW for z/OS installation datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224250 - SV-224250r1141582_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMVZA000
Vuln IDs
  • V-224250
  • V-16932
Rule IDs
  • SV-224250r1141582_rule
  • SV-33835
BMC MAINVIEW for z/OS installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-25923r1141580_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MVZRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMVZ0000). Verify that the accesses to the BMC MAINVIEW for z/OS installation datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to all authorized users. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix: F-25911r1141581_fix

The ISSO will ensure that WRITE and/or greater access to BMC MAINVIEW for z/OS installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users. The installing systems programmer will identify and document the product datasets and categorize them according to who will have WRITE and/or greater access, and if required, that all WRITE and/or greater access is logged. The programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Datasets to be protected will be: SYS2.BMCVIEW SYS3.BMCVIEW (Datasets that are not altered by product STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) BMCVIEW.- UID(<syspaudt>) R(A) W(L) A(L) E(A) BMCVIEW.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) BMCVIEW.- UID(<audtaudt>) R(A) E(A) BMCVIEW.- UID(authorized users) R(A) E(A) BMCVIEW.- UID(<audtaudt>) R(A) E(A) BMCVIEW.- UID(MAINVIEW STCs) R(A) E(A) $KEY(SYS3) BMCVIEW.- UID(<syspaudt>) R(A) W(L) A(L) E(A) BMCVIEW.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) BMCVIEW.- UID(<audtaudt>) R(A) E(A) BMCVIEW.- UID(authorized users) R(A) E(A) BMCVIEW.- UID(MAINVIEW STCs) R(A) E(A)

b
BMC MAINVIEW for z/OS STC datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224251 - SV-224251r1141585_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMVZA001
Vuln IDs
  • V-224251
  • V-17067
Rule IDs
  • SV-224251r1141585_rule
  • SV-37720
BMC MAINVIEW for z/OS STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-25924r1141583_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MVZSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMVZ0001). Verify that the accesses to the BMC MAINVIEW for z/OS STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to auditors and authorized users. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the BMC MAINVIEW for z/OS's STC(s) and/or batch user(s).

Fix: F-25912r1141584_fix

The ISSO will ensure that WRITE and/or greater access to BMC MAINVIEW for z/OS STC datasets is limited to systems programmers and/or BMC MAINVIEW for z/OS's STC(s) and/or batch user(s) only. READ access can be given to auditors and authorized users. The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Datasets to be protected will be: SYS3.BMCVIEW (Datasets that are altered by the product's STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) BMCVIEW.- UID(<syspaudt>) R(A) W(A) A(A) E(A) BMCVIEW.- UID(<tstcaudt>) R(A) W(A) A(A) E(A) BMCVIEW.- UID(MAINVIEW STCs) R(A) W(A) A(A) E(A) BMCVIEW.- UID(<audtaudt>) R(A) E(A) BMCVIEW.- UID(authorize users) R(A) E(A)

b
BMC MAINVIEW resources must be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224252 - SV-224252r1141588_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZMVZA020
Vuln IDs
  • V-224252
  • V-17947
Rule IDs
  • SV-224252r1141588_rule
  • SV-46311
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 nonsystems personnel with read only authority.
Checks: C-25925r1141586_chk

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection: - SENSITVE.RPT(ZMVZ0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMVZ0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC MAINVIEW Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. The ACF2 resources are defined with a default access of PREVENT. The ACF2 resource access authorizations restrict access to the appropriate personnel.

Fix: F-25913r1141587_fix

The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP). (Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Use BMC MAINVIEW Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirement for BMC MAINVIEW. Ensure the guidelines for the resource type, resources, and/or generic equivalent specified in the z/OS STIG Addendum are followed. The ACF2 resources as designated in the above table are defined with a default access of PREVENT. The ACF2 resource access authorizations restrict access to the appropriate personnel as designated in the above table. The following commands are provided as a sample for implementing resource controls: $KEY(BBM) TYPE(BMV) ssid.CN UID(autoaudt) ALLOW ssid.CN UID(dasdaudt) ALLOW ssid.CN UID(mqsaaudt) ALLOW ssid.CN UID(Mainview STCs) ALLOW ssid.CN UID(mvzread) ALLOW ssid.CN UID(mvzupdt) ALLOW ssid.CN UID(pcspaudt) ALLOW ssid.CN UID(syspaudt) ALLOW - UID(*) PREVENT

b
BMC Mainview for z/OS Started Task name must be properly identified and/or defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224253 - SV-224253r1144185_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZMVZA030
Vuln IDs
  • V-224253
  • V-17452
Rule IDs
  • SV-224253r1144185_rule
  • SV-33838
BMC Mainview for z/OS requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.
Checks: C-25926r1144184_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Ensure that the logonids(s) for the BMC Mainview for z/OS started task(s) includes the following. If the following attributes are defined, this is not a finding. STC NO-SMC

Fix: F-25914r518969_fix

Ensure that a product's Started Task(s) is properly identified and/or 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 INSERT MV$CAS STC NO-SMC INSERT MV$PAS STC NO-SMC INSERT MV$MVS STC NO-SMC

b
BMC Mainview for z/OS Resource Class will be defined or active in the ACP.
AC-25 - Medium - CCI-002358 - V-224254 - SV-224254r1141592_rule
RMF Control
AC-25
Severity
M
CCI
CCI-002358
Version
ZMVZA038
Vuln IDs
  • V-224254
  • V-18011
Rule IDs
  • SV-224254r1141592_rule
  • SV-33844
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.
Checks: C-25927r1141591_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ACFGSO). If the following GSO CLASMAP record entry(ies) is (are) defined, this is not a finding. CLASMAP.class RESOURCE(class) RSRCTYPE(type) ENTITYLN(nn) Note: The site determines the appropriate three letter RSRCTYPE that is unique for Mainview. The ENTITYLN should be appropriate for the site's installation. If the following GSO SAFDEF record entries are defined this not a finding. INSERT SAFDEF.ssid ID(BBCS) MODE(GLOBAL)REP - RACROUTE(SUBSYS=ssid REQSTOR=-)

Fix: F-25915r868211_fix

Use SAF security to define and protect the Products resouceresource class(es). Ensure that the following GSO CLASMAP record entry(ies) is (are) defined: CLASMAP.class RESOURCE(class) RSRCTYPE(type) ENTITYLN(nn) Note: The site determines the appropriate three letter RSRCTYPE that is unique for Mainview. The ENTITYLN should be appropriate for the site's installation. Example: SET C(GSO) LIST CLASMAP.BMCVIEW INSERT CLASMAP.BMCVIEW ENTITYLN(39) RESOURCE(BMCVIEW) RSRCTYPE(BBM) F ACF2,REFRESH(CLASMAP) Ensure that the following GSO SAFDEF record entry(ies) is (are) defined: SAFDEF.ssid ID(BBCS) MODE(GLOBAL)REP RACROUTE(SUBSYS=ssid REQSTOR=-) Example: ACF SET C(GSO) LIST SAFDEF.ssid INSERT SAFDEF.ssid ID(BBCS) MODE(GLOBAL)REP RACROUTE(SUBSYS=ssid REQSTOR=-) F ACF2,REFRESH(SAFDEF)

b
BMC MAINVIEW for z/OS configuration/parameter values are not specified properly.
AC-2 - Medium - CCI-000015 - V-224255 - SV-224255r1141594_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000015
Version
ZMVZA040
Vuln IDs
  • V-224255
  • V-18014
Rule IDs
  • SV-224255r1141594_rule
  • SV-37806
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.
Checks: C-25928r1141593_chk

Refer to the Configuration Location dataset and member specified in the z/OS Dialog Management Procedures for BMC MAINVIEW for z/OS. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZMVZ0040). The following keywords will have the specified values in the BMC MAINVIEW for z/OS security parameter member, this is not a finding. Statement(values) ESMTYPE(AUTO|ACF2)

Fix: F-25916r1069968_fix

The BMC MAINVIEW for z/OS Systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Set the standard values for the BMC MAINVIEW for z/OS security parameters for the specific ACP environment along with additional IOA security parameters with standard values as documented below. Statement(values) ESMTYPE(AUTO|ACF2)