The ISSO will ensure that WRITE and/or greater access to CA 1 TMC, AUDIT and optional RDS and VPD data sets are limited to only systems programming personnel and tape management personnel. UPDATE access can be given to CA 1 STCs and/or batch users. READ access can be given to application support personnel, production control and scheduling personnel, operations personnel, and auditors. ALL access will be logged. The 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 ensure they are properly restricted to the Access Control Program (ACP) active on the system. (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.) Due to the unique file structure of the TMC and Audit data sets, CA 1 uses the YSVC programs to handle all direct I/O activity. Because standard OPEN/CLOSE macros are not used, typical data set security checks are not performed. Even if a user does not have READ access to these data sets, the YSVC programs can enable that user to read and update records within these files. Therefore, control READ access to the TMC and Audit data sets by the YSVCUNCD and YSVCCOND resource names. Typical users should be restricted to conditional READ access. Restrict CA 1 batch production jobs, and CA 1 started tasks to the following access authority: Unconditional READ and UPDATE access to the TMC, Audit, Retention, and Vault Pattern Description data sets. Note: READ and UPDATE access to the TMC and Audit data sets are controlled by the YSVCUNCD and YSVCCOND resource names, and by standard ACP data set controls, because some CA 1 utilities use conventional OPEN/CLOSE methods. The following commands are provided as a sample for implementing data set controls: TSS ADD(SYS3) DSN(SYS3) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(READ) TSS PERMIT(CA1 STCs) DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.AUDIT) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.RDS) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(READ) TSS PERMIT(CA1 STCs) DSN(SYS3.CA1.TMC) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.TMC) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT() DSN(SYS3.CA1.VPD) ACCESS(UPDATE)

z/OS CA 1 Tape Management for TSS Security Technical Implementation Guide

Checks (11)