{"stig":{"title":"z/OS CA VTAPE for ACF2 Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224279","ruleId":"SV-224279r1141660_rule","severity":"medium","ruleTitle":"CA VTAPE installation datasets are not properly protected.","description":"CA VTAPE installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these 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(VTARPT).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZVTA0000).\n\nVerify that the accesses to the CA VTAPE installation datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset rules for the datasets restrict READ access to all authorized users.\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 specify that all (i.e., failures and successes) WRITE and/or greater access is logged.","fixText":"The ISSO will ensure that WRITE and/or greater access to CA VTAPE installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users.\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 WRITE and/or greater 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.VTAPE\nSYS3.VTAPE (Datasets that are not altered by product STCs can be more specific.)\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nVTAPE.- UID(<syspaudt>) R(A) W(L) A(L) E(A)\nVTAPE.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)\nVTAPE.- UID(<audtaudt>) R(A) E(A)\nVTAPE.- UID(authorized users) R(A) E(A)\nVTAPE.- UID(<audtaudt>) R(A) E(A)\nVTAPE.- UID(VTAPE STCs) R(A) E(A)\n\n$KEY(SYS3)\nVTAPE.- UID(<syspaudt>) R(A) W(L) A(L) E(A)\nVTAPE.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)\nVTAPE.- UID(<audtaudt>) R(A) E(A)\nVTAPE.- UID(authorized users) R(A) E(A)\nVTAPE.- UID(VTAPE STCs) R(A) E(A)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224280","ruleId":"SV-224280r1141663_rule","severity":"medium","ruleTitle":"CA VTAPE STC datasets will be properly protected.","description":"CA VTAPE STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these 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(VTASTC).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZVTA0001).\n\nVerify that the accesses to the CA VTAPE STC datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset rules for the datasets restrict READ access to auditors and authorized users.\n\nThe ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel and Tape Management personnel.\n\nThe ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s).","fixText":"The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC datasets is limited to systems programmers, tape management personnel, and/or CA VTAPE's STC(s) and/or batch user(s) only. READ access can be given to auditors and authorized users.\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 WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.\n\nDatasets to be protected will be: \nSYS3.VTAPE (Datasets that are altered by the product's STCs can be more specific.)\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS3)\nVTAPE.- UID(<syspaudt>) R(A) W(A) A(A) E(A)\nVTAPE.- UID(<tapeaudt>) R(A) W(A) A(A) E(A)\nVTAPE.- UID(<tstcaudt>) R(A) W(A) A(A) E(A)\nVTAPE.- UID(VTAPE STCs) R(A) W(A) A(A) E(A)\nVTAPE.- UID(<audtaudt>) R(A) E(A)\nVTAPE.- UID(authorize users) R(A) E(A)","ccis":["CCI-001499"]},{"vulnId":"V-224281","ruleId":"SV-224281r1144188_rule","severity":"medium","ruleTitle":"CA VTAPE Started Task name is not properly identified/defined to the system ACP.","description":"CA VTAPE requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.","checkContent":"Refer to the following report produced by the ACF2 Data Collection:\n\n- ACF2CMDS.RPT(ATTSTC).\n\nVerify that the logonid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nSTC\nNO-SMC","fixText":"The CA VTAPE 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\nINSERT SVTS STC NO-SMC\nINSERT SVTSAS STC NO-SMC","ccis":["CCI-000764"]}]}