{"stig":{"title":"z/OS CA VTAPE for RACF Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224444","ruleId":"SV-224444r1145288_rule","severity":"medium","ruleTitle":"CA VTAPE installation data sets are not properly protected.","description":"CA VTAPE installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets 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 Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(VTARPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZVTA0000).\n\nVerify that the accesses to the CA VTAPE installation data sets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe RACF data set rules for the data sets restricts READ access to all authorized users.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.","fixText":"The ISSO will ensure that WRITE and/or greater access to CA VTAPE installation data sets is limited to system 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 data sets 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. The installing systems programmer will identify if any additional groups have WRITE and/or greater 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.\n\nData sets to be protected will be: \nSYS2.VTAPE.**\nSYS3.VTAPE.** (data sets that are not altered by product STCs, can be more specific)\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS2.VTAPE.**' uacc(none) owner(sys2) -\n\taudit(success(update) failures(read)) -\n\tdata('CA VTAPE Install DS')\npe 'SYS2.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS2.VTAPE.**' id(<audtaudt> authorized users) acc(r)\npe 'SYS2.VTAPE.**' id(VTAPE STCs)\n\nad 'SYS3.VTAPE.**' uacc(none) owner(sys3) -\n\taudit(success(update) failures(read)) -\n\tdata('CA VTAPE Install DS')\npe 'SYS3.VTAPE.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS3.VTAPE.**' id(<audtaudt> authorized users) acc(r)\npe 'SYS3.VTAPE.**' id(VTAPE STCs)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224445","ruleId":"SV-224445r1145290_rule","severity":"medium","ruleTitle":"CA VTAPE STC data sets will be properly protected.","description":"CA VTAPE STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets 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 Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(VTASTC).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZVTA0001).\n\nVerify that the accesses to the CA VTAPE STC data sets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe RACF data set rules for the data sets restricts READ access to auditors and authorized users.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel and Tape Management personnel.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s).\n\nThe RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.","fixText":"The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC data sets 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 data sets 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. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, 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\nData sets to be protected will be: \nSYS3.VTAPE (data sets that are altered by the product's STCs, this can be more specific)\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS3.VTAPE.**' uacc(none) owner(sys3) -\n\taudit(failures(read)) -\n\tdata('Vendor DS Profile: CA VTAPE')\npe 'SYS3.VTAPE.**' id(<syspaudt> <tstcaudt> VTAPE STCs) acc(a)\npe 'SYS3.VTAPE.**' id(<tapeaudt> VTAPE STCs) acc(a)\npe 'SYS3.VTAPE.**' id(<audtaudt> authorized users) acc(r)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499"]},{"vulnId":"V-224446","ruleId":"SV-224446r1145291_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, data sets, 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 RACF Data Collection:\n\n- RACFCMDS.RPT(LISTUSER).\n\nVerify that the userid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nPROTECTED","fixText":"The CA VTAPE system 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\nA sample is provided here:\n\nau SVTS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass\nau SVTSAS name('CA VTAPE') owner(stc) dfltgrp(stc) nopass","ccis":["CCI-000764"]},{"vulnId":"V-224447","ruleId":"SV-224447r1145023_rule","severity":"medium","ruleTitle":"CA VTAPE Started task(s) must be properly defined to the STARTED resource class for RACF.","description":"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.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- DSMON.RPT(RACSPT).\n\nAutomated Analysis\nRefer to the following report produced by the RACF Data Collection:\n\n- PDI(ZVTA0032).\n\nVerify that the CA VTAPE started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.","fixText":"The CA VTAPE system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. \n\nA unique userid must be assigned for the CA VTAPE started task(s) thru a corresponding STARTED class entry.\n\nThe following sample set of commands is shown here as a guideline:\n\nrdef started SVTS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTS) group(stc))\nrdef started SVTSAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(SVTSAS) group(stc))\n\nsetr racl(started) ref","ccis":["CCI-000764"]}]}