Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS CA MICS for ACF2 Security Technical Implementation Guide

V7R2 · · · Released 01 Oct 2025 · 2 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Digest of Updates vs. V7R1 · 02 Apr 2025 ✎ 2

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 2

  • V-224270 Medium descriptioncheckfix CA MICS Resource Management installation datasets must be properly protected.
  • V-224271 Medium descriptioncheckfix CA MICS Resource Management User datasets must be properly protected.
Sort by
b
CA MICS Resource Management installation datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224270 - SV-224270r1141561_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMICA000
Vuln IDs
  • V-224270
  • V-16932
Rule IDs
  • SV-224270r1141561_rule
  • SV-49769
CA MICS Resource Management 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-25943r1141559_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MICSRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMIC0000). Verify that the accesses to the CA MICS Resource Management 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 (e.g., auditors, security administrators, and MICS end 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 MICS administrators. The ACF2 dataset access authorizations specify that all (i.e., failures and successes) WRITE and/or greater accesses are logged.

Fix: F-25931r1141560_fix

The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management installation datasets 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 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.MICS The following commands are provided as a sample for implementing dataset 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)

b
CA MICS Resource Management User datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224271 - SV-224271r1141564_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMICA002
Vuln IDs
  • V-224271
  • V-21592
Rule IDs
  • SV-224271r1141564_rule
  • SV-50080
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 datasets could result in unauthorized access to sensitive data.
Checks: C-25944r1141562_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(MICSUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZMIC0002). Verify that the accesses to the CA MICS Resource Management User 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 (e.g., auditors, security administrators, and MICS end 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 SMF Batch user(s) and MICS Administrators.

Fix: F-25932r1141563_fix

The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management User datasets 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 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 (additional datasets may be required): SYS2.MICS.DATA The following commands are provided as a sample for implementing dataset 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)