Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS CA VTAPE for TSS Security Technical Implementation Guide

V6R4 · · · Released 27 Jul 2020 · 4 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Sort by
b
CA VTAPE installation data sets are not properly protected.
AC-3 - Medium - CCI-000213 - V-224632 - SV-224632r519688_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZVTAT000
Vuln IDs
  • V-224632
  • V-16932
Rule IDs
  • SV-224632r519688_rule
  • SV-33826
CA VTAPE installation 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.
Checks: C-26315r519686_chk

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. ___ The TSS data set rules for the data sets restricts READ access to all authorized users. ___ The TSS data set rules for the data sets restricts UPDATE and/or ALL access to systems programming personnel. ___ The TSS data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALL access are logged.

Fix: F-26303r519687_fix

The IAO will ensure that update and allocate access to CA VTAPE installation data sets is limited to System Programmers only, and all update and allocate access is logged. Read 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 update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS2.VTAPE. SYS3.VTAPE. (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: TSS PERMIT(<syspaudt>) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS2.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<tstcaudt>) DSN(SYS2.VTAPE.) ACCESS(R) TSS PERMIT(<tstcaudt>) DSN(SYS2.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<audtaudt>) 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(<syspaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS3.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<tstcaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(<tstcaudt>) DSN(SYS3.VTAPE.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<audtaudt>) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(authorized users) DSN(SYS3.VTAPE.) ACCESS(R) TSS PERMIT(VTAPE STCs) DSN(SYS3.VTAPE.) ACCESS(R)

b
CA VTAPE STC data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224633 - SV-224633r519691_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZVTAT001
Vuln IDs
  • V-224633
  • V-17067
Rule IDs
  • SV-224633r519691_rule
  • SV-33829
CA VTAPE STC 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.
Checks: C-26316r519689_chk

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 restricts READ access to auditors and authorized users. ___ The TSS data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel and Tape Management personnel. ___ The TSS data set rules for the data sets restricts WRITE and/or greater access to the CA VTAPE’s STC(s) and/or batch user(s).

Fix: F-26304r519690_fix

The IAO will ensure that WRITE and/or greater access to CA VTAPE STC data sets is limited to System 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 data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.VTAPE (data 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(<syspaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(<tapeaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(<tstcaudt>) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(VTAPE STCs) DSN(SYS3.VTAPE) ACCESS(ALL) TSS PERMIT(<audtaudt>) DSN(SYS3.VTAPE) ACCESS(R) TSS PERMIT(authorize user) DSN(SYS3.VTAPE) ACCESS(R)

b
CA VTAPE Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224634 - SV-224634r519694_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZVTAT030
Vuln IDs
  • V-224634
  • V-17452
Rule IDs
  • SV-224634r519694_rule
  • SV-33832
CA VTAPE requires a started task that will be restricted to certain resources, datasets and other system functions. By 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.
Checks: C-26317r519692_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) Review each CA VTAPE STC/Batch ACID(s) for the following: ___ Defined with Facility of STC and/or BATCH for SVTS and SVTAS. ___ Is sourced to the INTRDR.

Fix: F-26305r519693_fix

The CA VTAPE system programmer and the IAO 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. 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

b
CA VTAPE Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
IA-2 - Medium - CCI-000764 - V-224635 - SV-224635r519697_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZVTAT032
Vuln IDs
  • V-224635
  • V-17454
Rule IDs
  • SV-224635r519697_rule
  • SV-33834
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.
Checks: C-26318r519695_chk

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) Verify that the CA VTAPE started task(s) is (are) defined in the TSS STC record.

Fix: F-26306r519696_fix

The CA VTAPE system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique ACID must be assigned for the CA VTAPE started task(s) thru 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)