Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(VTARPT). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZVTA0000). Verify that the accesses to the CA VTAPE installation datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to all authorized users. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
The ISSO will ensure that WRITE and/or greater access to CA VTAPE installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users. The 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. Datasets to be protected will be: SYS2.VTAPE SYS3.VTAPE (Datasets that are not altered by product STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) VTAPE.- UID(<syspaudt>) R(A) W(L) A(L) E(A) VTAPE.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) VTAPE.- UID(<audtaudt>) R(A) E(A) VTAPE.- UID(authorized users) R(A) E(A) VTAPE.- UID(<audtaudt>) R(A) E(A) VTAPE.- UID(VTAPE STCs) R(A) E(A) $KEY(SYS3) VTAPE.- UID(<syspaudt>) R(A) W(L) A(L) E(A) VTAPE.- UID(<tstcaudt>) R(A) W(L) A(L) E(A) VTAPE.- UID(<audtaudt>) R(A) E(A) VTAPE.- UID(authorized users) R(A) E(A) VTAPE.- UID(VTAPE STCs) R(A) E(A)
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(VTASTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZVTA0001). Verify that the accesses to the CA VTAPE STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ access to auditors and authorized users. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel and Tape Management personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s).
The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC datasets is limited to systems programmers, tape management personnel, and/or CA VTAPE's STC(s) and/or batch user(s) only. READ access can be given to auditors and authorized users. The 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 ACP (Access Control Program) active on the system. Datasets to be protected will be: SYS3.VTAPE (Datasets that are altered by the product's STCs can be more specific.) The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) VTAPE.- UID(<syspaudt>) R(A) W(A) A(A) E(A) VTAPE.- UID(<tapeaudt>) R(A) W(A) A(A) E(A) VTAPE.- UID(<tstcaudt>) R(A) W(A) A(A) E(A) VTAPE.- UID(VTAPE STCs) R(A) W(A) A(A) E(A) VTAPE.- UID(<audtaudt>) R(A) E(A) VTAPE.- UID(authorize users) R(A) E(A)
Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC). Verify that the logonid(s) for the CA VTAPE started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. STC NO-SMC
The CA VTAPE systems programmer and the ISSO will ensure that a product's Started Task(s) is properly identified/defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. Example: SET LID INSERT SVTS STC NO-SMC INSERT SVTSAS STC NO-SMC