CL/SuperSession STC datasets must be properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224285	SRG-OS-000259	ZCLSA001	SV-224285r1141416_rule	2025-09-27	7

Description
CL/SuperSession STC 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
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(KLSSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCLS0001). Verify that the accesses to the CL/SuperSession STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors and authorized users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the product STC(s) and/or batch job(s).

ℹ️ Check

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(KLSSTC). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCLS0001). Verify that the accesses to the CL/SuperSession STC datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors and authorized users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to the product STC(s) and/or batch job(s).

✔️ Fix
Ensure that WRITE and/or greater access to CL/SuperSession STC datasets are limited to systems programmers and CL/SuperSession STC only. READ access can be given to auditors and authorized users. 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 WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific. The following datasets are an example of datasets to be protected: SYS3.OMEGAMON.RLSNAF SYS3.OMEGAMON.RLSNAM SYS3.OMEGAMON.RLSTDB SYS3.OMEGAMON.RLSVLOG The following commands are provided as an example for implementing dataset controls: $KEY(SYS3) OMEGAMON.RLSNAF UID() R(A) E(A) OMEGAMON.RLSNAF UID(audtaudt) R(A) E(A) OMEGAMON.RLSNAF UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAF UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAM UID() R(A) E(A) OMEGAMON.RLSNAM UID(audtaudt) R(A) E(A) OMEGAMON.RLSNAM UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAM UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSTDB UID() R(A) E(A) OMEGAMON.RLSTDB UID(audtaudt) R(A) E(A) OMEGAMON.RLSTDB UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSTDB UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSVLOG UID() R(A) E(A) OMEGAMON.RLSVLOG UID(audtaudt) R(A) E(A) OMEGAMON.RLSVLOG UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSVLOG UID(stc KLS) R(A) W(A) A(A) E(A)

✔️ Fix

Ensure that WRITE and/or greater access to CL/SuperSession STC datasets are limited to systems programmers and CL/SuperSession STC only. READ access can be given to auditors and authorized users. 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 WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific. The following datasets are an example of datasets to be protected: SYS3.OMEGAMON.RLSNAF SYS3.OMEGAMON.RLSNAM SYS3.OMEGAMON.RLSTDB SYS3.OMEGAMON.RLSVLOG The following commands are provided as an example for implementing dataset controls: $KEY(SYS3) OMEGAMON.RLSNAF UID(*) R(A) E(A) OMEGAMON.RLSNAF UID(audtaudt) R(A) E(A) OMEGAMON.RLSNAF UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAF UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAM UID(*) R(A) E(A) OMEGAMON.RLSNAM UID(audtaudt) R(A) E(A) OMEGAMON.RLSNAM UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSNAM UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSTDB UID(*) R(A) E(A) OMEGAMON.RLSTDB UID(audtaudt) R(A) E(A) OMEGAMON.RLSTDB UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSTDB UID(stc KLS) R(A) W(A) A(A) E(A) OMEGAMON.RLSVLOG UID(*) R(A) E(A) OMEGAMON.RLSVLOG UID(audtaudt) R(A) E(A) OMEGAMON.RLSVLOG UID(syspaudt) R(A) W(A) A(A) E(A) OMEGAMON.RLSVLOG UID(stc KLS) R(A) W(A) A(A) E(A)