STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 7 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to z/OS CL/SuperSession for TSS Security Technical Implementation Guide

V-224651

CAT II (Medium)

CL/SuperSession Install data sets must be properly protected.

Rule ID

SV-224651r1145869_rule

STIG

z/OS CL/SuperSession for TSS Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499CCI-002234

Discussion

CL/SuperSession 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.

Check Content

Refer to the following report produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(KLSRPT).

Automated Analysis:
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZCLS0000).

Verify that access to the CL/SuperSession Install data sets are properly restricted. If the following guidance is true, this is not a finding.

The TSS data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel.

The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

Fix Text

Ensure that WRITE and/or greater access to CL/SuperSession install data sets are limited to systems programmers only, and all WRITE and/or greater access is logged.

The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater 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 ACP (Access Control Program ) active on the system.

The following are an example of data sets to be protected:
sys2.omegamon. 
sys2.omegamon.*.tlsload
sys2.omegamon.*.tlvload
sys3.omegamon.
sys3.omegamon.rlsload

The following commands are provided as an example for implementing data set controls: 
TSS PERMIT(syspaudt) DSN(sys2.omegamon.) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlsload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlsload) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlvload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlvload) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.*.rlsload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.*.rlsload) ACCESS(all) ACTION(audit)