None Computing title z/OS BMC MAINVIEW for z/OS for TSS Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224607 Rule_ID SV-224607r1146357_rule Severity medium Rule_Title BMC MAINVIEW for z/OS installation data sets are not properly protected. Vuln_Discuss 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. Check_Content 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 restrict READ access to all authorized users. The TSS data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged. Fix_Text The ISSO will ensure that WRITE and/or greater access to BMC MAINVIEW for z/OS installation data sets 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 data sets 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 installing systems programmer will identify if any additional groups have WRITE and/or greater 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; 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) Not_Reviewed Vuln_Num V-224608 Rule_ID SV-224608r1146359_rule Severity medium Rule_Title BMC MAINVIEW for z/OS STC data sets are not properly protected. Vuln_Discuss 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. Check_Content 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 restrict READ access to auditors and authorized users. The TSS data set rules for the data sets restrict UPDATE and/or ALL access to systems programming personnel. The TSS data set rules for the data sets restrict 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 WRITE and/or greater 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 WRITE and/or greater access and if required 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 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: 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: 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) Not_Reviewed Vuln_Num V-224609 Rule_ID SV-224609r1146076_rule Severity medium Rule_Title BMC MAINVIEW resources must be properly defined and protected. Vuln_Discuss 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. Check_Content Refer to the following reports 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. Fix_Text 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 resource class, actual 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 zOS 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 TSS resources as designated in the above table are owned and/or DEFPROT is specified for the resource class. The TSS 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: TSS ADD(dept-acid) #BMCVIEW(BBM) TSS PERMIT(autoaudt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(dasdaudt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(mqsaaudt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(Mainview STCs) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(mvzread) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(mvzupdt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(pcspaudt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) TSS PERMIT(syspaudt) #BMCVIEW(BBM.ssid.CN) ACCESS(ALL) Not_Reviewed Vuln_Num V-224610 Rule_ID SV-224610r1146079_rule Severity medium Rule_Title BMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP. Vuln_Discuss BMC Mainview for z/OS requires a started task that will be restricted to certain resources, data sets, 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. Check_Content Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review BMC Mainview for z/OS STC/Batch ACID(s). If the following attributes are defined, this is not a finding. For MV$CAS and MV$PAS FACILITY(STC, BBI3) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND MASTFAC(BBI3) For MV$MVS FACILITY(STC, BBI3) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND Fix_Text The BMC Mainview for z/OS systems programmer and the ISSO 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: 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 Not_Reviewed Vuln_Num V-224611 Rule_ID SV-224611r1146082_rule Severity medium Rule_Title BMC Mainview for z/OS Started task(s) must be properly defined to the Started Task Table ACID for Top Secret. Vuln_Discuss 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. Check_Content 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). If 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 systems programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the system ACP. A unique ACID must be assigned for the BMC Mainview for z/OS started task(s) through 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) Not_Reviewed Vuln_Num V-224612 Rule_ID SV-224612r1146085_rule Severity medium Rule_Title BMC Mainview for z/OS is not properly defined to the Facility Matrix Table for Top Secret. Vuln_Discuss Improperly defined security controls for BMC Mainview for z/OS could result in the compromise of the network, operating system, and customer data. Check_Content Refer to the following reports 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. If the BMC Mainview for z/OS Facility Matrix table is defined as 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 systems programmer and the ISSO 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) Not_Reviewed Vuln_Num V-224613 Rule_ID SV-224613r1146087_rule Severity medium Rule_Title BMC Mainview for z/OS Resource Class must be defined or active in the ACP. Vuln_Discuss 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. Check_Content 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 Fix_Text The ISSO will ensure the BMC Mainview for z/OS resource class(es) is (are) defined in the TSS RDT. (Note: The RESCLASS and/or RESCODE identified below are examples of a possible installation. The actual RESCLASS and/or RESCODE values are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Use the following commands as an example: TSS ADDTO(RDT) RESCLASS(BMCVIEW) - RESCODE(3B) DEFACC(READ) - ATTR(MASK|NOMASK,DEFPROT,LONG,GENERIC) - ACLST(NONE,READ,UPDATE,ALL) Not_Reviewed Vuln_Num V-224614 Rule_ID SV-224614r1146089_rule Severity medium Rule_Title BMC MAINVIEW for z/OS configuration/parameter values are not specified properly. Vuln_Discuss 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. Check_Content Refer to the Configuration Location data 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). If the following keywords specify the values in the BMC MAINVIEW for z/OS security parameter member, this is not a finding. Statement(values) ESMTYPE(AUTO|TSS) Fix_Text 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 Access Control Program (ACP) environment along with additional IOA security parameters with standard values as documented below. Statement(values) ESMTYPE(AUTO|TSS) Not_Reviewed