V7R2 changes
z/OS TDMF for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 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 1Discussion 1
Updated in V7R2 (2)
V-224347CAT IITransparent Data Migration Facility (TDMF) configuration/parameter/option values are not specified properly.Check text, Fix text
Check text
a) Have the theproduct's products systems programmer display the configuration/parameters control statements used in the current runingrunning product to define or enable security.
b)If Verify the following specifications: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
c) If (b) above is true, there is no finding.
d) If (b) above is untrue, this is a finding
Fix text
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.
SeeRefer to the required parameters below:
Parameter Options:
VOLUME SECURITY = YES
CHECK TARGET EMPTY = YES
Session Options:
Volume Security is not available.
CHECKTarget|CHKTarget
NOTENote: The ISSO will ensure that volume resource protection is defined to the ACP and access to volumes beis given to the appropiateappropriate personnel.
V-224348CAT IITransparent Data Migration Facility (TDMF) installation datasets will be not properly protected.Title, Check text, Fix text, Discussion
Title
Transparent Data Migration Facility (TDMF) installation data sets will be not properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(TDMFRPT).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZTDM0000).
Verify that the accesses to the Transparent Data Migration Facility (TDMF) installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restricts READ access to auditors.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restricts WRITE and/or greater access to systems programming personnel.
___ The ACF2 datadataset set rules for the datadatasets sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
Fix text
The ISSO will ensure that The ISSO will ensure that WRITE and/or greater access to Transparent Data Migration Facility (TDMF) installation datadatasets sets 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 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 seeensure that they are properly restricted to the ACP (Access Control Program) active on the system.
DataDatasets sets to be protected will be:
SYS2.TDMF.
SYS3.TDMF.
The following commands are provided as a sample for implementing datadataset set 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)
Discussion
Transparent Data Migration Facility (TDMF) 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.
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.