| V-224332 | medium | Quest NC-Pass installation datasets will be properly protected. | 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. |
| V-224333 | medium | Quest NC-Pass STC datasets will be properly protected. | 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. |
| V-224334 | medium | Quest NC-Pass will be used by Highly-Sensitive users. | 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. |
| V-224335 | medium | Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP. | 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. |