V7R2 changes
z/OS CA MIM for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 6 checks updated. It has 6 checks, against 6 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 6 updated
Updated fields: Check text 6Fix text 2Discussion 2
Updated in V7R2 (6)
V-224438CAT IICA MIM Resource Sharing external security options must be specified properly.Check text, Discussion
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).
EnsureVerify 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-224439CAT IICA MIM Resource Sharing installation data sets will be properly protected.Check text
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 RACF data set access authorizations restrict READ access to all authorized users.
The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel.
The RACF data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged.
The RACF data set access authorizations specify UACC(NONE) and NOWARNING.
V-224440CAT IICA MIM Resource Sharing STC data sets will be properly protected.Check text, Fix text
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 RACF data set access authorizations restrict READ access to auditors and authorized users.
___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel.
___ The RACF data set access authorizations restrict WRITE and/or greater access to the CA MIM Resource Sharing's STC(s) and/or batch user(s).
___ The RACF data set access authorizations for the data sets specify UACC(NONE) and NOWARNING.
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) 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:
ad 'SYS3.MIMGR.**' uacc(none) owner(sys3) -
audit(failures(read)) -
data('Vendor DS Profile: CA MIM Resource Sharing')
pe 'SYS3.MIMGR.**' id(<syspaudt> <tstcaudt> CA MIM STCs) acc(a)
pe 'SYS3.MIMGR.**' id(<audtaudt> authorized users) acc(r)
setr generic(dataset) refresh
V-224441CAT IICA MIM Resource Sharing resources will be properly defined and protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(ZMIM0020).
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 RACF resources are defined with a default access of NONE.
The RACF resource access authorizations restrict access to the appropriate personnel.
The RACF resource access authorizations are defined with UACC(NONE) and NOWARNING.
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 listlists 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 RACF resources as designated in the above table are defined with a default access of NONE.
The RACF resource access authorizations restrict access to the appropriate personnel as designated in the above table.
The RACF resource rules for the resources designated in the above table specify UACC(NONE) and NOWARNING.
The following commands are provided as a sample for implementing resource controls:
RDEFINE OPERCMDS prefix.** UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ))
RDEFINE OPERCMDES prefix.ACTIVATE UACC(NONE) OWNER(ADMIN) AUDIT(FAILURE(READ))
PERMIT prefix.ACTIVATE CLASS(OPERCMDS) ACCESS(UPDATE) ID(syspaudt)
V-224442CAT IICA MIM Resource Sharing Started Task name will be properly identified and/or defined to the system ACP.Check text, Discussion
Check text
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(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. PROTECTED
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-224443CAT IICA MIM Resource Sharing Started task will be properly defined to the STARTED resource class for RACF.Check text
Check text
Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZMIM0032). If the CA MIM Resource Sharing started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.