Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
a) Have the products systems programmer display the configuration/parameters control statements used in the current running product to define or enable security. b) Verify the following specifications: 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
The product systems programmer will verify that any configuration / parameters that are required to control the security of the product are properly configured and syntactically correct. See 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 be given to the appropriate personnel.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TDMFRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTDM0000) Verify that the accesses to the Transparent Data Migration Facility (TDMF) installation 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 restricts READ access to all authorized users. ___ The RACF data set rules for the data sets restricts 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 is logged. ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
The ISSO will ensure that WRITE and/or greater access to Transparent Data Migration Facility (TDMF) installation data 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 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 see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS2.TDMF. SYS3.TDMF. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.TDMF.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Transparent Data Migration Facility (TDMF) Install DS') pe 'SYS2.TDMF.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.TDMF.**' id(<audtaudt>) acc(r) ad 'SYS3.TDMF.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Transparent Data Migration Facility (TDMF) Install DS') pe 'SYS3.TDMF.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.TDMF.**' id(<audtaudt>) acc(r) setr generic(dataset) refresh