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 ACF2 Security Technical Implementation Guide

V-224284

CAT II (Medium)

CL/SuperSession Install datasets must be properly protected.

Rule ID

SV-224284r1141413_rule

STIG

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

Version

V7R2

CCIs

CCI-001499CCI-002234

Discussion

CL/SuperSession Install datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets 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 dataset and Resource Data Collection:

- SENSITVE.RPT(KLSRPT).

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

- PDI(ZCLS0000).

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

The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel.

The ACF2 dataset rules for the datasets do not 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 datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. Auditors should have READ access.

The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have UPDATE access for specific datasets, and once documented will work with the ISSO to ensure that they are properly  restricted to the ACP (Access Control Program ) active on the system.

The following datasets are an example of datasets to be protected: 

SYS2.OMEGAMON
SYS2.OMEGAMON.V-.TLSLOAD
SYS2.OMEGAMON.V-.TLVLOAD
SYS3.OMEGAMON
SYS3.OMEGAMON.RLSLOAD

The following commands are provided as an example for implementing dataset controls: 

$KEY(SYS2)
OMEGAMON.- UID(syspaudt) R(A) W(L) A(L) E(A)
OMEGAMON.V-.TLSLOAD UID(syspaudt) R(A) W(L) A(L) E(A) 
OMEGAMON.V-.TLVLOAD UID(syspaudt) R(A) W(L) A(L) E(A) 
OMEGAMON.- UID(audtaudt) R(A) E(A)

$KEY(SYS3)
OMEGAMON.- UID(syspaudt) R(A) W(L) A(L) E(A)
OMEGAMON.RLSLOAD UID(syspaudt) R(A) W(L) A(L) E(A) 
OMEGAMON.- UID(audtaudt) R(A) E(A)