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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-16932	ZMIMA000	SV-46158r1_rule	DCSL-1 ECAR-1 ECAR-2 ECCD-1 ECCD-2	Medium

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

STIG	Date
z/OS CA MIM for ACF2 STIG	2015-01-15

Details

Check Text ( C-11663r3_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 ACF2 data set access authorizations restrict READ access to all authorized users. ___ The ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

Check Text ( C-11663r3_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 ACF2 data set access authorizations restrict READ access to all authorized users.

___ The ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel.

___ The ACF2 data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

Fix Text (F-407r3_fix)
The IAO will ensure that WRITE and/or greater access to CA MIM Resource Sharing installation data sets is limited to System 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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the IAO to see that 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: $KEY(SYS2) MIMGR.- UID() R(A) W(L) A(L) E(A) MIMGR.- UID() R(A) W(L) A(L) E(A) MIMGR.- UID() R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID() R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A) $KEY(SYS3) MIMGR.- UID() R(A) W(L) A(L) E(A) MIMGR.- UID() R(A) W(L) A(L) E(A) MIMGR.- UID() R(A) E(A) MIMGR.- UID(authorized users) R(A) E(A) MIMGR.- UID(CA MIM STCs) R(A) E(A)

Fix Text (F-407r3_fix)

The IAO will ensure that WRITE and/or greater access to CA MIM Resource Sharing installation data sets is limited to System 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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the IAO to see that 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:

$KEY(SYS2)
MIMGR.- UID() R(A) W(L) A(L) E(A)
MIMGR.- UID() R(A) W(L) A(L) E(A)
MIMGR.- UID() R(A) E(A)
MIMGR.- UID(authorized users) R(A) E(A)
MIMGR.- UID() R(A) E(A)
MIMGR.- UID(CA MIM STCs) R(A) E(A)

$KEY(SYS3)
MIMGR.- UID() R(A) W(L) A(L) E(A)
MIMGR.- UID() R(A) W(L) A(L) E(A)
MIMGR.- UID() R(A) E(A)
MIMGR.- UID(authorized users) R(A) E(A)
MIMGR.- UID(CA MIM STCs) R(A) E(A)