z/OS Quest NC-Pass for RACF Security Technical Implementation Guide
Overview
| Version | Date | Finding Count (5) | Downloads | ||
| 7 | 2025-03-04 | CAT I (High): 0 | CAT II (Medium): 5 | CAT III (Low): 0 | |
| STIG Description |
| 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. |
Findings - MAC III - Administrative Sensitive
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224523 | Quest NC-Pass installation data sets will be properly protected. | Quest NC-Pass installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict a... | |
| V-224524 | Quest NC-Pass STC data sets will be properly protected. | 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 ... | |
| V-224525 | 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... | |
| V-224526 | 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. By defining the started task ... | |
| V-224527 | Quest NC-Pass Started task will be properly defined to the STARTED resource class for RACF. | Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to ... |