Fast Dump Restore (FDR) install data sets are not properly protected.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224482 | SRG-OS-000080 | ZFDRR000 | SV-224482r1145237_rule | 2025-09-27 | 7 |
| Description |
|---|
| Fast Dump Restore (FDR) install have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data. |
| ℹ️ Check |
|---|
| 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). 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 restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access will be logged. |
| ✔️ Fix |
|---|
| The ISSO will ensure that WRITE and/or greater access to Fast Dump Restore (FDR) install data sets is limited to systems programmers only, and all WRITE and/or greater 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 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 UPDATE 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 data 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 |