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

z/OS CSSMTP for TSS Security Technical Implementation Guide

V7R1 · · · Released 02 Jul 2025 · 3 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. V6R6 · 23 Nov 2022 ✎ 3

Comparison against the immediately-prior release (V6R6). 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 3

  • V-224666 Medium descriptioncheckfix IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) STC data sets must be properly protected.
  • V-224667 Medium checkfix IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) Started Task name is not properly identified and/or defined to the system Access Control Program (ACP).
  • V-224668 Medium descriptionfix IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
Sort by
b
IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) STC data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224666 - SV-224666r1116163_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZSMTT001
Vuln IDs
  • V-224666
  • V-17067
Rule IDs
  • SV-224666r1116163_rule
  • SV-89727
IBM CSSMTP STC data sets have the ability 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-26355r1116161_chk

Examine the running started task for CSSMTP. Verify that access to the IBM CSSMTP STC data sets are properly restricted. The data sets to be protected are identified in the data set referenced in the DD statements of the CSSMTP started task(s) and/or batch job(s). Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(SMTPSTC) Automated Analysis: Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSMT0001) If the following guidance is true, this is not a finding: The TSS data set access authorizations restrict READ access to auditors. The TSS data set access authorizations restrict WRITE and/or greater access to systems programming personnel. The TSS data set access authorizations restrict WRITE and/or greater access to the product STC(s) and/or batch job(s).

Fix: F-26343r1116162_fix

Ensure that WRITE and/or greater access to the IBM CSSMTP STC data sets are limited to systems programmers and CSSMTP STC and/or batch jobs only. READ access can be given to auditors at the ISSOs discretion. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have what type of access and if required which type of access is logged. The installing systems programmer will identify any additional groups requiring access to specific data sets, and once documented the installing systems programmer will work with the ISSO to see that 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 commands are provided as an example for implementing data set controls: TSS PERMIT(audtaudt) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(R) TSS PERMIT(tstcaudt) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(R) TSS PERMIT(icststc) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(R) TSS PERMIT(syspaudt) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(ALL) TSS PERMIT(tstcaudt) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(ALL) TSS PERMIT(icststc) DSN(SYS3.TCPIP.CSSMTP.) ACCESS(ALL)

b
IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) Started Task name is not properly identified and/or defined to the system Access Control Program (ACP).
IA-2 - Medium - CCI-000764 - V-224667 - SV-224667r1116166_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZSMTT030
Vuln IDs
  • V-224667
  • V-17452
Rule IDs
  • SV-224667r1116166_rule
  • SV-37481
IBM CSSMTP requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
Checks: C-26356r1116164_chk

Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) Review each IBM CSSMTP STC/Batch ACID(s) for the following: Defined with Facility of STC (the TSS FACILITY Matrix Table entry defined for this product), and/or BATCH for CSSMTP. Is sourced to the INTRDR.

Fix: F-26344r1116165_fix

The IBM CSSMTP system programmer and the ISSO will ensure that a product's Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. A sample is provided here: TSS CREATE(CSSMTP) TYPE(USER) - NAME('IBM CSSMTP') DEPT(xxxx) - FAC(STC) - PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND

b
IBM Communications Server Simple Mail Transfer Protocol (CSSMTP) Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
IA-2 - Medium - CCI-000764 - V-224668 - SV-224668r1116169_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZSMTT032
Vuln IDs
  • V-224668
  • V-17454
Rule IDs
  • SV-224668r1116169_rule
  • SV-37484
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, Access Control Program (ACP), and customer data.
Checks: C-26357r1116167_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(ZSMT0032) Verify that the IBM CSSMTP started task(s) is (are) defined in the TSS STC record.

Fix: F-26345r1116168_fix

The IBM CSSMTP system 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 IBM CSSMTP started task(s) thru a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(CSSMTP) ACID(CSSMTP)