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

z/OS TADz for RACF STIG

V6R4 · · · Released 20 Jan 2015 · 4 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

Digest of Updates vs. V6R3 · 28 Oct 2011 ✎ 3

Comparison against the immediately-prior release (V6R3). 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 3

  • V-16932 Medium description Tivoli Asset Discovery for z/OS (TADz) Install data sets are not properly protected.
  • V-17067 Medium description Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are not properly protected.
  • V-17452 Medium description Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) is not properly identified / defined to the system ACP.
Sort by
b
Tivoli Asset Discovery for z/OS (TADz) Install data sets are not properly protected.
AC-3 - Medium - CCI-000213 - V-16932 - SV-28470r1_rule
RMF Control
AC-3
Severity
M
CCI
CCI-000213
Version
ZTADR000
Vuln IDs
  • V-16932
Rule IDs
  • SV-28470r1_rule
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.Information Assurance OfficerSystems ProgrammerDCSL-1, ECAR-1, ECAR-2, ECCD-1, ECCD-2
Checks: C-28857r1_chk

a) 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) b) Verify that access to the TADz Install data set are properly restricted. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The RACF 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. c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.

Fix: F-25889r1_fix

The IAO will ensure that update and alter access to program product data sets is limited to System Programmers and all update and allocate 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 alter access and if required that all update and alter access is logged. He will identify if any additional groups have update 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 set prefix to be protected will be: SYS2.TADZ. SYS2.TADZ.*.SHSIMOD1.** (optional fully-qualified APF). SYS3.TADZ. The following commands are provided as a sample for implementing dataset controls: ad 'sys2.TADZ.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: TADZ') pe 'sys2.TADZ.**' id(syspaudt) acc(a) pe 'sys2.tadz.**' id(audtaudt) ad 'sys2.tadz.*.shsimod1.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: Tivoli Asset Discovery APF DS') pe 'sys2.tadz.*.shsimod1.**' id(syspaudt) acc(a) pe 'sys2.tadz.*.shsimod1.**' id(audtaudt) ad 'sys3.TADZ.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('TADZ Vendor Datasets') pe 'sys3.TADZ.**' id(syspaudt) acc(a) pe 'sys3.tadz.**' id(audtaudt) setr generic(dataset) refresh

b
Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-17067 - SV-28548r1_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZTADR001
Vuln IDs
  • V-17067
Rule IDs
  • SV-28548r1_rule
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.Information Assurance OfficerSystems ProgrammerDCSL-1, ECAR-1, ECAR-2, ECAR-3, ECCD-1, ECCD-2
Checks: C-29339r1_chk

a) 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) b) Verify that acess to the TADz STC and/or batch data sets are properly restricted. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to the product STC(s) and/or batch job(s). c) If all of the above are untrue, there is NO FINDING. d) If any of the above is true, this is a FINDING.

Fix: F-26366r1_fix

The IAO will ensure that update and alter access to Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are limited to system programmers and TADz STC and/or batch jobs only. Read access may be granted to auditors at the IAOs discretion. 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 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.TADZ The following commands are provided as a sample for implementing dataset controls: ad 'sys3.tadz.*.iq*.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') ad 'sys3.tadz.*.uiq.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') ad 'sys3.tadz.*.um.**' uacc(none) owner(daztech) - audit(success(update) failures(read)) - data('TADZ Output Data') pe 'sys3.tadz.*.iq*.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.iq*.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.iq*.**' id(tadzinq) acc(a) pe 'sys3.tadz.*.uiq.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.uiq.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.uiq.**' id(tadzinq) acc(a) pe 'sys3.tadz.*.um.**' id(syspaudt) acc(a) pe 'sys3.tadz.*.um.**' id(tadzmon) acc(a) pe 'sys3.tadz.*.um.**' id(tadzinq) acc(a)

b
Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) is not properly identified / defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-17452 - SV-28554r1_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZTADR030
Vuln IDs
  • V-17452
Rule IDs
  • SV-28554r1_rule
Products that require a started task will require that the started task 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. Information Assurance OfficerSystems ProgrammerECCD-1, ECCD-2
Checks: C-28853r1_chk

a) Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) b) If the userid(s) for the TADz started task is defined to the security database, there is NO FINDING. c) If the userid(s) for the TADz started task is not defined to the security database, this is a FINDING.

Fix: F-25885r1_fix

The Systems Programmer and IAO will ensure that the started task for TADz is properly defined. Define the started task for TADz. Example: au tadzmon name('stc, tivoli AD') nopass - dfltgrp(stc) owner(stc) - data('stc for tivoli asset discovery')

b
IBM Tivoli Asset Discovery for zOS (TADz) Started task(s) must be properly defined to the STARTED resource class for RACF.
IA-2 - Medium - CCI-000764 - V-17454 - SV-28561r1_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZTADR032
Vuln IDs
  • V-17454
Rule IDs
  • SV-28561r1_rule
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.Information Assurance OfficerECCD-1, ECCD-2
Checks: C-20575r1_chk

Refer to the following report produced by the RACF Data Collection: - DSMON.RPT(RACSPT) Automated Analysis Refer to the following report produced by the RACF Data Collection: - PDI(ZTAD0032) Verify that the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry.

Fix: F-339r1_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 userid must be assigned for the IBM Tivoli Asset Discovery for zOS (TADz) started task(s) thru a corresponding STARTED class entry. The following sample set of commands is shown here as a guideline: rdef started TADZMON.** uacc(none) owner(admin) audit(all(read)) stdata(user(TADZMON) group(stc)) setr racl(started) ref