V7R2 changes
z/OS Quest NC-Pass for TSS STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 6 checks updated. It has 6 checks, against 6 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 6 updated
Updated fields: Check text 6Fix text 5Discussion 3Title 1
Updated in V7R2 (6)
V-225592CAT IIQuest NC-Pass installation 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(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 TSS data set rules for the data sets restrictsrestrict READ access to all authorized users.
The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to systems programming personnel.
The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
Fix text
The ISSO will ensure that WRITE and/or greater access to Quest NC-Pass installation data sets is limited to systemsystems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users.
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 ensure they are properly restricted to the Access Control Program (ACP) active on the system.
Data sets to be protected will be:
SYS2.NCPASS.
SYS3.NCPASS. (dataData sets that are not altered by product STCs,; this can be more specific)
The following commands are provided as a sample for implementing data set controls:
TSS PERMIT(<syspaudt>) DSN(SYS2.NCPASS.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS2.NCPASS.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<tstcaudt>) DSN(SYS2.NCPASS.) ACCESS(R)
TSS PERMIT(<tstcaudt>) DSN(SYS2.NCPASS.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<audtaudt>) DSN(SYS2.NCPASS.) ACCESS(R)
TSS PERMIT(ALL) DSN(SYS2.NCPASS.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.) ACCESS(R)
TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.) ACCESS(ALL) ACTION(AUDIT)
TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.) ACCESS(R)
TSS PERMIT(*) DSN(SYS3.NCPASS.) ACCESS(R)
V-225593CAT 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 TSS data set rules for the data sets restrictsrestrict READ access to auditors.
___ The TSS data set rules for the data sets restrictsrestrict UPDATE access to domain level security administrators.
___ The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to systems programming personnel.
___ The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to the Quest NC-Pass's STC(s) and/or batch user(s).
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 (ACP) 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:
TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL)
TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL)
TSS PERMIT(NCASS STCs) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL)
TSS PERMIT(<secaaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(U)
TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(R)
TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL)
TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL)
TSS PERMIT(NCASS STCs) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL)
TSS PERMIT(<secaaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(U)
TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(R)
V-225594CAT IIQuest NC-Pass will be used by highly sensitive users.Check text, Discussion
Check text
Refer to the following reports produced by the TSS Data Collection and Data Set and Resource Data Collection:
- TSSCMDS.RPT(@ACIDS).
- TSSCMDS.RPT(@ALL).
- SENSITVE.RPT(WHOHABS).
If all sensitive users requiring NC-Pass validation has the NCPASS Facility and permitted to the SECURID resource in the ABSTRACT resource class, 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.
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-225595CAT IIQuest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(@ACIDS).
VerifyReview that the ACID(s) for the Quest NC-Pass startedSTC/Batch taskACID(s) is (are) properly defined. If the following attributes are defined, this is not a finding.
FACILITY(STC, BATCH)
PASSWORD(xxxxxxxx,0)
SOURCE(INTRDR)
NOSUSPEND
MASTFAC(NCPASS)
Fix text
The IAOISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the Systemsystem ACP.
If the product requires a Started Task, verify that it is properly defined to the Systemsystem ACP with the proper attributes.
Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.
The following commands are provided as a sample for defining Started Task(s):
TSS CREATE(NCPASS) TYPE(USER) -
NAME('STC, Quest NC-Pass') DEPT(xxxx) -
FAC(STC,BATCH) PASS(xxxxxxxx,0) -
SOURCE(INTRDR) NOSUSPEND
MASTFAC(NCPASS)
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-225596CAT IIQuest NC-Pass Started task will be properly defined to the Started Task Table ACID for Top Secret.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(#STC).
Automated Analysis
Refer to the following report produced by the TSS Data Collection:
- PDI(ZNCP0032).
If the Quest NC-Pass started task(s) is (are) defined in the TSS STC record, this is not a finding.
Fix text
The IAOISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the Systemsystem ACP.
A unique ACID must be assigned for the CA 1 Tape Management started task(s) thruthrough a corresponding STC table entry.
The following commands are provided as a sample for defining Started Task(s):
TSS ADD(STC) PROCNAME(NCPASS) ACID(NCPASS)
Discussion
Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.
V-225597CAT IIQuest NC-Pass will be properly defined to the Facility Matrix Table.Title, Check text, Fix text
Title
Quest NC-Pass will be properly defined to the Facility Matrix Table.
Check text
Refer to the following reportreports produced by the TSS Data Collection:
- TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values.
- TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup.
If the Quest NC-Pass Facility Matrix table is defined as stated below, this is not a finding.
FACILITY DISPLAY FOR NCPASS
INITPGM=NCS ID=14 TYPE=099
ATTRIBUTES=IN-USE,ACTIVE,SHRPRF,NOASUBM,NOABEND,MULTIUSER,NOXDEF
ATTRIBUTES=LUMSG,STMSG,SIGN(M),INSTDATA,NORNDPW,AUTHINIT
ATTRIBUTES=NOPROMPT,NOAUDIT,RES,WARNPW,NOTSOC,LCFTRANS
ATTRIBUTES=MSGLC,NOTRACE,NOEODINIT,IJU,NODORMPW,NONPWR
ATTRIBUTES=LUUPD
MODE=FAIL DOWN=GLOBAL LOGGING=INIT,SMF,MSG,SEC9
UIDACID=8 LOCKTIME=000 DEFACID=*NONE* KEY=8
MAXUSER=03000 PRFT=003
Fix text
The IAOISSO working with the systems programmer will ensure the Facility Matrix Table for Quest NC-Pass is proper defined using the following example:
*****NCPASS
FAC(USERxx=NAME=NCPASS,PGM=NCS,ID=nn,ACTIVE,NOASUBM)
FAC(NCPASS=LUMSG,STMSG,NORNDPW,WARNPW,MODE=FAIL)
FAC(NCPASS=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)
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.