z/OS Quest NC-Pass for RACF STIG Version Comparison

There are 1 differences between versions v6 r2 (Jan. 20, 2015) (the "left" version) and v6 r3 (Nov. 23, 2022) (the "right" version).

Check ZNCPR001 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

Quest NC-Pass STC data sets will be properly protected.

Check Content

Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(NCPASSTC) Automated SENSITVE.RPT(NCPASSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNCP0001) Verify Collection: - PDI(ZNCP0001) Verify that the accesses to the Quest NC-Pass STC data sets are properly restricted. ___ The restricted. ___ The RACF data set rules for the data sets restricts READ access to auditors. ___ The auditors. ___ The RACF data set rules for the data sets restricts UPDATE access to domain level security administrators. ___ The administrators. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The personnel. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to the Quest NC-Pass’s NC-Pass's STC(s) and/or batch user(s). ___ The user(s). ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Discussion

Quest NC-Pass STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

Fix

The IAO ISSO will ensure that WRITE and/or greater access to Quest NC-Pass STC data sets is limited to System systems Programmers programmers and/or Quest NC-Pass’s NC-Pass's STC(s) and/or batch user(s) only. UPDATE access can be given to domain level security administrators. READ access can be given to auditors. The installing Systems systems Programmer programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO ISSO to ensure see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.NCPASS.*.PASSCAF SYS3.NCPASS.*.PASSVSDD The following commands are provided as a sample for implementing data set controls: ad 'SYS3.NCPASS.*.PASSCAF.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: Quest NC-Pass') ad 'SYS3.NCPASS.*.PASSVSDD.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: Quest NC-Pass') pe ' SYS3.NCPASS.*.PASSCAF.**' id(<syspaudt> <tstcaudt> NCPASS STCs) acc(a) pe ' SYS3.NCPASS.*.PASSCAF.**' id(<secaaudt>) acc(u) pe ' SYS3.NCPASS.*.PASSCAF.**' id(<audtaudt>) acc(r) pe ' SYS3.NCPASS.*.PASSVSDD.**' id(<syspaudt> <tstcaudt> NCPASS STCs) acc(a) pe ' SYS3.NCPASS.*.PASSVSDD.**' id(<secaaudt>) acc(u) pe ' SYS3.NCPASS.*.PASSVSDD.**' id(<audtaudt>) acc(r) setr generic(dataset) refresh