Rule ID
SV-225620r1146190_rule
Version
V7R2
CCIs
CCI-000213
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.
Refer to the following reports produced by the Data Set and Resource Data Collection: - TSSCMDS.RPT(WHOOCBIN). - TSSCMDS.RPT(WHOHCBIN). - SENSITVE.RPT(WHOHCBIN). If the following items are in effect for CBIND resource protection, this is not a finding. The CB. resource is owned appropriately in the BIND resource class. 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).
Ensure the following items are in effect for CBIND resource protection: The CB. resource is owned appropriately in the BIND resource class. For Example: TSS ADD(cbowner) CBIND(CB) 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 access 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.