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

z/OS TADz for TSS STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 4 checks updated. It has 4 checks, against 4 in V7R1.

  • 0 added
  • 0 removed
  • 4 updated

Updated fields: Check text 4Fix text 4Discussion 2Title 1

Updated in V7R2 (4)

V-225608CAT IITivoli Asset Discovery for z/OS (TADz) install data sets are not properly protected.Check text, Fix text

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 sets are properly restricted. If the following guidance is true, this is not a finding. The TSS data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. The TSS 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 is true, this is a finding.

Fix text

The ISSO will ensure that updateWRITE and allocate/createor greater access to program product data sets is limited to systemsystems programmers only, and all updateWRITE and allocate/createor greater 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 allocate/createor greater access and if required that all updateWRITE and allocate/createor greater 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 sets to be protected will be: SYS2.TADZ SYS2.TADZ .V-.SHSIMOD1 (optional fully-qualified APF). SYS3.TADZ The following commands are provided as a sample for implementing datasetdata set controls: TSS PERMIT(syspaudt) DSN(SYS2.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2.TADZ.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS2.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys2.tadz.*.shsimod1) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys2.tadz.*.shsimod1) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS2.TADZ.*.shsimod1) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TADZ.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS3.TADZ.) ACCESS(R)

V-225609CAT IITivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are not properly protected.Check text, Fix text

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 TSS 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 anyTSS 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 (ACP) 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: TSS PERMIT(syspaudt) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.um.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.um.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.um.) ACCESS(ALL)

V-225610CAT IITivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified/defined to the system ACP.Title, Check text, Fix text, Discussion

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 reports produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review each TADz STC/Batch ACID(s) for the following: ___ Is defined with Facility of STC and/or BATCH. ___ Is sourced to the INTRDR. If all of the abovefollowing attributes are truedefined, therethis is NOnot FINDINGa finding. If any of the above is untrueFACILITY(STC, this is a FINDING.BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND

Fix text

The TADz Systems Programmer and ISSO will ensure that the started task(s) for TADz is properly defined. Define the started task for TADz. Example: TSS CRE(TADZMON) DEPT(Dept) NAME('TADz STC') - FAC(STC) PASSWORD(password,0) - SOURCE(INTRDR) NOSUSPEND

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. By 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-225611CAT IIIBM Tivoli Asset Discovery for zOS (TADz) Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.Check text, Fix text, Discussion

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZTAD0032). Verify that the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) is (are) defined in the TSS STC record. If this guidance is true, this is not a finding.

Fix text

The IBM Tivoli Asset Discovery for zOS (TADz) systemsystemsprogrammer programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the Systemsystem ACP. A unique ACID must be assigned for the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) thruthrough a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(TADZMON) ACID(TADZMON)

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.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.