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

► Kerberos (KRB5) authentication mechanism
Although not available in the base release of V7.0, support for Kerberos as an
authentication mechanism will be included in a future release.
► Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) Web
authentication
SPNEGO Web authentication has been introduced as a substitute for
SPNEGO TAI. It can be configured by using the Integrated Solutions Console.
It allows the dynamic reload of SPNEGO without the need of a server restart.
12.2 Security in WebSphere Application Server
The fundamental reason for having security in your systems is to protect them
from intruders (external or internal to your organization) and to ensure that there
is no accidental or intentional misuse of your systems or the data flowing through
your systems.
When planning security for WebSphere Application Server, it is important to have
a comprehensive security policy in place that coordinates neatly with the overall
environment security. WebSphere Application Server adheres to standard Java
Enterprise Edition (Java EE) specifications and integrates with existing security
systems. There is no single solution for security concerns. However, proper
planning and diligence can keep systems functional and minimize the impact on
business.
Security can be divided into the following areas:
► Physical security
Physical security encompasses the area where the environment is located.
The major concerns are access to the site and protection against
environmental conditions. Commonly, such areas are physically secured and
access is limited to a small number of individuals.
► Logical security
Logical security includes the mechanisms provided to protect systems and
applications from having unauthorized accesses through the system console
or through the network. User authentication is the most common logical
security mechanism but there are others like encryption, certificates, or
firewalls.
Chapter 12. Security 381