V7R2 changes
z/OS BMC MAINVIEW for z/OS for TSS STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 8 checks updated. It has 8 checks, against 8 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 8 updated
Updated fields: Check text 8Fix text 5Discussion 2
Updated in V7R2 (8)
V-224607CAT IIBMC MAINVIEW for z/OS installation data sets are not properly protected.Check text, Fix text
Check text
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. If the following guidance is true, this is not a finding.
The TSS data set rules for the data sets restrictsrestrict READ access to all authorized users.
The TSS data set rules for the data sets restrictsrestrict UPDATEWRITE and/or ALLgreater access to systems programming personnel.
The TSS data set rules for the data sets specify that all (i.e., failures and successes) UPDATEWRITE and/or ALLgreater access are logged.
Fix text
The ISSO will ensure that updateWRITE and/or allocategreater access to BMC MAINVIEW for z/OS installation data sets is limited to systemsystems programmers only, and all updateWRITE and/or allocategreater access is logged. Read 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 updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater 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. (dataData sets that are not altered by product STCs,; this can be more specific)
The following commands are provided as a sample for implementing data set controls:
TSS PERMIT(<syspaudt>) DSN(SYS2.BMCVIEW.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS2.BMCVIEW.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<tstcaudt>) DSN(SYS2.BMCVIEW.) ACCESS(R)
TSS PERMIT(<tstcaudt>) DSN(SYS2.BMCVIEW.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<audtaudt>) DSN(SYS2.BMCVIEW.) ACCESS(R)
TSS PERMIT(authorized users) DSN(SYS2.BMCVIEW.) ACCESS(R)
TSS PERMIT(MAINVIEW STCs) DSN(SYS2.BMCVIEW.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS3.BMCVIEW.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS3.BMCVIEW.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<tstcaudt>) DSN(SYS3.BMCVIEW.) ACCESS(R)
TSS PERMIT(<tstcaudt>) DSN(SYS3.BMCVIEW.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<audtaudt>) DSN(SYS3.BMCVIEW.) ACCESS(R)
TSS PERMIT(authorized users) DSN(SYS3.BMCVIEW.) ACCESS(R)
TSS PERMIT(MAINVIEW STCs) DSN(SYS3.BMCVIEW.) ACCESS(R)
V-224608CAT IIBMC MAINVIEW for z/OS STC data sets are not properly protected.Check text, Fix text
Check text
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.
If the following guidance is true, this is not a finding.
___
The TSS data set rules for the data sets restrictsrestrict READ access to auditors and authorized users.
___ The TSS data set rules for the data sets restrictsrestrict UPDATE and/or ALL access to systems programming personnel.
___ The TSS data set rules for the data sets restrictsrestrict UPDATE and/or ALL access to the BMC MAINVIEW for z/OS's STC(s) and/or batch user(s).
Fix text
The ISSO will ensure that updateWRITE and/or allocategreater 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. ReadREAD 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 updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater 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 (ACP) active on the system.
Data sets to be protected will be:
SYS3.BMCVIEW (dataData 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:
TSS PERMIT(<syspaudt>) DSN(SYS3.BMCVIEW) ACCESS(ALL)
TSS PERMIT(<tstcaudt>) DSN(SYS3.BMCVIEW) ACCESS(ALL)
TSS PERMIT(MAINVIEW STCs) DSN(SYS3.BMCVIEW) ACCESS(ALL)
TSS PERMIT(<audtaudt>) DSN(SYS3.BMCVIEW) ACCESS(R)
TSS PERMIT(authorize user) DSN(SYS3.BMCVIEW) ACCESS(R)
V-224609CAT IIBMC MAINVIEW resources must be properly defined and protected.Check text
Check text
Refer to the following reportreports produced by the TSS Data Collection and Data Set and Resource Data Collection:
- SENSITVE.RPT(ZMVZ0020).
- TSSCMDS.RPT(#RDT).
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 TSS resources are owned or DEFPROT is specified for the resource class.
The TSS resource access authorizations restrict access to the appropriate personnel.
V-224610CAT IIBMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(@ACIDS).
Review each BMC Mainview for z/OS STC/Batch ACID(s). forIf the following:
___ Defined withattributes Facilityare of STCdefined, BBI3 (the TSS FACILITY Matrix Table entry defined for this product),is and/ornot BATCHa forfinding.
For MV$CAS, and MV$PAS
FACILITY(STC, andBBI3)
PASSWORD(xxxxxxxx,0)
SOURCE(INTRDR)
NOSUSPEND
MASTFAC(BBI3)
For MV$MVS.
___ DefinedFACILITY(STC, with Master Facility of BBI3 )
PASSWORD(the TSS FACILITY Matrix Table entry defined for this productxxxxxxxx,0) for MV$CAS and MV$PAS.
___ Is sourced to the SOURCE(INTRDR.)
NOSUSPEND
Fix text
The BMC Mainview for z/OS systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly identified and/or defined to the Systemsystem ACP.
If the product requires a Started Task, verify that it is properly defined to the Systemsystem 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:
TSS CREATE(MV$CAS) TYPE(USER) -
NAME('CAS, BMC Mainview for z/OS') DEPT(xxxx) -
FAC(STC,BBI3) -
MASTFAC(BBI3) PASS(xxxxxxxx,0) -
SOURCE(INTRDR) NOSUSPEND
TSS CREATE(MV$PAS) TYPE(USER) -
NAME('PAS, BMC Mainview for z/OS') DEPT(xxxx) -
FAC(STC,BBI3) -
MASTFAC(BBI3) PASS(xxxxxxxx,0) -
SOURCE(INTRDR) NOSUSPEND
TSS CREATE(MV$MVS) TYPE(USER) -
NAME('MVS, BMC Mainview for z/OS') DEPT(xxxx) -
FAC(STC,BBI3) -
PASS(xxxxxxxx,0) -
SOURCE(INTRDR) NOSUSPEND
Discussion
BMC Mainview for z/OS requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining 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-224611CAT IIBMC Mainview for z/OS Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(#STC).
Automated Analysis
Refer to the following report produced by the TSS Data Collection:
- PDI(ZMVZ0032).
VerifyIf that the BMC Mainview for z/OS started task(s) is (are) defined in the TSS STC record, this is not a finding.
Fix text
The BMC Mainview for z/OS systemsystems programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the Systemsystem ACP.
A unique ACID must be assigned for the BMC Mainview for z/OS started task(s) thruthrough a corresponding STC table entry.
The following sample set of commands is shown here as a guideline:
TSS ADD(STC) PROCNAME(MV$CAS) ACID(MV$CAS)
TSS ADD(STC) PROCNAME(MV$MVS) ACID(MV$MVS)
Discussion
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-224612CAT IIBMC Mainview for z/OS is not properly defined to the Facility Matrix Table for Top Secret.Check text, Fix text
Check text
Refer to the following reportreports produced by the TSS Data Collection:
- TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values.
- TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup.
EnsureIf the BMC Mainview for z/OS Facility Matrix table is defined as follows:stated below, this is not a finding.
BBI3:
FAC(USERxx=NAME=BBI3,PGM=BBM,ID=nn,ACTIVE,SHRPRF,ASUBM)
FAC(BBI3=NOABEND,MULTIUSER,NOXDEF,SIGN(S),RES,LUMSG)
FAC(BBI3=STMSG,WARNPW,NORNDPW,NOAUDIT,NOTSOC,MODE=FAIL)
FAC(BBI3=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)
Fix text
The BMC Mainview for z/OS systemsystems programmer and the IAOISSO will ensure that the TOP SECRET Facility Matrix Table is proper defined using the following example:
**** BBI3
*
FACILITY(USERxx=NAME=BBI3,PGM=BBM,ID=nn,ACTIVE,SHRPRF)
FACILITY(BBI3=ASUBM,NOABEND,MULTIUSER,NOXDEF)
FACILITY(BBI3=LUMSG,STMSG,SIGN(S),NORNDPW)
FACILITY(BBI3=NOAUDIT,RES,WARNPW,NOTSOC)
FACILITY(BBI3=MODE=FAIL,LOG(SMF,INIT,MSG,SEC9))
FACILITY(BBI3=UIDACID=8,LOCKTIME=000)
V-224613CAT IIBMC Mainview for z/OS Resource Class must be defined or active in the ACP.Check text
Check text
Refer to the following report produced by the ACP Data Collection: - TSSCMDS.RPT(#RDT). If the BMC Mainview for z/OS Resource Class(es) is (are) defined in the Resource Definition Table (RDT) as follows, this is not a finding. RESOURCE CLASS = class RESOURCE CODE = X'hex code' ATTRIBUTE = MASK|NOMASK,MAXOWN(08),MAXPERMIT(044),ACCESS,DEFPROT ACCESS = NONE(0000),CONTROL(0400),UPDATE(6000),READ(4000) ACCESS = WRITE(2000),ALL(FFFF) DEFACC = READ
V-224614CAT IIBMC MAINVIEW for z/OS configuration/parameter values are not specified properly.Check text
Check text
Refer to the Configuration Location datasetdata set 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).
TheIf the following keywords willspecify have the specified values in the BMC MAINVIEW for z/OS security parameter member:, this is not a finding.
Statement(values)
ESMTYPE(AUTO|TSS)
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.