Simon Kapadia held the WAS (WebSphere Application Server) Infrastructure Security Hardening session at this years IBM Transaction & Messaging Technical Conference. Simon explained the following attack levels:
-Network
-Machine
-External Application
-Internal Application Isolation
WAS V6.1 has improved security hardening by the the meaning “Secure by default” which means that Administrative Security is on by default and most subsystems as well.
The following list are some of the more important things to think about concerning security in your WAS environment.
Network Design Considerations
-Use two firewall DMZ
-No WAS in the DMZ
-Firewall protection from intranet
Use HTTPS for the browser
-WAS can enforce https by configuring this in the web.xml file
Configure Secure File Transfer
Keep up to date with patches and and fixes
-Important! Security updates are rolled into the next release/refreshpack and then no longer listed on the recommended update page.
Enable Application Security
-That enables applications to leverage Java EE security
Restrict Access to WebSphere MQ
-Custom security exit for client authentication
-A simpler approach is to use MQ SSL client authentication
SIBus
-Configure inter-engine authentication alias
Harden the Web Server and Host
-Harden the OS
-Harden the Web Server
-Limit the modules loaded
-Review the Web Server configuration
-Consider limiting the SSL strength allowed
-Ensure that the WAS plugin is configured to only forward traffic for the right application
-Remove the JRE’s installed when installing the Web Server and the Web Server Plugin
-WAS V6.0 and later can manage Web Servers as part of the Cell, this is NOT recommended in a production environment
Harden the Proxy Host
-Standard OS hardening applies
-Harden the Proxy
-Ensure the Proxy is only forwarding what should be forwarded
-Best bet for Web Services Proxy: DataPower
Configure and use TAI’s carefully
-Trust Associations Interceptors extend the trust domain
-TAI must be carefully designed and carefully deployed
-Mistakes result in serious security weaknesses
Consider Authenticating Web Server to WAS link
-Any http client can connect to the web container
Limiting Web Container Access to trusted servers
-Create new trust store that contains only the Web Server Plugin signers
-Create new SSL configuration
-Disable HTTP transport on Web Container
-Ensure web plugin has needed signer
Don’t run samples in production
Choose an appropriate process identity
Protect your configuration files & private keys
Encrypt the LDAP link
-APAR PK34088 is needed to accomplish this
This were some of the most important measures to take into consideration when revising the WAS infrastructure security.
Simon then explained the medium and less important security hints to us, unfortunately the time was up very soon. This topic definitely needs more time to be discussed.