Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
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.
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)
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).
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)
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.
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
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
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