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

An XCCDF Rule

Description

<VulnDiscussion>Sensitive CICS transactions offer the ability to circumvent transaction level controls for accessing resources under CICS. These transactions must be protected so that only authorized users can access them. Unauthorized use can result in the compromise of the confidentiality, integrity, and availability of the operating system or customer data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID: SV-224493r520267_rule
Severity: Medium
References: CCI-000213
Updated: 9 months ago

Develop a plan to implement the required changes.

1. Most transactions are protected in groups. An example would be "L2TRANS" which would contain all Category 2 transactions. L2TRANS is defined to RACF as a profile and contains all the Category 2 transactions. An example of how to implement this within RACF is shown here:

RDEF GCICSTRN L2TRANS UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ))
RALT GCICSTRN L2TRANS ADDMEM(CADP CBAM CDBC)

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

PE L2TRANS CL(GCICSTRN) id(<syspaudt>)

Note that a refresh is generally needed to the member class.
In this case TCICSTRN is the member class for GCICSTRN and a sample refresh command is

SETR RACL(TCICSTRN) REFRESH

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

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

Description

Remediation - Manual Procedure