{"stig":{"title":"z/OS CA Common Services for RACF Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224433","ruleId":"SV-224433r1144691_rule","severity":"medium","ruleTitle":"CA Common Services installation data sets will be properly protected.","description":"CA Common Services 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(CCSRPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZCCS0000).\n\nVerify that the accesses to the CA Common Services 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 is logged.\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 Common Services installation data sets 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 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 see that they are properly restricted to the ACP (Access Control Program) active on the system.\n\nData sets to be protected may begin with:\nSYS2.CCS.\nSYS2A.CCS.\nSYS3.CCS.\n\nThe following commands are provided as a sample for implementing data set controls:\n\nAD 'sys2.ccs.**' UACC(NONE) OWNER(SYS2) AUDIT(SUCCESS(UPDATE) FAILURES(READ))\n\nPE 'sys2.ccs.**' ID(syspaudt) ACC(A)\nPE 'sys2.ccs.**' ID(authorized users/*) ACC(R)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224434","ruleId":"SV-224434r1144693_rule","severity":"medium","ruleTitle":"CA Common Services Started Task name will be properly identified and/or defined to the system ACP.","description":"CA Common Services 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 Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nPROTECTED","fixText":"The ISSO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or 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 a Started Task is identified and any additional attributes that must be specified.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nau CAS9 name('STC, CAS9') owner(stc) dfltgrp(stc) nopass -\n\tdata('CCS stc')","ccis":["CCI-000764"]},{"vulnId":"V-224435","ruleId":"SV-224435r1144695_rule","severity":"medium","ruleTitle":"CA Common Services Started task will be properly defined to the STARTED resource class for RACF.","description":"Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could 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(ZCCS0032).\n\nIf the CA Common Services started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.","fixText":"The ISSO working with the systems programmer will ensure the CA Common Services Started Task(s) is properly identified and/or defined to the System ACP. \n\nA unique userid must be assigned for the CA Common Services started task(s) thru a corresponding STARTED class entry.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nrdef started CAS9.** uacc(none) owner(admin) audit(all(read)) -\n\tstdata(user(CAS9) group(stc))\nsetr racl(started) ref","ccis":["CCI-000764"]}]}