What changed in z/OS CA MIM for TSS STIG V7R2V7R2 changes

Check text

Refer to the contents of MIMINIT member of the data set(s) specified in the MIMPARMS DD statement of the started task procedures. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZMIM0040). Ensure the following CA MIM Resource Sharing parameter(s) is (are) specified in the MIMINIT member of the data set(s) specified in the MIMPARMS DD statement of the started task procedures. If the following guidance is true, this is not a finding. Parameter Value SAFCMDAUTH ON

Discussion

CA MIM Resource Sharing offers external security interfaces that are controlled by parameters specified in the MIMINIT member in the MIMPARMS DD statement of the started task procedures. These interfaces provide security controls for CA MIM. Without proper controls to ensure that security is active, the integrity of the CA MIM Resource Sharing System and the confidentiality of data stored on the system may be compromised.

V-224626 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MIMRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMIM0000). Verify that the accesses to the CA MIM Resource Sharing installation 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 all authorized users. The TSS data set access authorizations restrictsrestrict 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 CA MIM Resource Sharing 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. 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 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. (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.MIMGR. SYS3.MIMGR. (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(&ltsyspaudt>) DSN(SYS2.MIMGR.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS2.MIMGR.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&lttstcaudt>) DSN(SYS2.MIMGR.) ACCESS(R) TSS PERMIT(&lttstcaudt>) DSN(SYS2.MIMGR.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS2.MIMGR.) ACCESS(R) TSS PERMIT(authorized users) DSN(SYS2.MIMGR.) ACCESS(R) TSS PERMIT(CA MIM STCs) DSN(SYS2.MIMGR.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS3.MIMGR.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS3.MIMGR.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&lttstcaudt>) DSN(SYS3.MIMGR.) ACCESS(R) TSS PERMIT(&lttstcaudt>) DSN(SYS3.MIMGR.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.MIMGR.) ACCESS(R) TSS PERMIT(authorized users) DSN(SYS3.MIMGR.) ACCESS(R) TSS PERMIT(CA MIM STCs) DSN(SYS3.MIMGR.) ACCESS(R)

V-224627 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MIMSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMIM0001). Verify that the accesses to the CA MIM Resource Sharing STC 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 and authorized users. ___ 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 CA MIM Resource Sharing's STC(s) and/or batch user(s).

Fix text

The ISSO will ensure that WRITE and/or greater access to CA MIM Resource Sharing STC data sets is limited to systems programmers and/or CA MIM Resource Sharing'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 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 (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.MIMGR. (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(&ltsyspaudt>) DSN(SYS3.MIMGR) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(SYS3.MIMGR) ACCESS(ALL) TSS PERMIT(CA MIM STCs) DSN(SYS3.MIMGR) ACCESS(ALL) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.MIMGR) ACCESS(R) TSS PERMIT(authorize user) DSN(SYS3.MIMGR) ACCESS(R)

V-224628 in V7R2

Check text

Refer to the following reportreports produced by the TSS Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(ZMIM0020). - TSSCMDS.RPT(#RDT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMIM0020). Verify that the accesses to resources and/or generic equivalent are properly restricted according to the requirements specified in CA MIM Resource Sharing 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 resources and/or resource prefixes identified below are examples of a possible installation. The 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 CA MIM Resource Sharing Resources table in the zOS STIG Addendum. This table list the resources, access requirements, and logging requirement for CA MIM Resource Sharing. Ensure the guidelines for the resources and/or generic equivalent specified in the z/OS STIG Addendum are followed. Note: SAFPREFIX identifies the prefix for all resources. The default value for this keyword parameter is MIMGR. It is coded in the MIMINIT member of the data set specified in the MIMPARMS DD statement of the started task procedures. 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) OPERCMDS(prefix) TSS PERMIT(syspaudt) OPERCMDS(prefix.ACTIVATE) ACCESS(UPDATE)

V-224629 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). VerifyReview that the ACID(s) for the CA MIM Resource Sharing startedSTC/Batch taskACID(s) is (are) properly defined. If the following attributes are defined, this is not a finding. FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND

Fix text

The IAOISSO working with the systems programmer will ensure the CA MIM Resource Sharing 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. The following commands are provided as a sample for defining Started Task(s): TSS CREATE(MIMGR) TYPE(USER) - NAME('STC, CA MIM') DEPT(xxxx) - FAC(STC,BATCH) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

Discussion

CA MIM Resource Sharing 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-224630 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(ZMIM0032). If the CA MIM Resource Sharing started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The IAOISSO working with the systems programmer will ensure the CA MIM Resource Sharing Started Task(s) is properly identified and/or defined to the Systemsystem ACP. A unique ACID must be assigned for the CA MIM Resource Sharing started task(s) thruthrough a corresponding STC table entry. The following commands are provided as a sample for defining Started Task(s): TSS ADD(STC) PROCNAME(MIMGR) ACID(MIMGR)

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