CA VTAPE installation data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224444	SRG-OS-000080	ZVTAR000	SV-224444r1082303_rule	2025-03-04	7

Description
CA VTAPE installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

ℹ️ Check
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTARPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0000) Verify that the accesses to the CA VTAPE installation data sets are properly restricted. The RACF data set rules for the data sets restricts READ access to all authorized users. The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

ℹ️ Check

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTARPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0000) Verify that the accesses to the CA VTAPE installation data sets are properly restricted. The RACF data set rules for the data sets restricts READ access to all authorized users. The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

✔️ Fix
The ISSO will ensure that update and alter access to CA VTAPE installation data sets is limited to system programmers only, and all update and alter access is logged. Read access can be given to all authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and alter access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Data sets to be protected will be: SYS2.VTAPE. SYS3.VTAPE. (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.VTAPE.' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS2.VTAPE.' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.VTAPE.' id(<audtaudt> authorized users) acc(r) pe 'SYS2.VTAPE.' id(VTAPE STCs) ad 'SYS3.VTAPE.' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS3.VTAPE.' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.VTAPE.' id(<audtaudt> authorized users) acc(r) pe 'SYS3.VTAPE.' id(VTAPE STCs) setr generic(dataset) refresh

✔️ Fix

The ISSO will ensure that update and alter access to CA VTAPE installation data sets is limited to system programmers only, and all update and alter access is logged. Read access can be given to all authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and alter access is logged. The installing systems programmer will identify if any additional groups have update and/or alter access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Data sets to be protected will be: SYS2.VTAPE.** SYS3.VTAPE.** (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.VTAPE.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS2.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.VTAPE.**' id(<audtaudt> authorized users) acc(r) pe 'SYS2.VTAPE.**' id(VTAPE STCs) ad 'SYS3.VTAPE.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('CA VTAPE Install DS') pe 'SYS3.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.VTAPE.**' id(<audtaudt> authorized users) acc(r) pe 'SYS3.VTAPE.**' id(VTAPE STCs) setr generic(dataset) refresh