1. Application
Applies to Web sites deployed using WebSphere.
2. Skill requirements
Familiar with WebSphere installation and deployment, familiar with common WebSphere vulnerability exploits, and able to use WebSphere for site security hardening.
3. Preconditions
Verify that the site is deployed using WebSphere based on the site’s open port and process ID;
Find the WebSphere site location
4. Perform detailed operations
4.1 Account Security
See configuration operations:
1. Change the user password. The password contains at least eight characters and contains at least three of the four types of digits, lowercase letters, uppercase letters, and special characters.
4.2 Log Configuration
See configuration operations:
1. In the navigation pane, click Servers > Application Servers –> Click what you want
Name of the server used (Server1) –> Under Troubleshooting, click NCSA Access and HTTP Error Logging –> In General Properties, check enable logging service when the server starts.
2. Restart the service to take effect. Log file address: ${WebSphere}\AppServer\profiles\AppSrv01\logs\server1\http_access.log
4.3 Best practices
4.3.1 Disabling Directory Browsing
See configuration operations:
Open it with a text editor
$WAS_HOME/<profilepath>/config/cells/<hostname>/applications/
<yourapplication>.ear/<yourapplication>.war/WEB-INF/ibm-web-ext.xmi
Set the fileServingEnabled = “false”
Set the directoryBrowsingEnabled = “false”
4.3.2 Error Page Handling
See configuration operations:
1. Open it with a text editor
${WebSphere}/<profilepath>/config/cells/<hostname>/applications/
<yourapplication>.ear/<yourapplication>.war/WEB-INF/ibm-web-ext.xmi
Set the defaultErrorPage = “/ error. HTML”
2. In the root directory of the site
${WebSphere}\AppServer\profiles\AppSrv01\installedApps \<hostname>\<yourapplication>.ear\<yourapplication>.war/
Create a new error.html file
4.3.3 Secure Backup
See configuration operations:
The Config and Properties directories are backed up weekly, and the WebSphere full directory is backed up at least monthly, which is required before production configuration changes.
(1) As WAS, execute:
#$WAS_HOME/bin/backupConfig.sh
(2) If the user is root, it is best to run:
#tar cvf $WAS_HOME/profiles/default/config
#tar cvf $WAS_HOME/profiles/default/properties
4.3.4 Enabling session Security
See configuration operations:
1. In the navigation pane, click Servers > Application Servers –> Click what you want
Name of the server used (Server1) –> Click Session Management –> In general Properties, check override session Management and security integration.
4.4 Risky Operations
4.4.1 Deleting the default program
See configuration operations:
Open the administrative console as an administrator and run:
1. Go to “Applications” > “Enterprise Applications”
2. Select the sample program and then click the “Uninstall” button to uninstall it.
DefaultApplication, PlantsByWebSphere,
“SamplesGallery”, “ivtApp” and other subroutines
3. Click to save the Settings to the master configuration
${WebSphere}\AppServer\ Profiles \AppSrv01\installedApps directory source
4.4.2 Patch Updates
View version information:
cd $WAS_HOME/bin
/versionInfo.sh
Find the latest patches and versions and install them
The last
Welcome to pay attention to personal wechat public number: Bypass–, an original technical dry goods every week.
