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

Check text

Refer to the contents of MIMINIT member of the data setdataset(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). EnsureVerify the following CA MIM Resource Sharing parameter(s) is (are) specified in the MIMINIT member of the data setdataset(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

Fix text

The systems programmer/ISSO will ensure that the CA MIM Resource Sharing parameter(s) is (are) specified. CA MIM Resource Sharing security interfaces are controlled by parameters coded in the MIMINIT member of the data setdataset(s) specified in the MIMPARMS DD statement of the started task procedures. 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-224274 in V7R2

Title

CA MIM Resource Sharing installation data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(MIMRPT). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZMIM0000). Verify that the accesses to the CA MIM Resource Sharing installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 datadataset set access authorizations restrict READ access to all authorized users. The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 datadataset set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access areis logged.

Fix text

The ISSO will ensure that WRITE and/or greater access to CA MIM Resource Sharing installation datadatasets 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 datadatasets, sets and categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 setsdatasets, 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 datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS2.MIMGR. SYS3.MIMGR. (dataDatasets sets that are not altered by product STCs, can be more specific.) The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) MIMGR.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(&lttstcaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(&ltaudtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID(&ltaudtaudt>) R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A) $KEY(SYS3) MIMGR.- UID(&ltsyspaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(&lttstcaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(&ltaudtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A)

Discussion

CA MIM Resource Sharing installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224275 in V7R2

Title

CA MIM Resource Sharing STC data sets will be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(MIMSTC). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZMIM0001). Verify that the accesses to the CA MIM Resource Sharing STC datadatasets sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set access authorizations restrict READ access to auditors and authorized users. ___ The ACF2 datadataset set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 datadataset 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 datadatasets 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 datadatasets, sets and categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 setsdatasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. (Note: The datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets 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.) DataDatasets sets to be protected will be: SYS3.MIMGR. (DataDatasets sets that are altered by the product's STCs, this can be more specific.) The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS3) MIMGR.- UID(&ltsyspaudt>) R(A) W(A) A(A) E(A) MIMGR.- UID(&lttstcaudt>) R(A) W(A) A(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) W(A) A(A) E(A) MIMGR.- UID(&ltaudtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A)

Discussion

CA MIM Resource Sharing STC datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.omising the operating system or sensitive data.

V-224276 in V7R2

Check text

Refer to the following report produced by the ACF2 Data Collection and Datadataset Set and Resource Data Collection: - SENSITVE.RPT(ZMIM0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the Datadataset 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 ACF2 resources are defined with a default access of PREVENT. The ACF2 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 z/OS STIG Addendum. This table lists 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 datadataset set specified in the MIMPARMS DD statement of the started task procedures. The ACF2 resources as designated in the above table are defined with a default access of PREVENT. The ACF2 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: $KEY(prefix) TYPE(OPR) ACTIVATE UID(syspaudt) SERVICE(UPDATE) ALLOW - UID(*) PREVENT

Discussion

CA MIM Resource Sharing 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 systemsystems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.

V-224277 in V7R2

Check text

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Verify that the logonid(s) for the CA MIM Resource Sharing started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC NO-SMC

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 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. The following commands are provided as a sample for defining Started Task(s): SET LID insert MIMGR stc no-smc name('STC, CA MIM')

Discussion

CA MIM Resource Sharing requires a started task that will be restricted to certain resources, datasets, 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-224278 in V7R2