{"stig":{"title":"z/OS TADz for ACF2 Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224344","ruleId":"SV-224344r1141645_rule","severity":"medium","ruleTitle":"Tivoli Asset Discovery for z/OS (TADz) Install datasets are not properly protected.","description":"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.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(TADZRPT).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZTAD0000).\n\nVerify that access to the TADz Install datasets is properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset rules for the datasets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.","fixText":"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.\n\nThe 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.\n\nDatasets to be protected will be: \nSYS2.TADZ \nSYS2.TADZ .V-.SHSIMOD1\nSYS3.TADZ \n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nTADZ.- UID(syspaudt) R(A) W(L) A(L) E(A)\nTADZ.V-.SHSIMOD1 UID(syspaudt) R(A) W(L) A(L) E(A)\nTADZ.- UID(audtaudt) R(A) E(A)\n\n$KEY(SYS3)\nTADZ.- UID(syspaudt) R(A) W(L) A(L) E(A)\nTADZ.- UID(audtaudt) R(A) E(A)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224345","ruleId":"SV-224345r1141648_rule","severity":"medium","ruleTitle":"Tivoli Asset Discovery for zOS (TADz) STC and/or batch datasets are not properly protected.","description":"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.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(TADZSTC).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZTAD0001).\n\nVerify that access to the TADz STC and/or batch datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe 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).\n\nThe ACF2 dataset rules for the datasets restrict READ access to job scheduling products.\n\nThe ACF2 dataset rules for the datasets restrict READ access to auditors.","fixText":"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. \n\nGrant READ access to any scheduling products that are in use.\n \nGrant READ access to auditors at the ISSO's discretion.\n\nIdentify 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.\n\nDatasets to be protected will be: \nSYS3.TADZ\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS3)\nTADZ.- UID(syspaudt) R(A) W(A) A(A) E(A)\nTADZ.- UID(audtaudt) R(A) E(A)\nTADZ.-.UM.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)\nTADZ.-.IQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)\nTADZ.-.UIQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)\nTADZ.- UID(stc id TADZMON) R(A) W(A) A(A) E(A)","ccis":["CCI-001499"]},{"vulnId":"V-224346","ruleId":"SV-224346r1141651_rule","severity":"medium","ruleTitle":"Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP.","description":"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.","checkContent":"Refer to the following report produced by the ACF2 Data Collection:\n\n- ACF2CMDS.RPT(LOGONIDS).\n\nVerify 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.\n\nFor each STC logonid:\n\nSTC\n\nFor each Batch logonid:\n\nJOB","fixText":"The TADz systems programmer and the ISSO will ensure that a product's Started Task(s) is properly identified / defined to the System ACP. \n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.\n\nExample:\n\nSET LID\nCHANGE TADZMON STC","ccis":["CCI-000764"]}]}