Securing a Production Environment
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Before you deploy WebLogic Server and your J2EE applications into a production environment, determine your security needs and make sure that you have taken the appropriate security measures, as described in the following sections:
To better understand your security needs, ask yourself the following questions:
There are many resources in the production environment that can be protected including information in databases accessed by WebLogic Server and the availability, performance, and the integrity of the Web site. Consider the resources you want to protect when deciding the level of security you must provide.
For most Web sites, resources must be protected from everyone on the Internet. But should the Web site be protected from the employees on the intranet in your enterprise? Should your employees have access to all resources within the WebLogic Server environment? Should the system administrators have access to all WebLogic 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 to 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 companies or individual clients that use the Web site. Understanding the security ramifications of each resource will help you protect it properly.
Whether you deploy WebLogic Server on the Internet or on an intranet, 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. BEA partners offer services and products that can help you to secure a WebLogic Server production environment. See the BEA Partner's Page at http://www.bea.com/partners.
Currently, the WebLogic Server installation includes the entire JDK and some additional WebLogic Server development utilities (for example, beasvc). These development programs could be a security vulnerability. The following are recommendations for making a WebLogic Server installation more secure:
Note: There is always a potential of making mistakes when deleting executables, files, and directories from the WebLogic Server installation. Therefore, BEA recommends testing your changes in a secure, development environment before implementing them in a production environment.
![]() ![]() |
![]() |
![]() |