SV-3901r3_rule
V-3901
ZWAS0050
ZWAS0050
CAT II
10
The IAO will ensure that the WebSphere Application Server directives in the httpd.conf file are configured as outlined below.
Ensure that all WAS-related directives are configured using the ServerInit, Service, and ServerTerm statements as outlined below.
The following path entries were added to the /etc/httpd.conf file for WebSphere 3.5:
ServerInit /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:init_exit /usr/lpp/WebSphere/etc/WebSphere/AppServer/properties/was.conf
Service /webapp/examples/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jhtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.shtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /servlet/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jsp /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit ServerTerm /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:term_exit
The following path entries are added to the /etc/httpd.conf file for WebSphere 4.0.1:
ServerInit -/usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:init_exit
Service - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:service_exit
ServerTerm - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:term_exit
NOTE: The /etc/WebSphere clause for ServerInit matches the directory name above where the site customization was.conf file was established. Specific items to review include proper path, was.conf, and plug-in settings.
a) Refer to the following report produced by the UNIX System Services Data Collection:
- USSCMDS.RPT(AHTTPD)
Collect the following information for each IBM HTTP server:
- The JCL procedure library and member name used to start each IBM HTTP server. DOC(IHSPROCS)
- For each IBM HTTP server, supply the following information:
Web server ID defined to the ACP
Web server administration group defined to the ACP
Web server standard HFS directory
b) Review the HTTP server JCL procedure to determine the httpd.conf file to review.
c) Ensure that all WAS-related directives are configured using the ServerInit, Service, and ServerTerm statements as outlined below.
The following path entries were added to the /etc/httpd.conf file for WebSphere 3.5:
ServerInit /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:init_exit /usr/lpp/WebSphere/etc/WebSphere/AppServer/properties/was.conf
Service /webapp/examples/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jhtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.shtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /servlet/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jsp /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
ServerTerm /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:term_exit
The following path entries are added to the /etc/httpd.conf file for WebSphere 4.0.1:
ServerInit - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:init_exit
Service - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:service_exit
ServerTerm - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:term_exit
NOTE: The /etc/WebSphere clause for ServerInit matches the directory name above where the site customization was.conf file was established.
Specific items to review include proper path, was.conf, and plug-in settings.
d) If all WAS-related directives are configured properly, there is NO FINDING.
e) If any WAS-related directive is not configured properly, this is a FINDING.
V-3901
False
ZWAS0050
a) Refer to the following report produced by the UNIX System Services Data Collection:
- USSCMDS.RPT(AHTTPD)
Collect the following information for each IBM HTTP server:
- The JCL procedure library and member name used to start each IBM HTTP server. DOC(IHSPROCS)
- For each IBM HTTP server, supply the following information:
Web server ID defined to the ACP
Web server administration group defined to the ACP
Web server standard HFS directory
b) Review the HTTP server JCL procedure to determine the httpd.conf file to review.
c) Ensure that all WAS-related directives are configured using the ServerInit, Service, and ServerTerm statements as outlined below.
The following path entries were added to the /etc/httpd.conf file for WebSphere 3.5:
ServerInit /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:init_exit /usr/lpp/WebSphere/etc/WebSphere/AppServer/properties/was.conf
Service /webapp/examples/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jhtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.shtml /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /servlet/* /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
Service /*.jsp /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:service_exit
ServerTerm /usr/lpp/WebSphere/AppServer/bin/was350plugin.so:term_exit
The following path entries are added to the /etc/httpd.conf file for WebSphere 4.0.1:
ServerInit - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:init_exit
Service - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:service_exit
ServerTerm - /usr/lpp/WebSphere401/WebServerPlugIn/bin/was400plugin.so:term_exit
NOTE: The /etc/WebSphere clause for ServerInit matches the directory name above where the site customization was.conf file was established.
Specific items to review include proper path, was.conf, and plug-in settings.
d) If all WAS-related directives are configured properly, there is NO FINDING.
e) If any WAS-related directive is not configured properly, this is a FINDING.
M
Information Assurance Officer
3361