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

z/OS CA MIM for RACF Security Technical Implementation Guide

  • Version/Release: V6R4
  • Published: 2022-10-07
  • Released: 2022-11-23
  • 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.
AC-4 - Medium - CCI-000035 - V-224438 - SV-224438r519631_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZMIM0040
Vuln IDs
  • V-224438
  • V-18014
Rule IDs
  • SV-224438r519631_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-26115r519629_chk

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

Fix: F-26103r519630_fix

The systems programmer/IAO 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 set(s) specified in the MIMPARMS DD statement of the started task procedures. Parameter Value SAFCMDAUTH ON

b
CA MIM Resource Sharing installation data sets will be properly protected.
AC-3 - Medium - CCI-000213 - V-224439 - SV-224439r868482_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
ZMIMR000
Vuln IDs
  • V-224439
  • V-16932
Rule IDs
  • SV-224439r868482_rule
  • SV-46159
CA MIM Resource Sharing installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26116r868477_chk

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.

Fix: F-26104r868479_fix

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 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: SYS2.MIMGR. SYS3.MIMGR. (Data sets that are not altered by product STCs, can be more specific.) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.MIMGR.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('CA MIM Resource Sharing Install DS') pe 'SYS2.MIMGR.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.MIMGR.**' id(<audtaudt> authorized users) acc(r) pe 'SYS2.MIMGR.**' id(CA MIM STCs) ad 'SYS3.MIMGR.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('CA MIM Resource Sharing Install DS') pe 'SYS3.MIMGR.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.MIMGR.**' id(<audtaudt> authorized users) acc(r) pe 'SYS3.MIMGR.**' id(CA MIM STCs) setr generic(dataset) refresh

b
CA MIM Resource Sharing STC data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224440 - SV-224440r868486_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZMIMR001
Vuln IDs
  • V-224440
  • V-17067
Rule IDs
  • SV-224440r868486_rule
  • SV-46166
CA MIM Resource Sharing STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26117r868483_chk

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: F-26105r868484_fix

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. Read 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

b
CA MIM Resource Sharing resources will be properly defined and protected.
AC-4 - Medium - CCI-000035 - V-224441 - SV-224441r868491_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000035
Version
ZMIMR020
Vuln IDs
  • V-224441
  • V-17947
Rule IDs
  • SV-224441r868491_rule
  • SV-46208
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 non systems personnel with read only authority.
Checks: C-26118r868489_chk

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: F-26106r868490_fix

The ISSO will work with the systems programmer to verify that the following are properly specified in the 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 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)

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-224442 - SV-224442r868497_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZMIMR030
Vuln IDs
  • V-224442
  • V-17452
Rule IDs
  • SV-224442r868497_rule
  • SV-46211
CA MIM Resource Sharing requires a started task that will be restricted to certain resources, datasets and other system functions. By 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.
Checks: C-26119r868492_chk

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

Fix: F-26107r868495_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): au MIMGR name('STC, CA MIM') owner(stc) dfltgrp(stc) nopass - data('CA MIM')

b
CA MIM Resource Sharing Started task will be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-224443 - SV-224443r868502_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
ZMIMR032
Vuln IDs
  • V-224443
  • V-17454
Rule IDs
  • SV-224443r868502_rule
  • SV-46213
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.
Checks: C-26120r868498_chk

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.

Fix: F-26108r868499_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. A unique userid must be assigned for the CA MIM Resource Sharing started task(s) thru a corresponding STARTED class entry. The following commands are provided as a sample for defining Started Task(s): rdef started MIMGR.** uacc(none) owner(admin) audit(all(read)) - stdata(user(MIMGR) group(stc)) setr racl(started) ref