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

z/OS TADz for TSS Security Technical Implementation Guide

V7R1 · · · Released 02 Apr 2025 · 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.
Digest of Updates vs. V6R7 · 23 Nov 2022 ✎ 1

Comparison against the immediately-prior release (V6R7). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 1

  • V-225608 Medium descriptioncheckfix Tivoli Asset Discovery for z/OS (TADz) install data sets are not properly protected.
Sort by
b
Tivoli Asset Discovery for z/OS (TADz) install data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-225608 - SV-225608r1082573_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZTADT000
Vuln IDs
  • V-225608
  • V-16932
Rule IDs
  • SV-225608r1082573_rule
  • SV-28471
Tivoli Asset Discovery for z/OS (TADz) Install data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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-27308r1070318_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0000) Verify that access to the TADz Install data sets are properly restricted. The TSS data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. The TSS data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.

Fix: F-27296r1082573_fix

The ISSO will ensure that update and allocate/create access to program product data sets is limited to system programmers only, and all update and allocate/create access is logged. Auditors should have read access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and allocate/create access and if required that all update and allocate/create access is logged. The installing systems programmer will identify if any additional groups have update 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.TADZ SYS2.TADZ .V-.SHSIMOD1 (optional fully-qualified APF). SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: TSS PERMIT(syspaudt) DSN(SYS2.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS2.TADZ.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS2.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys2.tadz.*.shsimod1) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys2.tadz.*.shsimod1) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS2.TADZ.*.shsimod1) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TADZ.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TADZ.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(audtaudt) DSN(SYS3.TADZ.) ACCESS(R)

b
Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-225609 - SV-225609r958616_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZTADT001
Vuln IDs
  • V-225609
  • V-17067
Rule IDs
  • SV-225609r958616_rule
  • SV-28549
Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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-27309r868760_chk

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0001) For all (TADz) STC and/or batch data sets: If the UPDATE or greater access is restricted to systems programming personnel and the product STC(s) and/or batch job(s) this is not a finding. If any job scheduling products are in use and access is restricted to READ this is not a finding. If auditors have READ access this is not a finding.

Fix: F-27297r868761_fix

Grant update and alter access to Tivoli Asset Discovery for z/OS (TADz) STC and/or batch data sets are limited to systems programmers and TADz STC and/or batch jobs only. Grant Read access to any scheduling products that are in use. Grant Read access to auditors at the ISSO's discretion. 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. Identify if any additional groups have update access for specific data sets, and assure that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: TSS PERMIT(syspaudt) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.iq*.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.iq*.) ACCESS(ALL) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.uiq.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.uiq.) ACCESS(ALL) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.um.) ACCESS(R) TSS PERMIT(syspaudt) DSN(sys3.tadz.*.um.) ACCESS(ALL) TSS PERMIT(tadzmon) DSN(sys3.tadz.*.um.) ACCESS(ALL) TSS PERMIT(tadzinq) DSN(sys3.tadz.*.um.) ACCESS(ALL)

b
Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-225610 - SV-225610r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZTADT030
Vuln IDs
  • V-225610
  • V-17452
Rule IDs
  • SV-225610r958482_rule
  • SV-28555
Tivoli Asset Discovery for z/OS (TADz) requires a started task(s) that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system Access Control Program (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-27310r472629_chk

Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) Review each TADz STC/Batch ACID(s) for the following: ___ Is defined with Facility of STC and/or BATCH. ___ Is sourced to the INTRDR. If all of the above are true, there is NO FINDING. If any of the above is untrue, this is a FINDING.

Fix: F-27298r472630_fix

The TADz Systems Programmer and ISSO will ensure that the started task(s) for TADz is properly defined. Define the started task for TADz. Example: TSS CRE(TADZMON) DEPT(Dept) NAME('TADz STC') - FAC(STC) PASSWORD(password,0) - SOURCE(INTRDR)

b
IBM Tivoli Asset Discovery for zOS (TADz) Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
IA-2 - Medium - CCI-000764 - V-225611 - SV-225611r958482_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZTADT032
Vuln IDs
  • V-225611
  • V-17454
Rule IDs
  • SV-225611r958482_rule
  • SV-28562
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-27311r472632_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(ZTAD0032) Verify that the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) is (are) defined in the TSS STC record.

Fix: F-27299r472633_fix

The IBM Tivoli Asset Discovery for zOS (TADz) 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 IBM Tivoli Asset Discovery for zOS (TADz) 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(TADZMON) ACID(TADZMON)