Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

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

V7R2 · · · Released 01 Oct 2025 · 10 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

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.
Digest of Updates vs. V7R1 · 30 Jan 2025 ✎ 10

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 10

  • V-224649 Medium check CL/SuperSession profile options are set improperly.
  • V-224650 Medium check CL/SuperSession must be properly configured to generate SMF records for audit trail and accounting reports.
  • V-224651 Medium checkfix CL/SuperSession Install data sets must be properly protected.
  • V-224652 Medium checkfix CL/SuperSession STC data sets must be properly protected.
  • V-224653 Medium descriptioncheckfix CL/SuperSession Started Task name is not properly identified/defined to the system ACP.
  • V-224654 Medium checkfix CL/SuperSession Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
  • V-224655 Medium check CL/SuperSession is not properly defined to the Facility Matrix Table for Top Secret.
  • V-224656 Medium check CL/SuperSession's Resouce Class is not defined or active in the ACP.
  • V-224657 Medium check CL/SuperSession KLVINNAM member must be configured in accordance with security requirements.
  • V-224658 Medium check CL/SuperSession APPCLASS member is not configured in accordance with the proper security requirements.
Sort by
b
CL/SuperSession profile options are set improperly.
AC-11 - Medium - CCI-000057 - V-224649 - SV-224649r1145864_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000057
Version
ZCLS0040
Vuln IDs
  • V-224649
  • V-18014
Rule IDs
  • SV-224649r1145864_rule
  • SV-27197
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.
Checks: C-26332r1145863_chk

The following steps are necessary for reviewing the CL/SuperSession options: Request online access from the site administrator to view CL/SuperSession parameter settings. Once access to the CL/SuperSession Main Menu has been obtained, select the option for the ADMINISTRATOR menu. From the ADMINISTRATOR menu, select the option for the PROFILE SELECTION menu. From the PROFILE SELECTION menu, select the View GLOBAL Profile option. After selection of the View GLOBAL Profile option, the Update GLOBAL Profile menu appears. From this menu select the profile to be reviewed: - To view the Common profile, select: _Common - To view the SUPERSESSION profile, select: _SupSess Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCLS0040). Compare the security parameters as specified in the Required CL/SuperSession Common Profile Options and Required CL/SuperSession Profile Options Tables in the z/OS STIG Addendum against the settings in CL/SuperSession. If all options as specified in the Required CL/SuperSession Common Profile Options and Required CL/SuperSession Profile Options Tables in the z/OS STIG Addendum are in effect, this is not a finding.

Fix: F-26320r1041400_fix

The systems programmer and ISSO will review all session manager security parameters and control options for compliance with the requirements of the z/OS STIG Addendum Required CL/SuperSession Common Profile Options and Required CL/SuperSession Profile Options Tables. Verify that the options are set properly.

b
CL/SuperSession must be properly configured to generate SMF records for audit trail and accounting reports.
AU-12 - Medium - CCI-000172 - V-224650 - SV-224650r1145866_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000172
Version
ZCLS0041
Vuln IDs
  • V-224650
  • V-22689
Rule IDs
  • SV-224650r1145866_rule
  • SV-27198
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.
Checks: C-26333r1145865_chk

Version 3 of CL/SuperSession Review the member KLKINNAF in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure to determine SMF number. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Version 2 of CL/SuperSession Review the member KLVINNAF in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure to determine SMF number. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Refer to the following report produced by the z/OS Data Collection: - EXAM.RPT(SMFOPTS). Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCLS0041). If the SMF= field specifies an SMF record number and the SMFOPTS report specifies that SMF is writing the record number specified by SMF=, this is not a finding.

Fix: F-26321r1041403_fix

Ensure that the Session Manager generates SMF records for audit trail and accounting reports. To provide an audit trail of user activity in CL/SuperSession, configure the Network Accounting Facility (NAF) to require SMF recording of accounting and audit data. Accounting to the journal data set is optional at the discretion of the site. To accomplish this for version 3 of CL/SuperSession, configure the following NAF startup parameters in the KLKINNAF member of the RLSPARM initialization parameter library as follows: DSNAME= dsname - Name of the NAF journal data set. Required only if the site is collecting accounting and audit data in the journal data set in addition to the SMF data. MOD - If the journal data set is used, this parameter should be set to ensure that logging data in the data set is not overwritten. SMF=nnn - SMF record number. This field is mandatory to ensure that CL/SuperSession data is always written to the SMF files.

b
CL/SuperSession Install data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224651 - SV-224651r1145869_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZCLST000
Vuln IDs
  • V-224651
  • V-16932
Rule IDs
  • SV-224651r1145869_rule
  • SV-27092
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.
Checks: C-26334r1145867_chk

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: F-26322r1145868_fix

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)

b
CL/SuperSession STC data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224652 - SV-224652r1146313_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZCLST001
Vuln IDs
  • V-224652
  • V-17067
