Part of ZB000001
Associated with IA controls: ECCD-2, ECAR-3, ECAR-2, ECCD-1, ECAR-1, DCSL-1
Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
a) Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0001) b) Verify that acess to the TADz STC and/or batch data sets are properly restricted. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to the product STC(s) and/or batch job(s). c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.
The IAO will ensure that update and alter access to Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are limited to system programmers and TADz STC and/or batch jobs only. Read access may be granted to auditors at the IAOs discretion. 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 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.TADZ The following commands are provided as a sample for implementing dataset controls: ad 'sys3.tadz.*.iq*.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') ad 'sys3.tadz.*.uiq.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') ad 'sys3.tadz.*.um.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') pe 'sys3.tadz.*.iq*.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.iq*.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.iq*.**' id(tadzinq) acc(a) pe 'sys3.tadz.*.uiq.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.uiq.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.uiq.**' id(tadzinq) acc(a) pe 'sys3.tadz.*.um.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.um.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.um.**' id(tadzinq) acc(a)
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