What changed in z/OS CA VTAPE for TSS STIG V7R2V7R2 changes

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTARPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0000). Verify that the accesses to the CA VTAPE installation data sets are properly restricted. If the following guidance is true, this is not a finding. The TSS data set rules for the data sets restrictsrestrict READ access to all authorized users. The TSS data set rules for the data sets restrictsrestrict UPDATEWRITE and/or ALLgreater access to systems programming personnel. The TSS data set rules for the data sets specify that all (i.e., failures and successes) UPDATEWRITE and/or ALLgreater access are logged.

Fix text

The ISSO will ensure that updateWRITE and/or allocategreater access to CA VTAPE installation data sets is limited to systemsystems programmers only, and all updateWRITE and/or allocategreater access is logged. ReadREAD access can be given to all authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater 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. Data sets to be protected will be: SYS2.VTAPE. SYS3.VTAPE. (dataData sets that are not altered by product STCs,; this can be more specific) The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS2.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&lttstcaudt>) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(&lttstcaudt>) DSN(SYS2.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(authorized users) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(VTAPE STCs) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(&ltsyspaudt>) DSN(SYS3.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&lttstcaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(&lttstcaudt>) DSN(SYS3.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(authorized users) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(VTAPE STCs) DSN(SYS3.VTAPE.) ACCESS(R)

V-224632 in V7R2

Check text

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(VTASTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZVTA0001). Verify that the accesses to the CA VTAPE STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set rules for the data sets restrictsrestrict READ access to auditors and authorized users. ___ The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to systems programming personnel and Tape Management personnel. ___ The TSS data set rules for the data sets restrictsrestrict WRITE and/or greater access to the CA VTAPE's STC(s) and/or batch user(s).

Fix text

The ISSO will ensure that WRITE and/or greater access to CA VTAPE STC data sets is limited to systems programmers, Tape Management personnel and/or CA VTAPE's STC(s) and/or batch user(s) only. ReadREAD access can be given to auditors and authorized users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater 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 (ACP) active on the system. Data sets to be protected will be: SYS3.VTAPE (dataData sets that are altered by the product's STCs,; this can be more specific) The following commands are provided as a sample for implementing data set controls: TSS PERMIT(&ltsyspaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(&lttapeaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(&lttstcaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(VTAPE STCs) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(&ltaudtaudt>) DSN(SYS3.VTAPE) ACCESS(R) TSS PERMIT(authorize user) DSN(SYS3.VTAPE) ACCESS(R)

V-224633 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review each CA VTAPE STC/Batch ACID(s). forIf the following: ___ Defined withattributes Facilityare ofdefined, STCthis and/oris BATCHnot fora SVTS and SVTASfinding. ___ IsFACILITY(STC, sourced to the BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR.) NOSUSPEND

Fix text

The CA VTAPE systemsystems programmer and the IAOISSO will ensure that a product's Started Task(s) is properly identified/defined to the Systemsystem ACP. If the product requires a Started Task, verify that it is properly defined to the Systemsystem ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. A sample is provided here: TSS CREATE(SVTS) TYPE(USER) - NAME('CA VTAPE') DEPT(xxxx) - FAC(STC) - PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND TSS CREATE(SVTSAS) TYPE(USER) - NAME('CA VTAPE') DEPT(xxxx) - FAC(STC) - PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

Discussion

CA VTAPE requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.

V-224634 in V7R2

Check text

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZVTA0032). VerifyIf that the CA VTAPE started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix text

The CA VTAPE systemsystems programmer and the IAOISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the Systemsystem ACP. A unique ACID must be assigned for the CA VTAPE started task(s) thruthrough a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(CVTS) ACID(CVTS) TSS ADD(STC) PROCNAME(CVTSAS) ACID(CVTSAS)

Discussion

Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.

V-224635 in V7R2