Rule IDs
  • SV-224652r1146313_rule
  • SV-27098
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.
Checks: C-26335r1145870_chk

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

Fix: F-26323r1146312_fix

Ensure that WRITE and/or greater access to CL/SuperSession STC data sets 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 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 WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific. The following are an example of data sets 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 data set controls: TSS PERMIT(syspaudt) DSN(sys3.omegamon.rlsnaf) ACCESS(ALL) TSS PERMIT(kls) DSN(sys3.omegamon.rlsnaf) ACCESS(ALL) TSS PERMIT(audtaudt) DSN(sys3.omegamon.rlsnaf) ACCESS(READ) TSS PERMIT(all) DSN(sys3.omegamon.rlsnaf) ACCESS(READ) TSS PERMIT(syspaudt) DSN(sys3.omegamon.rlsnam) ACCESS(ALL) TSS PERMIT(kls) DSN(sys3.omegamon.rlsnam) ACCESS(ALL) TSS PERMIT(audtaudt) DSN(sys3.omegamon.rlsnam) ACCESS(READ) TSS PERMIT(all) DSN(sys3.omegamon.rlsnam) ACCESS(READ) TSS PERMIT(syspaudt) DSN(sys3.omegamon.rlstdb) ACCESS(ALL) TSS PERMIT(kls) DSN(sys3.omegamon.rlstdb) ACCESS(ALL) TSS PERMIT(audtaudt) DSN(sys3.omegamon.rlstdb) ACCESS(READ) TSS PERMIT(all) DSN(sys3.omegamon.rlstdb) ACCESS(READ) TSS PERMIT(syspaudt) DSN(sys3.omegamon.rlsvlog) ACCESS(ALL) TSS PERMIT(kls) DSN(sys3.omegamon.rlsvlog) ACCESS(ALL) TSS PERMIT(audtaudt) DSN(sys3.omegamon.rlsvlog) ACCESS(READ) TSS PERMIT(all) DSN(sys3.omegamon.rlsvlog) ACCESS(READ)

b
CL/SuperSession Started Task name is not properly identified/defined to the system ACP.
IA-2 - Medium - CCI-000764 - V-224653 - SV-224653r1145875_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZCLST030
Vuln IDs
  • V-224653
  • V-17452
Rule IDs
  • SV-224653r1145875_rule
  • SV-28592
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.
Checks: C-26336r1145873_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS). Review the CL/SuperSession STC/Batch ACID(s). If the following attributes are defined, this is not a finding. FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND MASTFAC(KLS)

Fix: F-26324r1145874_fix

The Systems Programmer and ISSO will ensure that the started task for CL/SuperSession is properly defined. Review all session manager security parameters and control options for compliance. Develop a plan of action and implement the changes as specified. Define the started task userid KLS for CL/SuperSession. Example: TSS CRE(KLS) DEPT(Dept) NAME('CL/SuperSession STC') - FAC(STC) MASTFAC(KLS) PASSWORD(password,0) - SOURCE(INTRDR) NOSUSPEND

b
CL/SuperSession Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
IA-2 - Medium - CCI-000764 - V-224654 - SV-224654r1145878_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZCLST032
Vuln IDs
  • V-224654
  • V-17454
Rule IDs
  • SV-224654r1145878_rule
  • SV-27238
Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.
Checks: C-26337r1145876_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC). Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZCLS0032). If the CL/SuperSession started task(s) is (are) defined in the TSS STC record, this is not a finding.

Fix: F-26325r1145877_fix

The CL/SuperSession systems programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the system ACP. A unique ACID must be assigned for the CL/SuperSession started task(s) through a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(KLS) ACID(KLS)

b
CL/SuperSession is not properly defined to the Facility Matrix Table for Top Secret.
IA-2 - Medium - CCI-000764 - V-224655 - SV-224655r1145880_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZCLST036
Vuln IDs
  • V-224655
  • V-17469
Rule IDs
  • SV-224655r1145880_rule
  • SV-27240
Improperly defined security controls for the Product could result in the compromise of the network, operating system, and customer data.
Checks: C-26338r1145879_chk

Refer to the following reports produced by the TSS Data Collection: - TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values. - TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup. If the CL/SuperSession Facility Matrix table is defined as stated below, this is not a finding. *KLS CL/SUPERSESSION FACILITY(USERxx=NAME=KLS) FACILITY(KLS=MODE=FAIL,ACTIVE,SHRPRF) FACILITY(KLS=PGM=KLV,NOASUBM,NOABEND,NOXDEF) FACILITY(KLS=ID=xx,MULTIUSER,RES,LUMSG,STMSG,WARNPW,SIGN(M)) FACILITY(KLS=NOINSTDATA,NORNDPW,AUTHINIT,NOPROMPT,NOAUDIT) FACILITY(KLS=NOTSOC,LOG(INIT,SMF,MSG,SEC9))

