Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
CA VTAPE Started Task name is not properly identified/defined to the system ACP.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-224446 | ZVTAR030 | SV-224446r519682_rule | Medium |
| Description |
|---|
| 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 userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data. |
| STIG | Date |
|---|---|
| z/OS CA VTAPE for RACF Security Technical Implementation Guide | 2022-10-07 |
Details
| Check Text ( C-26123r519680_chk ) |
|---|
| Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) The CA VTAPE started task(s) and/or batch job userid(s) is defined and is assigned the RACF PROTECTED attribute. |
| Fix Text (F-26111r519681_fix) |
|---|
| The CA VTAPE system programmer and the IAO will ensure that a product's Started Task(s) is properly identified/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. A sample is provided here: au SVTS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass au SVTSAS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass |