The CBIND Resource(s) for the WebSphere Application Server is(are) not protected in accordance with security requirements.

An XCCDF Rule

Description

<VulnDiscussion>SAF resources provide the ability to control access to functions and services of the WebSphere Application Server (WAS) environment. Many of these resources provide operational and administrative support for WAS. Failure to properly protect these resources may lead to unauthorized access. This exposure could compromise the integrity and availability of application services and customer data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><IAControls></IAControls>

ID: SV-7266r3_rule
Severity: Medium
References: CCI-000213
Updated: 9 months ago

Ensure the following items are in effect for CBIND resource protection: 

1)	The CB. resource is owned appropriately in the BIND resource class. 

For Example:
TSS ADD(cbowner) CBIND(CB)
2)	Access to the CB.BIND.server_name and CB.server_name resources is restricted to WAS server (STC) ACIDs and systems management ACIDs (e.g., WebSphere administrator ID). 

For Example:  
The WebSphere administrator ID needs read authority to the CB.BBOASR1 and CB.BIND.BBOASR1 servers:

TSS PERMIT(was_admin_acid) CBIND(CB.BBOASR1) ACCESS(READ)
TSS PERMIT(was_admin_acid) CBIND(CB.BIND.BBOASR1) ACCESS(READ)

NOTE:	When adding a new server, all systems management userids (e.g., WebSphere administrator ID) must be authorized to have read access to the CB.server_name and CB.BIND.server_name resources.

The CBIND Resource(s) for the WebSphere Application Server is(are) not protected in accordance with security requirements.

Description

Remediation - Manual Procedure