Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS Quest NC-Pass for ACF2 Security Technical Implementation Guide

V7R2 · · · Released 01 Oct 2025 · 4 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V7R1 · 02 Apr 2025 ✎ 4

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 4

  • V-224332 Medium descriptioncheckfix Quest NC-Pass installation datasets will be properly protected.
  • V-224333 Medium descriptioncheckfix Quest NC-Pass STC datasets will be properly protected.
  • V-224334 Medium descriptioncheck Quest NC-Pass will be used by Highly-Sensitive users.
  • V-224335 Medium descriptioncheckfix Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.
Sort by
b
Quest NC-Pass installation datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224332 - SV-224332r1141597_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZNCPA000
Vuln IDs
  • V-224332
  • V-16932
Rule IDs
  • SV-224332r1141597_rule
  • SV-40863
Quest NC-Pass installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
Checks: C-26009r1141595_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(NCPASRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZNCP0000). Verify that the accesses to the Quest NC-Pass installation datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to all authorized users. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.

Fix: F-25997r1141596_fix

The ISSO will ensure that WRITE and/or greater access to Quest NC-Pass installation datasets is limited to systems 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Datasets to be protected will be: SYS2.NCPASS SYS3.NCPASS (Datasets that are not altered by product STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) NCPASS.- UID(<syspaudt>) R(A) W(L) A(L) E(A) NCPASS.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) NCPASS.- UID(<audtaudt>) R(A) E(A) NCPASS.- UID(*) R(A) E(A) $KEY(SYS3) NCPASS.- UID(<syspaudt>) R(A) W(L) A(L) E(A) NCPASS.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) NCPASS.- UID(<audtaudt>) R(A) E(A) NCPASS.- UID(*) R(A) E(A)

b
Quest NC-Pass STC datasets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224333 - SV-224333r1141600_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZNCPA001
Vuln IDs
  • V-224333
  • V-17067
Rule IDs
  • SV-224333r1141600_rule
  • SV-40866
Quest NC-Pass STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26010r1141598_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(NCPASSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZNCP0001). Verify that the accesses to the Quest NC-Pass STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to auditors. The ACF2 dataset rules for the datasets restrict WRITE access to domain level security administrators. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the Quest NC-Pass's STC(s) and/or batch user(s).

Fix: F-25998r1141599_fix

The ISSO will ensure that WRITE and/or greater access to Quest NC-Pass STC datasets 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 datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Datasets to be protected will be: SYS3.NCPASS.*.PASSCAF SYS3.NCPASS.*.PASSVSDD The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) NCPASS.-.PASSCAF.- UID(<syspaudt>) R(A) W(A) A(A) E(A) NCPASS.-.PASSCAF.- UID(<tstcaudt>) R(A) W(A) A(A) E(A) NCPASS.-.PASSCAF.- UID(NCPASS STCs) R(A) W(A) A(A) E(A) NCPASS.-.PASSCAF.- UID(secaaudt) R(A) W(A) E(A) NCPASS.-.PASSCAF.- UID(<audtaudt>) R(A) E(A) NCPASS.-.PASSVSDD.- UID(<syspaudt>) R(A) W(A) A(A) E(A) NCPASS.-.PASSVSDD.- UID(<tstcaudt>) R(A) W(A) A(A) E(A) NCPASS.-.PASSVSDD.- UID(NCPASS STCs) R(A) W(A) E(A) NCPASS.-.PASSVSDD.- UID(<secaaudt>) R(A) W(A) E(A) NCPASS.-.PASSVSDD.- UID(<audtaudt>) R(A) E(A)

b
Quest NC-Pass will be used by Highly-Sensitive users.
AC-3 - Medium - CCI-000213 - V-224334 - SV-224334r1141602_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZNCPA020
Vuln IDs
  • V-224334
  • V-17947
Rule IDs
  • SV-224334r1141602_rule
  • SV-40869
DISA has directed that Quest NC-Pass extended authentication be implemented on all domains. All users with update and alter access to sensitive system-level datasets 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.
Checks: C-26011r1141601_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(TSOUSERS). If all sensitive users requiring NC-Pass validation has the AUTHSUP1 attribute, 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: F-25999r1070010_fix

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. The following attributes must be set for logonids requiring NC-Pass validation: SET LID CHANGE logonid AUTHSUP1

b
Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224335 - SV-224335r1144117_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZNCPA030
Vuln IDs
  • V-224335
  • V-17452
Rule IDs
  • SV-224335r1144117_rule
  • SV-40872
Quest NC-Pass requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.
Checks: C-26012r1141603_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Verify that the logonid(s) for the Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC MUSASS NO-SMC MUSUPDT

Fix: F-26000r1141604_fix

The ISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System 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): SET LID insert NCPASS stc name('STC, Quest NC-Pass') musass no-smc musupdt