z/OS ROSCOE for TSS STIG Version Comparison

There are 1 differences between versions v6 r7 (Jan. 20, 2015) (the "left" version) and v6 r9 (Oct. 24, 2024) (the "right" version).

Check ZROST020 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

ROSCOE resources must be properly defined and protected.

Check Content

Refer to the following report produced by the TSS Data Collection and Data Set and Resource Data Collection: - SENSITVE.RPT(ZROS0020) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZROS0020) Ensure that all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum. Note: Wherever an access or user group is missing, use the Site Security Plan to determine access and/or user group. If the following guidance is true, this is not a finding. ___ The TSS resources and/or generic equivalent as designated in the above table are owned or DEFPROT is specified for the resource class. ___ The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table. ___ The TSS resource logging is specified as designated in the above table.

Discussion

ROSCOE can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality and integrity of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain non systems personnel with read only authority.

Fix

The ISSO will work with the systems programmer to verify that the following are properly specified in the ACP. (Note: The resources and/or resource prefixes identified below are examples of a possible installation. The actual resources and/or resource prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Ensure that all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum. Use CA ROSCOE Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for ROSCOE ensure the following guidelines are followed: The TSS resources and/or generic equivalent as designated in the above table are owned or DEFPROT is specified for the resource class. The TSS resource access authorizations restrict access to the appropriate personnel as designated in the above table. The TSS resource logging is specified as designated in the above table. The following commands are provided as a sample for implementing resource controls: TSS ADD(dept-acid) ROSRES(rosid) TSS PERMIT(ALL) ROSRES(rosid.ROSCMD.ETSO) ACCESS(READ) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.MONITOR.) ACCESS(ALL) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.MONITOR.AMS) ACCESS(ALL) TSS PERMIT(ALL) ROSRES(rosid.ROSCMD.MONITOR.AMS) ACCESS(READ) TSS PERMIT(syspaudt) ROSRES(rosid.ROSCMD.) ACCESS(ALL)