z/OS CA VTAPE for RACF Security Technical Implementation Guide
V7 · Released 2025-03-04
You are viewing V7. This is not the latest release. View latest release (V7R2) → · Version history
Overview
| Version | Date | Finding Count (4) | ||
| V7 | 2025-03-04 | CAT I (High): 0 | CAT II (Medium): 4 | 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 — All
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224444 | CA VTAPE installation data sets are not properly protected. | CA VTAPE installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access... | |
| V-224445 | CA VTAPE STC data sets will be properly protected. | CA VTAPE STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these... | |
| V-224446 | CA VTAPE Started Task name is not properly identified/defined to the system ACP. | CA VTAPE requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a ... | |
| V-224447 | CA VTAPE Started task(s) must 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 ... |