{"stig":{"title":"z/OS SRRAUDIT for TSS Security Technical Implementation Guide","version":"7","release":"1"},"checks":[{"vulnId":"V-225606","ruleId":"SV-225606r1146148_rule","severity":"medium","ruleTitle":"SRRAUDIT installation data sets must be properly protected.","description":"SRRAUDIT 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(SRRPROD).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZSRR0000).\n\nVerify that the accesses to the SRRAUDIT installation data sets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe TSS data set access authorizations restrict READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors.\n\nThe TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe TSS data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater accesses are logged.","fixText":"The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation data sets is limited to systems programmers only, and all WRITE and/or greater access is logged. All failures and successful WRITE and/or greater accesses are logged.\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 accesses are 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\n(Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.)\n\nData sets to be protected will be: \nSYS2.SRRAUDIT.\n\nThe following commands are provided as a sample for implementing data set controls:\n\nTSS PERMIT(syspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)\nTSS PERMIT(syspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(tstcaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)\nTSS PERMIT(tstcaudt) DSN(SYS2.SRRAUDIT.) ACCESS(ALL) ACTION(AUDIT)\nTSS PERMIT(audtaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)\nTSS PERMIT(pcspaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)\nTSS PERMIT(secaaudt) DSN(SYS2.SRRAUDIT.) ACCESS(R)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-225607","ruleId":"SV-225607r1146369_rule","severity":"medium","ruleTitle":"SRRAUDIT User data sets are not properly protected.","description":"SRRAUDIT User data sets provide the capability 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(SRRUSER).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZSRR0002).\n\nVerify that access to the SRRAUDIT User 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 restrict READ and/or greater access to systems programming personnel, security personnel, and auditors.\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 READ, UPDATE, and ALL access to program product user data sets is limited to systems programmers, security personnel, and auditors and all WRITE and/or greater access is logged.\n\nThe installing systems programmer will identify and document the product user 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 ACP (Access Control Program ) active on the system.\n\nData set prefix to be protected will be:\n\nSYS3.SRRAUDIT.\n\nIf doing a full SRR review using the z/OS STIG Instruction, the following data set prefix to be protected will be:\n\nSYS3.FSO.\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.SRRAUDIT.) ACC(R)\nTSS PER(secaaudt) DSN(SYS3.SRRAUDIT.) ACC(R)\nTSS PER(audtaudt) DSN(SYS3.SRRAUDIT.) ACC(R)\nTSS PER(syspaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT)\nTSS PER(secaaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT)\nTSS PER(audtaudt) DSN(SYS3.SRRAUDIT.) ACC(A) ACTION(AUDIT)\n\nTSS PER(syspaudt) DSN(SYS3.FSO.) ACC(R)\nTSS PER(secaaudt) DSN(SYS3.FSO.) ACC(R)\nTSS PER(audtaudt) DSN(SYS3.FSO.) ACC(R)\nTSS PER(syspaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT)\nTSS PER(secaaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT)\nTSS PER(audtaudt) DSN(SYS3.FSO.) ACC(A) ACTION(AUDIT)","ccis":["CCI-001499"]}]}