STIGQter STIGQter: STIG Summary: z/OS IBM CICS Transaction Server for TSS Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025:

Sensitive CICS transactions are not protected in accordance with security requirements.

DISA Rule

SV-224730r1145844_rule

Vulnerability Number

V-224730

Group Title

SRG-OS-000080

Rule Version

ZCIC0020

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Develop a plan to implement the required changes.

Most transactions are protected by profiles. An example would be "L2TRANS" which would be permitted all Category 2 transactions. L2TRANS is defined to CA-TSS as a profile and is permitted to all the Category 2 transactions. An example of how to implement this within CA-TSS is shown here:

TSS CRE(L2TRANS) TYPE(PROF) DEPT(<dept acid>) NAME('L2 TRANS') INSTDATA('PROFILE GRANTING ACCESS TO ALL CATEGORY 2 TRANS')

TSS ADD(<owning acid>) OTRAN(CADP CBAM CDBC)

TSS PER(L2TRANS) OTRAN(CADP CBAM CDBC)

Permission to the transaction group can be accomplished with a sample command:

TSS PER(USERID)OTRAN(TRANSACTION)

Permission to the transactions can be accomplished by adding the L2TRANS profile to a user's ACID.

Example:

TSS ADD(<user's acid>) PROF(L2TRANS)

Transactions groups should be defined and permitted in accordance with the CICS Transaction tables listed in the zOS STIG Addendum.

Check Contents

Refer to the following reports produced by the TSS Data Collection and Data Set and Resource Data Collection:

- TSSCMDS.RPT(WHOOOTRA).
- SENSITVE.RPT(WHOHOTRA).

Refer to the CICS Systems Programmer Worksheets filled out from previous vulnerability ZCIC0010.

If the following items are in effect for all CICS regions, this is not a finding.

Note: Authorized personnel include systems programming and security staffs. Additional guidance regarding authorized personnel for specific transactions is included in this z/OS STIG Addendum. For example, CEMT SPI provides a broader use of this sensitive transaction by restricting execution to inquiries.

Transactions listed in tables CICS CATEGORY 2 CICS AND OTHER PRODUCT TRANSACTIONS and CICS CATEGORY 4 COTS-SUPPLIED SENSITIVE TRANSACTIONS, in the z/OS STIG Addendum, are restricted to authorized personnel.

Note: The exception to this is the CEOT and CSGM transactions, which can be made available to all users.
Note: The exception to this is the CWBA transaction, can be made available to the CICS Default user.
Note: The transactions beginning with "CK" apply to regions running WebSphere MQ.
Note: Category 1 transactions are internally restricted to CICS region userids.

Vulnerability Number

V-224730

Documentable

False

Rule Version

ZCIC0020

Severity Override Guidance

Refer to the following reports produced by the TSS Data Collection and Data Set and Resource Data Collection:

- TSSCMDS.RPT(WHOOOTRA).
- SENSITVE.RPT(WHOHOTRA).

Refer to the CICS Systems Programmer Worksheets filled out from previous vulnerability ZCIC0010.

If the following items are in effect for all CICS regions, this is not a finding.

Note: Authorized personnel include systems programming and security staffs. Additional guidance regarding authorized personnel for specific transactions is included in this z/OS STIG Addendum. For example, CEMT SPI provides a broader use of this sensitive transaction by restricting execution to inquiries.

Transactions listed in tables CICS CATEGORY 2 CICS AND OTHER PRODUCT TRANSACTIONS and CICS CATEGORY 4 COTS-SUPPLIED SENSITIVE TRANSACTIONS, in the z/OS STIG Addendum, are restricted to authorized personnel.

Note: The exception to this is the CEOT and CSGM transactions, which can be made available to all users.
Note: The exception to this is the CWBA transaction, can be made available to the CICS Default user.
Note: The transactions beginning with "CK" apply to regions running WebSphere MQ.
Note: Category 1 transactions are internally restricted to CICS region userids.

Check Content Reference

M

Target Key

4195