Securing applications and their environment
Secure the application serving environment. This information applies generally to all types of applications deployed in the environment.
Part of your security framework WebSphere® Application Server plays an integral part of the multiple-tier enterprise computing framework. Based on open architecture, WebSphere Application Server provides many plug-in points to integrate with enterprise software components to provide end-to-end security.
Product security Security infrastructure and mechanisms protect Java Platform, Enterprise Edition (Java EE) resources and administrative resources, addressing your enterprise security requirements.
Subtopics
- How do I secure applications and their environments?
Follow these shortcuts to get started quickly with popular tasks. Task overview: Securing resources
WebSphere Application Server supports the Java™ Platform, Enterprise Edition (Java EE) model for creating, assembling, securing, and deploying applications. Applications are often created, assembled, and deployed in different phases and by different teams.Setting up, enabling and migrating security
You must address several issues prior to authenticating users, authorizing access to resources, securing applications, and securing communications. These security issues include migration, interoperability, and installation.Configuring multiple security domains
By default, all administrative and user applications in WebSphere Application Server use the global security configuration. For example, a user registry defined in global security is used to authenticate users for every application in the cell. Out-of-the-box, this behavior is the same as it was in previous releases of WebSphere Application Server. You can create additional WebSphere security domains if you want to specify different security attributes for some or all of your user applications. This section describes how to configure a security domain by using the administrative console.Authenticating users
The process of authenticating users involves a user registry and an authentication mechanism. Optionally, you can define trust between WebSphere Application Server and a proxy server, configure single sign-on capability, and specify how to propagate security attributes between application servers.Authorizing access to resources
WebSphere Application Server provides many different methods for authorizing accessing resources. For example, you can assign roles to users and configure a built-in or external authorization provider.Securing communications
WebSphere Application Server provides several methods to secure communication between a server and a client.Developing extensions to the WebSphere security infrastructure
WebSphere Application Server provides various plug points so that you can extend the security infrastructure. Extending this security infrastructure involves several activities including: Developing custom user registries, developing applications that use programmatic security, and customizing web application login forms.Auditing the security infrastructure
You can use the Auditing Facility to report and track auditable events to ensure the integrity of your system.Tuning, hardening, and maintaining security configurations
After installing WebSphere Application Server, there are several considerations for tuning, strengthening, and maintaining your security configuration.Troubleshooting security configurations
The following topics help to troubleshoot specific problems that are related to configuring and enabling security configurations.Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WebSphere Application Server.- Securing the application server by using HTTP Strict Transport Security (HSTS)
You can secure the application server by first setting up HTTP Strict Transport Security (HSTS) in IBM® HTTP Server. Then, add IBM HTTP Server as a front end to your application server environment so that connections between your application server and a client are over HTTPS. Securing client applications
This page provides a starting point for finding information about application clients and client applications. Application clients provide a framework on which application code runs, so that your client applications can access information on the application server.Securing data access resources
This page provides a starting point for finding information about data access. Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.Securing EJB applications
This page provides a starting point for finding information about enterprise beans.Securing messaging resources
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere Application Server.Securing Mail, URLs, and other Java EE resources
This page provides a starting point for finding information about resources that are used by applications that are deployed on a Java Enterprise Edition (Java EE)-compliant application server. They include:Securing OSGi applications
This page provides a starting point for finding out how to secure OSGi applications.Securing portlet applications
This page provides a starting point for finding information about portlet applications, which are special reusable Java servlets that appear as defined regions on portal pages. Portlets provide access to many different applications, services, and web content.Securing service integration
This page provides a starting point for finding information about service integration.Securing a service map
This page provides a starting point for finding out how to secure a service map.Securing Session Initiation Protocol (SIP) applications
This page provides a starting point for finding information about SIP applications, which are Java programs that use at least one Session Initiation Protocol (SIP) servlet written to the JSR 116 specification.Securing web applications
This page provides a starting point for finding information about web applications, which are comprised of one or more related files that you can manage as a unit, including:Securing web services
This page provides a starting point for finding information about web services.


File name: welc6topsecuring.html