STIGQter: STIG Summary: z/OS IBM CICS Transaction Server for ACF2 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-224303r1141378_rule

Vulnerability Number

V-224303

Group Title

SRG-OS-000080

Rule Version

ZCIC0020

Severity

CAT II

CCI(s)

• CCI-000213 - Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Weight

10

Fix Recommendation

The ISSO will ensure that each CICS region is associated with a unique userid and that userid is properly defined.

Develop a plan to implement the required changes.

Most transactions are protected in groups. An example would be "KT2", which would contain all Category 2 transactions. KT2 is defined to ACF2 as a resource and contains all the Category 2 transactions.

An example of how to implement this within ACF2 is shown here:

$KEY(CEMT) TYPE(KT2)
UID(syspaudt) ALLOW
UID(*) PREVENT

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

Check Contents

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection:

- SENSITVE.RPT(TRANS).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.

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

Browse the dataset allocated by the ACF2PARM DD statement in each CICS startup procedure. Determine the resource type for transactions. Example:

CICSKEY OPTION=VALIDATE,TYPE=resource type, RESOURCE=TRANS

Verify the following items are in effect for all CICS transactions for each resource type. If the following guidance is true, 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, which 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-224303

Documentable

False

Rule Version

ZCIC0020

Severity Override Guidance

Refer to the following report produced by the ACF2 Data Collection and dataset and Resource Data Collection:

- SENSITVE.RPT(TRANS).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.

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

Browse the dataset allocated by the ACF2PARM DD statement in each CICS startup procedure. Determine the resource type for transactions. Example:

CICSKEY OPTION=VALIDATE,TYPE=resource type, RESOURCE=TRANS

Verify the following items are in effect for all CICS transactions for each resource type. If the following guidance is true, 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, which 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

4122