acceptedz/OS TADz for ACF2 Security Technical Implementation GuideThis 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.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 02 Apr 20253.51.10.07I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000080<GroupDescription></GroupDescription>ZTADA000Tivoli Asset Discovery for z/OS (TADz) Install data sets are not properly protected.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS TADz for ACF2DISADPMS TargetzOS TADz for ACF24130V-16932SV-28469CCI-001499CCI-002234The ISSO will ensure that update and allocate access to program product data sets is limited to system programmers only, 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 allocate 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
SYS3.TADZ
The following commands are provided as a sample for implementing dataset controls:
$KEY(SYS2)
TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A)
TADZ.V-.SHSIMOD1 UID(syspaudt) R(A) W(L) A(L) E(A)
TADZ.- UID(audtaudt) R(A) E(A)
$KEY(SYS3)
TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A)
TADZ.- UID(audtaudt) R(A) E(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)
Verify that access to the TADz Install data sets are properly restricted.
The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel.
The ACF2 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.SRG-OS-000259<GroupDescription></GroupDescription>ZTADA001Tivoli Asset Discovery for zOS (TADz) STC and/or batch data sets are not properly protected.<VulnDiscussion>Tivoli Asset Discovery for zOS (TADz) STC 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS TADz for ACF2DISADPMS TargetzOS TADz for ACF24130SV-28547V-17067CCI-001499Grant update and alter access to Tivoli Asset Discovery for z/OS (TADz) STC and/or batch data sets are limited to system 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:
$KEY(SYS3)
TADZ.- UID(syspaudt) R(A) W(A) A(A) E(A)
TADZ.- UID(audtaudt) R(A) E(A)
TADZ.-.UM.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)
TADZ.-.IQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)
TADZ.-.UIQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A)
TADZ.- UID(stc id TADZMON) R(A) W(A) A(A) E(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)
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.SRG-OS-000104<GroupDescription></GroupDescription>ZTADA030Tivoli Asset Discovery for z/OS (TADz) Started Task name(s) must be properly identified / defined to the system ACP.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target zOS TADz for ACF2DISADPMS TargetzOS TADz for ACF24130SV-28612V-17452CCI-000764The TADz system programmer and the ISSO 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.
Example:
SET LID
CHANGE TADZMON STCRefer to the following report produced by the ACF2 Data Collection:
- ACF2CMDS.RPT(LOGONIDS)
Ensure the following field is completed for each STC logonid for the product:
STC
Ensure the following field is completed for each Batch logonid for the product:
JOB
If the logonids specified in (b) and/or (c) have all the required field is completed, this is not a FINDING.
If the logonids specified in (b) and/or (c) do not have the above field completed, this is a FINDING.