V7R2 changes
z/OS CA MICS for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 2 checks updated. It has 2 checks, against 2 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 2 updated
Updated fields: Check text 2Fix text 2Title 2Discussion 2
Updated in V7R2 (2)
V-224270CAT IICA MICS Resource Management installation datasets must be properly protected.Title, Check text, Fix text, Discussion
Title
CA MICS Resource Management installation data sets must be properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(MICSRPT).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZMIC0000).
Verify that the accesses to the CA MICS Resource Management 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 (e.g., auditors, security administrators, and MICS end 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 MICS administrators.
The ACF2 datadataset set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater accesses are logged.
Fix text
The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management installation datadatasets sets is limited to systems programmers and MICS administrators. READ access can be given to all authorized users (e.g., auditors, security administrators, and MICS end 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.MICS.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS2)
MICS.- UID(syspaudt) R(A) W(L) A(L) E(A)
MICS.- UID(tstcaudt) R(A) W(L) A(L) E(A)
MICS.- UID(micsadm) R(A) W(L) A(L) E(A)
MICS.- UID(audtaudt) R(A) E(A)
MICS.- UID(micsuser) R(A) E(A)
MICS.- UID(secaaudt) R(A) E(A)
Discussion
CA MICS Resource Management 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-224271CAT IICA MICS Resource Management User datasets must be properly protected.Title, Check text, Fix text, Discussion
Title
CA MICS Resource Management User data sets must be properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(MICSUSER).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZMIC0002).
Verify that the accesses to the CA MICS Resource Management User 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 (e.g., auditors, security administrators, and MICS end 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 SMF Batch user(s) and MICS Administrators.
Fix text
The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management User datadatasets sets is limited to SMF Batch user(s), MICS Administrators, and systems programming personnel. READ access can be given to all authorized users (e.g., auditors, security administrators, and MICS end 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 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 (additional datadatasets sets may be required):
SYS2.MICS.DATA.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS2)
MICS.DATA.- UID(syspaudt) R(A) W(A) A(A) E(A)
MICS.DATA.- UID(tstcaudt) R(A) W(A) A(A) E(A)
MICS.DATA.- UID(micsadm) R(A) W(A) A(A) E(A)
MICS.DATA.- UID(smfbaudt) R(A) W(A) A(A) E(A)
MICS.DATA.- UID(audtaudt) R(A) E(A)
MICS.DATA.- UID(micsuser) R(A) E(A)
MICS.DATA.- UID(secaaudt) R(A) E(A)
Discussion
CA MICS Resource Management User datasets contain sensitive data obtained through the MICS data collection process. Failure to properly identify and restrict access to these datadatasets sets could result in unauthorized access to sensitive data.
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.