None Computing title z/OS TADz for ACF2 Security Technical Implementation Guide version 7 releaseinfo Release: 2 Vuln_Num V-224344 Rule_ID SV-224344r1141645_rule Severity medium Rule_Title Tivoli Asset Discovery for z/OS (TADz) Install datasets are not properly protected. Vuln_Discuss Tivoli Asset Discovery for z/OS (TADz) Install datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets 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 dataset and Resource Data Collection: - SENSITVE.RPT(TADZRPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZTAD0000). Verify that access to the TADz Install datasets is properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged. Fix_Text The ISSO will ensure that WRITE and/or greater access to program product datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. Auditors should have READ access. The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have UPDATE access for specific datasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Datasets to be protected will be: SYS2.TADZ SYS2.TADZ .V-.SHSIMOD1 SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.V-.SHSIMOD1 UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.- UID(audtaudt) R(A) E(A) $KEY(SYS3) TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.- UID(audtaudt) R(A) E(A) Not_Reviewed Vuln_Num V-224345 Rule_ID SV-224345r1141648_rule Severity medium Rule_Title Tivoli Asset Discovery for zOS (TADz) STC and/or batch datasets are not properly protected. Vuln_Discuss Tivoli Asset Discovery for zOS (TADz) STC datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets 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 dataset and Resource Data Collection: - SENSITVE.RPT(TADZSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZTAD0001). Verify that access to the TADz STC and/or batch datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel and the product STC(s) and/or batch job(s). The ACF2 dataset rules for the datasets restrict READ access to job scheduling products. The ACF2 dataset rules for the datasets restrict READ access to auditors. Fix_Text Grant WRITE and/or greater access to Tivoli Asset Discovery for z/OS (TADz) STC and/or batch datasets are limited to systems programmers and TADz STC and/or batch jobs only. Grant READ access to any scheduling products that are in use. Grant READ access to auditors at the ISSO's discretion. Identify and document the product datasets and categorize them according to who will have WRITE and/or greater access and, if required, that all WRITE and/or greater access is logged. Identify if any additional groups have UPDATE access for specific datasets, and assure that they are properly restricted to the ACP (Access Control Program) active on the system. Datasets to be protected will be: SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) TADZ.- UID(syspaudt) R(A) W(A) A(A) E(A) TADZ.- UID(audtaudt) R(A) E(A) TADZ.-.UM.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.-.IQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.-.UIQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.- UID(stc id TADZMON) R(A) W(A) A(A) E(A) Not_Reviewed Vuln_Num V-224346 Rule_ID SV-224346r1141651_rule Severity medium Rule_Title Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP. Vuln_Discuss Tivoli Asset Discovery for z/OS (TADz) requires a started task(s) that will be restricted to certain resources, datasets 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. Check_Content Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(LOGONIDS). Verify that the logonid(s) for the TADz started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. For each STC logonid: STC For each Batch logonid: JOB Fix_Text The TADz systems programmer and the ISSO will ensure that a product's Started Task(s) is properly identified / defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. Example: SET LID CHANGE TADZMON STC Not_Reviewed