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

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

V7R1 · · · Released 02 Apr 2025 · 7 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.
Digest of Updates vs. V6R8 · 23 Nov 2022 ✎ 3

Comparison against the immediately-prior release (V6R8). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 3

  • V-224423 Medium descriptioncheckfix BMC MAINVIEW for z/OS installation data sets are not properly protected.
  • V-224425 Medium descriptioncheckfix BMC MAINVIEW resources must be properly defined and protected.
  • V-224429 Medium fix BMC MAINVIEW for z/OS configuration/parameter values are not specified properly.
Sort by
b
BMC MAINVIEW for z/OS installation data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224423 - SV-224423r1070191_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMVZR000
Vuln IDs
  • V-224423
  • V-16932
Rule IDs
  • SV-224423r1070191_rule
  • SV-33836
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.
Checks: C-26100r1070189_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MVZRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMVZ0000) Verify that the accesses to the BMC MAINVIEW for z/OS installation data sets are properly restricted. The RACF data set rules for the data sets restricts READ access to all authorized users. The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

Fix: F-26088r1070190_fix

The ISSO will ensure that update and alter access to BMC MAINVIEW for z/OS installation data sets is limited to system programmers only, and all update and alter access is logged. Read access can be given to all authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Data sets to be protected will be: SYS2.BMCVIEW.** SYS3.BMCVIEW.** (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.BMCVIEW.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('BMC MAINVIEW for z/OS Install DS') pe 'SYS2.BMCVIEW.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.BMCVIEW.**' id(<audtaudt> authorized users) acc(r) pe 'SYS2.BMCVIEW.**' id(MAINVIEW STCs) ad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('BMC MAINVIEW for z/OS Install DS') pe 'SYS3.BMCVIEW.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r) pe 'SYS3.BMCVIEW.**' id(MAINVIEW STCs) setr generic(dataset) refresh

b
BMC MAINVIEW for z/OS STC data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224424 - SV-224424r958616_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMVZR001
Vuln IDs
  • V-224424
  • V-17067
Rule IDs
  • SV-224424r958616_rule
  • SV-37723
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.
Checks: C-26101r868504_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MVZSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMVZ0001) Verify that the accesses to the BMC MAINVIEW for z/OS STC data sets are properly restricted. ___ The RACF data set rules for the data sets restricts READ access to auditors and authorized users. ___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. ___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to the BMC MAINVIEW for z/OS's STC(s) and/or batch user(s).

Fix: F-26089r868505_fix

The ISSO will ensure that update and allocate access to BMC MAINVIEW for z/OS STC data sets 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 data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.BMCVIEW (data sets that are altered by the product's STCs, this can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: BMC MAINVIEW for z/OS') pe 'SYS3.BMCVIEW.**' id(<syspaudt> <tstcaudt> MAINVIEW STCs) acc(a) pe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r) setr generic(dataset) refresh

b
BMC MAINVIEW resources must be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224425 - SV-224425r1070176_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZMVZR020
Vuln IDs
  • V-224425
  • V-17947
Rule IDs
  • SV-224425r1070176_rule
  • SV-46312
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-26102r1070174_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZMVZ0020) Automated Analysis Refer to the following report produced by the Data Set 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 RACF resources are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel. The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.

Fix: F-26090r1070175_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 class, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource class, resources, and/or prefixes are determined when the product is actually 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 resources and/or generic equivalent specified in the z/OS STIG Addendum are followed. The RACF resources as designated in the above table are defined with a default access of NONE. The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table. The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING. The following commands are provided as a sample for implementing resource controls: RDEFINE #BMCVIEW BBM.ssid.CN UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ)) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(autoaudt) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(dasdaudt) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mqsaaudt) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(Mainview STCs) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mvzread) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mvzupdt) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(pcspaudt) PERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(syspaudt)

b
BMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224426 - SV-224426r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZMVZR030
Vuln IDs
  • V-224426
  • V-17452
Rule IDs
  • SV-224426r958482_rule
  • SV-33839
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.
Checks: C-26103r518986_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) The BMC Mainview for z/OS started task(s) and/or batch job userid(s) is defined and is assigned the RACF PROTECTED attribute.

Fix: F-26091r518987_fix

The BMC Mainview for z/OS system programmer and the IAO will 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. A sample is provided here: au MV$CAS name('CAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass au MV$PAS name('PAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass au MV$MVS name('MVS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass

b
BMC Mainview for z/OS Started task(s) must be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-224427 - SV-224427r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZMVZR032
Vuln IDs
  • V-224427
  • V-17454
Rule IDs
  • SV-224427r958482_rule
  • SV-33841
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.
Checks: C-26104r518989_chk

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZMVZ0032) Verify that the BMC Mainview for z/OS started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry.

Fix: F-26092r518990_fix

The BMC Mainview system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the BMC Mainview started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started MV$CAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$CAS) group(stc)) rdef started MV$MVS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$MVS) group(stc)) setr racl(started) ref

b
BMC Mainview for z/OS Resource Class will be defined or active in the ACP.
CM-4 - Medium - CCI-000336 - V-224428 - SV-224428r987853_rule
RMF Control
CM-4
Severity
M
CCI
CCI-000336
Version
ZMVZR038
Vuln IDs
  • V-224428
  • V-18011
Rule IDs
  • SV-224428r987853_rule
  • SV-33845
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-26105r518992_chk

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(SETROPTS) - DSMON.RPT(RACCDT) - Alternate list of active resource classes Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZMVZ0038) Ensure that the BMC Mainview for z/OS resource class(es) is (are) defined and active.

Fix: F-26093r518993_fix

The IAO will ensure that the BMC Mainview for z/OS Resource Class(es) is (are) active. Use the following commands as an example: RDEFINE CDT class - CDTINFO( MAXLENGTH(64) DEFAULTUACC(NONE) - FIRST(ALPHA) CASE(UPPER) - OTHER(ALPHA,NUMERIC,NATIONAL,SPECIAL) - POSIT(301) RACLIST(REQUIRED) - GENERIC(ALLOWED) GENLIST(ALLOWED) - OPERATIONS(YES) - ) UACC(NONE) SETROPTS CLASSACT(CDT) RACLIST(CDT) SETROPTS RACLIST(CDT) REFRESH SETROPTS GENERIC(class) GENCMD(class) SETROPTS CLASSACT(class) RACLIST(class) SETROPTS RACLIST(class) REFRESH

b
BMC MAINVIEW for z/OS configuration/parameter values are not specified properly.
AC-2 - Medium - CCI-000015 - V-224429 - SV-224429r1070113_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000015
Version
ZMVZR040
Vuln IDs
  • V-224429
  • V-18014
Rule IDs
  • SV-224429r1070113_rule
  • SV-37807
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-26106r518995_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: Statement(values) ESMTYPE(AUTO|RACF)

Fix: F-26094r1070112_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|RACF)