STIGUI

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

Version 7 · Released 2025-09-27 · 9 rules

This 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.

Rules in z/OS CL/SuperSession for RACF Security Technical Implementation Guide
Description
V-224461CAT II · MediumCL/SuperSession profile options are set improperly.Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data.
V-224462CAT II · MediumCL/SuperSession must be properly configured to generate SMF records for audit trail and accounting reports.Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications and compromise the confidentiality of customer data.
V-224463CAT II · MediumCL/SuperSession Install data sets must be properly protected.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.
V-224464CAT II · MediumCL/SuperSession STC data sets must be properly protected.CL/SuperSession 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.
V-224465CAT II · MediumCL/SuperSession Started Task name is not properly identified/defined to the system ACP.CL/SuperSession requires a started task that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.
V-224466CAT II · MediumCL/SuperSession Started task(s) must be properly defined to the STARTED resource class for RACF.Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could compromise the operating system, ACP, and customer data.
V-224467CAT II · MediumCL/SuperSessions Resouce Class must be defined or active in the ACP.Failure to use a robust ACP to control a product could compromise the integrity and availability of the MVS operating system and user data.
V-224468CAT II · MediumCL/SuperSession KLVINNAM member must be configured in accordance with security requirements.CL/SuperSession configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications and compromise the confidentiality of customer data.
V-224469CAT II · MediumCL/SuperSession APPCLASS member is not configured in accordance with the proper security requirements.Product configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly specified, security and operational controls may be weakened. This exposure may threaten the availability of the product applications, and compromise the confidentiality of customer data.