CA VTAPE STC data sets will be properly protected.

From z/OS CA VTAPE for RACF STIG

Part of ZB000001

Associated with IA controls: ECCD-2, ECAR-3, ECAR-2, ECCD-1, ECAR-1, DCSL-1

Associated with: CCI-001499

SV-33828r1_rule CA VTAPE STC data sets will be properly protected.

Vulnerability discussion

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 data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

Check content

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTASTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0001) Verify that the accesses to the CA VTAPE STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set rules for the data sets restricts READ access to auditors and authorized users. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel and Tape Management personnel. ___ The RACF data set rules for the data sets restricts WRITE and/or greater access to the CA VTAPE’s STC(s) and/or batch user(s). ___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.

Fix text

The IAO will ensure that WRITE and/or greater access to CA VTAPE STC data sets is limited to System Programmers, Tape Management personnel and/or CA VTAPE’s STC(s) and/or batch user(s) only. READ access can be given to auditors and 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 allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.VTAPE (data sets that are altered by the product’s STCs, this can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS3.VTAPE.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA VTAPE') pe 'SYS3.VTAPE.**' id( VTAPE STCs) acc(a) pe 'SYS3.VTAPE.**' id( VTAPE STCs) acc(a) pe 'SYS3.VTAPE.**' id( authorized users) acc(r) setr generic(dataset) refresh

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer