WebSphere Application Server V7 Advanced Security Enhancement, part 2nd

Advanced Security Considerations

Brief introduction

The 1th part explains how the IBM WebSphere application Server V6.1 and later versions consider the default security security principles at design time. The goal is to give the product a reasonable level of security by default in the most common configurations and simpler environments, even though the goal is not yet perfectly implemented. The previous article finally describes many of the important infrastructure-based preventative security measures already used in WebSphere application Server. This article describes other preventative measures based on your application, and then discusses some important considerations.

Although the information in this article is based on the IBM WebSphere application Server V7, most of the issues discussed also apply to V6.1. For a particular version of the problem, we will specifically point out.

Application-based preventative measures

Configuration measures

So far, this article focuses on the basic steps you can take to create a secure IBM WebSphere application Server infrastructure. This is obviously important, but focusing on infrastructure alone is not enough. Now that the infrastructure has been strengthened, it is important to look at what the application needs to do to ensure security. Of course, applications must take advantage of the infrastructure provided by WebSphere application Server, but application developers must also perform (or avoid) some other actions to maximize the security of the application.

Do not set the document root of the WEB server to WAR

Carefully check that each servlet alias is secure

Do not provide servlet through class name

Do not place sensitive information in the WAR root directory

To define a default error handler

Consider disabling file services and directory browsing

Enable Session security

Attention to custom JMX network access

To help you relate these measures to specific attack categories, each measure uses the tag described in part 1th to represent the category of attack.

1. Do not set the Web server's document ROOT to WAR

The WAR file contains application code and a large amount of sensitive information. Only part of the information is content that can be provided to the WEB. Therefore, it is not appropriate to set the Web server document root to the WAR root directory. If you do this, the WEB server will provide all the contents of the WAR file without explanation. This can lead to the provision of code, unprocessed JSPs, and other content to end users. (This is only useful when the WEB server and application server are put together.) ）