z/OS TDMF for ACF2 Security Technical Implementation Guide - V7R2

  • Version/Release: V7R2
  • Published: 2025-09-26
  • Released: 2025-10-01
  • 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
Transparent Data Migration Facility (TDMF) configuration/parameter/option values are not specified properly.
CM-7 - Medium - CCI-000381 - V-224347 - SV-224347r1144122_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
ZTDM0040
Vuln IDs
  • V-224347
  • V-18014
Rule IDs
  • SV-224347r1144122_rule
  • SV-24802
Transparent Data Migration Facility (TDMF) configuration/parameter/option settings control the security and operational characteristics of product. If these setting values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of system and customer data.
Checks: C-26024r1144121_chk

Have the product's systems programmer display the configuration/parameters control statements used in the current running product to define or enable security. If the following keywords specify the values in the Transparent Data Migration Facility (TDMF) security parameter member, this is not a finding. Parameter Options: VOLUME SECURITY = YES CHECK TARGET EMPTY = YES Session Options: Volume Security is not available. CHECKTarget|CHKTarget

Fix: F-26012r1144122_fix

The product's systems programmer will verify that any configuration/parameters that are required to control the security of the product are properly configured and syntactically correct. Refer to the required parameters below: Parameter Options: VOLUME SECURITY = YES CHECK TARGET EMPTY = YES Session Options: Volume Security is not available. CHECKTarget|CHKTarget Note: The ISSO will ensure that volume resource protection is defined to the ACP and access to volumes is given to the appropriate personnel.

b
Transparent Data Migration Facility (TDMF) installation datasets will be not properly protected.
CM-5 - Medium - CCI-001499 - V-224348 - SV-224348r1141657_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
ZTDMA000
Vuln IDs
  • V-224348
  • V-16932
Rule IDs
  • SV-224348r1141657_rule
  • SV-24781
Transparent Data Migration Facility (TDMF) 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-26025r1141655_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(TDMFRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZTDM0000). Verify that the accesses to the Transparent Data Migration Facility (TDMF) installation datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to auditors. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix: F-26013r1141656_fix

The ISSO will ensure that The ISSO will ensure that WRITE and/or greater access to Transparent Data Migration Facility (TDMF) installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors. 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 that they are properly restricted to the ACP (Access Control Program) active on the system. Datasets to be protected will be: SYS2.TDMF SYS3.TDMF The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) TDMF.- UID(<syspaudt>) R(A) W(L) A(L) E(A) TDMF.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) TDMF.- UID(<audtaudt>) R(A) E(A) $KEY(SYS3) TDMF.- UID(<syspaudt>) R(A) W(L) A(L) E(A) TDMF.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) TDMF.- UID(<audtaudt>) R(A) E(A)