![]() ![]() ![]() ![]() ![]() ![]() |
Before you deploy WebLogic Operations Control (WLOC) into a production environment, determine your security needs and make sure that you take the appropriate security measures, as described in the following sections:
To better understand your security needs, ask yourself the following questions:
Many resources in the production environment can be protected. Consider the resources you want to protect when deciding the level of security you must provide.
For most WLOC Controllers and Agents, resources must be protected from everyone on the Internet. But should the Controller or Agent be protected from the employees on the intranet in your enterprise? Should your employees have access to all resources within the WLOC environment? Should the system administrators have access to all WLOC resources? Should the system administrators be able to access all data? You might consider giving access to highly confidential data or strategic resources to only a few well trusted system administrators. Perhaps it would be best to allow no system administrators access to the data or resources.
In some cases, a fault in your security scheme is easily detected and considered nothing more than an inconvenience. In other cases, a fault might cause great damage to applications controlled by WLOC. Understanding the security ramifications of each resource will help you protect it properly.
However you deploy WLOC it is a good idea to hire an independent security expert to go over your security plan and procedures, audit your installed systems, and recommend improvements. Oracle On Demand offers services and products that can help you to secure a WebLogic Server production environment. See the Oracle On Demand page at
http://www.oracle.com/ondemand/index.html
.
https://support.bea.com/application_content/product_portlets/securityadvisories/index.html
.
Report possible security issues in Oracle products to secalert_us@oracle.com
.
Currently, the WLOC installation includes the entire JDK and some additional WLOC utilities (for example, beasvc
). These programs could be a security vulnerability. The following are recommendations for making a WLOC installation more secure:
Note: | There is always a potential of making mistakes when deleting executables, files, and directories from the WLOC installation. Therefore, Oracle recommends testing your changes in a secure, development environment before implementing them in a production environment. |
![]() ![]() ![]() |