← Back to z/OS Quest NC-Pass for RACF Security Technical Implementation Guide

V-224524

CAT II (Medium)

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

Rule ID

SV-224524r1145269_rule

STIG

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

Version

V7R2

CCIs

CCI-001499

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.

Check Content

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 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 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