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-224730r520294_rule
Severity: Medium
References: CCI-000213
Updated: 8 months ago

Develop a plan to implement the required changes.

1. 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)

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