Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

z/OS CA MIM for ACF2 Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-27
  • Released: 2025-10-01
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
CA MIM Resource Sharing external security options must be specified properly.
CM-7 - Medium - CCI-000381 - V-224274 - SV-224274r1141567_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
ZMIM0040
Vuln IDs
  • V-224274
  • V-18014
Rule IDs
  • SV-224274r1141567_rule
  • SV-46150
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.
Checks: C-25947r1141565_chk

Refer to the contents of MIMINIT member of the dataset(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). Verify the following CA MIM Resource Sharing parameter(s) is (are) specified in the MIMINIT member of the dataset(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: F-25935r1141566_fix

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 dataset(s) specified in the MIMPARMS DD statement of the started task procedures. Parameter Value SAFCMDAUTH ON

b
CA MIM Resource Sharing installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224275 - SV-224275r1141570_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZMIMA000
Vuln IDs
  • V-224275
  • V-16932
Rule IDs
  • SV-224275r1141570_rule
  • SV-46158
CA MIM Resource Sharing installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-25948r1141568_chk

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

Fix: F-25936r1141569_fix

The ISSO will ensure that WRITE and/or greater access to CA MIM Resource Sharing installation datasets 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 datasets, 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS2.MIMGR SYS3.MIMGR (Datasets that are not altered by product STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) MIMGR.- UID(<syspaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(<audtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID(<audtaudt>) R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A) $KEY(SYS3) MIMGR.- UID(<syspaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) MIMGR.- UID(<audtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A)

b
CA MIM Resource Sharing STC datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224276 - SV-224276r1141573_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZMIMA001
Vuln IDs
  • V-224276
  • V-17067
Rule IDs
  • SV-224276r1141573_rule
  • SV-46163
CA MIM Resource Sharing STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets 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.
Checks: C-25949r1141571_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MIMSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMIM0001). Verify that the accesses to the CA MIM Resource Sharing STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors and authorized users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset access authorizations restrict WRITE and/or greater access to the CA MIM Resource Sharing's STC(s) and/or batch user(s).

Fix: F-25937r1141572_fix

The ISSO will ensure that WRITE and/or greater access to CA MIM Resource Sharing STC datasets is limited to systems programmers and/or CA MIM Resource Sharing's STC(s) and/or batch user(s) only. READ access can be given to auditors and authorized users. The installing systems programmer will identify and document the product datasets, 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS3.MIMGR (Datasets that are altered by the product's STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) MIMGR.- UID(<syspaudt>) R(A) W(A) A(A) E(A) MIMGR.- UID(<tstcaudt>) R(A) W(A) A(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) W(A) A(A) E(A) MIMGR.- UID(<audtaudt>) R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A)

b
CA MIM Resource Sharing resources will be properly defined and protected.
AC-3 - Medium - CCI-000213 - V-224277 - SV-224277r1141576_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZMIMA020
Vuln IDs
  • V-224277
  • V-17947
Rule IDs
  • SV-224277r1141576_rule
  • SV-46207
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 systems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.
Checks: C-25950r1141574_chk

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection: - SENSITVE.RPT(ZMIM0020). - ACF2CMDS.RPT(RESOURCE) - Alternate report. Automated Analysis Refer to the following report produced by the dataset 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: F-25938r1141575_fix

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 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 dataset 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

b
CA MIM Resource Sharing Started Task name will be properly identified and/or defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224278 - SV-224278r1144187_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZMIMA030
Vuln IDs
  • V-224278
  • V-17452
Rule IDs
  • SV-224278r1144187_rule
  • SV-46210
CA MIM Resource Sharing requires a started task that will be restricted to certain resources, datasets, 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.
Checks: C-25951r1141577_chk

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: F-25939r1141578_fix

The ISSO 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')