{"stig":{"title":"z/OS HCD for TSS Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224726","ruleId":"SV-224726r1146337_rule","severity":"medium","ruleTitle":"IBM Hardware Configuration Definition (HCD) install data sets are not properly protected.","description":"IBM HCD product has the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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(HCDRPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZHCD0000).\n\nVerify that access to the IBM Hardware Configuration Definition (HCD) install data sets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe TSS data set rules for the data sets restricts READ access to auditors, automated operations, operators, and systems programming personnel.\n\nThe TSS data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe TSS data set rules for the data sets specifies that all (i.e., failures and successes) WRITE and/or greater access are logged.","fixText":"The ISSO will ensure that update and ALL access to IBM HCD install data sets is limited to systems programmers only, and all update and ALL access is logged. Auditors, automated operations, and operators should have READ access.\n\nThe installing systems programmer will identify and document the product data sets and categorize them according to who will have update and ALL access and if required that all update and ALL access is logged. The installing systems programmer will identify if any additional groups have update and/or ALL 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: \nSYS1.SCBD*\n\nThe following commands are provided as a sample for implementing data set controls: \n\nTSS PERMIT(audtaudt) DSN(SYS1.SCBD) ACCESS(R)\nTSS PERMIT(autoaudt) DSN(SYS1.SCBD) ACCESS(R)\nTSS PERMIT(operaudt) DSN(SYS1.SCBD) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS1.SCBD) ACCESS(R)\nTSS PERMIT(tstcaudt) DSN(SYS1.SCBD) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS1.SCBD) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(tstcpaudt) DSN(SYS1.SCBD) ACCESS(ALL) ACTION(AUDIT)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224727","ruleId":"SV-224727r1146339_rule","severity":"medium","ruleTitle":"IBM Hardware Configuration Definition (HCD) User data sets are not properly protected.","description":"IBM HCD product has the capability to use privileged functions and/or to have access to sensitive data. Failure to properly restrict access to their 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(HCDUSER).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZHCD0002).\n\nVerify that the access to the IBM Hardware Configuration Definition (HCD) install data sets is properly restricted. The data sets to be protected are the production and working IODF data sets as well as the activity log for the IODF data sets. If the following guidance is true, this is not a finding.\n\nNote: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**.\n\nThe TSS data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel.\n\nThe TSS data set rules for the data sets restrict READ access to automated operations users and operations personnel.\n\nThe TSS data set rules for the data sets 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 user data sets is limited to systems programmers and all WRITE and/or greater access is logged. Ensure that READ access is limited to auditors, operations personnel, and automated operations 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 UPDATE 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:\n\nThe production IODF data sets. (i.e., hhhhhhhh.IODFnn)\nThe working IODF data sets. (i.e., hhhhhhhh.IODFnn.)\nThe activity log for the IODF data sets. (i.e., hhhhhhhh.IODFnn.ACTLOG)\n\nNote: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**.\n\nThe following commands are provided as a sample for implementing data set controls:\n\nTSS ADD(SYS3) DSN(SYS3)\nTSS PER(syspaudt) DSN(SYS3.IODF) ACC(R)\nTSS PER(tstcaudt) DSN(SYS3.IODF) ACC(R)\nTSS PER(audtaudt) DSN(SYS3.IODF) ACC(R)\nTSS PER(autoaudt) DSN(SYS3.IODF) ACC(R)\nTSS PER(operaudt) DSN(SYS3.IODF) ACC(R)\nTSS PER(syspaudt) DSN(SYS3.IODF) ACC(A) ACTION(AUDIT)\nTSS PER(tstcaudt) DSN(SYS3.IODF) ACC(A) ACTION(AUDIT)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224728","ruleId":"SV-224728r1146001_rule","severity":"medium","ruleTitle":"IBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.","description":"Program products can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to program 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 nonsystems personnel with read only authority.","checkContent":"Refer to the following reports produced by the Data Set and Resource Data Collection:\n\n- TSSCMDS.RPT(WHOOIBMF).\n- SENSITVE.RPT(WHOHIBMF).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZHCD0020).\n\nReview the following items for the IBM Hardware Configuration Definition (HCD) resources in the IBMFAC resource class. If the following guidance is true, this is not a finding.\n\nThe TSS owner is defined for the CBD resource and/or IBMFAC RDT entry has DEFPROT specified.\nThere is no TSS rules that allow access to the CBD resource.\nThe TSS rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.\nThe TSS rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.","fixText":"The systems programmer will work with the ISSO to verify that the following are properly specified in the Access Control Program (ACP).\n\nThe TSS owner is defined for the CBD resources and/or IBMFAC RDT entry has DEFPROT specified.\n\nFor example:\n\nTSS ADD(dept-acid)IBMFAC(CBD.)\n\nTSS REP(RDT)RESCLASS(IBMFAC)ATTR(DEFPROT)\n\nThere are no TSS rules that allow access to the CBD resource.\n\nThe RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.\n\nThe RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.\n\nExample:\n\nTSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ)\nTSS PERMIT(operaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ)\nTSS PERMIT(autoaudt)IBMFAC(CBD.CPC.IOCDS)ACCESS(READ)\nTSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IOCDS) -\n\tACCESS(UPDATE)ACTION(AUDIT)\nTSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ)\nTSS PERMIT(operaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ)\nTSS PERMIT(autoaudt)IBMFAC(CBD.CPC.IPLPARM)ACCESS(READ)\nTSS PERMIT(syspaudt)IBMFAC(CBD.CPC.IPLPARM) -\n\tACCESS(UPDATE)ACTION(AUDIT)","ccis":["CCI-000213","CCI-002234"]}]}