{"stig":{"title":"z/OS CA MICS for ACF2 Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224270","ruleId":"SV-224270r1141561_rule","severity":"medium","ruleTitle":"CA MICS Resource Management installation datasets must be properly protected.","description":"CA MICS Resource Management installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets 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 dataset and Resource Data Collection:\n\n- SENSITVE.RPT(MICSRPT).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZMIC0000).\n\nVerify that the accesses to the CA MICS Resource Management installation datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset access authorizations restrict READ access to all authorized users (e.g., auditors, security administrators, and MICS end users).\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to MICS administrators.\n\nThe ACF2 dataset 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 CA MICS Resource Management installation datasets is limited to systems programmers and MICS administrators. READ access can be given to all authorized users (e.g., auditors, security administrators, and MICS end users). All failures and successful WRITE and/or greater accesses are logged. \n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be: \nSYS2.MICS\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nMICS.- UID(syspaudt) R(A) W(L) A(L) E(A)\nMICS.- UID(tstcaudt) R(A) W(L) A(L) E(A)\nMICS.- UID(micsadm) R(A) W(L) A(L) E(A)\nMICS.- UID(audtaudt) R(A) E(A)\nMICS.- UID(micsuser) R(A) E(A)\nMICS.- UID(secaaudt) R(A) E(A)","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224271","ruleId":"SV-224271r1141564_rule","severity":"medium","ruleTitle":"CA MICS Resource Management User datasets must be properly protected.","description":"CA MICS Resource Management User datasets contain sensitive data obtained through the MICS data collection process. Failure to properly identify and restrict access to these datasets could result in unauthorized access to sensitive data.","checkContent":"Refer to the following report produced by the dataset and Resource Data Collection:\n\n- SENSITVE.RPT(MICSUSER).\n\nAutomated Analysis\nRefer to the following report produced by the dataset and Resource Data Collection:\n\n- PDI(ZMIC0002).\n\nVerify that the accesses to the CA MICS Resource Management User datasets are properly restricted. If the following guidance is true, this is not a finding.\n \nThe ACF2 dataset access authorizations restrict READ access to all authorized users (e.g., auditors, security administrators, and MICS end users).\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.\n\nThe ACF2 dataset access authorizations restrict WRITE and/or greater access to SMF Batch user(s) and MICS Administrators.","fixText":"The ISSO will ensure WRITE and/or greater access to CA MICS Resource Management User datasets is limited to SMF Batch user(s), MICS Administrators, and systems programming personnel. READ access can be given to all authorized users (e.g., auditors, security administrators, and MICS end users).\n\nThe installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)\n\nDatasets to be protected will be (additional datasets may be required):\nSYS2.MICS.DATA\n\nThe following commands are provided as a sample for implementing dataset controls: \n\n$KEY(SYS2)\nMICS.DATA.- UID(syspaudt) R(A) W(A) A(A) E(A)\nMICS.DATA.- UID(tstcaudt) R(A) W(A) A(A) E(A)\nMICS.DATA.- UID(micsadm) R(A) W(A) A(A) E(A)\nMICS.DATA.- UID(smfbaudt) R(A) W(A) A(A) E(A)\nMICS.DATA.- UID(audtaudt) R(A) E(A)\nMICS.DATA.- UID(micsuser) R(A) E(A)\nMICS.DATA.- UID(secaaudt) R(A) E(A)","ccis":["CCI-001499"]}]}