{"stig":{"title":"z/OS CA Auditor for RACF Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224430","ruleId":"SV-224430r1145195_rule","severity":"medium","ruleTitle":"CA Auditor installation data sets are not properly protected.","description":"CA Auditor 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(ADTRPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZADT0000).\n\nVerify that the accesses to the CA Auditor 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 restrict READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users.\n\nThe RACF data set rules for the data sets restrict 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 Auditor installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, security administrators, and/or CA Auditor's STCs and batch 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: \nSYS2.EXAMINE\nSYS2A.EXAMINE\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS2.EXAMINE.**' uacc(none) owner(sys2) -\n\taudit(success(update) failures(read)) -\n\tdata('Vendor DS Profile: CA Auditor/Examine')\npe 'SYS2.EXAMINE.**' id(<syspaudt>) acc(a)\npe 'SYS2.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r)\nad 'SYS2A.EXAMINE.**' uacc(none) owner(sys2a) -\n\taudit(success(update) failures(read)) -\n\tdata('Vendor DS Profile: CA Auditor/Examine')\npe 'SYS2A.EXAMINE.**' id(<syspaudt>) acc(a)\npe 'SYS2A.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224431","ruleId":"SV-224431r1145197_rule","severity":"medium","ruleTitle":"CA Auditor User data sets are not properly protected.","description":"CA Auditor User 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(ADTUSER).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZADT0002).\n\nVerify that the accesses to the CA Auditor User 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 WRITE and/or greater access to systems programming personnel, security personnel and auditors.","fixText":"The ISSO will ensure that WRITE and/or greater access to CA Auditor User data sets are limited to System Programmers, security personnel and auditors.\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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system.\n\nData sets to be protected will be: \nSYS3.EXAMINE\n\nThe following commands are provided as a sample for implementing data set controls: \n\nad 'SYS3.EXAMINE.**' uacc(none) owner(sys3) -\n\taudit(failures(read)) -\n\tdata('Vendor DS Profile: CA Auditor')\npe 'SYS3.EXAMINE.**' id(<syspaudt>) acc(a)\npe 'SYS3.EXAMINE.**' id(<audtaudt> <secaaudt>) acc(A)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499"]},{"vulnId":"V-224432","ruleId":"SV-224432r1144649_rule","severity":"medium","ruleTitle":"CA Auditor resources are not properly defined and protected.","description":"CA Auditor can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(ZADT0020).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZADT0020).\n\nVerify that the access to the LTDMMAIN resource in the PROGRAM resource class is restricted. If the following guidance is true, this is not a finding.\n\nThe RACF rules for the resources specify a default access of NONE.\n\nThe RACF rules for the resources are restricted access to system programmers, auditors, and security personnel.\n\nAll RACF rules are defined with UACC(NONE).","fixText":"The ISSO will verify that the LTDMMAIN resource in the PROGRAM resource class is restricted to system programmers, auditors, and security personnel.\n\nThe RACF rules for the LTDMMAIN resource specify a default access of NONE and no RACF rules that allow access to the LTDMMAIN resource.\n\nExample:\n\nrdef program LTDMMAIN uacc(none) owner(admin) audit(failures(read)) -\ndata('added per PDI ZADT0020') \n\nThe RACF rules for the LTDMMAIN resource is restricted access to systems programmers, auditors, and security personnel with access of READ. All RACF rules are defined with UACC(NONE).\n\nExample:\n\nrdef program ltdmmain -                \n addmem('SYS2A.EXAMINE.V120SP01.CAILIB'//nopadchk) -  \n data('Required by SRR PDI ZADTR020') -        \n audit(failures(read)) uacc(none) owner(admin)       \npe LTDMMAIN cl(program) id(syspaudt) acc(r)\npe LTDMMAIN cl(program) id(audtaudt) acc(r)\npe LTDMMAIN cl(program) id(secaaudt) acc(r)\n\nsetr when(program) ref","ccis":["CCI-000213"]}]}