From z/OS Compuware Abend-AID for ACF2 STIG
Part of ZB000002
Associated with IA controls: ECCD-2, ECAR-2, ECCD-1, ECAR-1, DCSL-1
Associated with: CCI-000213
Compuware Abend-AID 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.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(AIDUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZAID0002) Verify that the accesses to the following Compuware Abend-AID user data sets are properly restricted: Region dump datasets Report databases Source listing files/source listing shared directories If the following guidance is true, this is not a finding. ___ The ACF2 data set rules for the listed data sets restricts READ access to auditors. ___ The ACF2 data set rules for the listed data sets restricts WRITE and/or greater access to systems programming personnel. ___ The ACF2 data set rules for the listed data sets restricts WRITE and/or greater access to the Compuware Abend-AID’s STC(s) and/or batch user(s). ___ The ACF2 data set rules for the listed data sets restricts WRITE access to Application Development Programmers and Application Production Support Team members.
Ensure that WRITE and/or greater access to Compuware Abend-AID user data sets is limited to System Programmers and Compuware Abend-AID STC(s) and/or batch user(s) only. Ensure that WRITE access to Compuware Abend-AID user data sets is limited to Application Development Programmers and Application Production Support Team members. Read access can be given to auditors. (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.) Data sets to be protected will be: Region dump datasets Report databases Source listing files/source listing shared directories The following commands are provided as a sample for implementing data set controls: $KEY(S3A) $PREFIX(SYS3) ABENDAID.SHARED-.- UID(appdaudt) R(A) W(A) ABENDAID.SHARED-.- UID(appsaudt) R(A) W(A) ABENDAID.SHARED-.- UID(AbendAID STCs) R(A) W(A) A(A) E(A) ABENDAID.SHARED-.- UID(syspaudt) R(A) W(A) A(A) E(A) ABENDAID.SHARED-.- UID(tstcaudt) R(A) W(A) A(A) E(A) ABENDAID.SHARED-.- UID(audtaudt) R(A) ABENDAID.REPORTDB-.- UID(appdaudt) R(A) W(A) ABENDAID.REPORTDB-.- UID(appsaudt) R(A) W(A) ABENDAID.REPORTDB-.- UID(AbendAID STCs) R(A) W(A) A(A) E(A) ABENDAID.REPORTED-.- UID(syspaudt) R(A) W(A) A(A) E(A) ABENDAID.REPORTED-.- UID(tstcaudt) R(A) W(A) A(A) E(A) ABENDAID.REPORTDB-.- UID(audtaudt) R(A) SET RULE COMPILE 'ACF2.MVA.DSNRULES(S3A)' STORE
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer