What changed in zOS BMC CONTROL-M for TSS STIG V7R2V7R2 changes

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0000). Verify that the accesses to the BMC CONTROL-M installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrict READ access to auditors, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), and BMC STCs and/or batch users. ___ The TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set access authorizations 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 CONTROL-M installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), and BMC STCs and/or batch users. All failures and successful WRITE and/or greater accesses are logged. 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. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets 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.) Data sets to be protected will be: SYS2.IOA.*.CTMI. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltautoaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltbmcuser>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltdpcsaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltoperaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(&ltpcspaudt>) DSN(SYS2.IOA.*.CTMI.) ACCESS(R) TSS PERMIT(CONTROLM) DSN(SYS2.IOA.*.CTMI.) ACCESS(R)

V-224569 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0001). Verify that the accesses to the BMC CONTROL-M STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrictsrestrict READ access to auditors and BMC users. ___ The TSS data set access authorizations restrictsrestrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set access authorizations restrictsrestrict UPDATE access to the BMC STCs and/or batch users. ___ The TSS data set access authorizations restrictsrestrict UPDATE access to scheduled batch jobs, operations, and production control and scheduling personnel.

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M STC data sets are limited to systems programmers only. UPDATE access can be given to scheduled batch jobs, operations, and production control and scheduling personnel, BMC STCs and/or batch users. READ access can be given to auditors and/or BMC 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. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets 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.) Data sets to be protected will be: SYS3.IOA.*.CTMO. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(ALL) TSS PERMIT(CONTDAY) DSN(SYS3.IOA.*.CTMO.) ACCESS(U) TSS PERMIT(CONTROLM) DSN(SYS3.IOA.*.CTMO.) ACCESS(U) TSS PERMIT(&ltautoaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(U) TSS PERMIT(&ltoperaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(U) TSS PERMIT(&ltpcspaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(U) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.IOA.*.CTMO.) ACCESS(R) TSS PERMIT(&ltbmcuser>) DSN(SYS3.IOA.*.CTMO.) ACCESS(R)

V-224570 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0002). Verify that the accesses to the BMC CONTROL-M User data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrict READ access to auditors. ___ The TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The TSS data set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The TSS data set access authorizations restrict UPDATE access to the BMC Users, operations, and production control and scheduling personnel (both domain level and Application level).

Fix text

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M User data sets are limited to systems programmers and/or BMC STCs and/or batch users only. UPDATE access can be given to the BMC Users, operations, and production control and scheduling personnel (both domain level and Application level). READ access can be given to auditors. 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. (Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets 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.) Data sets to be protected will be: SYS3.IOA.*.CTMC. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.IOA.*.CTMC.) ACCESS(ALL) TSS PERMIT(BMC STCs) DSN(SYS3.IOA.*.CTMC.) ACCESS(ALL) TSS PERMIT(&ltbmcuser>) DSN(SYS3.IOA.*.CTMC.) ACCESS(UPDATE) TSS PERMIT(&ltoperaudt>) DSN(SYS3.IOA.*.CTMC.) ACCESS(UPDATE) TSS PERMIT(&ltpcspaudt>) DSN(SYS3.IOA.*.CTMC.) ACCESS(UPDATE) TSS PERMIT(&ltdpcsaudt>) DSN(SYS3.IOA.*.CTMC.) ACCESS(UPDATE) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.IOA.*.CTMC.) ACCESS(READ)

V-224571 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMJCL). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL data sets are limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. ___ The TSS data set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. ___ The TSS data set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. ___ The TSS data set access authorizations restrict UPDATE access to the Production Control and Scheduling personnel (both domain level and Application level) and BMC STCs and/or batch users. Accesses must be reviewed and approved by the ISSO based on a documented need to perform job duties. Application (external users) will not have access to internal/site data sets. Note: Update or greater access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. Update or greater access of the site's (LPAR Level) IA (Security) administrative batch processing JCL and Procedures must be limited to only the LPAR LEVEL ISSO/ISSM Team. It is recommended that multiple data sets be created, one of which that contains JCL and Procedures that are considered restricted and this data set be authorized to those user with justification to maintain and run these restricted JCL and Procedures.

