V7R2 changes
z/OS Quest NC-Pass for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 5 checks updated. It has 5 checks, against 5 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 5 updated
Updated fields: Check text 5Fix text 2Discussion 2
Updated in V7R2 (5)
V-224523CAT IIQuest NC-Pass installation data sets will be properly protected.Check text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(NCPASRPT).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZNCP0000).
Verify that the accesses to the Quest NC-Pass 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.
V-224524CAT IIQuest NC-Pass STC data sets will be properly protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(NCPASSTC).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZNCP0001).
Verify that the accesses to the Quest NC-Pass STC 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 auditors.
___ The RACF data set rules for the data sets restricts UPDATE access to domain level security administrators.
___ 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 restricts WRITE and/or greater access to the Quest NC-Pass's STC(s) and/or batch user(s).
___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
Fix text
The ISSO will ensure that WRITE and/or greater access to Quest NC-Pass STC data sets is limited to systems programmers and/or Quest 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 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 updateWRITE and/or altergreater access for specific data sets, and once documented will work with the ISSO to ensure 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
V-224525CAT IIQuest NC-Pass will be used by Highly-Sensitive users.Check text, Fix text, Discussion
Check text
Refer to the following reports produced by the RACF Data Collection:
- RACFCMDS.RPT(LISTUSER).
- RACFCMDS.RPT(LISTGRP).
If the SECURID group is defined and all sensitive users are connected to the SECURID group, this is not a finding.
Note: Sensitive users include systems programming personnel, security personnel, and other staff (e.g., DASD management, operations, auditors, technical support, etc.) with access to sensitive resources (e.g., operator commands, ACP privileges, etc.) that can modify the operating system and system software, and review/modify the security environment.
Fix text
The ISSO will ensure that sensitive users are properly validated to Quest NC-Pass.
Note: Sensitive users include systems programming personnel, security personnel, and other staff (e.g., DASD management, operations, auditors, technical support, etc.) with access to sensitive resources (e.g., operator commands, ACP privileges, etc.) that can modify the operating system and system software, and review/modify the security environment.
Ensure SECURID is defined to RACF. Use the following RACF AddGroup command:
AG SECURID SUPGROUP(ADMIN) OWNER(ADMIN)
Ensure sensitive users that require NC-Pass validation is connected to the SECURID group. Use the following command:
CO userid GROUP(SECURID) OWNER(SECURID)
Discussion
DISA has directed that Quest NC-Pass extended authentication be implemented on all domains. All users with updateWRITE and/or altergreater access to sensitive system-level data sets and resources, or who possess special security privileges, are required to use NC-Pass for extended authentication. Typical personnel required to use NC-Pass include, but are not limited to, systems programming, security, operations, network/communications, storage management, and production control.
Improper enforcement of extended authentication through NC-Pass could potentially compromise the operating system, Access Control Program (ACP), and customer data.
V-224526CAT IIQuest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.Check text, Discussion
Check text
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED
Discussion
Quest NC-Pass requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
V-224527CAT IIQuest NC-Pass Started task will be properly defined to the STARTED resource class for RACF.Check text
Check text
Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZNCP0032). If the Quest NC-Pass started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.
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.