z/OS TADz for RACF Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
- RMF Control
- AC-3
- Severity
- M
- CCI
- CCI-000213
- Version
- ZTADR000
- Vuln IDs
-
- V-224537
- V-16932
- Rule IDs
-
- SV-224537r855214_rule
- SV-28470
Checks: C-26220r520898_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-26208r520899_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
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- ZTADR001
- Vuln IDs
-
- V-224538
- V-17067
- Rule IDs
-
- SV-224538r868557_rule
- SV-28548
Checks: C-26221r868555_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-26209r868556_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: 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)
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000764
- Version
- ZTADR030
- Vuln IDs
-
- V-224539
- V-17452
- Rule IDs
-
- SV-224539r520906_rule
- SV-28554
Checks: C-26222r520904_chk
Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) If the userid(s) for the TADz started task is defined to the security database, there is NO FINDING. If the userid(s) for the TADz started task is not defined to the security database, this is a FINDING.
Fix: F-26210r520905_fix
The Systems Programmer and ISSO 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')
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000764
- Version
- ZTADR032
- Vuln IDs
-
- V-224540
- V-17454
- Rule IDs
-
- SV-224540r520909_rule
- SV-28561
Checks: C-26223r520907_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-26211r520908_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