{"stig":{"title":"z/OS BMC MAINVIEW for z/OS for RACF Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224423","ruleId":"SV-224423r1145261_rule","severity":"medium","ruleTitle":"BMC MAINVIEW for z/OS installation data sets are not properly protected.","description":"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.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(MVZRPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZMVZ0000).\n\nVerify 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.\n\nThe RACF data set rules for the data sets restricts READ access to all authorized users.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.","fixText":"The ISSO will ensure that WRITE and/or greater access to BMC MAINVIEW for z/OS installation data sets is limited to system programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users.\n\nThe 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.\n\nData sets to be protected will be: \nSYS2.BMCVIEW.**\nSYS3.BMCVIEW.** (data sets that are not altered by product STCs, can be more specific)\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS2.BMCVIEW.**' uacc(none) owner(sys2) -\n\taudit(success(update) failures(read)) -\n\tdata('BMC MAINVIEW for z/OS Install DS')\npe 'SYS2.BMCVIEW.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS2.BMCVIEW.**' id(<audtaudt> authorized users) acc(r)\npe 'SYS2.BMCVIEW.**' id(MAINVIEW STCs)\n\nad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) -\n\taudit(success(update) failures(read)) -\n\tdata('BMC MAINVIEW for z/OS Install DS')\npe 'SYS3.BMCVIEW.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r)\npe 'SYS3.BMCVIEW.**' id(MAINVIEW STCs)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224424","ruleId":"SV-224424r1145263_rule","severity":"medium","ruleTitle":"BMC MAINVIEW for z/OS STC data sets are not properly protected.","description":"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.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(MVZSTC).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZMVZ0001).\n\nVerify 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.\n \nThe RACF data set rules for the data sets restricts READ access to auditors and authorized users.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to the BMC MAINVIEW for z/OS's STC(s) and/or batch user(s).","fixText":"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.\n\nThe 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 ACP (Access Control Program) active on the system.\n\nData sets to be protected will be: \nSYS3.BMCVIEW (data sets that are altered by the product's STCs, this can be more specific)\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) -\n\taudit(failures(read)) -\n\tdata('Vendor DS Profile: BMC MAINVIEW for z/OS')\npe 'SYS3.BMCVIEW.**' id(<syspaudt> <tstcaudt> MAINVIEW STCs) acc(a)\npe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499"]},{"vulnId":"V-224425","ruleId":"SV-224425r1145265_rule","severity":"medium","ruleTitle":"BMC MAINVIEW resources must be properly defined and protected.","description":"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.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(ZMVZ0020).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZMVZ0020).\n\nVerify 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.\n\nThe RACF resources are defined with a default access of NONE.\n\nThe RACF resource access authorizations restrict access to the appropriate personnel.\n\nThe RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.","fixText":"The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP).\n\n(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 installed on a system through the product's installation guide and can be site specific.)\n\nUse 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.\n\nThe RACF resources as designated in the above table are defined with a default access of NONE.\n\nThe RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table.\n\nThe RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING.\n\nThe following commands are provided as a sample for implementing resource controls:\n\nRDEFINE #BMCVIEW BBM.ssid.CN UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ))\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(autoaudt)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(dasdaudt)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mqsaaudt)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(Mainview STCs)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mvzread)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(mvzupdt)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(pcspaudt)\nPERMIT BBM.ssid.CN CLASS(#BMCVIEW) ACCESS(ALTER) ID(syspaudt)","ccis":["CCI-000213"]},{"vulnId":"V-224426","ruleId":"SV-224426r1144923_rule","severity":"medium","ruleTitle":"BMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP.","description":"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.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- RACFCMDS.RPT(LISTUSER).\n\nVerify that the userid(s) for the BMC Mainview for z/OS started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nPROTECTED","fixText":"The BMC Mainview for z/OS system programmer and the ISSO will ensure that a product's Started Task(s) is properly identified and/or defined to the System ACP. \n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.\n\nA sample is provided here:\n\nau MV$CAS name('CAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass\nau MV$PAS name('PAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass\nau MV$MVS name('MVS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass","ccis":["CCI-000764"]},{"vulnId":"V-224427","ruleId":"SV-224427r1144926_rule","severity":"medium","ruleTitle":"BMC Mainview for z/OS Started task(s) must be properly defined to the STARTED resource class for RACF.","description":"Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could compromise the operating system, ACP, and customer data.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- DSMON.RPT(RACSPT).\n\nAutomated Analysis\nRefer to the following report produced by the RACF Data Collection:\n\n- PDI(ZMVZ0032).\n\nVerify that the BMC Mainview for z/OS started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.","fixText":"The BMC Mainview system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. \n\nA unique userid must be assigned for the BMC Mainview started task(s) thru a corresponding STARTED class entry.\n\nThe following sample set of commands is shown here as a guideline:\n\nrdef started MV$CAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$CAS) group(stc))\nrdef started MV$MVS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$MVS) group(stc))\n\nsetr racl(started) ref","ccis":["CCI-000764"]},{"vulnId":"V-224428","ruleId":"SV-224428r1144929_rule","severity":"medium","ruleTitle":"BMC Mainview for z/OS Resource Class will be defined or active in the ACP.","description":"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.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- RACFCMDS.RPT(SETROPTS).\n- DSMON.RPT(RACCDT) - Alternate list of active resource classes.\n\nAutomated Analysis\nRefer to the following report produced by the RACF Data Collection:\n\n- PDI(ZMVZ0038).\n\nIf the BMC Mainview for z/OS resource class(es) is (are) active, this is not a finding.","fixText":"The ISSO will ensure that the BMC Mainview for z/OS Resource Class(es) is (are) active.\n\nUse the following commands as an example:\n\nRDEFINE CDT class -\nCDTINFO( MAXLENGTH(64) DEFAULTUACC(NONE) -\nFIRST(ALPHA) CASE(UPPER) -\nOTHER(ALPHA,NUMERIC,NATIONAL,SPECIAL) -\nPOSIT(301) RACLIST(REQUIRED) -\nGENERIC(ALLOWED) GENLIST(ALLOWED) -\nOPERATIONS(YES) -\n) UACC(NONE)\n\nSETROPTS CLASSACT(CDT) RACLIST(CDT)\nSETROPTS RACLIST(CDT) REFRESH\n\nSETROPTS GENERIC(class) GENCMD(class)\nSETROPTS CLASSACT(class) RACLIST(class)\nSETROPTS RACLIST(class) REFRESH","ccis":["CCI-000336","CCI-002358"]},{"vulnId":"V-224429","ruleId":"SV-224429r1144931_rule","severity":"medium","ruleTitle":"BMC MAINVIEW for z/OS configuration/parameter values are not specified properly.","description":"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.","checkContent":"Refer to the Configuration Location data set and member specified in the z/OS Dialog Management Procedures for BMC MAINVIEW for z/OS.\n\nAutomated Analysis\nRefer to the following report produced by the z/OS Data Collection:\n\n- PDI(ZMVZ0040).\n\nIf the following keywords specify the values in the BMC MAINVIEW for z/OS security parameter member, this is not a finding.\n\nStatement(values)\nESMTYPE(AUTO|RACF)","fixText":"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.\n\nStatement(values)\nESMTYPE(AUTO|RACF)","ccis":["CCI-000015","CCI-000381"]}]}