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

z/OS CA MICS for RACF Security Technical Implementation Guide

V7R1 · · · Released 02 Apr 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. V6R5 · 23 Nov 2022 ✎ 2

Comparison against the immediately-prior release (V6R5). 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-224436 Medium descriptioncheckfix CA MICS Resource Management installation data sets must be properly protected.
  • V-224437 Medium checkfix CA MICS Resource Management User data sets must be properly protected.
Sort by
b
CA MICS Resource Management installation data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224436 - SV-224436r1070149_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMICR000
Vuln IDs
  • V-224436
  • V-16932
Rule IDs
  • SV-224436r1070149_rule
  • SV-49858
CA MICS Resource Management 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-26113r1070147_chk

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

Fix: F-26101r1070148_fix

The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management installation data 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 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 Access Control Program (ACP) 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.MICS. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.MICS.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('CA-MICS Resource Management Install DS') pe 'SYS2.MICS.**' id(syspaudt tstcaudt micsadm) acc(a) pe 'SYS2.MICS.**' id(audtaudt micsuser secaaudt) acc(r) setr generic(dataset) refresh

b
CA MICS Resource Management User data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224437 - SV-224437r1070152_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZMICR002
Vuln IDs
  • V-224437
  • V-21592
Rule IDs
  • SV-224437r1070152_rule
  • SV-50081
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 data sets could result in unauthorized access to sensitive data.
Checks: C-26114r1070150_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MICSUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMIC0002) Verify that the accesses to the CA MICS Resource Management User 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 (e.g., auditors, security administrators, and MICS end 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 SMF Batch user(s) and MICS Administrators. The RACF data set access authorizations for the data sets specify UACC(NONE) and NOWARNING.

Fix: F-26102r1070151_fix

The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management User data 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 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 Access Control Program (ACP) 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 (additional data sets may be required): SYS2.MICS.DATA. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.MICS.DATA.**' uacc(none) owner(sys2) - audit(failures(read)) - data('Vendor DS Profile: Product') pe 'SYS2.MICS.DATA.**' id(syspaudt tstcaudt micsadm smfbaudt) acc(a) pe 'SYS2.MICS.DATA.**' id(audtaudt micsuser secaaudt) acc(r) setr generic(dataset) refresh