WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

It is the responsibility of the WebSphere Application Server infrastructure to
provide all the services required by applications to run in a secured environment.
It is imperative then, to have security in mind when planning for a WebSphere
Application Server infrastructure. In many cases you will find reusable
components of a security infrastructure already in place.
Consider how security will affect your infrastructure:
► Understand the security policy and requirements for your future environment.
► Work with a security subject matter expert to develop a security infrastructure
that adheres to the requirements and integrates in the existing infrastructure.
► Make sure that sufficient physical security is in place.
► Make sure the application developers understand the security requirements
and code the application accordingly.
► Consider the user registry (or registries) you plan to use. WebSphere
Application Server V7.0 supports multiple user registries and multiple security
domains.
► Make sure that the user registries are not breaking the high availability
requirements. Even if the user registries you are using are out of scope of the
WebSphere Application Server project, considerations for high availability
need to be taken and requested. For example, make sure that your LDAP
user registries are made highly available and are not a single point of failure.
► Define the trust domain for your environment. All computers in the same
WebSphere security domain trust each other. This trust domain can be
extended, and when using SPNEGO / Kerberos, even out to the Windows
desktop of the users in your enterprise.
► Assess your current implementation design and ensure that every possible
access to your systems is secured.
► Consider the level of auditing required and how to implement it.
► Consider how you will secure stored data. Think of operating system security
and encryption of stored data.
► Define a password policy, including considerations for handling password
expirations for individual users.
► Consider encryption requirements for network traffic. Encryption introduces
overhead and increased resource costs, so use encryption only where
appropriate.
► Define the encryption (SSL) endpoints in your communications.
Chapter 4. Infrastructure 103