What changed in z/OS FDR for RACF STIG V7R2V7R2 changes

z/OS FDR for RACF 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 2

Updated in V7R2 (2)

V-224481CAT IFDR (Fast Dump Restore) security options are improperly specified.Check text, Fix text

Check text

a) The following steps are necessary for reviewing the FDR options: 1) Issue the following command on the command line at option 6 in TSO to bring up the FDR ISPF dialog: EXEC 'SYS2.FDR.Vxxxx.CLIST(ABRALLOC)' 2) Select '"I'" on the FDR primary panel for INSTALL. 3) Select '"4'" on the FDR installation options panel to select SETOPT. 4) Verify the FDR Program Library Data Set on this panel specifies the following: Example: 'SYS2A.FDR.Vxxxx.LOADLIB'. 5) Select '"1'" for SECURITY OPTIONS. 6) Review the setting for ALLCALL. Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZFDR0040) b) If ALLCALL is set to YES, there is no finding. c) If ALLCALL is set to NO, this is not a finding.

Fix text

The systems programmer will verify that the security option ALLCALL is set to YesYES. 1) Execute the FDR ISPF dialog by entering the following on the command line: EXEC 'SYS2.FDR.VXXXX.CLIST(ABRALLOC)' 2) Select 'I' on the FDR PRIMARY OPTIONS MENU for INSTALL. 3) Select '4' on the INSTALLATION OPTIONS MENU to select SETOPT - SET INSTALLATION OPTIONS IN THE FDR GLOBAL OPTIONS TABLE. 4) Verify the FDR program library data set on this panel is set to the current LOADLIB. Example: 'SYS2A.FDR.Vxxxx.LOADLIB'. 5) Select '1' to select SECURITY OPTIONS. 6) On the SET FDR GLOBAL SECURITY OPTIONS, review the ALLCALL setting, ensure it is set to YES.

V-224481 in V7R2

V-224482CAT IIFast Dump Restore (FDR) install data sets are not properly protected.Check text, Fix text

Check text

a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(FDRRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZFDR0000). b) Verify that access to the Fast Dump Restore (FDR) Install data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. ___ The RACF data set rules for the datasetsdata doessets not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged. c) If all of the above are untrue, there is no finding. d) If any of the above is true, this is a finding.

Fix text

The ISSO will ensure that updateWRITE and/or allocategreater access to Fast Dump Restore (FDR) install data sets is limited to systems programmers only, and all updateWRITE and/or allocategreater access is logged. Auditors should have READ access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE access for specific data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program ) active on the system. Data sets to be protected will be: SYS2.FDR SYS2A.FDR The following commands are provided as a sample for implementing datasetdata set controls: ad 'sys2.fdr.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: fdr') pe 'sys2.fdr.**' id(syspaudt) acc(a) pe 'sys2.fdr.**' id(dasdaudt dasbaudt audtaudt) acc(r) ad 'sys2a.fdr.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) - data('fdr Vendor Datasets') pe 'sys2a.fdr.**' id(syspaudt) acc(a) pe 'sys2a.fdr.**' id(dasdaudt dasbaudt audtaudt) acc(r) ad 'sys3.fdr.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Site Custom DS Profile: fdr') pe 'sys3.fdr.**' id(syspaudt) acc(a) pe 'sys3.fdr.**' id(dasdaudt dasbaudt audtaudt) acc(r) setr generic(dataset) refresh

V-224482 in V7R2

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.