STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS Quest NC-Pass for ACF2 Security Technical Implementation Guide

V-224333

CAT II (Medium)

Quest NC-Pass STC datasets will be properly protected.

Rule ID

SV-224333r1141600_rule

STIG

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

Version

V7R2

CCIs

CCI-001499

Discussion

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.

Check Content

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 Text

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)