Fix text

Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL data sets are limited to systems programmers and/or BMC administrators only. UPDATE access can be given to the production control and scheduling personnel (both domain level and Application level) and BMC STCs and/or batch users. READ access can be given to auditors, automated batch user(s), BMC users, and operations. Access will be based on a documented need to know requirement. Application (external users) will not have access to internal/site data sets. The installing Systemssystems Programmerprogrammer 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 Systemssystems Programmerprogrammer 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 seeensure that they are properly restricted to the ACP (Access Control Program (ACP) active on the system. (NOTENote: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets 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.) Data sets to be protected will be: IOA. The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltbmcadmin>) DSN(IOA.) ACCESS(ALL) TSS PERMIT(&ltsyspaudt>) DSN(IOA.) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(IOA.) ACCESS(ALL) TSS PERMIT(CONTDAY) DSN(IOA.) ACCESS(UPDATE) TSS PERMIT(CONTROLM) DSN(IOA.) ACCESS(UPDATE) TSS PERMIT(dpcsaudt) DSN(IOA.) ACCESS(UPDATE) TSS PERMIT(&ltpcspaudt>) DSN(IOA.) ACCESS(UPDATE) TSS PERMIT(&ltaudtaudt>) DSN(IOA.) ACCESS(READ) TSS PERMIT(&ltautoaudt>) DSN(IOA.) ACCESS(READ) TSS PERMIT(&ltbmcuser>) DSN(IOA.) ACCESS(READ) TSS PERMIT(&ltoperaudt>) DSN(IOA.) ACCESS(READ)

V-224572 in V7R2

Check text

Refer to the following reportsreport produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZCTM0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in BMC CONTROL-M Resources table in the z/OS STIG Addendum. If the following guidance is true, this is not a finding. Note: To determine what resource class is used review the IOACLASS setting in SECPARM. The "Trigger" resources, i.e., $$SECxxx (xxx is unique to the product) are defined in the FACILITY resource class ___ The TSS resources are owned or DEFPROT is specified for the resource class. ___ The TSS resource access authorizations restrict access to the appropriate personnel. ___ The TSS resource logging requirements are specified.

V-224573 in V7R2

Title

BMC CONTROL-M Started Task name is not properly identified / defined to the system ACP.

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review each BMC CONTROL-M STC/Batch ACID(s). forIf the following: ___ Defined withattributes Facilityare ofdefined, STCthis and/oris BATCH. ___ Definednot witha Master Facility of CONTROLMfinding. ___ IsFACILITY(STC, sourced to the BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR.) NOSUSPEND MASTFAC(CONTROLM)

Fix text

The BMC CONTROL-M systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly Identified identified/ 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(CONTROLM) TYPE(USER) - NAME('*STC* for IOA') DEPT(xxxx) - FAC(STC) - MASTFAC(CONTROLM) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

Discussion

BMC CONTROL-M 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-224574 in V7R2

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(ZCTM0032). VerifyIf that the BMC CONTROL-M started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The BMC CONTROL-M 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 CONTROL-M 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(CONTOLM) ACID(CONTROLM)

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-224575 in V7R2

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 CONTROL-M Facility Matrix table is defined as follows:, this is not a finding. FAC(USERxx=NAME=CONTROLM,PGM=CTM,ID=nn,ACTIVE,SHRPRF) FAC(CONTROLM=ASUBM,NOABEND,MULTIUSER,NOXDEF,SIGN(S)) FAC(CONTROLM=RES,LUMSG,STMSG,WARNPW,NORNDPW) FAC(CONTROLM=NOAUDIT,NOTSOC,MODE=FAIL) FAC(CONTROLM=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

Fix text

The BMC CONTROL-M systemsystems programmer and the IAOISSO will ensure that the TOP SECRET Facility Matrix Table is properly defined using the following example: CONTROLM: FAC(USERxx=NAME=CONTROLM,PGM=CTM,ID=nn,ACTIVE,SHRPRF) FAC(CONTROLM=ASUBM,NOABEND,MULTIUSER,NOXDEF) FAC(CONTROLM=LUMSG,STMSG,SIGN(S),WARNPW,NORNDPW) FAC(CONTROLM=NOAUDIT,NOTSOC,MODE=FAIL) FAC(CONTROLM=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)

V-224576 in V7R2

Check text

Refer to the following applicable reportsreport produced by the z/OS Data Collection: - IOA.RPT(SECPARM). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCTM0040). TheIf the following keywords willspecify have the specified values in the BMC CONTROL-M security parameter member:, this is not a finding. Keyword Value DEFMCHKM $$CTMEDM SECTOLM NO DFMM01 EXTEND DFMM02 EXTEND DFMM08 EXTEND TSSJCARD U MSUBCHK NO

V-224577 in V7R2