Fix: F-26326r519783_fix

Define the CT/Engine started task name KLS as a Facility to TOP SECRET in the Facility Matrix Table using the following example: *KLS CL/SUPERSESSION FACILITY(USERxx=NAME=KLS) FACILITY(KLS=MODE=FAIL,ACTIVE,SHRPRF) FACILITY(KLS=PGM=KLV,NOASUBM,NOABEND,NOXDEF) FACILITY(KLS=ID=xx,MULTIUSER,RES,LUMSG,STMSG,WARNPW,SIGN(M)) FACILITY(KLS=NOINSTDATA,NORNDPW,AUTHINIT,NOPROMPT,NOAUDIT) FACILITY(KLS=NOTSOC,LOG(INIT,SMF,MSG,SEC9))

b
CL/SuperSession's Resouce Class is not defined or active in the ACP.
CM-4 - Medium - CCI-000336 - V-224656 - SV-224656r1145883_rule
RMF Control
CM-4
Severity
M
CCI
CCI-000336
Version
ZCLST038
Vuln IDs
  • V-224656
  • V-18011
Rule IDs
  • SV-224656r1145883_rule
  • SV-27190
Failure to use a robust ACP to control a product could potentially compromise the integrity and availability of the MVS operating system and user data.
Checks: C-26339r1145881_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#RDT). If the resource class of KLS is defined in the Resource Definition Table (RDT), this is not a finding.

Fix: F-26327r1145882_fix

Add the resource KLS to the TOP SECRET RDT using the following TSS command example: TSS ADD(RDT) RESCLASS(KLS) RESCODE(xx) (where xx is an unused hex value)

b
CL/SuperSession KLVINNAM member must be configured in accordance with security requirements.
CM-7 - Medium - CCI-000381 - V-224657 - SV-224657r1145885_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
ZCLST042
Vuln IDs
  • V-224657
  • V-22690
Rule IDs
  • SV-224657r1145885_rule
  • SV-27258
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.
Checks: C-26340r1145884_chk

Version 3 of CL/SuperSession Review the member KLKINNAM in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Version 2 of CL/SuperSession Review the member KLVINNAM in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCLS0042). If one of the following configuration settings is specified for each control point defined in the KLKINNAM member for version 3 of CL/SuperSession or KLVINNAM member for version 2 of CL/SuperSession, this is not a finding. DEFAULT DSNAME(SYS3.OMEGAMON.qualifier.RLSNAM) - RACF - CLASSES=APPCLASS - NODB - EXIT=KLSTSNEV (The following is for z/OS CAC logon processing) DEFAULT DSNAME(SYS3.OMEGAMON.qualifier.RLSNAM) - SAF - CLASSES=APPCLASS - NODB - EXIT=KLSNFPTX or KLSTSPTX

Fix: F-26328r952263_fix

Ensure that the parameter options for member KLKINNAM for version 3 of CL/SuperSession or KLVINNAM for version 2 CL/SuperSession are coded to the specifications below. (Note: The data set identified below is an example of a possible installation. The actual data set is determined when the product is actually installed on a system through the product's installation guide and can be site specific.) Review the member KLKINNAM or KLVINNAM in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Ensure all session manager security parameters and control options are in compliance according to the following: DEFAULT DSNAME(SYS3.OMEGAMON.qualifier.RLSNAM) - RACF - CLASSES=APPCLASS - NODB - EXIT=KLSTSNEV (The following is for z/OS CAC logon processing) DEFAULT DSNAME(SYS3.OMEGAMON.qualifier.RLSNAM) - SAF - CLASSES=APPCLASS - NODB - EXIT=KLSNFPTX or KLSTSPTX

b
CL/SuperSession APPCLASS member is not configured in accordance with the proper security requirements.
CM-7 - Medium - CCI-000381 - V-224658 - SV-224658r1145887_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
ZCLST043
Vuln IDs
  • V-224658
  • V-22691
Rule IDs
  • SV-224658r1145887_rule
  • SV-27261
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.
Checks: C-26341r1145886_chk

Review the member APPCLASS in the TLVPARM DD statement concatenation of the CL/Supersession STC procedure. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Automated Analysis Refer to the following report produced by the z/OS Data Collection: - PDI(ZCLS0043). If the parameters for the member APPCLASS are configured as follows, this is not a finding. VGWAPLST EXTERNAL=KLS

Fix: F-26329r1041410_fix

The systems programmer and ISSO will ensure that the parameter options for member APPCLASS are coded to the below specifications. Review the member APPCLASS in the TLVPARM DD statement concatenation of the CL/SuperSession STC procedure. (This member is located in SYS3.OMEGAMON.qualifier.RLSPARM.) Ensure all session manager security parameters and control options are in compliance according to the following: VGWAPLST EXTERNAL=KLS