What changed in z/OS TADz for RACF STIG V7R2V7R2 changes

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0000). Verify that access to the TADz Install data setsets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. The RACF data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged. If all of the above are untrue, this is not a finding. If any of the above are true, this is a finding.

Fix text

The ISSO will ensure that updateWRITE and/or altergreater access to program product data sets is limited to system programmers and all updateWRITE and/or allocategreater access is logged. Auditors should have readREAD access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or altergreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE 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 set prefix to be protected will be: SYS2.TADZ. SYS2.TADZ.*.SHSIMOD1.** (optional fully-qualified APF). SYS3.TADZ. The following commands are provided as a sample for implementing datasetdata set controls: ad 'sys2.TADZ.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: TADZ') pe 'sys2.TADZ.**' id(syspaudt) acc(a) pe 'sys2.tadz.**' id(audtaudt) ad 'sys2.tadz.*.shsimod1.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: Tivoli Asset Discovery APF DS') pe 'sys2.tadz.*.shsimod1.**' id(syspaudt) acc(a) pe 'sys2.tadz.*.shsimod1.**' id(audtaudt) ad 'sys3.TADZ.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('TADZ Vendor Datasets') pe 'sys3.TADZ.**' id(syspaudt) acc(a) pe 'sys3.tadz.**' id(audtaudt) setr generic(dataset) refresh

V-224537 in V7R2

Check text

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). ForVerify allthat (access to the TADz) STC and/or batch data sets: are properly restricted. If the following guidance is true, this is not a finding. IfThe RACF data set rules for the UPDATEdata sets restrict WRITE and/or greater access is restricted to systems programming personnel and the product STC(s) and/or batch job(s) this is not a finding. IfThe anyRACF jobdata schedulingset productsrules arefor inthe usedata andsets restrict READ access is restricted to READany thisjob isscheduling notproducts athat finding. Ifare auditorsin haveuse READand access this is not a findingauditors.

Fix text

Grant updateWRITE and/or altergreater access to Tivoli Asset Discovery for z/OS (TADz) STC and/or batch data sets are limited to systems programmers and TADz STC and/or batch jobs only. Grant ReadREAD access to any scheduling products that are in use. Grant ReadREAD access to auditors at the ISSO's discretion. Identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. Identify if any additional groups have updateUPDATE access for specific data sets, and assure 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 datasetdata set 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)

V-224538 in V7R2

Title

Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP.

Check text

Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). IfVerify that the userid(s) for the TADz started task(s) is defined(are) toproperly the security database, there is NO FINDINGdefined. If the userid(s)following forattributes theare TADz started task is not defined to the security database, this is not a FINDINGfinding. PROTECTED

Discussion

Tivoli Asset Discovery for z/OS (TADz) requires a started task(s) that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining defining the started task as a userid to the system Access Control Program (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.

V-224539 in V7R2

Check text

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT). Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZTAD0032). Verify that the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Fix text

The IBM Tivoli Asset Discovery for zOS (TADz) system programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique userid must be assigned for the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started TADZMON.** uacc(none) owner(admin) audit(all(read)) stdata(user(TADZMON) group(stc)) setr racl(started) ref

Discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

V-224540 in V7R2